[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Charles changed: What|Removed |Added CC||charlesfhub...@gmail.com --- Comment #43 from Charles --- Created attachment 103078 --> https://bugs.kde.org/attachment.cgi?id=103078&action=edit Tablet Log I was having a problem with my pressure sensitivity stopping after a time until I updated my tablet drivers to the most recent version. Now I'm having this problem too. I'm on a Ugee 1910B, using 3.1.1 I had to cheat a bit (by moving my pen away from my tablet quickly) to reproduce the stroke jumping because Krita gets better about knowing where my stylus is when the Tablet Logging is on. With Tablet logging on it basically works like it should, just a bit laggy. Let me know if you need any more info. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 --- Comment #44 from Charles --- If it makes any difference, I tried my tablet (Ugee 1910B) on my old desktop and it worked fine with the same driver. The computer I'm having a problem on has a AMD FX-8350 CPU The computer that works fine has an Intel(R) Core(TM) i5-3570k CPU Let me know if there is any other information I can provide that could be helpful. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 393557] New: Calligra Words crash when deleting centered spaces below a table
https://bugs.kde.org/show_bug.cgi?id=393557 Bug ID: 393557 Summary: Calligra Words crash when deleting centered spaces below a table Product: calligrawords Version: 3.1.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: gulagehierleit...@gmail.com Target Milestone: --- Application: calligrawords (3.1.0) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: Deleteting two page-centered spaces below a table, crash resulting after deleting the second (last) space below the table. This error reoccurs after I open the recovered document and repeat the action. - Custom settings of the application: Kvantum theme engine, global file menu, Window Width: 939 Width: 678, Add object applet docked to the right and collapsed, Primary? applet/section docked to the right under it and expanded. I was editing on the second page at the time. The table was split with two rows of cells on the second page. The crash can be reproduced sometimes. -- Backtrace: Application: Calligra Words (calligrawords), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70ffddc8c0 (LWP 8794))] Thread 3 (Thread 0x7f70d3051700 (LWP 9441)): #0 0x7f70f7062a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f70f701ddb9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70f701e330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70f701e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f70fe2a75cb in QEventDispatcherGlib::processEvents (this=0x7f70cc0599c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f70fe24e64a in QEventLoop::exec (this=this@entry=0x7f70d3050d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f70fe06e554 in QThread::exec (this=) at thread/qthread.cpp:522 #7 0x7f70fe0736eb in QThreadPrivate::start (arg=0x3023490) at thread/qthread_unix.cpp:376 #8 0x7f70f86896ba in start_thread (arg=0x7f70d3051700) at pthread_create.c:333 #9 0x7f70ff7f241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f70de428700 (LWP 8797)): #0 0x7f70ff7e227d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f70f70616f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70f701de74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70f701e330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f70f701e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f70fe2a75cb in QEventDispatcherGlib::processEvents (this=0x7f70d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f70fe24e64a in QEventLoop::exec (this=this@entry=0x7f70de427cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f70fe06e554 in QThread::exec (this=this@entry=0x7f70f8f48d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:522 #8 0x7f70f8cd42c5 in QDBusConnectionManager::run (this=0x7f70f8f48d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7f70fe0736eb in QThreadPrivate::start (arg=0x7f70f8f48d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:376 #10 0x7f70f86896ba in start_thread (arg=0x7f70de428700) at pthread_create.c:333 #11 0x7f70ff7f241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f70ffddc8c0 (LWP 8794)): [KCrash Handler] #6 QScopedPointer >::data (this=0x29) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:140 #7 qGetPtrHelper > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1013 #8 QTextObject::d_func (this=0x21) at text/qtextobject.h:84 #9 QTextObject::format (this=0x21) at text/qtextobject.cpp:124 #10 0x7f70f940504f in QTextTable::format (this=) at text/qtexttable.h:128 #11 QTextTablePrivate::update (this=this@entry=0x30585f0) at text/qtexttable.cpp:445 #12 0x7f70f94054c6 in QTextTable::columns (this=) at text/qtexttable.cpp:1271 #13 0x7f70fd6f84e9 in ?? () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #14 0x7f70fd6f796e in ?? () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #15 0x7f70fd6d3e69 in KoTextLayoutArea::layout(FrameIterator*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #16 0x7f70fd6ebe4d in KoTextLayoutRootArea:
[systemsettings] [Bug 389133] Exiting Web Shortcuts crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=389133 --- Comment #3 from Charles --- Created attachment 110293 --> https://bugs.kde.org/attachment.cgi?id=110293&action=edit New crash information added by DrKonqi systemsettings5 (5.11.5) using Qt 5.9.3 - What I was doing when the application crashed: Every time I click Shortcuts, Web-Shortcuts, then as soon as I click Global Shortcuts systemsettings crashes. - Custom settings of the application: The entire application is the settings application. I have "Use preferred shortcuts only" selected. I use kvantum manager and Arc Dark Transparent theme. I use Papirus Icons. I use "de:en_US.UTF-8" language. -- Backtrace (Reduced): #7 0x7f9b5123653e in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320 #8 qDeleteAll > (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328 #9 ProvidersModel::~ProvidersModel (this=0x5c16f50, __in_chrg=) at /workspace/build/src/urifilters/ikws/ikwsopts.cpp:43 #10 0x7f9b512365a9 in ProvidersModel::~ProvidersModel (this=0x5c16f50, __in_chrg=) at /workspace/build/src/urifilters/ikws/ikwsopts.cpp:44 #11 0x7f9b8819cd63 in QObjectPrivate::deleteChildren (this=this@entry=0x128aee0) at kernel/qobject.cpp:1992 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389133] Exiting Web Shortcuts crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=389133 Charles changed: What|Removed |Added CC||gulagehierleit...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390887] New: Crash when opening systemsettings5 as root
https://bugs.kde.org/show_bug.cgi?id=390887 Bug ID: 390887 Summary: Crash when opening systemsettings5 as root Product: systemsettings Version: 5.12.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gulagehierleit...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.1) Qt Version: 5.9.3 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I ran `export $(dbus-launch)` and then `systemsettings5` from konsole and shortly after selecting the first menu, the application crashed. - Custom settings of the application: The entire application is the settings application :( -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe787c448c0 (LWP 12861))] Thread 5 (Thread 0x7fe74dfe5700 (LWP 12881)): #0 0x7fe77d981f25 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe77d9823f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe7480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe74dfe4ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x75f2910) at thread/qthread.cpp:515 #6 0x7fe7819b0d25 in QQmlThreadPrivate::run (this=0x75f2910) at qml/ftw/qqmlthread.cpp:147 #7 0x7fe783e3f709 in QThreadPrivate::start (arg=0x75f2910) at thread/qthread_unix.cpp:368 #8 0x7fe77fc306ba in start_thread (arg=0x7fe74dfe5700) at pthread_create.c:333 #9 0x7fe78374e41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fe755ade700 (LWP 12866)): #0 0x7fe78374274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe77d98238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe758c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe755addce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x2a6bc60) at thread/qthread.cpp:515 #6 0x7fe7819b0d25 in QQmlThreadPrivate::run (this=0x2a6bc60) at qml/ftw/qqmlthread.cpp:147 #7 0x7fe783e3f709 in QThreadPrivate::start (arg=0x2a6bc60) at thread/qthread_unix.cpp:368 #8 0x7fe77fc306ba in start_thread (arg=0x7fe755ade700) at pthread_create.c:333 #9 0x7fe78374e41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fe75f666700 (LWP 12865)): #0 0x7fe78374274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe77d98238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe7580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe75f665ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x27f7260) at thread/qthread.cpp:515 #6 0x7fe7819b0d25 in QQmlThreadPrivate::run (this=0x27f7260) at qml/ftw/qqmlthread.cpp:147 #7 0x7fe783e3f709 in QThreadPrivate::start (arg=0x27f7260) at thread/qthread_unix.cpp:368 #8 0x7fe77fc306ba in start_thread (arg=0x7fe75f666700) at pthread_create.c:333 #9 0x7fe78374e41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fe76b72f700 (LWP 12863)): #0 0x7fe78374274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe77d98238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe7640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe76b72ecd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x7fe785bdbd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holde
[systemsettings] [Bug 390887] Crash when opening systemsettings5 as root
https://bugs.kde.org/show_bug.cgi?id=390887 --- Comment #2 from Charles --- Got it. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 186354] Suppress Audit Log links when Audit Log is not available
https://bugs.kde.org/show_bug.cgi?id=186354 Charles changed: What|Removed |Added CC||charles.vasquez@supremofood ||s.com -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 73913] KGpg "Processing decryption" window doesn't disappear when decryption failed
https://bugs.kde.org/show_bug.cgi?id=73913 Charles changed: What|Removed |Added CC||charles.vasquez@supremofood ||s.com -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 388693] New: Error Retrieving Audit Log
https://bugs.kde.org/show_bug.cgi?id=388693 Bug ID: 388693 Summary: Error Retrieving Audit Log Product: kleopatra Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: charles.vasq...@supremofoods.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- Kleopatra Version 3.0.1-gpg4win-3.0.2 Error Retrieving Audit Log: Decryption failed Files are stored in the \users\ "username"\AppData\Local\Temp with the name kleopatra, the file has some random characters. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389734] New: systemsettings5 crash when mindlessly clicking through menus
https://bugs.kde.org/show_bug.cgi?id=389734 Bug ID: 389734 Summary: systemsettings5 crash when mindlessly clicking through menus Product: systemsettings Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gulagehierleit...@gmail.com Target Milestone: --- Application: systemsettings5 (5.11.5) Qt Version: 5.9.3 Frameworks Version: 5.42.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: Clicking through menus from the bottom up. Sidebar mode (v5.11.5+?). Under Network. I clicked the Bluetooth. (it's deactivated). I clicked Connectivity. I clicked Settings. I maybe clicked Browser Identification. I maybe clicked Cookies, Cache, SSL Preferences, Connection Preferences, etc. At about that point it crashed. My locale was misconfigured. I can give you the saved output of the locale command. My install is new approx 1-30-18 user edition iso. - Custom settings for the application: Umm, the entire application is settings... :( Though, since I have done little activity on this installation so far, I've archived most of my .config directory. Maybe that helps. I can give you it. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f756b5ae8c0 (LWP 1705))] Thread 8 (Thread 0x7f7522b67700 (LWP 1735)): #0 0x7f75672aa74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f756124538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7561245712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f752b93d9d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f756126bbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f75630ce6ba in start_thread (arg=0x7f7522b67700) at pthread_create.c:333 #6 0x7f75672b641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f751affd700 (LWP 1734)): #0 0x7f75672a627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f75612886f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7561244e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7561245330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f756124549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f75612454d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f756126bbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f75630ce6ba in start_thread (arg=0x7f751affd700) at pthread_create.c:333 #8 0x7f75672b641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f753254e700 (LWP 1716)): #0 0x7f75672aa74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f756124538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f756124549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7567bd16cb in QEventDispatcherGlib::processEvents (this=0x7f752c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7567b79e2a in QEventLoop::exec (this=this@entry=0x7f753254dce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f75679a28f4 in QThread::exec (this=this@entry=0x1797380) at thread/qthread.cpp:515 #6 0x7f7565a57d25 in QQmlThreadPrivate::run (this=0x1797380) at qml/ftw/qqmlthread.cpp:147 #7 0x7f75679a7709 in QThreadPrivate::start (arg=0x1797380) at thread/qthread_unix.cpp:368 #8 0x7f75630ce6ba in start_thread (arg=0x7f753254e700) at pthread_create.c:333 #9 0x7f75672b641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f7538f56700 (LWP 1712)): #0 0x7f75672a627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f75612886f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7561244e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7561245330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f756124549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7567bd16cb in QEventDispatcherGlib::processEvents (this=0x7f75340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7567b79e2a in QEventLoop::exec (this=this@entry=0x7f7538f55ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f75679a28f4 in QThread::exec (this=this@entry=0x1806180) at thread/qthread.cpp:515 #8 0x7f7565a57d25 in QQmlThread
[kate] [Bug 383963] New: Kate is not opening current folder when it's remote (KIO, sftp)
https://bugs.kde.org/show_bug.cgi?id=383963 Bug ID: 383963 Summary: Kate is not opening current folder when it's remote (KIO, sftp) Product: kate Version: 17.04.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: charles.vej...@yale.edu Target Milestone: --- Hi, When I open a remote folder in Kate (sftp://) and open some file from there, it works. If I click to open a file again then the dialog open my local home and not the remote folder. Reproducible: Always Steps to Reproduce: 1) Open remote file with Kate 2) Try to open a second file. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 430349] New Ktorrent version past 5.1.2.2 running as root failed
https://bugs.kde.org/show_bug.cgi?id=430349 --- Comment #1 from Charles --- KDE Frameworks Version : 5.77.0 Qt Version : 5.15.2 Note : adding --no-sandbox to command line give error : Unknown option -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Charles changed: What|Removed |Added CC||chaw...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 408174] fish:// and sftp:// opens a non-existing folder fish:////
https://bugs.kde.org/show_bug.cgi?id=408174 Charles changed: What|Removed |Added CC||chaw...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448827] New: Using NVidia Driver G06 version 510.39.01-51, after resuming from sleep, Plasma crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=448827 Bug ID: 448827 Summary: Using NVidia Driver G06 version 510.39.01-51, after resuming from sleep, Plasma crashed unexpectedly Product: plasmashell Version: 5.23.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: charles.christie...@hey.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.5) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.0-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Resuming from sleep; Some windows had graphical inconsistencies and garbled graphics. As I was closing/minimizing windows, Plasma crashed. - Unusual behavior I noticed: Graphical issues within windows. Interacting with the windows led to a crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 QSGAreaAllocatorNode::isLeaf() (this=0x1f30011) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:93 #5 QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) (this=this@entry=0x7f437c179170, pos=..., node=0x1f30011) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:170 #6 0x7f43d592afc6 in QSGAreaAllocator::deallocate(QRect const&) (this=this@entry=0x7f437c179170, rect=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:116 #7 0x7f43d59314ef in QSGOpenGLAtlasTexture::AtlasBase::remove(QSGOpenGLAtlasTexture::TextureBase*) (this=0x7f437c179160, t=t@entry=0x7f437c8571b0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:286 #8 0x7f43d593163d in QSGOpenGLAtlasTexture::TextureBase::~TextureBase() (this=0x7f437c8571b0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:516 #9 QSGOpenGLAtlasTexture::Texture::~Texture() (this=0x7f437c8571b0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543 #10 0x7f43d5931659 in QSGOpenGLAtlasTexture::Texture::~Texture() (this=0x7f437c8571b0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543 #11 0x7f43c4edd2bd in QScopedPointerDeleter::cleanup(QSGTexture*) (pointer=) at /usr/include/qt5/QtCore/qscopedpointer.h:60 #12 QScopedPointer >::~QScopedPointer() (this=0x7f437c8a40a0, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #13 Plasma::WindowTextureProvider::~WindowTextureProvider() (this=0x7f437c8a4090, this=) at /usr/src/debug/plasma-framework-5.90.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149 #14 Plasma::WindowTextureProvider::~WindowTextureProvider() (this=0x7f437c8a4090, this=) at /usr/src/debug/plasma-framework-5.90.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149 #15 0x7f43d597b182 in QSGRenderThread::event(QEvent*) (this=0x55eb4aa81f50, e=0x55eb4d08b230) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:493 #16 0x7f43d5974b6f in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55eb4aa81f50) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:937 #17 0x7f43d5977009 in QSGRenderThread::run() (this=0x55eb4aa81f50) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.4.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1053 #18 0x7f43d3cbee71 in QThreadPrivate::start(void*) (arg=0x55eb4aa81f50) at thread/qthread_unix.cpp:329 #19 0x7f43d38233d7 in start_thread () at /lib64/libc.so.6 #20 0x7f43d38ac6e0 in clone3 () at /lib64/libc.so.6 Thread 11 (Thread 0x7f4387575640 (LWP 3555) "Qt bearer threa"): #1 0x7f43d21df0be in () at /lib64/libglib-2.0.so.0 #2 0x7f43d21df1df in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f43d3efb306 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f4378000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f43d3ea27bb in QEventLoop::exec(QFlags) (this=this@entry=0x7f4387574b80, flags=..., flags@entr
[kstars] [Bug 470914] New: Mouse courser 'X' and 'o' do not show on the kstars star chart if you use the Wayland graphic platform. Works OK if using the X11 graphic platform.
https://bugs.kde.org/show_bug.cgi?id=470914 Bug ID: 470914 Summary: Mouse courser 'X' and 'o' do not show on the kstars star chart if you use the Wayland graphic platform. Works OK if using the X11 graphic platform. Classification: Applications Product: kstars Version: 3.6.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: kennedy.charle...@gmail.com Target Milestone: --- 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. Switch display platform from default X11 to Wayland 2. Open kstars. Make sure mouse pointer curser is set to 'X' or 'O'. 3. Note that mouse curser disappears when on star chart. OBSERVED RESULT Mouse curser disappears EXPECTED RESULT Mouse curser appears. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KUBUNTU 23.04 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION duplicated this problem on two different systems. all running the same versions of everything. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 470914] Mouse courser 'X' and 'o' do not show on the kstars star chart if you use the Wayland graphic platform. Works OK if using the X11 graphic platform.
https://bugs.kde.org/show_bug.cgi?id=470914 Charles changed: What|Removed |Added CC||kennedy.charle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Charles changed: What|Removed |Added CC|chaw...@zoho.com| -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455003] New: Mouse pointer speed resets after boot/reboot
https://bugs.kde.org/show_bug.cgi?id=455003 Bug ID: 455003 Summary: Mouse pointer speed resets after boot/reboot Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: carlos75...@gmail.com Target Milestone: --- SUMMARY Pointer speed in KDE is resetting every time I reboot. I set the mouse speed in the System Settings → Input Devices → Pointer speed to the value I want (6th bar) → Hit “Apply” and everything is great. After reboot, the mouse is much faster. When I go into the settings, they don’t seem to be changed. Pointer speed is still on the 6th bar. To fix it, I have to move it to a different value, hit apply, move it back to the one I want and hit apply again. Mouse used: 1. Razer Viper Ultimate (wireless mouse with its own USB dongle). 2. Logitech M185: budget wireless mouse (also with its own dongle) 2. Steelseries Sensei 310: regular wired mouse The bug occurs with all models above, specifically on the wireless ones, but it happens randomly on the wired mouse (when it does, first both left and right mouse buttons stop working. After unplug and plugging the mouse, the buttons works again, but pointer speed has been altered to some default speed. STEPS TO REPRODUCE 1. Set desired pointer speed 2. Reboot the system 3. Check if speed has been altered. OBSERVED RESULT Pointer speed is altered even though the selected value (6th bar, for instance) hasn't changed, apparently. EXPECTED RESULT Pointer speed should remain the same after boot or reboot SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro. Kernel version: 5.15.41-1 (LTS) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Hardware info: CPU: Ryzen 9 3900X MoBo: Asus Rog Strix B550-F RAM: 2x8GB G.Skill TridentZ 3600MHz Storage device: Samsung 970 EVO Plus 500GB NVMe GPU: Nvidia RTX 3080 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439381] New: The Wipe with dissolve feature doesn't apply to rendered video
https://bugs.kde.org/show_bug.cgi?id=439381 Bug ID: 439381 Summary: The Wipe with dissolve feature doesn't apply to rendered video Product: kdenlive Version: 21.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: crazedtec...@gmail.com Target Milestone: --- SUMMARY The Wipe with dissolve feature doesn't apply to rendered video STEPS TO REPRODUCE 1. Add 2 clips 2. Overlap begining of second clip to end of first clip and click corner of overlap 3. Try render OBSERVED RESULT clips never dissolved into one another. EXPECTED RESULT The clips should smoothly switch/dissolve into each other SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 469870] New: KStars crashed when setting up a new optical train
https://bugs.kde.org/show_bug.cgi?id=469870 Bug ID: 469870 Summary: KStars crashed when setting up a new optical train Classification: Applications Product: kstars Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: kennedy.charle...@gmail.com Target Milestone: --- Application: kstars (3.6.4 Stable) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-20-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I was adding a telescope and stuff into the optical train window when it just crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault [KCrash Handler] #4 0x56472e30fc54 in Ekos::OpticalTrainManager::addOpticalTrain (this=this@entry=0x564736246b80, main=main@entry=false, name=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:301 #5 0x56472e312722 in operator() (__closure=0x56473a314800) at /usr/src/kstars-bleeding-6:3.6.4+202304120910~ubuntu23.04.1/kstars/ekos/auxiliary/opticaltrainmanager.cpp:139 #6 QtPrivate::FunctorCall, QtPrivate::List<>, void, Ekos::OpticalTrainManager::OpticalTrainManager():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #7 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #8 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x56473a3147f0, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #9 0x7f0f022f39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f0f030604a6 in QAbstractButton::clicked(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f0f0306071e in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f0f0306235c in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f0f0306257b in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f0f02faec28 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f0f02f6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f0f02f74612 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f0f022bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f0f02f72712 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f0f02fc81cc in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f0f02fcb590 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f0f02f6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f0f022bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f0f0274240d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #24 0x7f0f027164bc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7f0efc6fa54e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #26 0x7f0f015f249d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f0f0164d178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f0f015f11b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f0f02314e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f0f022b97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f0f022c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x56472de4756b in main (argc=, argv=) at /usr/src/kstars-bleeding-6:3.6.4+202304120910~ubuntu23.04.1/kstars/main.cpp:385 [Inferior 1 (process 11520) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 472181] New: Project does not build
https://bugs.kde.org/show_bug.cgi?id=472181 Bug ID: 472181 Summary: Project does not build Classification: Applications Product: KTechLab Version: 0.50.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: zoltan.pad...@gmail.com Reporter: charles.hu...@hotmail.fr CC: jul...@svg4all.de Target Milestone: --- Created attachment 160247 --> https://bugs.kde.org/attachment.cgi?id=160247&action=edit build logs Hello, I cloned the project "https://invent.kde.org/sdk/ktechlab"; and followed the instruction to build it after the installation of all the dependencies. The project does not build because of 2 errors. Please find the log file in attachment. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 472181] Project does not build
https://bugs.kde.org/show_bug.cgi?id=472181 charles changed: What|Removed |Added CC||charles.hu...@hotmail.fr -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 472181] Project does not build
https://bugs.kde.org/show_bug.cgi?id=472181 --- Comment #1 from charles --- Comment on attachment 160247 --> https://bugs.kde.org/attachment.cgi?id=160247 build logs == starting build at mer. 12 juil. 2023 11:44:11 CEST == [ 1%] Generating ts... [ 1%] Generating mo... [ 1%] Built target tsfiles-073a86723a69281a85f2259982bbd97b [ 1%] Automatic MOC for target microbe [ 1%] Built target microbe_autogen [ 1%] Automatic MOC for target test_ktechlab [ 1%] Built target test_ktechlab_autogen [ 1%] Automatic MOC for target ktechlab [ 1%] Built target ktechlab_autogen [ 1%] Automatic MOC for target core [ 1%] Built target pofiles-073a86723a69281a85f2259982bbd97b [ 1%] Built target core_autogen [ 1%] Automatic MOC for target elements [ 1%] Automatic MOC for target flowparts [ 1%] Built target elements_autogen [ 1%] Automatic MOC for target micro [ 1%] Built target flowparts_autogen [ 1%] Built target micro_autogen [ 1%] Automatic MOC for target mechanics [ 1%] Automatic MOC for target drawparts [ 1%] Built target drawparts_autogen [ 1%] Built target mechanics_autogen [ 1%] Automatic MOC for target ktlqt3support [ 1%] Automatic MOC for target math [ 1%] Built target math_autogen [ 1%] Built target ktlqt3support_autogen [ 1%] Built target doc-en-index-cache-bz2 [ 1%] Building CXX object microbe/CMakeFiles/microbe.dir/instruction.cpp.o [ 1%] Automatic MOC for target test_loaded_icons [ 1%] Built target test_loaded_icons_autogen [ 1%] Building CXX object src/CMakeFiles/test_ktechlab.dir/gui/itemeditor/propertyeditorlist.cpp.o /home/charles/ktechlab/ktechlab/microbe/instruction.cpp: In member function ‘virtual QString Instr_sourceCode::code() const’: /home/charles/ktechlab/ktechlab/microbe/instruction.cpp:3758:50: error: ‘SkipEmptyParts’ is not a member of ‘Qt’ 3758 | QStringList sourceLines = m_raw.split("\n", Qt::SkipEmptyParts); // QString::split("\n",m_raw); | ^~ make[2]: *** [microbe/CMakeFiles/microbe.dir/build.make:180 : microbe/CMakeFiles/microbe.dir/instruction.cpp.o] Erreur 1 make[1]: *** [CMakeFiles/Makefile2:1600 : microbe/CMakeFiles/microbe.dir/all] Erreur 2 make[1]: *** Attente des tâches non terminées [ 1%] Building CXX object src/CMakeFiles/test_ktechlab.dir/gui/itemeditor/orientationwidget.cpp.o /home/charles/ktechlab/ktechlab/src/gui/itemeditor/propertyeditorlist.cpp: In constructor ‘PropertyEditorList::PropertyEditorList(QWidget*, Property*)’: /home/charles/ktechlab/ktechlab/src/gui/itemeditor/propertyeditorlist.cpp:130:64: error: ‘textActivated’ is not a member of ‘PropComboBox’ 130 | connect(m_combo, qOverload(&PropComboBox::textActivated), this, &PropertyEditorList::valueChanged); | ^ make[2]: *** [src/CMakeFiles/test_ktechlab.dir/build.make:265 : src/CMakeFiles/test_ktechlab.dir/gui/itemeditor/propertyeditorlist.cpp.o] Erreur 1 make[2]: *** Attente des tâches non terminées make[1]: *** [CMakeFiles/Makefile2:1654 : src/CMakeFiles/test_ktechlab.dir/all] Erreur 2 make: *** [Makefile:141 : all] Erreur 2 -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 472181] Project does not build
https://bugs.kde.org/show_bug.cgi?id=472181 --- Comment #2 from charles --- Created attachment 160249 --> https://bugs.kde.org/attachment.cgi?id=160249&action=edit build logs latest -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 472181] Project does not build
https://bugs.kde.org/show_bug.cgi?id=472181 --- Comment #3 from charles --- My version of QT is 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 472181] Project does not build
https://bugs.kde.org/show_bug.cgi?id=472181 --- Comment #5 from charles --- thx. I'll try that -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462533] New: Crash at render
https://bugs.kde.org/show_bug.cgi?id=462533 Bug ID: 462533 Summary: Crash at render Classification: Applications Product: kdenlive Version: 22.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: crazedtec...@gmail.com Target Milestone: --- Render will crash shortly after starting but only while using defish effect. *** Rendering of /home/charles/Videos/YouTube/NEXT/enclave2.mp4 crashed mlt_repository_init: failed to dlopen /usr/lib/mlt-7/libmltopencv.so (libopencv_tracking.so.406: cannot open shared object file: No such file or directory) mlt_repository_init: failed to dlopen /usr/lib/mlt-7/libmltmovit.so (libmovit.so.8: cannot open shared object file: No such file or directory) mlt_repository_init: failed to dlopen /usr/lib/mlt-7/libmltsox.so (libsox.so.3: cannot open shared object file: No such file or directory) x265 [info]: HEVC encoder version 3.5 x265 [info]: build info [Linux][GCC 11.2.0][64 bit] 8bit+10bit+12bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 x265 [info]: Main profile, Level-5 (Main tier) x265 [info]: Thread pool created using 32 threads x265 [info]: Slices : 1 x265 [info]: frame threads / pool features : 16 / wpp(34 rows) x265 [info]: Coding QT: max CU size, min CU size : 64 / 8 x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra x265 [info]: ME / range / subpel / merge : hex / 57 / 1 / 2 x265 [info]: Keyframe min / max / scenecut / bias : 25 / 250 / 40 / 5.00 x265 [info]: Lookahead / bframes / badapt : 15 / 4 / 0 x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0 x265 [info]: References / ref-limit cu / depth : 2 / on / on x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1 x265 [info]: Rate Control / qCompress : CRF-15.0 / 0.60 x265 [info]: tools: rd=2 psy-rd=2.00 early-skip rskip mode=1 signhide tmvp x265 [info]: tools: fast-intra strong-intra-smoothing lslices=8 deblock sao STEPS TO REPRODUCE 1. add video file 2. Add defish to the effect for entire track or to video clip. I set defish to 780 under amount. 3. Attempt to render video. I am using 4k video. OBSERVED RESULT Crash upon render EXPECTED RESULT Actually render the video SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel version: 5.15.78-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462533] Crash at render
https://bugs.kde.org/show_bug.cgi?id=462533 --- Comment #3 from Charles --- Turning off parallel processing fixed it. I always had that on without issues previously though. So the bug is still there. It may be something in my version of Manjaro/system kernel or kdenlive, I'm not sure. At least I can get the work I need done though thanks. Lots going on in software these days and I'm no genius in the world of PC. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 393557] New: Calligra Words crash when deleting centered spaces below a table
https://bugs.kde.org/show_bug.cgi?id=393557 Bug ID: 393557 Summary: Calligra Words crash when deleting centered spaces below a table Product: calligrawords Version: 3.1.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: gulagehierleit...@gmail.com Target Milestone: --- Application: calligrawords (3.1.0) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: Deleteting two page-centered spaces below a table, crash resulting after deleting the second (last) space below the table. This error reoccurs after I open the recovered document and repeat the action. - Custom settings of the application: Kvantum theme engine, global file menu, Window Width: 939 Width: 678, Add object applet docked to the right and collapsed, Primary? applet/section docked to the right under it and expanded. I was editing on the second page at the time. The table was split with two rows of cells on the second page. The crash can be reproduced sometimes. -- Backtrace: Application: Calligra Words (calligrawords), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70ffddc8c0 (LWP 8794))] Thread 3 (Thread 0x7f70d3051700 (LWP 9441)): #0 0x7f70f7062a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f70f701ddb9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70f701e330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70f701e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f70fe2a75cb in QEventDispatcherGlib::processEvents (this=0x7f70cc0599c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f70fe24e64a in QEventLoop::exec (this=this@entry=0x7f70d3050d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f70fe06e554 in QThread::exec (this=) at thread/qthread.cpp:522 #7 0x7f70fe0736eb in QThreadPrivate::start (arg=0x3023490) at thread/qthread_unix.cpp:376 #8 0x7f70f86896ba in start_thread (arg=0x7f70d3051700) at pthread_create.c:333 #9 0x7f70ff7f241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f70de428700 (LWP 8797)): #0 0x7f70ff7e227d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f70f70616f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70f701de74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70f701e330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f70f701e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f70fe2a75cb in QEventDispatcherGlib::processEvents (this=0x7f70d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f70fe24e64a in QEventLoop::exec (this=this@entry=0x7f70de427cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f70fe06e554 in QThread::exec (this=this@entry=0x7f70f8f48d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:522 #8 0x7f70f8cd42c5 in QDBusConnectionManager::run (this=0x7f70f8f48d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7f70fe0736eb in QThreadPrivate::start (arg=0x7f70f8f48d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:376 #10 0x7f70f86896ba in start_thread (arg=0x7f70de428700) at pthread_create.c:333 #11 0x7f70ff7f241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f70ffddc8c0 (LWP 8794)): [KCrash Handler] #6 QScopedPointer >::data (this=0x29) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:140 #7 qGetPtrHelper > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1013 #8 QTextObject::d_func (this=0x21) at text/qtextobject.h:84 #9 QTextObject::format (this=0x21) at text/qtextobject.cpp:124 #10 0x7f70f940504f in QTextTable::format (this=) at text/qtexttable.h:128 #11 QTextTablePrivate::update (this=this@entry=0x30585f0) at text/qtexttable.cpp:445 #12 0x7f70f94054c6 in QTextTable::columns (this=) at text/qtexttable.cpp:1271 #13 0x7f70fd6f84e9 in ?? () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #14 0x7f70fd6f796e in ?? () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #15 0x7f70fd6d3e69 in KoTextLayoutArea::layout(FrameIterator*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #16 0x7f70fd6ebe4d in KoTextLayoutRootArea:
[systemsettings] [Bug 389133] Exiting Web Shortcuts crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=389133 --- Comment #3 from Charles --- Created attachment 110293 --> https://bugs.kde.org/attachment.cgi?id=110293&action=edit New crash information added by DrKonqi systemsettings5 (5.11.5) using Qt 5.9.3 - What I was doing when the application crashed: Every time I click Shortcuts, Web-Shortcuts, then as soon as I click Global Shortcuts systemsettings crashes. - Custom settings of the application: The entire application is the settings application. I have "Use preferred shortcuts only" selected. I use kvantum manager and Arc Dark Transparent theme. I use Papirus Icons. I use "de:en_US.UTF-8" language. -- Backtrace (Reduced): #7 0x7f9b5123653e in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320 #8 qDeleteAll > (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328 #9 ProvidersModel::~ProvidersModel (this=0x5c16f50, __in_chrg=) at /workspace/build/src/urifilters/ikws/ikwsopts.cpp:43 #10 0x7f9b512365a9 in ProvidersModel::~ProvidersModel (this=0x5c16f50, __in_chrg=) at /workspace/build/src/urifilters/ikws/ikwsopts.cpp:44 #11 0x7f9b8819cd63 in QObjectPrivate::deleteChildren (this=this@entry=0x128aee0) at kernel/qobject.cpp:1992 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389133] Exiting Web Shortcuts crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=389133 Charles changed: What|Removed |Added CC||gulagehierleit...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390887] New: Crash when opening systemsettings5 as root
https://bugs.kde.org/show_bug.cgi?id=390887 Bug ID: 390887 Summary: Crash when opening systemsettings5 as root Product: systemsettings Version: 5.12.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gulagehierleit...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.1) Qt Version: 5.9.3 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I ran `export $(dbus-launch)` and then `systemsettings5` from konsole and shortly after selecting the first menu, the application crashed. - Custom settings of the application: The entire application is the settings application :( -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe787c448c0 (LWP 12861))] Thread 5 (Thread 0x7fe74dfe5700 (LWP 12881)): #0 0x7fe77d981f25 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe77d9823f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe7480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe74dfe4ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x75f2910) at thread/qthread.cpp:515 #6 0x7fe7819b0d25 in QQmlThreadPrivate::run (this=0x75f2910) at qml/ftw/qqmlthread.cpp:147 #7 0x7fe783e3f709 in QThreadPrivate::start (arg=0x75f2910) at thread/qthread_unix.cpp:368 #8 0x7fe77fc306ba in start_thread (arg=0x7fe74dfe5700) at pthread_create.c:333 #9 0x7fe78374e41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fe755ade700 (LWP 12866)): #0 0x7fe78374274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe77d98238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe758c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe755addce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x2a6bc60) at thread/qthread.cpp:515 #6 0x7fe7819b0d25 in QQmlThreadPrivate::run (this=0x2a6bc60) at qml/ftw/qqmlthread.cpp:147 #7 0x7fe783e3f709 in QThreadPrivate::start (arg=0x2a6bc60) at thread/qthread_unix.cpp:368 #8 0x7fe77fc306ba in start_thread (arg=0x7fe755ade700) at pthread_create.c:333 #9 0x7fe78374e41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fe75f666700 (LWP 12865)): #0 0x7fe78374274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe77d98238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe7580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe75f665ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x27f7260) at thread/qthread.cpp:515 #6 0x7fe7819b0d25 in QQmlThreadPrivate::run (this=0x27f7260) at qml/ftw/qqmlthread.cpp:147 #7 0x7fe783e3f709 in QThreadPrivate::start (arg=0x27f7260) at thread/qthread_unix.cpp:368 #8 0x7fe77fc306ba in start_thread (arg=0x7fe75f666700) at pthread_create.c:333 #9 0x7fe78374e41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fe76b72f700 (LWP 12863)): #0 0x7fe78374274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe77d98238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe77d98249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7840696cb in QEventDispatcherGlib::processEvents (this=0x7fe7640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe784011e2a in QEventLoop::exec (this=this@entry=0x7fe76b72ecd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe783e3a8f4 in QThread::exec (this=this@entry=0x7fe785bdbd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holde
[systemsettings] [Bug 390887] Crash when opening systemsettings5 as root
https://bugs.kde.org/show_bug.cgi?id=390887 --- Comment #2 from Charles --- Got it. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 388693] New: Error Retrieving Audit Log
https://bugs.kde.org/show_bug.cgi?id=388693 Bug ID: 388693 Summary: Error Retrieving Audit Log Product: kleopatra Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: charles.vasq...@supremofoods.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- Kleopatra Version 3.0.1-gpg4win-3.0.2 Error Retrieving Audit Log: Decryption failed Files are stored in the \users\ "username"\AppData\Local\Temp with the name kleopatra, the file has some random characters. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389734] New: systemsettings5 crash when mindlessly clicking through menus
https://bugs.kde.org/show_bug.cgi?id=389734 Bug ID: 389734 Summary: systemsettings5 crash when mindlessly clicking through menus Product: systemsettings Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gulagehierleit...@gmail.com Target Milestone: --- Application: systemsettings5 (5.11.5) Qt Version: 5.9.3 Frameworks Version: 5.42.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: Clicking through menus from the bottom up. Sidebar mode (v5.11.5+?). Under Network. I clicked the Bluetooth. (it's deactivated). I clicked Connectivity. I clicked Settings. I maybe clicked Browser Identification. I maybe clicked Cookies, Cache, SSL Preferences, Connection Preferences, etc. At about that point it crashed. My locale was misconfigured. I can give you the saved output of the locale command. My install is new approx 1-30-18 user edition iso. - Custom settings for the application: Umm, the entire application is settings... :( Though, since I have done little activity on this installation so far, I've archived most of my .config directory. Maybe that helps. I can give you it. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f756b5ae8c0 (LWP 1705))] Thread 8 (Thread 0x7f7522b67700 (LWP 1735)): #0 0x7f75672aa74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f756124538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7561245712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f752b93d9d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f756126bbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f75630ce6ba in start_thread (arg=0x7f7522b67700) at pthread_create.c:333 #6 0x7f75672b641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f751affd700 (LWP 1734)): #0 0x7f75672a627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f75612886f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7561244e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7561245330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f756124549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f75612454d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f756126bbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f75630ce6ba in start_thread (arg=0x7f751affd700) at pthread_create.c:333 #8 0x7f75672b641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f753254e700 (LWP 1716)): #0 0x7f75672aa74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f756124538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f756124549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7567bd16cb in QEventDispatcherGlib::processEvents (this=0x7f752c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7567b79e2a in QEventLoop::exec (this=this@entry=0x7f753254dce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f75679a28f4 in QThread::exec (this=this@entry=0x1797380) at thread/qthread.cpp:515 #6 0x7f7565a57d25 in QQmlThreadPrivate::run (this=0x1797380) at qml/ftw/qqmlthread.cpp:147 #7 0x7f75679a7709 in QThreadPrivate::start (arg=0x1797380) at thread/qthread_unix.cpp:368 #8 0x7f75630ce6ba in start_thread (arg=0x7f753254e700) at pthread_create.c:333 #9 0x7f75672b641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f7538f56700 (LWP 1712)): #0 0x7f75672a627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f75612886f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7561244e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7561245330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f756124549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7567bd16cb in QEventDispatcherGlib::processEvents (this=0x7f75340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7567b79e2a in QEventLoop::exec (this=this@entry=0x7f7538f55ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f75679a28f4 in QThread::exec (this=this@entry=0x1806180) at thread/qthread.cpp:515 #8 0x7f7565a57d25 in QQmlThread
[kleopatra] [Bug 186354] Suppress Audit Log links when Audit Log is not available
https://bugs.kde.org/show_bug.cgi?id=186354 Charles changed: What|Removed |Added CC||charles.vasquez@supremofood ||s.com -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 73913] KGpg "Processing decryption" window doesn't disappear when decryption failed
https://bugs.kde.org/show_bug.cgi?id=73913 Charles changed: What|Removed |Added CC||charles.vasquez@supremofood ||s.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383963] New: Kate is not opening current folder when it's remote (KIO, sftp)
https://bugs.kde.org/show_bug.cgi?id=383963 Bug ID: 383963 Summary: Kate is not opening current folder when it's remote (KIO, sftp) Product: kate Version: 17.04.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: charles.vej...@yale.edu Target Milestone: --- Hi, When I open a remote folder in Kate (sftp://) and open some file from there, it works. If I click to open a file again then the dialog open my local home and not the remote folder. Reproducible: Always Steps to Reproduce: 1) Open remote file with Kate 2) Try to open a second file. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Charles changed: What|Removed |Added CC||charlesfhub...@gmail.com --- Comment #43 from Charles --- Created attachment 103078 --> https://bugs.kde.org/attachment.cgi?id=103078&action=edit Tablet Log I was having a problem with my pressure sensitivity stopping after a time until I updated my tablet drivers to the most recent version. Now I'm having this problem too. I'm on a Ugee 1910B, using 3.1.1 I had to cheat a bit (by moving my pen away from my tablet quickly) to reproduce the stroke jumping because Krita gets better about knowing where my stylus is when the Tablet Logging is on. With Tablet logging on it basically works like it should, just a bit laggy. Let me know if you need any more info. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 --- Comment #44 from Charles --- If it makes any difference, I tried my tablet (Ugee 1910B) on my old desktop and it worked fine with the same driver. The computer I'm having a problem on has a AMD FX-8350 CPU The computer that works fine has an Intel(R) Core(TM) i5-3570k CPU Let me know if there is any other information I can provide that could be helpful. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 374113] New: Reversed Touchpad Scrolling has no effect in Testing Area on ubuntu + kubuntu-desktop
https://bugs.kde.org/show_bug.cgi?id=374113 Bug ID: 374113 Summary: Reversed Touchpad Scrolling has no effect in Testing Area on ubuntu + kubuntu-desktop Product: Touchpad-KCM Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kcm Assignee: rajeeshknamb...@gmail.com Reporter: busho...@gmail.com Target Milestone: --- I was trying to set reverse scrolling in Ubuntu 16.04 after installing kubuntu-desktop. I opened KCM, ticked the Reverse Scrolling for vertical. When I tested it in the "Testing Area", it did not reverse. I hit Apply, it still did not reverse. However... when testing the scroll in an actual desktop window, the scrolling actually had reversed. To be clear, the bug is only for the Testing Area in KCM. I'm not sure how check the currently installed version of this, but it's the latest after apt upgrade. I can get a more specific version if pointed in the right direction. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382252] New: "On you wrote:" has wrong timezone
https://bugs.kde.org/show_bug.cgi?id=382252 Bug ID: 382252 Summary: "On you wrote:" has wrong timezone Product: kmail2 Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: char...@derkarl.org Target Milestone: --- My machine is set to a certain timezone (EEST right now). I got an email sent from someone in a different timezone (PDT). In my inbox, the original email shows the correct time (i.e., the time as seen from my own timezone). When I click "Reply", the composer appears and adds the text "On you wrote:". This text has the correct date as seen from the original author's side (i.e., it shows the date in PDT), but the timezone shows my timezone. * Alice writes me an email, the time is 11:00 AM PDT or 09:00 PM. * My inbox shows Alice's email (correctly) as 09:00 EEST. * I click "Reply" * The composer now shows "On 11 July 2017 11:00 AM EEST". It should be either "11:00 AM PDT" or "09:00 PM EEST" `date` shows my computer as set to EEST correctly The inbox is correct The message headers are correct -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382907] New: Plasma died whilst completing "apt-get install" from a konsole window
https://bugs.kde.org/show_bug.cgi?id=382907 Bug ID: 382907 Summary: Plasma died whilst completing "apt-get install" from a konsole window Product: plasmashell Version: 5.5.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cfaulk40.andr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.8.0-36-generic i686 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: I was installing Audacity via a Konsole window, using apt-get install (and running in the window as root using su). The procedure for obtaining all the required files had been completed, and final installation was taking place, when the konsole window froze. - Unusual behavior I noticed: Artefacts on the display when I was closing other desktop windows behind the konsole, also the machine became very slow and lagged to keyboard and mouse input. - Custom settings of the application: The konsole was running a customized profile, using Black on Light yellow with large text (size 22 font due to visual issues). The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1b2c800 (LWP 1712))] Thread 8 (Thread 0x9f1ffb40 (LWP 2016)): #0 0xb5297daf in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #1 0xb442aada in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb442b0b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb442b254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb5298964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb523d7a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb523dbfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb5063f1d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0x9f90f980 in KCupsConnection::run() () from /usr/lib/i386-linux-gnu/libkcupslib.so #9 0xb506943b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb4c3e295 in start_thread (arg=0x9f1ffb40) at pthread_create.c:333 #11 0xb4d9605e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 7 (Thread 0xa585cb40 (LWP 1810)): #0 0xb7760ce5 in __kernel_vsyscall () #1 0xb4d8be7f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb4439b20 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb442b11c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb442b254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb5298964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb523d7a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb523dbfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb5063f1d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb6cb57a9 in ?? () from /usr/lib/i386-linux-gnu/libQt5Quick.so.5 #10 0xb506943b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb4c3e295 in start_thread (arg=0xa585cb40) at pthread_create.c:333 #12 0xb4d9605e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 6 (Thread 0xa6f3ab40 (LWP 1799)): #0 0xb7760ce5 in __kernel_vsyscall () #1 0xb4c43a6c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb4da27bd in __pthread_cond_wait (cond=0xb76cf8d0, mutex=0xb76cf8b8) at forward.c:149 #3 0xb7597a2c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #4 0xb7597a6c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #5 0xb4c3e295 in start_thread (arg=0xa6f3ab40) at pthread_create.c:333 #6 0xb4d9605e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 5 (Thread 0xa8063b40 (LWP 1797)): #0 0xb447145d in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb442aaec in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb442b0b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb442b254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb5298964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb523d7a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb523dbfa in QEvent
[KScreen] [Bug 396552] New: OSD for shows continuously, forever.
https://bugs.kde.org/show_bug.cgi?id=396552 Bug ID: 396552 Summary: OSD for shows continuously, forever. Product: KScreen Version: 5.13.2 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kded Assignee: se...@kde.org Reporter: carussell...@gmail.com Target Milestone: --- Hardware: Razer Blade 2017 When I plug in a second monitor connect thru my HDMI port. The OSD play keeps showing like the attached gif. The only way to stop it from showing the OSD and get control of my system is to stop "Kscreen 2" service in the background services. I am a developer in my day job, and I am willing to help in anyway possible. I believe the issue is with the intel-nvidia-bumblebee drivers. I think the since the HDMI port is connect to the NVidia graphics card that is not awake at the time the HDMI cable is inserted, that causes the problem. However, even I remove the HDMI cable the OSD still continue to flicker/pulse. I would really appreciate any insight into the problem if possible. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396552] OSD for shows continuously, forever.
https://bugs.kde.org/show_bug.cgi?id=396552 --- Comment #2 from Charles Russell --- sorry file size was too big. I uploaded to imgur. https://imgur.com/a/ufBylE3 I will also try to get some debugging information -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396552] OSD for shows continuously, forever.
https://bugs.kde.org/show_bug.cgi?id=396552 --- Comment #3 from Charles Russell --- Created attachment 113994 --> https://bugs.kde.org/attachment.cgi?id=113994&action=edit kscreen.log -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396552] OSD for shows continuously, forever.
https://bugs.kde.org/show_bug.cgi?id=396552 --- Comment #4 from Charles Russell --- Created attachment 113995 --> https://bugs.kde.org/attachment.cgi?id=113995&action=edit config1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396552] OSD for shows continuously, forever.
https://bugs.kde.org/show_bug.cgi?id=396552 --- Comment #5 from Charles Russell --- Created attachment 113996 --> https://bugs.kde.org/attachment.cgi?id=113996&action=edit config2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396552] OSD for shows continuously, forever.
https://bugs.kde.org/show_bug.cgi?id=396552 --- Comment #6 from Charles Russell --- As for clarification, the issue occurs once I connect HDMI cable to laptop HDMI port, it will continue even if i remove the HDMI cable. The only way to stop it is, reboot computer or stop kscreen background service. Thank you for you time and patience. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396812] New: Konsole suddenly shows no user groups, no problem when sudo
https://bugs.kde.org/show_bug.cgi?id=396812 Bug ID: 396812 Summary: Konsole suddenly shows no user groups, no problem when sudo Product: konsole Version: 17.12.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: busho...@gmail.com Target Milestone: --- I recently started having an issue where my Konsole windows won't have any user groups at login. An example of the issue is below. All my /etc/group file is fine. $ id uid=1001(charles) gid=1001(charles) groups=1001(charles) $ sudo - # id uid=0(root) gid=0(root) groups=0(root) # su - charles $ id uid=1001(charles) gid=1001(charles) groups=1001(charles),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),117(lpadmin),128(sambashare),130(vboxusers),999(docker),1002(chrome-remote-desktop) I've tried creating a brand new user on my system. At boot with Gnome, it had proper groups at login. At boot with KDE Plasma, I had no groups aside from my own user. I'm not positive this is an issue with Konsole, but I'm not sure how I would find out or where to look to go higher in the chain. -- You are receiving this mail because: You are watching all bug changes.
offerta di prestito
Ciao, Sono Dr Eric CHARLES, legittimo e affidabile prestito mutuante Da Skye Financial Service. Offriamo prestiti su una termini chiari e comprensibili e le condizioni a tasso di interesse del 3%. A partire da $ 5,000.00 a $ 450,000,000.00USD, euro e sterline solo. Offriamo Business Prestiti, prestiti personali, prestiti agli studenti, prestiti auto e prestiti per pagare le bollette, BG / SBLC a tassi bassi disponibili anche, Contattaci via e-mail ora.
[dolphin] [Bug 362436] Dolphin crash copying from a SMB: NAS device
https://bugs.kde.org/show_bug.cgi?id=362436 --- Comment #6 from charles dial --- The only additional information I can give you is that the problem involved a D-link dns-323 network storage device. This model is probably at least 10 years old and is no longer supported by D-Link. In general, both windows and Linux were able to access this NAS device, but there were sometimes long time outs when the computer was trying to find and connect to the device. It seems like there was a substantial wait, either for a thread to complete or for a thread which had completed and somehow or other was not recognized as a completed thread. This issue may or may not still be an issue. Charles Dial On Mon, Apr 2, 2018, 1:33 PM Elvis Angelaccio wrote: > https://bugs.kde.org/show_bug.cgi?id=362436 > > Elvis Angelaccio changed: > >What|Removed |Added > > > Status|REOPENED|NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #5 from Elvis Angelaccio --- > Changing back as needsinfo/backtrace. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382252] "On you wrote:" has wrong timezone
https://bugs.kde.org/show_bug.cgi?id=382252 Charles Samuels changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357524] GTK2 apps does not use custom color scheme
https://bugs.kde.org/show_bug.cgi?id=357524 Charles Huber changed: What|Removed |Added CC||genpfa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 289941] does not upgrade
https://bugs.kde.org/show_bug.cgi?id=289941 Charles Rocha changed: What|Removed |Added CC||charlesc.ro...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
offerta di prestito
Ciao, Sono Dr Eric CHARLES, legittimo e affidabile prestito mutuante Da Skye Financial Service. Offriamo prestiti su una termini chiari e comprensibili e le condizioni a tasso di interesse del 3%. A partire da $ 5,000.00 a $ 450,000,000.00USD, euro e sterline solo. Offriamo Business Prestiti, prestiti personali, prestiti agli studenti, prestiti auto e prestiti per pagare le bollette, BG / SBLC a tassi bassi disponibili anche, Contattaci via e-mail ora.
[kdelibs] [Bug 198172] printer margin settings are forgotten at restart
https://bugs.kde.org/show_bug.cgi?id=198172 Charles Dennett changed: What|Removed |Added CC||cdenn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 434560] New: Tray icon is useless (patch)
https://bugs.kde.org/show_bug.cgi?id=434560 Bug ID: 434560 Summary: Tray icon is useless (patch) Product: elisa Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: char...@derkarl.org Target Milestone: --- Created attachment 136799 --> https://bugs.kde.org/attachment.cgi?id=136799&action=edit Change tray behavior I have multiple virtual desktops and sometimes Elisa lives on another virtual desktop and I have to play "hunt the window". Also, having the tray icon only visible when the main window is just unnecessary. It doesn't help in any way. I think as-is, the tray icon is basically useless if you use virtual desktops. So please apply this patch that 1. Makes the tray icon always visible 2. Clicking on the tray icon always brings the window to the front (rather than just doing nothing if it's on another virtual desktop) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434415] Crash at update firewall policy from System Settings
https://bugs.kde.org/show_bug.cgi?id=434415 --- Comment #5 from Charles Dong --- Created attachment 136890 --> https://bugs.kde.org/attachment.cgi?id=136890&action=edit New crash information added by DrKonqi systemsettings5 (5.21.3) using Qt 5.15.2 - What I was doing when the application crashed: After configuring firewall, when I left and went back to the "firewall" section, the whole settings app crashed. - Custom settings of the application: Changed default incoming rules and added some rules. -- Backtrace (Reduced): #4 0x7f2e4022be26 in FirewallClient::capabilities (this=) at ./kcm/core/firewallclient.cpp:155 #5 0x7f2e40cdbb53 in KCMFirewall::KCMFirewall (this=0x55d7c8fb94c0, parent=, args=...) at ./kcm/kcm.cpp:36 #6 0x7f2e40cdf4ee in KPluginFactory::createInstance (parentWidget=, parent=, args=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:519 #7 0x7f2e98270a52 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #8 0x7f2e99884ba8 in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434415] Crash at update firewall policy from System Settings
https://bugs.kde.org/show_bug.cgi?id=434415 Charles Dong changed: What|Removed |Added CC||minidy20001...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427278] New: Panel & desktop config of secondary monitor lost after ScreenConnectors renumbering
https://bugs.kde.org/show_bug.cgi?id=427278 Bug ID: 427278 Summary: Panel & desktop config of secondary monitor lost after ScreenConnectors renumbering Product: plasmashell Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: genpfa...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The panel and desktop configruation of a monitor can get 'lost' after a ScreenConnectors renumbering, requiring manual editing of plasmashellrc to restore. STEPS TO REPRODUCE On my dual-monitor setup ~/.config/plasmashellrc looks like this: [ScreenConnectors] 0=DisplayPort-0 1=DisplayPort-1 DisplayPort-0 is the left display, DisplayPort-1 on the right. 1. Starting x0tigervncserver and connecting from another computer with TigerVNC Viewer 1.11.0 & the "Resize remote session to the local window" option checked ends up with DisplayPort-0 being resized to 800x600 and DisplayPort-1 being shut off. plasmashellrc ends up looking like this: x0tightvncserver [ScreenConnectors] 0=:0.0 1=DisplayPort-0 2=DisplayPort-1 No idea where :0.0 came from during that but it's apparently the primary connector now. 2. Disconnecting from VNC & and using the "Display Configuration" applet to re-enable & re-arrange both monitors like they were before gives me: [ScreenConnectors] 0=DisplayPort-0 1=:0.0 2=DisplayPort-1 OBSERVED RESULT Now the panel/desktop config for slot 1 is 'lost', stuck on :0.0. DisplayPort-1 ends up using a default panel & desktop config. I didn't see an obvious way to fix this situation in any of the System Settings applets. Editing plasmashellrc to put DisplayPort-1 back on slot 1 like it was in step #1 and restarting plasmashell restores the 'lost' panel/desktop config for DisplayPort-1. EXPECTED RESULT Ideally once I set things back up in the "Display Configuration" applet then DisplayPort-1 would end up back on slot 1 somehow and my panel/desktop config for that monitor would be restored. SOFTWARE/OS VERSIONS Kubuntu 20.04, amd64 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-45-generic -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427278] Panel & desktop config of secondary monitor lost after ScreenConnectors renumbering
https://bugs.kde.org/show_bug.cgi?id=427278 --- Comment #1 from Charles Huber --- This patch fixes things for me: https://invent.kde.org/genpfault/plasma-workspace/commit/181fc5746e9b4aaf491a90e76e770df866d880ad -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427350] New: digikam dng converter fails to correctly encode white balance or camera metadata for CR3
https://bugs.kde.org/show_bug.cgi?id=427350 Bug ID: 427350 Summary: digikam dng converter fails to correctly encode white balance or camera metadata for CR3 Product: digikam Version: 7.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Plugin-Bqm-DngConverter Assignee: digikam-bugs-n...@kde.org Reporter: charles.fig...@wartburg.edu Target Milestone: --- SUMMARY The white balance for CR3 images converted using the linux digikam 7.1.0 is corrupted, and image metadata (lens,aperture,ISO,exposure, focal length, etc) is absent. Images are strongly magenta. Other software (such as darktable) produces a warning ("failed to read camera white balance information"). Images converted through Adobe Digital Negative Converter 12.4.0.555 on Wine work as expected. STEPS TO REPRODUCE 1. Set the checkbox "convert DGN" 2. Import the images OBSERVED RESULT CR3 files converted to DGN format have corrupted white balance information. The JPG preview has a bad white balance. The image metadate is lacking all camera metadata (lens, aperture, exposure, ISO, etc) EXPECTED RESULT The resultant DGN format image should have white balance information that reflects the image. The white balance and metadata should be able to be read by other image manipulation programs capable of reading DGN files. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Running Digikam 7.1.0 I have sample images, but as these are raw and DGN image produced by the Canon R5, these images are 41-45MB in size. How can I submit these? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 409192] When modifying a file, and selecting Save As, Gwen-view saves and goes to the first file in the directory.
https://bugs.kde.org/show_bug.cgi?id=409192 Charles MacDonald changed: What|Removed |Added CC||aa...@ncf.ca -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 409192] New: When modifying a file, and selecting Save As, Gwen-view saves and goes to the first file in the directory.
https://bugs.kde.org/show_bug.cgi?id=409192 Bug ID: 409192 Summary: When modifying a file, and selecting Save As, Gwen-view saves and goes to the first file in the directory. Product: gwenview Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: aa...@ncf.ca Target Milestone: --- SUMMARY When modifying a file, and selecting Save As, Gwenview saves and goes to the first file in the directory STEPS TO REPRODUCE 1. View a file in the middle of a directory. 2. Rotate (or crop) the file 3. Do a Save AS OBSERVED RESULT File is saved, and Gwenview then displays the first file in the directory, rather than Previous behavior where it displayed (the saved file with the notation that they file has been changed) User then has to find the Saved file to locate where they were working this is of course confusing when Going through a directory with Several files that one wants to modify before sharing. (without changing the original) EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 422400] New: qqc2-desktop-style hard to use statically.
https://bugs.kde.org/show_bug.cgi?id=422400 Bug ID: 422400 Summary: qqc2-desktop-style hard to use statically. Product: frameworks-qqc2-desktop-style Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: barto.charlie+kde_b...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: --- SUMMARY qqc2desktopstyleplugin is very hard to static link against. When you static link qml plugins you usually use the cmake qt5_import_qml_plugins(TARGET) command, however for qqc2-desktop-style links against the plugin but fails to compile due to: "Qt5_QmlPlugins_Imports_mediagui.cpp.obj:-1: error: LNK2019: unresolved external symbol "struct QStaticPlugin const __cdecl qt_static_plugin_QQc2DesktopStylePlugin(void)" (?qt_static_plugin_QQc2DesktopStylePlugin@@YA?BUQStaticPlugin@@XZ) referenced in function "public: __cdecl StaticQQc2DesktopStylePluginPluginInstance::StaticQQc2DesktopStylePluginPluginInstance(void)" (??0StaticQQc2DesktopStylePluginPluginInstance@@QEAA@XZ)" I suspect this is because qqc2-desktop-style isn't defining something it needs to when building as a static plugin, but I'm not totally sure. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 (available in About System) KDE Frameworks Version: master Qt Version: 5.15 Compiler: Microsoft (R) C/C++ Optimizing Compiler Version 19.27.28826 for x64 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 422400] qqc2-desktop-style hard to use statically.
https://bugs.kde.org/show_bug.cgi?id=422400 --- Comment #1 from Charles Barto --- update: you need to define QT_STATICPLUGIN when building the static plugin, and also add classname QQc2DesktopStylePlugin to qmldir. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 407132] New: install "poker cards" does not give the poker cards.
https://bugs.kde.org/show_bug.cgi?id=407132 Bug ID: 407132 Summary: install "poker cards" does not give the poker cards. Product: kpat Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: solver Assignee: co...@kde.org Reporter: aa...@ncf.ca CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY install "poker cards" does not give the poker cards. STEPS TO REPRODUCE 1. Go to change apperance 2. search for Poker 3. install OBSERVED RESULT EXPECTED RESULT poker deck does not apper as selectable SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.95 Kpatience Version 3.6 ADDITIONAL INFORMATION going through the instuctions to downlaod and extract svg-poker-comon and move it to ~/.kde/carddecks/ also did not show the poker cards. Those are the only ones that look like real cards. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 407132] install "poker cards" does not give the poker cards.
https://bugs.kde.org/show_bug.cgi?id=407132 --- Comment #2 from Charles MacDonald --- On 2019-05-15 5:36 p.m., Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=407132 > > Albert Astals Cid changed: > > What|Removed |Added > >Component|solver |general > CC||aa...@kde.org > > --- Comment #1 from Albert Astals Cid --- > Works fine for me https://i.imgur.com/9oYXfOI.png > > I know it's not much solace knowing it works for other people. > > You don't really need to follow those instructions, just hitting the install > button makes the card appear as selectable to me. > did find it, it was selectable but in the middle of the long list. I had scrolled past it without seeing it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 418905] New: Unable to build as static library because of interaction w/ GenerateExportHeader
https://bugs.kde.org/show_bug.cgi?id=418905 Bug ID: 418905 Summary: Unable to build as static library because of interaction w/ GenerateExportHeader Product: frameworks-kirigami Version: Master Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: barto.charlie+kde_b...@gmail.com Target Milestone: Not decided SUMMARY It's not possible to build as a static library, because kirigami sets the STATIC_LIBRARY variable to "1" when building as a static library, then it tries to use GenerateExportHeader, which has code like the following: get_property(type TARGET ${TARGET_LIBRARY} PROPERTY TYPE) if(NOT ${TYPE} STREQUAL "STATIC_LIBRARY" ...) this if statement fails, because the "${type}" parameter is expanded to STATIC_LIBRARY, which is then expanded by the if statement to "1"! STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KDE Config Driver Manager] [Bug 402545] New: issue with booting
https://bugs.kde.org/show_bug.cgi?id=402545 Bug ID: 402545 Summary: issue with booting Product: KDE Config Driver Manager Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: charlesdean2...@gmail.com Target Milestone: --- SUMMARY I do not understand where to put this . One it ask what product fail UNKNOWN. All I know is this POP OS with a new System 76 laptop lost the audio input to play audio from Face book . Test with you tube same result. Try to reboot to see it it returns , will not boot. Advised to turn on the laptop and hold space bar and recover . I did that and restart when it wants to go live , install and forgot what the other option was.. It boots , play audio and then audio stops when opening another audio in Face Book. 4 days looking for the problem in here and I am lost and confused . I am not up on the lingo I see here and I am not the technician on this. When some one gives advice it is in a lingo I am not privy to. Called System 76 last week with no response when I left a msg on its voice mail . STEPS TO REPRODUCE 1. open a FB Video 2. reboot 3. boot under hold space bar and use restore OBSERVED RESULT same result EXPECTED RESULT To work as expected , but the input only has one and that is the internal microphone. SOFTWARE/OS VERSIONS Pop!_OS 18.10 64 bit with System 76 gazelle Laptop Linux/KDE Plasma: Pop!_OS 18.10 (available in About System) KDE Plasma Version: Not in the about window KDE Frameworks Version: Not in the about window Qt Version: Not in the about window ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402914] New: Crash when selecting custom icon for tag
https://bugs.kde.org/show_bug.cgi?id=402914 Bug ID: 402914 Summary: Crash when selecting custom icon for tag Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Manager Assignee: digikam-bugs-n...@kde.org Reporter: ursi...@mac.com Target Milestone: --- SUMMARY Using a Mac (Retina 5K, 27-inch, 2017), macOS Mojave, Version 10.14.2, Digikam Version 6.0.0-beta3, Build date: Dec 28 2018. digiKam crashes when selecting a custom icon for a tag using the Tag Manager. STEPS TO REPRODUCE 1. Open Tag Manager and click on Tag Properties. 2. Select a Tag, click on the Icon button in the Tag Properties window. 3. In the pop-up, select "Other icons" and then click on "Browse". 4. You are then presented with a "Finder" window, which cannot be manipulated. 5. Upon closing this window or choosing "Cancel", digiKam crashes. OBSERVED RESULT Trying to navigate to an icon results in a crash. EXPECTED RESULT Being able to navigate and select a custom icon for a tag. SOFTWARE/OS VERSIONS Windows: MacOS: macOS Mojave, Version 10.14.2 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Digikam Version 6.0.0-beta3, Build date: Dec 28 2018. Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379649] Application Launcher search box does not accept keyboard input
https://bugs.kde.org/show_bug.cgi?id=379649 Charles Samuels changed: What|Removed |Added CC||char...@derkarl.org --- Comment #9 from Charles Samuels --- I reported the same bug here (workaround included): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922334 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391991] Keyboard Layout switching stops working when ibus is installed
https://bugs.kde.org/show_bug.cgi?id=391991 Charles Samuels changed: What|Removed |Added CC||char...@derkarl.org --- Comment #2 from Charles Samuels --- Also seen in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922334 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467845] Kmail crashes when clicking on mail which is gpg signed
https://bugs.kde.org/show_bug.cgi?id=467845 Charles Darwin changed: What|Removed |Added CC||raj...@uw.edu -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472787] Crash on Outbox
https://bugs.kde.org/show_bug.cgi?id=472787 Charles Darwin changed: What|Removed |Added CC||raj...@uw.edu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454101] kwin_wayland had high CPU usage
https://bugs.kde.org/show_bug.cgi?id=454101 Charles Dennett changed: What|Removed |Added CC||cdenn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Charles Brockman changed: What|Removed |Added CC||k...@cbpwd.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470845] New: Dolphin crashes in rawhide
https://bugs.kde.org/show_bug.cgi?id=470845 Bug ID: 470845 Summary: Dolphin crashes in rawhide Classification: Applications Product: dolphin Version: 23.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: charles.men...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.1) Qt Version: 5.15.9 Frameworks Version: 5.107.0 Operating System: Linux 6.4.0-0.rc5.41.fc39.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 39 (Workstation Edition Prerelease) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Using Fedora Rawhide on a clean install, attempting to launch Dolphin, clicking on the taskbar icon it crashes every time. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7feda7ec0a74 in Solid::StorageAccess::isEncrypted() const () from /lib64/libKF5Solid.so.5 #5 0x7feda82744e9 in KIO::PreviewJobPrivate::createThumbnail(QString const&) () from /lib64/libKF5KIOWidgets.so.5 #6 0x7feda82779b0 in KIO::PreviewJob::slotResult(KJob*) () from /lib64/libKF5KIOWidgets.so.5 #7 0x7feda64e86c1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7feda783dfc6 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #9 0x7feda7843bab in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #10 0x7feda64e86c1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #11 0x7feda80159d7 in KIO::SlaveInterface::error(int, QString const&) () from /lib64/libKF5KIOCore.so.5 #12 0x7feda801aafe in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #13 0x7feda80157fb in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #14 0x7feda8018121 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #15 0x7feda64e86c1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7feda64df7ab in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7feda71aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7feda64b3db8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7feda64b7265 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #20 0x7feda6506e3f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #21 0x7feda43133ac in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #22 0x7feda4371448 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #23 0x7feda4310a33 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #24 0x7feda6506929 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7feda64b277b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7feda64baa0b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #27 0x55a7fb208185 in main () [Inferior 1 (process 4027) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 456713] plasma-kded.service hangs for around a minute or more on system shutdown
https://bugs.kde.org/show_bug.cgi?id=456713 Charles Dennett changed: What|Removed |Added CC||cdenn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433575] New: proxy setting not working
https://bugs.kde.org/show_bug.cgi?id=433575 Bug ID: 433575 Summary: proxy setting not working Product: systemsettings Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_proxy Assignee: konq-b...@kde.org Reporter: joker_char...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. open the Proxy --System Settings 2. select Use manually specified proxy configuration and apply(I entered the correct ip and port,It work well on my Windows10 computer) 3. No matter what browser I use, and curl tool, I can't get my curl tool to be proxied. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux version 5.8.0-45-generic (buildd@lcy01-amd64-010) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #51-Ubuntu SMP Fri Feb 19 13:24:51 UTC 2021 (available in About System) KDE Plasma Version: kde-plasma-desktop/groovy 5:106ubuntu1 amd64 KDE Frameworks Version: plasma-framework/groovy,now 5.74.0a-0ubuntu1 amd64 Qt Version: qt5-gtk-platformtheme/groovy,now 5.14.2+dfsg-6 amd64 [已安装,自动] qt5-image-formats-plugins/groovy,now 5.14.2-2 amd64 [已安装,自动] qtchooser/groovy,now 66-2build1 amd64 [已安装,自动] qtspeech5-flite-plugin/groovy,now 5.14.2-2 amd64 [已安装,自动] qttranslations5-l10n/groovy,groovy,now 5.14.2-2 all [已安装,自动] qtvirtualkeyboard-plugin/groovy,now 5.14.2+dfsg-2 amd64 [已安装,自动] qtwayland5/groovy,now 5.14.2-2 amd64 [已安装,自动] ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451900] New: FR: Ability to control Android Devices media playback by system hotkeys such as volume up/down pause/play fast-forward/rewind
https://bugs.kde.org/show_bug.cgi?id=451900 Bug ID: 451900 Summary: FR: Ability to control Android Devices media playback by system hotkeys such as volume up/down pause/play fast-forward/rewind Product: kdeconnect Version: unspecified Platform: Microsoft Windows OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: charliepor...@gmail.com Target Milestone: --- SUMMARY FR: Ability to control Android Devices media playback by system hotkeys such as volume up/down pause/play fast-forward/rewind Not just limited to Android and Windows though, MacOS, Linux you name it. I think this would be a valuable feature STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 431921] Black square appears sometimes in KMail
https://bugs.kde.org/show_bug.cgi?id=431921 Charles Samuels changed: What|Removed |Added CC||char...@derkarl.org --- Comment #3 from Charles Samuels --- I get it too on Debian Bullseye. I'd include a screenshot, but it's pretty much the same. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 431921] Black square appears sometimes in KMail
https://bugs.kde.org/show_bug.cgi?id=431921 --- Comment #4 from Charles Samuels --- The same problem appears to exist in qBittorrent <https://github.com/qbittorrent/qBittorrent/issues/13368> In both cases, it seems to be over a QSplitter. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 435004] New: Close button overlaps countdown circle in 150% scale
https://bugs.kde.org/show_bug.cgi?id=435004 Bug ID: 435004 Summary: Close button overlaps countdown circle in 150% scale Product: frameworks-knotifications Version: 5.80.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: minidy20001...@outlook.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 137097 --> https://bugs.kde.org/attachment.cgi?id=137097&action=edit A reproduction of the problem SUMMARY After setting scale to 150%, the close buttons of popups become bigger, which cover the countdown circles and make them hardly to be seen. (Actually this problem has been found since Plasma 5.20, but I just remember it just now.) STEPS TO REPRODUCE 1. Installed Plasma version >= 5.20 2. System Settings > Display and Monitor > Display Configuration > Global scale, change it to 150% 3. Try to activate a timed popup OBSERVED RESULT The close button covers the countdown circle. EXPECTED RESULT The countdown circle shows clearly. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Linux 5.4.0-70-generic / KDE 5.80.0 / Plasma 5.21.3 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446291] New: Window position changes after plugging in external monitor
https://bugs.kde.org/show_bug.cgi?id=446291 Bug ID: 446291 Summary: Window position changes after plugging in external monitor Product: kwin Version: 5.23.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: accou...@charlesbeauville.com Target Milestone: --- Created attachment 144091 --> https://bugs.kde.org/attachment.cgi?id=144091&action=edit Relevant log lines when I plug my external monitor 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux: 5.12.2-2-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446291] Window position changes after plugging in external monitor
https://bugs.kde.org/show_bug.cgi?id=446291 --- Comment #1 from Charles Beauville --- SUMMARY It's been a few days now that I've had this issue, basically when I plug my external monitor (which becomes the primary display to the left of my laptop, at the same resolution), my open windows keep the same size but their positions go to x=0 for the external monitor and to the top right corner for the laptop screen. Even when I set some window rules to force the x and y positions of the windows, this still happens. I have tried switching the primary display, still the same problem (except now the window moves to the right edge of the laptop screen) STEPS TO REPRODUCE 1. Have a window opened 2. Plug external monitor OBSERVED RESULT Opened window gets shifted to the left edge of the screen (for the external monitor). If the window was on the laptop screen, it gets shifted to the top right of it. EXPECTED RESULT The windows should stay in the center of the screen, in the same position as before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446291] Window position changes after plugging in external monitor
https://bugs.kde.org/show_bug.cgi?id=446291 --- Comment #2 from Charles Beauville --- Created attachment 144093 --> https://bugs.kde.org/attachment.cgi?id=144093&action=edit Opened window before plugging the external monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446291] Window position changes after plugging in external monitor
https://bugs.kde.org/show_bug.cgi?id=446291 --- Comment #3 from Charles Beauville --- Created attachment 144094 --> https://bugs.kde.org/attachment.cgi?id=144094&action=edit Opened window after plugging in the external monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446291] Window position changes after plugging in external monitor
https://bugs.kde.org/show_bug.cgi?id=446291 Charles Beauville changed: What|Removed |Added Keywords||multiscreen --- Comment #4 from Charles Beauville --- Note that this happens whether "Window Placement" is set as "Minimal Overlap" or as "Center". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 484639] Fallback to Breeze ignored by KIconLoader because of wrong global initialization order
https://bugs.kde.org/show_bug.cgi?id=484639 Charles Dennett changed: What|Removed |Added CC||cdenn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 486752] Missing systray icons
https://bugs.kde.org/show_bug.cgi?id=486752 Charles Dennett changed: What|Removed |Added CC||cdenn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474961] New: Crash while selecting scrolling text
https://bugs.kde.org/show_bug.cgi?id=474961 Bug ID: 474961 Summary: Crash while selecting scrolling text Classification: Applications Product: konsole Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: char...@derkarl.org Target Milestone: --- Application: konsole (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-11-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Note: this is not https://bugs.kde.org/show_bug.cgi?id=458822, because I'm using a version newer than v22.08.3 I can reproduce this by: 1. Run a program that generates a lot of text in Konsole: while true; do echo $RANDOM; sleep 0.005; done 2. Have the machine be under a lot of CPU load 3. Consider nicing +20 the konsole process 4. Start selecting text as it scrolls by, move the mouse around like a psycho. You may need to tweak the number "0.005" The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #5 0x7f7da74a9d9f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 0x7f7da745af32 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7f7da7445472 in __GI_abort () at ./stdlib/abort.c:79 #8 0x7f7da729d919 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f7da72a8e1a in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f7da72a8e85 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f7da72a90d8 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f7da72a026d in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #13 0x7f7da8e9c040 in Konsole::Screen::setSelectionEnd(int, int, bool) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #14 0x7f7da8e9df4f in ?? () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #15 0x7f7da8effe0c in Konsole::TerminalDisplay::extendSelection(QPoint const&) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #16 0x7f7da8f001ca in Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #17 0x7f7da85a4db8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f7da8562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f7da856b552 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f7da78b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f7da856965e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f7da85bdbd8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f7da85c0f60 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f7da8562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f7da78b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f7da7d3d3ed in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #27 0x7f7da7d11cac in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #28 0x7f7da14fbeca in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #29 0x7f7da5c607a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f7da5c60a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f7da5c60acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f7da7909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f7da78b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f7da78b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x55e281354e4c in ?? () #36 0x7f7da74461ca in __libc_start_call_main (main=main@entry=0x55e281354690, argc=argc@entry=1, argv=argv@entry=0x7ffed4a9f6d8) at ../sysdeps/nptl/libc_start_call_main.h:58 #37 0x7f7da7446285 in __libc_start_main_impl (main=0x55e281354690, argc=1, argv=0x7ffed4a9f6d8, init=, fini=, rtld_fini=, stack_end=0x7ffed4a9f6c8) at ../csu/libc-start.c:360 #38 0
[konsole] [Bug 474961] [PATCH] Crash while selecting scrolling text
https://bugs.kde.org/show_bug.cgi?id=474961 Charles Samuels changed: What|Removed |Added Summary|Crash while selecting |[PATCH] Crash while |scrolling text |selecting scrolling text --- Comment #1 from Charles Samuels --- Backtrace with debug information: ``` #7 0x061ea0d8 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x061e126d in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x049784b3 in std::vector, std::allocator > >::_M_range_check (this=0xd830870, __n=37) at /usr/include/c++/12/bits/stl_vector.h:1153 #10 0x04975109 in std::vector, std::allocator > >::at ( this=0xd830870, __n=37) at /usr/include/c++/12/bits/stl_vector.h:1175 #11 0x0496f6d6 in Konsole::Screen::setSelectionEnd (this=0xd830860, x=50, y=10036, trimTrailingWhitespace=false) at /home/charles/tmp/konsole-22.12.3/src/Screen.cpp:1815 #12 0x049816b6 in Konsole::ScreenWindow::setSelectionEnd (this=0x1d198b00, column=50, line=35, trimTrailingWhitespace=false) at /home/charles/tmp/konsole-22.12.3/src/ScreenWindow.cpp:145 #13 0x04a0f77b in Konsole::TerminalDisplay::extendSelection (this=0x1cf8f5c0, position=...) at /home/charles/tmp/konsole-22.12.3/src/terminalDisplay/TerminalDisplay.cpp:1469 #14 0x04a0e91e in Konsole::TerminalDisplay::mouseMoveEvent (this=0x1cf8f5c0, ev=0x1ffefff180) at /home/charles/tmp/konsole-22.12.3/src/terminalDisplay/TerminalDisplay.cpp:1306 #15 0x04f45db8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x04a16641 in Konsole::TerminalDisplay::event (this=0x1cf8f5c0, event=0x1ffefff180) at /home/charles/tmp/konsole-22.12.3/src/terminalDisplay/TerminalDisplay.cpp:2877 #17 0x04f03fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x04f0c552 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x05e9f6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x04f0a65e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x04f5ebd8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x04f61f60 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 ``` Fix: ``` --- Screen.cpp.old 2023-09-29 09:26:08.557129473 -0700 +++ Screen.cpp 2023-09-29 09:26:12.257118245 -0700 @@ -1809,7 +1809,7 @@ } // HACK: do not crash. -if (_screenLines.size() < line) { +if (_screenLines.size() <= line) { line = _screenLines.size() - 1; } const int length = _screenLines.at(line).count(); ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #63 from Charles Dennett --- Will what is planned for KDE 6 take into account multiple monitors and multiple virtual desktops so that apps start in the desired monitor/virtual desktop? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374113] Reversed Touchpad Scrolling has no effect in Testing Area on ubuntu + kubuntu-desktop
https://bugs.kde.org/show_bug.cgi?id=374113 --- Comment #3 from Charles Bushong --- Feel free to close this bug. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 459938] xdg-desktop-portal-kde error message appears from Journalctl log every reboot or re-login
https://bugs.kde.org/show_bug.cgi?id=459938 Charles Dennett changed: What|Removed |Added CC||cdenn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 --- Comment #62 from Charles Dennett --- Looks like the problem still exists in Plasma 5.26.3. I'm running that on Fedora 37. -- You are receiving this mail because: You are watching all bug changes.