[KScreen] [Bug 484808] Unresponsive black screen when disconnecting external monitor with laptop lid closed
https://bugs.kde.org/show_bug.cgi?id=484808 Leonardo changed: What|Removed |Added CC||rodon...@gmail.com --- Comment #1 from Leonardo --- Same problem on my side, also on tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483429] New: Screen freezes with Adaptive Sync enabled
https://bugs.kde.org/show_bug.cgi?id=483429 Bug ID: 483429 Summary: Screen freezes with Adaptive Sync enabled Classification: Plasma Product: kwin Version: 6.0.2 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leona...@neumann.dev.br Target Milestone: --- Created attachment 167093 --> https://bugs.kde.org/attachment.cgi?id=167093=edit Output from glxinfo SUMMARY The screen seems to freeze during certain animations with Adaptive Sync / VRR enabled. For instance, when opening the launcher, the screen freezes for a few seconds until I interact with the menu or other screen update happens, like taking a screenshot. STEPS TO REPRODUCE 1. Enable Adaptive Sync (set to always); 2. Open the application launcher. OBSERVED RESULT The animation freezes until any screen update happens. EXPECTED RESULT The animation finishes in time, without any noticeable increase in frame times. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 OS: NixOS 24.05 (Wakari) ADDITIONAL INFORMATION Output from glxinfo attached. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481242] Digital Signature Tool
https://bugs.kde.org/show_bug.cgi?id=481242 --- Comment #4 from Leonardo Uberti Gerage --- (In reply to Albert Astals Cid from comment #3) > Arg, the pt_BR version is outdated and doesn't have the additional section, > please see the one in english > https://docs.kde.org/stable5/en/okular/okular/signatures. > html#adding_digital_signatures >From what I understand, and I ask you to correct me if I'm wrong, the documentation indicated, in the English language, seems to be aimed at Linux distributions, since the manual mentions that Okular will look for the certificates, firstly, in the current Firefox folder (Note: I'm using Firefox from the Microsoft Store), secondly, in the system's "/etc/pki/nssdb" directory and, thirdly and finally, in the current user's "$HOME/ .pki/nssdb" folder. I tried configure Okular to look for certificates in the Firefox profile directory, but the directory shown in Firefox itself (via Microsoft Store), in the "about:profiles" tab, does not exist, not even hidden, in the "AppData\Roaming" folder (example: "C:Users\User\AppData\Roaming\Mozilla\Firefox\Profiles\profile.default-release"). Therefore, at this point, based on the manual indicated, it appears that Okular is not looking for the certificates in the directories/registries specific to Windows 11, just as it does on systems built on the Linux kernel. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481242] Digital Signature Tool
https://bugs.kde.org/show_bug.cgi?id=481242 --- Comment #2 from Leonardo Uberti Gerage --- (In reply to Albert Astals Cid from comment #1) > Have you read the manual? Yes, but the opened man page only shows when a PDF document containing an embedded digital signature is opened, a function that works perfectly (https://docs.kde.org/stable5/pt_BR/okular/okular/signatures.html ). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481242] New: Digital Signature Tool
https://bugs.kde.org/show_bug.cgi?id=481242 Bug ID: 481242 Summary: Digital Signature Tool Classification: Applications Product: okular Version: 23.08.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: leonardouger...@outlook.com Target Milestone: --- Created attachment 165760 --> https://bugs.kde.org/attachment.cgi?id=165760=edit Screenshot SUMMARY The "Digital Sign" function, present in the "Tools" menu, does not work in Okular installed via Microsoft Store, even with my token, respective drivers, and my digital certificate regularly installed on the machine. STEPS TO REPRODUCE 1. I insert my physical cryptographic key into any USB port on my computer. 2. I open any file in PDF format and Okular opens normally. 2. At the top of Okular, I select the "Tools" menu and then click on the "Digitally Sign..." function. OBSERVED RESULT Okular returns the following error message: "There are no available signing certificates. For more information, please see the section about Adding Digital Signatures in the manual.". EXPECTED RESULT That Okular recognizes the token and its respective digital certificate installed on the machine, allowing you to digitally sign documents in PDF format or any other supported format. SOFTWARE/OS VERSIONS Windows: Windows 11 23H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Version 5.109.0. Qt Version: Version 5.15.10 (compiled with 5.15.10). ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476325] New: Blur glitches appearing again in wayland with Nvidia GPU
https://bugs.kde.org/show_bug.cgi?id=476325 Bug ID: 476325 Summary: Blur glitches appearing again in wayland with Nvidia GPU Classification: Plasma Product: kwin Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leo0...@hotmail.com Target Milestone: --- Created attachment 162727 --> https://bugs.kde.org/attachment.cgi?id=162727=edit Picture of the glitch (whenever i try and use spectacle, the glitch disappears) 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 *** noticing the same glitch as Bug 455526, marked as solved. not finding anyhing remotely recent about this glitch, decided to open a report. these glitches do not appear using Xorg. STEPS TO REPRODUCE 1. Open konsole 2. Enable blur in Konsole 3. Move cursor over konsole window OBSERVED RESULT Blur effect glitches, notably a dark square following cursor movement. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Nvidia 1080 GPU, i can reproduce it on blurred dolphin as well. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 473688] New: Plasma-systemmonitor crashes and closes when switching tabs
https://bugs.kde.org/show_bug.cgi?id=473688
Bug ID: 473688
Summary: Plasma-systemmonitor crashes and closes when switching
tabs
Classification: Applications
Product: plasma-systemmonitor
Version: 5.27.7
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: leonardodasilva1...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
Target Milestone: ---
Application: plasma-systemmonitor (5.27.7)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.11-zen2-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
I found a bug in the plasma-systemmonitor that makes it crash and close when I
switch tabs within the application. Here are the details of the bug:
Environment: I am using Arch Linux with the latest version of
plasma-systemmonitor.
Steps to reproduce the bug:
Open the plasma-systemmonitor and select a tab, for example, Processes.
Switch to another tab, for example, Applications, History or Processes. Any of
these tabs makes the application break.
Expected result: The plasma-systemmonitor should show the tab that I selected
and continue working normally.
Actual result: The plasma-systemmonitor crashes and closes by itself, without
showing any error message.
Note: I tried to delete the cache files of the plasma-systemmonitor, but that
did not solve the problem.
The crash can be reproduced every time.
-- Backtrace:
Application: Monitor do sistema (plasma-systemmonitor), signal: Segmentation
fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 QListData::size() const (this=0x55b61628b9d8, this=) at
/usr/include/qt/QtCore/qlist.h:115
#7 QList::count() const (this=0x55b61628b9d8) at
/usr/include/qt/QtCore/qlist.h:359
#8 QQuickTransform::~QQuickTransform() (this=0x55b61628c0f8, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:156
#9 0x7f06217977b3 in QQuickMatrix4x4::~QQuickMatrix4x4() (this=, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquicktranslate.cpp:512
#10 QQuickPinchHandler::~QQuickPinchHandler() (this=0x55b61628bff0,
this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/handlers/qquickpinchhandler_p.h:62
#11 QQuickPinchHandler::~QQuickPinchHandler() (this=0x55b61628bff0,
this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/handlers/qquickpinchhandler_p.h:62
#12 0x7f06217a5af6 in QAccessibleQuickItem::role() const
(this=0x55b6162a2c20) at
../../include/QtQuick/../../../qtdeclarative/src/quick/items/qquickitem.h:468
#13 0x7f0622f4aa59 in AtSpiAdaptor::pathForInterface(QAccessibleInterface*)
const [clone .isra.0] (interface=0x55b6162a2c20, this=) at
../../../platformsupport/linuxaccessibility/atspiadaptor.cpp:1586
#14 0x7f0622f38312 in
AtSpiAdaptor::notifyStateChange(QAccessibleInterface*, QString const&, int)
(this=0x55b615561b60, interface=, state=..., value=1) at
../../../platformsupport/linuxaccessibility/atspiadaptor.cpp:878
#15 0x7f0622f398e6 in AtSpiAdaptor::notify(QAccessibleEvent*)
(this=0x55b615561b60, event=) at
../../../platformsupport/linuxaccessibility/atspiadaptor.cpp:903
#16 0x7f062163323c in QQuickItemPrivate::setEffectiveVisibleRecur(bool)
(this=this@entry=0x55b61628c0b0, newEffectiveVisible=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:6121
#17 0x7f06216370f3 in QQuickItem::setParentItem(QQuickItem*)
(this=0x55b61628bff0, parentItem=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:2737
#18 0x7f062162c4a2 in QQuickItem::~QQuickItem()
(this=this@entry=0x55b61628bff0, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:2335
#19 0x7f0620d562c7 in QQuickControl::~QQuickControl()
(this=this@entry=0x55b61628bff0, this=) at
/usr/src/debug/qt5-quickcontrols2/qtquickcontrols2/src/quicktemplates2/qquickcontrol.cpp:1002
#20 0x7f06107b200b in
QQmlPrivate::QQmlElement::~QQmlElement() (this=0x55b61628bff0,
this=) at /usr/include/qt/QtQml/qqmlprivate.h:144
#21 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55b61628bff0, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#22 0x7f0620c5209f in
QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*,
QQmlTableInstanceModel::DestructionMode) (this=,
modelItem=0x55b616292b10, mode=QQmlTableInstanceModel::Immediate) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmltableinstancemodel.cpp:245
#23 0x7f0620c7b0e2 in std::function::operator()(QQmlDelegateModelItem*) const
(__args#0=0x55b616292b10, this=0x7ffce7951300) at
/usr/include/c++/13.1.1/bits/std_function.h:591
#24
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 --- Comment #19 from Leonardo Cardoso Barreto --- (In reply to Leonardo Cardoso Barreto from comment #18) > I must add that this happens in FFXIV, apex, and CSGO. All games running wayland does this now. Gamescope is a workaround, but the newest version makes this happens again, downgrade to 3.11.51 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 Leonardo Cardoso Barreto changed: What|Removed |Added CC||lec...@hotmail.com --- Comment #18 from Leonardo Cardoso Barreto --- I must add that this happens in FFXIV, apex, and CSGO. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 473168] KDevelop fails to debug a project because it doesn't detect correctly the gdb debugger version
https://bugs.kde.org/show_bug.cgi?id=473168 Leonardo Berti changed: What|Removed |Added Summary|KDevelop fail to debug a|KDevelop fails to debug a |project because it doesn't |project because it doesn't |detect correctly the|detect correctly the gdb |versione of the fdb |debugger version |debugger| -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 473168] New: KDevelop fail to debug a project because it doesn't detect correctly the versione of the fdb debugger
https://bugs.kde.org/show_bug.cgi?id=473168 Bug ID: 473168 Summary: KDevelop fail to debug a project because it doesn't detect correctly the versione of the fdb debugger Classification: Applications Product: kdevelop Version: 5.5.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: leonardo.be...@ymail.com CC: niko.s...@gmail.com Target Milestone: --- Created attachment 160841 --> https://bugs.kde.org/attachment.cgi?id=160841=edit error screenshot SUMMARY When I try to debug a project I get a misleading error message: You need gdb 7.0.0 or higher. You are using: GNU gdb (Ubuntu 10.2-0ubuntu1~20.04~1) 10.2 It tells me that I need gdb 7.0.0 or higher but I have the gdb 10.2 STEPS TO REPRODUCE 1. Create a new C++ project 2. Create a new launch configuration with the default profile 3. Build the project 4. Click the Debug button OBSERVED RESULT The debugger fails to start and the above message is shown SOFTWARE/OS VERSIONS OS: NAME="Linux Mint" VERSION="20.1 (Ulyssa)" ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME="Linux Mint 20.1" VERSION_ID="20.1" ADDITIONAL INFORMATION KDevelop version 5.5.0 KDE Frameworks 5.68.0 Qt 5.12.8 (compiled with5.12.8) windows system xcb -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 468473] New: erro no aplicativo quando troca abas
https://bugs.kde.org/show_bug.cgi?id=468473 Bug ID: 468473 Summary: erro no aplicativo quando troca abas Classification: Applications Product: plasma-systemmonitor Version: 5.26.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: leonn...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.26.0) (Compiled from sources) Qt Version: 5.15.7 Frameworks Version: 5.99.0 Operating System: Linux 5.15.0-69-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.26 DrKonqi: 5.26.0 [KCrashBackend] -- Information about the crash: ao trocar para aba de aplicativos o sistema fecha do nada erro encontrado em ksystemlog é erro no xcb e não estou usando wayland The crash can be reproduced every time. -- Backtrace: Application: Monitor do sistema (plasma-systemmonitor), signal: Segmentation fault [New LWP 8812] [New LWP 8814] [New LWP 8815] [New LWP 8816] [New LWP 8817] [New LWP 8819] [New LWP 8827] [New LWP 8828] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fcb8c96799f in __GI___poll (fds=0x7ffe35149cb8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fcb894be940 (LWP 8810))] Thread 9 (Thread 0x7fcb5cab2700 (LWP 8828)): #0 0x7fcb822b98a4 in drmIoctl () from /lib/x86_64-linux-gnu/libdrm.so.2 #1 0x7fcb822bc760 in drmCommandWriteRead () from /lib/x86_64-linux-gnu/libdrm.so.2 #2 0x7fcb800913af in amdgpu_cs_query_reset_state2 () from /lib/x86_64-linux-gnu/libdrm_amdgpu.so.1 #3 0x7fcb80a55db4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fcb80a3ca78 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fcb80a3a0a5 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #6 0x7fcb8025f460 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #7 0x7fcb8019a323 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #8 0x7fcb8235a9c4 in glLabelObjectEXT () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0 #9 0x7fcb8234c135 in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0 #10 0x7fcb8233bee8 in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0 #11 0x7fcb891c1e8a in QGLXContext::swapBuffers (this=0x5593b9ff6920, surface=0x5593ba452690) at qglxintegration.cpp:637 #12 0x7fcb8d3a8011 in QOpenGLContext::swapBuffers (this=0x5593b9dab300, surface=) at kernel/qopenglcontext.cpp:1121 #13 0x7fcb8315cabc in QSGRenderThread::syncAndRender (this=0x5593b9ff0ee0, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:869 #14 0x7fcb83160877 in QSGRenderThread::run (this=0x5593b9ff0ee0) at scenegraph/qsgthreadedrenderloop.cpp:1042 #15 0x7fcb8ccf75a3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fcb8c09 in start_thread (arg=) at pthread_create.c:477 #17 0x7fcb8c974133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fcb5d2b3700 (LWP 8827)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5593ba67e2ac) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5593ba67e258, cond=0x5593ba67e280) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5593ba67e280, mutex=0x5593ba67e258) at pthread_cond_wait.c:647 #3 0x7fcb801f2b9d in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fcb801a533b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fcb801f2abb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #6 0x7fcb8c09 in start_thread (arg=) at pthread_create.c:477 #7 0x7fcb8c974133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fcb6e7fc700 (LWP 8819)): #0 0x7fcb8c96799f in __GI___poll (fds=0x7fcb58004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcb8b72f36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcb8b72f4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcb8cf38f9b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcb8cedcbab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcb8ccf63a2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcb8e66a929 in QQmlThreadPrivate::run (this=0x5593b9c22840) at qml/ftw/qqmlthread.cpp:155 #7 0x7fcb8ccf75a3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fcb8c09 in start_thread (arg=) at pthread_create.c:477 #9 0x7fcb8c974133 in clone () at
[konsole] [Bug 463654] New: konsole crash
https://bugs.kde.org/show_bug.cgi?id=463654 Bug ID: 463654 Summary: konsole crash Classification: Applications Product: konsole Version: 22.08.2 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: violanteleona...@libero.it Target Milestone: --- Application: konsole (22.08.2) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-28-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: La konsole si è chiusa inaspettatamente mentre era in corso la copia di alcune cartelle contenenti macchine virtuali vmware The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7f74a223e574 in Konsole::ProcessInfo::isValid() const () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #5 0x7f74a22c9e54 in Konsole::Session::getUrl() () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #6 0x7f74a22cec8d in Konsole::SessionController::url() const () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #7 0x7f74a22e40c9 in Konsole::SessionController::showDisplayContextMenu(QPoint const&) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #8 0x7f74a0cf36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f74a222ea69 in Konsole::TerminalDisplay::configureRequest(QPoint const&) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #10 0x7f74a22a84b2 in Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #11 0x7f74a19aeb48 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f74a196bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f74a19745b2 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f74a0cbae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f74a19726b2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f74a19c80dc in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f74a19cb4a0 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f74a196bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f74a0cbae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f74a11426fd in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #21 0x7f74a111663c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7f749acfa78e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #23 0x7f749f072569 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f749f0c73c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f749f06fd20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f74a0d14aea in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f74a0cb97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f74a0cc1c2a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x560bd29e47c1 in ?? () #30 0x7f74a0223510 in __libc_start_call_main (main=main@entry=0x560bd29e2ce0, argc=argc@entry=1, argv=argv@entry=0x7ffc86f3b548) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f74a02235c9 in __libc_start_main_impl (main=0x560bd29e2ce0, argc=1, argv=0x7ffc86f3b548, init=, fini=, rtld_fini=, stack_end=0x7ffc86f3b538) at ../csu/libc-start.c:381 #32 0x560bd29e5055 in ?? () [Inferior 1 (process 10441) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457761] I can't modify and save - past date
https://bugs.kde.org/show_bug.cgi?id=457761 Leonardo Bergamo changed: What|Removed |Added Summary|I can't modify and save |I can't modify and save - ||past date --- Comment #2 from Leonardo Bergamo --- I was trying modify to past date, this is not possible? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457761] I can't modify and save
https://bugs.kde.org/show_bug.cgi?id=457761 --- Comment #1 from Leonardo Bergamo --- I was trying modify to past date, this is not possible? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457761] I can't modify and save
https://bugs.kde.org/show_bug.cgi?id=457761 Leonardo Bergamo changed: What|Removed |Added CC||leobergam...@yahoo.com.br -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457761] New: I can't modify and save
https://bugs.kde.org/show_bug.cgi?id=457761 Bug ID: 457761 Summary: I can't modify and save Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: database Assignee: kmymoney-de...@kde.org Reporter: leobergam...@yahoo.com.br Target Milestone: --- I cannot modify a release and save. I do a release of expense and save. After I try modify a date and save, and it's not possible. I get the question if it's to save but the system doesn't save. Sorry my english. 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 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.
[krita] [Bug 442287] Replace fill layer's properties dialog color button with a color picker with instant preview
https://bugs.kde.org/show_bug.cgi?id=442287 --- Comment #2 from Leonardo --- When I created this ticket I was unaware of how poorly implemented fill layers were. See https://krita-artists.org/t/fill-layers-appear-poorly-optimized/34387 In summary: a single color fill layer ALWAYS performs worse memory-wise than a normal layer filled with a flat color. They can't be used like firealpacas's or Clip Studio Paint's 8 bit layers at all. Regardless, I mean, just look at the dialog. The "color" tab shows one color button to open a dialog to pick the color. The other tabs, which are far more complex, have all the settings on the tab. Like "pattern" shows a list of patterns for you to click on. You don't have a "select pattern" button that opens a dialog for you to choose a pattern. So I still think there you should be able to pick a color straight from the layer's properties without opening a second dialog, though iirc it was made this way because some users preferred the system color picker, so if it were changed it would have to have a convenient way to select the color on the layer dialog PLUS a button that works like currently to open the system color pick dialog for users who need it for some reason. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 453422] New: MIC - Inaudible or robotic voice. - Volume booster and channel adjustment
https://bugs.kde.org/show_bug.cgi?id=453422 Bug ID: 453422 Summary: MIC - Inaudible or robotic voice. - Volume booster and channel adjustment Product: plasma-pa Version: 5.24.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leonei...@gmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- MIC Inaudible or robotic voice. Volume booster and channel adjustment *** Nowadays using the microphone for online meetings has become essential. I had so much trouble adjusting my mic and I almost gave up on using Linux. Several people have the same problem and it happens in other distributions as well. Before an online meeting I test the microphone, but in the middle of the meeting it stops working. I noticed that the problem is in the auto volume adjustment. The solution I found was: 1 - (make the microphone sound audible and clear) install win7 mixer widget. has the option to adjust the left and right channels. For me the mic sound is good with 50% right and 15% left. 2 - Stop automatic volume adjustment - kate /usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf kate /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf Under “[Element Internal Mic Boost]” set “volume” to “zero”. Under “[Element Int Mic Boost]” set “volume” to “zero”. Under “[Element Mic Boost]” set “volume” to “zero”. My suggestion is that Plasma has the options to adjust the channel and stop the automatic volume adjustment. *** SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-39-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 136 Menory at b132 (64-bit, non-prefetchable) [size=16K] Menory at b130 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd hda intel Kernel modules: snd hda intel, snd soc skl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452731] Duckstation QT application stuck on top left when trying to go fullscreen
https://bugs.kde.org/show_bug.cgi?id=452731 --- Comment #4 from Leonardo --- (In reply to Vlad Zahorodnii from comment #2) > Based on the log, there are a few fullscreen windows created. KWin responds > with a correct configure event, which has 1366x768 size, but duckstation > attaches a buffer of size 640x480 for whatever reason. Do you know if it > forces some mode? For example, many video games allow you to choose > resolution, if there's such a setting, can you try changing it? Duckstation comes with the capability to render the internal resolution of a game at different levels x2,x3,etc (original playstation was 640x224)... for example x3 is for 720p, x5 for 1080p. As far as i know it's only rendering the game and not changing the resolution of the window by the same size. Just to be sure i used 1x (so upscaling disabled) but it's still the same problem. The strange thing is that for a brief moment goes fullscreen correctly, then goes stuck on the top left. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452731] Duckstation QT application stuck on top left when trying to go fullscreen
https://bugs.kde.org/show_bug.cgi?id=452731 --- Comment #1 from Leonardo --- Created attachment 148221 --> https://bugs.kde.org/attachment.cgi?id=148221=edit Screenshow showing the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452731] New: Duckstation QT application stuck on top left when trying to go fullscreen
https://bugs.kde.org/show_bug.cgi?id=452731 Bug ID: 452731 Summary: Duckstation QT application stuck on top left when trying to go fullscreen Product: kwin Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kinetoc...@hotmail.it Target Milestone: --- Created attachment 148220 --> https://bugs.kde.org/attachment.cgi?id=148220=edit Log of WAYLAND_DEBUG=1 SUMMARY Duckstation is a PS1 emulator that has a problem when goes fullscreen on a Wayland session. If you try to go fullscreen, the windows is put on the top left of my desktop, stuck there. STEPS TO REPRODUCE 1. Open Duckstation, Options->General Settings->Render to Main Window->Disabled (it's another problem with the program, if you try to render to main window, it's invisible, you can hear only the sound). 2. Download this homebrew [https://archive.org/details/magic-castle-2021-01-feb] (it's a community project, not a copyrighted game, so free to distribute). Unpack it where you want. 3. System->Start File->Point to it. 4. Try to go fullscreen with Alt+Enter. OBSERVED RESULT Windows stuck on top left. EXPECTED RESULT Fullscreen. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 (21.3.8) (Laptop monitor at 1366x768) ADDITIONAL INFORMATION Duckstation is built from AUR (https://aur.archlinux.org/packages/duckstation-git) and it uses QT 5.15.3. It worked around November 2021 but then stopped working. There is a VERY similar bug https://bugs.kde.org/show_bug.cgi?id=444962 but Duckstation doesn't use SDL for window management. I'll add a Wayland Debug log as requested on IRC, it's simply taken by starting a game and going in and out fullscreen 3-4 times. I've used this from terminal env WAYLAND_DEBUG=1 duckstation-qt > logfile 2>&1 . -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 284031] Copy-To-Clipboard in Okular does not work for some unicode characters
https://bugs.kde.org/show_bug.cgi?id=284031 Leonardo Michel changed: What|Removed |Added Platform|Microsoft Windows |Neon Packages CC||leonardo.michel.dom@gmail.c ||om OS|Microsoft Windows |Linux --- Comment #3 from Leonardo Michel --- Suddenly appears with unknown characters on a specific file made on WPS Office and merged with another via "ilovepdf", but weirdly it appears correctly on MS Edge's own integrated PDF Reader -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #96 from Leonardo --- Well, the bug can be closed 10 years after. A long journey! KDE 5.24 has released the overview functionality. In my opinion the thumbnails are a little small. And there is no option to hide krunner or the virtual desktops. But it works pretty well. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446556] New: Scale Image to New Size doesn't scale Transform Mask position.
https://bugs.kde.org/show_bug.cgi?id=446556 Bug ID: 446556 Summary: Scale Image to New Size doesn't scale Transform Mask position. Product: krita Version: 4.4.8 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: odraenco...@gmail.com Target Milestone: --- SUMMARY Using Image -> Scale Image to a New Size... doesn't scale transform masks properly, resulting in the scaled up/down image looking different form the original image. In particular, the position of a transform mask isn't scaled. STEPS TO REPRODUCE 1. Create a new image with 200px x 100px size. 2. Draw something on the left side. 3. Add a transform mask to the layer and select it. 4. Select the transform tool and move the mask so that the drawing ends up in the right side of the canvas. 5. Click image -> scale image to new size, set the size 100px x 50px, and click OK. OBSERVED RESULT The canvas is now blank. The drawing disappears. EXPECTED RESULT The drawing should be on the right side of the scaled down image, just like it was on the right side in the original image. ADDITIONAL INFORMATION In the original image with 200px of width, the left side ranged from 0px to 100px, and the right side 100px to 200px in the horizontal axis. The drawing was in the 0-100px range, the left side. We moved it to the 100-200px range, the right side. When the image was scaled down to 100px width, the position of the transform remained in the 100-200px range, which is now OUTSIDE of the canvas, hence why it disappeared (if we scaled up to 1000px, it would end up in the left side instead). That is, the position wasn't scaled at all. The expected result would have been for it to be scaled down to the 25-50px range. The current behavior is what you'd expect from Resize Canvas, not from Scale Image to New Size. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446223] New: Can't Paste a Clone Layer
https://bugs.kde.org/show_bug.cgi?id=446223 Bug ID: 446223 Summary: Can't Paste a Clone Layer Product: krita Version: 4.4.8 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: odraenco...@gmail.com Target Milestone: --- SUMMARY Attempting to cut-paste or copy-paste a Clone Layer automatically converts it into a Paint Layer. This means it's not possible to cut a Clone Layer from somewhere in the stack and paste it somewhere else to quickly move it. The only way to move a Clone Layer is by dragging it slowly through the entire stack. STEPS TO REPRODUCE 1. Create a Paint Layer and draw something on it. 2. Select it on the Layers docker and create a Clone Layer from it. 3. Select the Clone Layer on the Layers docker and press Ctrl-X or Ctrl+C, alternatively, right click on the Clone Layer and click Cut Layer or Copy Layer. 4. Press Ctrl+V or right click on the stack and click Paste Layer. OBSERVED RESULT What's pasted is a Paint Layer. You can edit it, and editing the first Paint Layer you created doesn't update what has been pasted. EXPECTED RESULT A Clone Layer should have been pasted, so that the Clone Layer you cut effectively just moved around, or that you've created a second clone of the first Paint Layer. SOFTWARE/OS VERSIONS Windows: 7 ADDITIONAL INFORMATION I haven't tested all layer types, but cut-pasting a Fill Layer works as expected. If the Clone Layer is in a Group and you cut-paste the Group, the whole Group is pasted as-is and the Clone Layer isn't converted. Given the above, converting the Clone Layer to a Paint Layer is inconsistent with how layer pasting normally works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439156] Diagonal lines produce aliasing at certain zoom level
https://bugs.kde.org/show_bug.cgi?id=439156 --- Comment #9 from Leonardo --- (In reply to Halla Rempt from comment #8) >It's more complicated than that, because the zoom levels aren't hard-coded, >but calculated >KoZoomAction::Private::generateSliderZoomLevels(). Is this the code for it? https://invent.kde.org/graphics/krita/-/blob/master/libs/widgets/KoZoomAction.cpp#L63 It seems to be already hard-coded. QList zoomLevels; qreal defaultZoomStep = sqrt(2.0); zoomLevels << 0.25 / 2.0; zoomLevels << 0.25 / 1.5; zoomLevels << 0.25; zoomLevels << 1.0 / 3.0; zoomLevels << 0.5; zoomLevels << 2.0 / 3.0; zoomLevels << 1.0; See, that's 100%, 67% (2/3), 50% (0.5), 33% (1/3), 25% (0.25), 17% (0.25 / 1.5) and 13% (0.25 / 2.0). For some reason the first zoom levels smaller than 100% are hard-coded, but the ones larger than 100% aren't hard-coded. You could fix this issue by simply adding something like: zoomLevels << 1.5; zoomLevels << 2.0; zoomLevels << 3.0; zoomLevels << 4.0; zoomLevels << 5.5; zoomLevels << 8.0; I say this is an UX issue because without using whole numbers for zoom levels the size of the pixels on display becomes unequal in unpredictable ways. It isn't much of an issue with high zoom levels like 550%, but with 283%, for example, some pixels are scaled into 3x3 squares, while others become 2x2 squares, and others become 2x3 or 3x2 rectangles. Consequently, if you draw a line, some pixels of the line appear bigger than others randomly, so some parts of the line appear thicker randomly, which gives the jagged appearance. This jagged appearance isn't expected by the user, so they'll think the brush isn't drawing right, or krita isn't anti-aliasing right, etc., until they figure out the zoom is weird in krita. Probably unnecessary, but for zoom levels higher than 800% one could adjust the calculated levels to round to the nearest 50%, e.g. by changing this: zoomLevels.append(zoom); To something like this: zoomLevels.append(whatever_round_to_nearest_integer_is_called_in_cpp(zoom * 2) / 2.0); In fact if you did this you wouldn't even need to hard code the zoom levels since 141%, 283%, and 566% round to the 150%, 300%, and 550% anyway. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439156] Diagonal lines produce aliasing at certain zoom level
https://bugs.kde.org/show_bug.cgi?id=439156 Leonardo changed: What|Removed |Added CC||odraenco...@gmail.com --- Comment #7 from Leonardo --- The problem is that Krita has weird zoom levels: 100%, 141%, 200%, 283%, 400%, 566%, 800% Normally, to avoid this exact issue, you'd use mainly integer zoom levels. For reference, zoom levels in other graphics software: SAI: 100%, 150%, 200%, 300%, 400%, 500%, 600%, 800%. Fire Alpaca: 100%, 150%, 200%, 300%, 400%, 600%, 800%. MyPaint: 100%, 150%, 200%, 300%, 400%, 550%, 800%. Photoshop: 100%, 200%, 300%, 400%, 500%, 600%, 700%, 800%. Gimp: 100%, 150%, 200%, 300%, 400%, 550%, 800%. iirc Krita's weird zoom levels come from KDE. They probably aren't an issue in other KDE software, but because Krita is a drawing software it becomes an issue here. I suggest changing Krita's zoom levels to match MyPaint: 100%, 150%, 200%, 300%, 400%, 550%, 800%, 1100%, 1600%, 2300%, 3200%, 4500%, 6400%. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442287] New: Replace fill layer's properties dialog color button with a color picker with instant preview
https://bugs.kde.org/show_bug.cgi?id=442287 Bug ID: 442287 Summary: Replace fill layer's properties dialog color button with a color picker with instant preview Product: krita Version: 4.4.7 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: odraenco...@gmail.com Target Milestone: --- SUMMARY It would be useful if Krita's fill layers were more like Fire Alpaca's 8 bit layers. Like this: https://i.imgur.com/45hO0E1.mp4 PROBLEM Currently, to change a fill layer's color in Krita the following steps are necessary: 1. open the layer's properties dialog. 2. click on the color button in the dialog. 3. click on a color. 4. click OK, now you can see the color changed. 5. click OK again, now the color is set. Fire Alpaca/Medibang have 8 bit and 1 bit paint layers that work in a way similar to Krita/Photoshop's fill layers, except that they're not designed as a bucket fill that applies automatically, but instead as a paint layer that can only have one color (they don't fill the canvas by default, and black is opaque instead of white). These 8 bit layers are useful for artists with workflows that make use of multiple single-color paint layers (typically cel-shaded style, with one base layer for color, and multiply/addition/etc. blend modes on top for shading). The "fill" layers in Krita/Photoshop are designed backwards for this use case, but one could still use them the same way as the 8 bit paint layers: you'd just need to delete the mask after creating the layer and draw with white instead of black. So long as you don't have a brush that uses a multiply blend mode, for example, it should work the same way. The problem is that the way color change is designed in Krita makes them practically unusable for this use case. Without this type of layer, artists with this workflow use a normal paint layer, and to change color they lock the layer's alpha, select a new color, and use a shortcut (such as CTRL+F) to fill. While this is a bit of a hassle, you can quickly click color, CTRL+F, click color, CTRL+F, click color, CTRL+F, until you find the color that you want. In photoshop and Fire Alpaca, the 8 bit/fill layer's properties dialog has a color picker immediately accessible. With just one click you can change the color and preview the result, so it's much easier to search for the color you want. In Krita, you can't preview the result as quickly. There's a color button instead of a picker, and the color button opens a dialog where you choose the color. Then you have to click OK to preview the color changed. If the color doesn't look good, you'll have to open the dialog again, click a new color, click ok again, and repeat. The process to change the color in a layer type designed to have only a single color ends up being more complicated than the same process in the general-purpose paint layer type that's designed to have any color. This isn't a problem if the fill layer is supposed to be just an automated bucket fill tool that you barely touch, similar to a filter layer, but I think with some small changes like this one these fill layers could also be used as single-color paint layers, which would be useful for artists with the aforementioned workflow. PROPOSED SOLUTION Replace the color button with a color picker, and make picking a color preview the change instantly. ADDITIONAL INFORMATION Bug 412928 proposes to change the way the brush's color picker works when fill layers are selected, which would equally make the color-change process faster. I don't think this should be done. First, tools should work seamlessly independent of layer. Selecting the gray color makes the brush paint gray, and it just happens in mask/fill layers gray means half-transparent. If you changed this, there would be no way to paint "gray" in a fill layer. I don't remember for sure, but I think there was a brush setting to make it replace the layer's alpha with the brush's opacity instead of adding alpha. You could use this instead, but you would need to create a custom brush just for fill layers. Second, if selecting the color for the brush changes the layer's color, then conversely selecting a fill layer should change the brush's color to match. This would mean the brush color changes without you changing it. If you were painting green on one layer, and selected a blue fill layer, when you go back to the previous layer, is your brush green or blue? In either case it would be very confusing. Instead it makes more sense that the same color (white in Krita's case) always mean opaque, so you don't need to watch the brush's color when changing layers. One solution could be if clicking on the fill layer thumbnail (which shows its solid color) in the layers docker
[krita] [Bug 412928] Use color selector dockers for fill color when a fill layer is selected.
https://bugs.kde.org/show_bug.cgi?id=412928 Leonardo changed: What|Removed |Added CC||odraenco...@gmail.com --- Comment #6 from Leonardo --- (In reply to Halla Rempt from comment #4) > I think would agree with Ian: it makes more sense to select the color for > the fill layer than the level of grayness for the brush, given that opacity > also works fine for editing the fill layer. > > I have to say, I have never seen anyone use fill layers like this, though :-) I disagree. The color selector is supposed to select the color of the brush tool, and tools are supposed to work seamlessly regardless of layer type. If you select the gray color, you can make any paint layer gray, and any mask 50% alpha, and you can make a fill layer's mask 50% alpha. if you changed this only for fill layers, then you would need to create a custom brush to force 50% alpha just for fill layers. You wouldn't be able to use the same brush you use in a normal layer or in a transparency mask layer. The use cases are limited but I believe painting with a gray brush should make the alpha 50%. It's how it works in Fire Alpaca/Medibang, for example. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 343703] Cannot set the trust level of a signature to ultimate
https://bugs.kde.org/show_bug.cgi?id=343703 Leonardo changed: What|Removed |Added CC||lcfior...@gmail.com --- Comment #3 from Leonardo --- Hello everybody, I use an Actalis S/MIME free e-mail certificate for corporate purposes with Mozilla Thunderbird. I recently launched Kleopatra to check details of this certificate by double-checking my e-mail address as shown in the certificate trust levels shown below: >Actalis Authentication Root CA >Actalis Client Authentication CA G3 >mycorporatelo...@myserver.com Whenever I do this a pop-up Windows shows the signature details as expected, and it shows 3 columns with my corporate e-mail address, my name and its corresponding trust level. Here comes my concern, though, because Kleopatra shows this certificate as invalid, and I wonder why this happens. I know this is not a Kleopatra bug, but I'd like to know what it means and how to change this "invalid" status to a "trusted" status, if possible. Thank you all, Leonardo. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439498] Plasma crashes when flash drive is unmounted and removed
https://bugs.kde.org/show_bug.cgi?id=439498 --- Comment #5 from Leonardo Izzi --- Created attachment 140847 --> https://bugs.kde.org/attachment.cgi?id=140847=edit New crash information added by DrKonqi plasmashell (5.22.4) using Qt 5.15.2 I was unmounting an external HDD from Dolphin and suddently Plasma crashed. -- Backtrace (Reduced): #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/11/bits/atomic_base.h:836 #7 std::atomic::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/11/atomic:570 #8 QAtomicOps::loadRelaxed (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #9 QBasicAtomicPointer::loadRelaxed (this=) at /usr/include/qt5/QtCore/qbasicatomic.h:248 #10 QQmlNotifierEndpoint::connect (this=this@entry=0x564684666320, source=0x5646845ab670, sourceSignal=46, engine=0x0, doNotify=doNotify@entry=true) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qml/qml/qqmlnotifier.cpp:122 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439498] Plasma crashes when flash drive is unmounted and removed
https://bugs.kde.org/show_bug.cgi?id=439498 Leonardo Izzi changed: What|Removed |Added CC||leonardoizz...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #87 from Leonardo --- (In reply to Nate Graham from comment #84) > The new QML-based Present Windows effect has been merged for Plasma 5.23, > and it does not dim the inactive/un-hovered windows. :) See > https://invent.kde.org/plasma/kwin/commit/ > 6132329c2c48e22d48a37e7ec40028f6faefa1fd > > Good things come to those who wait. :) Now, would be great some rude people saying thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440938] New: Krita crashes after resizing brush in a specific way
https://bugs.kde.org/show_bug.cgi?id=440938 Bug ID: 440938 Summary: Krita crashes after resizing brush in a specific way Product: krita Version: 4.4.7 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: odraenco...@gmail.com Target Milestone: --- SUMMARY If a brush is resized inside the brush editor and outside of it too much, repeatedly, Krita crashes. This is due to the masked brush's brush tip diameter becoming too large. Krita always generates a mask for the masked brush's brush tip diameter when loading the brush, even if the masked brush's "brush tip" entry in the brush editor is toggled off. The diameter of the masked brush is supposed to scale proportionally to the diameter of the actual brush. For example, if the brush diameter is 2px, and the masked brush diameter is 3px, and you use the slider in the toolbar to resize the brush to 10px, making it 5x bigger, then the masked brush diameter also gets 5x bigger, becoming 15px. Using hotkeys, shift dragging, or using the diameter slider in the toolbar all have this effect of resizing the masked brush diameter proportionally. This occurs EVEN if the masked brush "brush tip" entry is toggled off. However, setting the brush diameter in the brush editor doesn't affect the masked brush diameter. As a consequence, if you start with a brush that has 1px/1px brush/masked brush diameters, and resize it with the toolbar to 1000px/1000px, then open the brush editor and reset the brush diameter to 1px, you end up with 1px/1000px brush/masked brush diameters. This time, if you use the toolbar to resize it to 1000px, you should end up with 1000px/100px brush/masked brush diameters. Repeat this enough times and the masked brush diameter overflows. This occurs even if the user isn't using the masked brush feature at all, completely without his knowledge. It's also possible that you end up saving the brush with an extremely large masked brush size, so it will lag to load whens witching to the custom brush, and you'll have no idea it's because of the masked brush diameter since you didn't even toggle the masked brush setting on. STEPS TO REPRODUCE 1. select the b)_Basic-5_Size, open the brush editor, click save new brush preset and call it "test" or something. 2. select the test brush, open the brush editor, set the brush diameter to 1px. 3. leave the brush editor, use the diameter slider in the toolbar, hotkeys, or shift drag to resize the brush to 1000px. 4. open the brush editor, set the brush diameter to 1px. 5. leave the brush editor, resize the brush to 1000px again. 6. repeat 4, 5 a couple of times. Alternatively: 6. open the brush editor. Click overwrite brush. 7. select any other brush, e.g. a)_Eraser_Circle. 8. select the test brush. OBSERVED RESULT Krita crashed. Alternatively: there's a noticeable delay switching to the saved custom brush. It gets more noticeable the worse your computer is. EXPECTED RESULT No crashing. No delay. SOFTWARE/OS VERSIONS Windows: 7 Qt Version: 5.14.11 ADDITIONAL INFORMATION The same problem was reported in bug 423572. Even if the crash issue is addressed, there's also the issue of custom brushes saved with enormous mask diameters that the user is unaware of appearing to lag or sometimes make Krita hang when switched to. I think it makes more sense to not change the masked brush diameter if it's a brush that isn't making use of masked brushes in first place. I don't know why Krita appears to take a while generating a mask for the masked brush even when the masked brush is disabled. I guess normally the masked brush is so small it's a negligible delay? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #70 from Leonardo --- (In reply to Nate Graham from comment #69) > Heh, as it turns out, a QML-based replacement is actually in active > development over here: > https://invent.kde.org/plasma/kwin/-/merge_requests/1177. > > So this may get fixed to *everyone's* satisfaction sooner rather than later. > :) Let's see how that plays out. If it looks like it's getting stuck, I can > nudge it if need be. > > I know we're asked for a lot of patience, but I think the end is in sight > soon here. :) Thanks dude! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #68 from Leonardo --- (In reply to David Edmundson from comment #67) > >I just don't wanna make him waste time. > > Then please don't. > > We have decided we want an outline or some other clear visual > representation. There is a lot of active work going into making long term > solutions to do things properly. Ok, no problem. gonna wait (In reply to David Edmundson from comment #67) > >I just don't wanna make him waste time. > > Then please don't. > > We have decided we want an outline or some other clear visual > representation. There is a lot of active work going into making long term > solutions to do things properly. Okay, no problem. Let's wait -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #66 from Leonardo --- (In reply to Nate Graham from comment #59) > (In reply to Szczepan Hołyszewski from comment #56) > Hmm, that's true. I hadn't thought about that. Thanks for bringing it up. > Maybe it would be okay after all. @Nate Talking about that project: https://invent.kde.org/plasma/kwin/-/merge_requests/885 STARTING 1 - And if it starts with all thumbnails not showing effect(not dimming) it gets easy and very fast to find your target thumbnail. (as already happens in the mentioned project). 2 - And if it starts with all thubnails not showing it's names and icons. THEN Now if "on mouse over" the SELECTED thumbnail: 1 - Dims 2 - Shows the icon 3- Shows the window name 4 - Increases it's size (as already happens in the mentioned project) I'm talking to the dev and if you say yes he will work on it. I just don't wanna make him waste time. Is it enought to accept the fix and the merge request? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #65 from Leonardo --- (In reply to Manuel Geißer from comment #64) > @hvm @Leonardo > Apparently there is a little misunderstanding... Ok, got. So maybe we could hope a 10 years birthday gift. I mean a fix from KDE. <<<<<<<<>>>>>>>> -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #63 from Leonardo --- (In reply to Manuel Geißer from comment #58) > Therefore, I'll look into building Present Windows myself, the version I > like. I hope this procedure is documented and does not involve compiling the > whole KWin. > > > Thanks Szczepan for your continued commitment to this issue. Please, don't forget to share. Or why not help this project and share? (It seems to be almost done.) https://invent.kde.org/plasma/kwin/-/merge_requests/885 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #50 from Leonardo --- I think insults are not the best way. But clearly after this "https://invent.kde.org/plasma/kwin/-/merge_requests/885; we will not have our "dream feature" and there are forces acting against. It blows my mind just because is a hight demanded feature. Huge frustration here! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438753] Settings crash after trying to delete an example shortcut
https://bugs.kde.org/show_bug.cgi?id=438753 Leonardo Gerling changed: What|Removed |Added CC||leonardodag123...@gmail.com --- Comment #2 from Leonardo Gerling --- (In reply to Nate Graham from comment #1) > #5 0x7f4fc9305177 in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #6 0x7f4fc930664a in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #7 0x7f4fc93053ce in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #8 0x7f4fc92e7e06 in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #9 0x7f4fc92e7f23 in () at /usr/lib/qt/plugins/kcm_hotkeys.so > > Please install debug symbols for the khotkeys package and attach a new > backtrace. :) See also > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports I already tried to do that (I am on artix, so my distro doesn't have debug packages with symbols)(In reply to Nate Graham from comment #1) > #5 0x7f4fc9305177 in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #6 0x7f4fc930664a in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #7 0x7f4fc93053ce in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #8 0x7f4fc92e7e06 in () at /usr/lib/qt/plugins/kcm_hotkeys.so > #9 0x7f4fc92e7f23 in () at /usr/lib/qt/plugins/kcm_hotkeys.so > > Please install debug symbols for the khotkeys package and attach a new > backtrace. :) See also > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Sorry for the late reply, but I am on an arch-based system (artix) and I really tried everything to install the symbols, but nothing works. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 438697] google-chrome not open xdg-desktop-portal-kde
https://bugs.kde.org/show_bug.cgi?id=438697 --- Comment #4 from Leonardo Lins --- thanks a lot for response my question i am send this question in the chromiun bugs report thanks a lot man. kde this is a very powerfull desktop i will see my eyes the victory kde desktop about windows Operation system. Em qua., 16 de jun. de 2021 às 02:29, Jan Grulich escreveu: > https://bugs.kde.org/show_bug.cgi?id=438697 > > Jan Grulich changed: > >What|Removed |Added > > > CC||jgrul...@redhat.com > Resolution|--- |NOT A BUG > Status|REPORTED|RESOLVED > > --- Comment #3 from Jan Grulich --- > Why this is an issue in xdg-desktop-portal-kde? We have no way how to force > Chrome to use xdp-kde from our side. I also don't think it should actually > use > it. If you want this bug to be fixed, you have to open an issue for > Chromium > instead. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 438697] google-chrome not open xdg-desktop-portal-kde
https://bugs.kde.org/show_bug.cgi?id=438697 --- Comment #2 from Leonardo Lins --- Created attachment 139353 --> https://bugs.kde.org/attachment.cgi?id=139353=edit xdg-desktop-portal-kde is Ok save network shares -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 438697] google-chrome not open xdg-desktop-portal-kde
https://bugs.kde.org/show_bug.cgi?id=438697 --- Comment #1 from Leonardo Lins --- Created attachment 139352 --> https://bugs.kde.org/attachment.cgi?id=139352=edit kdialog erro not save network shares -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 438697] New: google-chrome not open xdg-desktop-portal-kde
https://bugs.kde.org/show_bug.cgi?id=438697 Bug ID: 438697 Summary: google-chrome not open xdg-desktop-portal-kde Product: xdg-desktop-portal-kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: leonn...@gmail.com Target Milestone: --- Created attachment 139351 --> https://bugs.kde.org/attachment.cgi?id=139351=edit Kdialog not save files in network shares SUMMARY STEPS TO REPRODUCE 1. Open google-chrome 2. Start save As 3. kdialog is running and not xdg-desktop-portal-kde OBSERVED RESULT kdialog does not offer network save function and is used instead of xdg-desktop-portal-kde I have tried everything including creating symbolic link but I was unsuccessful EXPECTED RESULT this problem can be solved simply by opening xdg-desktop-portal-kde just like firefox does and everything works perfectly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kde-Neon 5.22 (available in About System) KDE Plasma Version: 5.22 KDE Frameworks Version: 5.83 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 402042] Difference Chrome sources all display as "Chrome"
https://bugs.kde.org/show_bug.cgi?id=402042 Leonardo Lins changed: What|Removed |Added CC||leonn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 269744] Dolphin (and google chrome) crashes when dragging .jpg files from dolphin to (anonymous) Chrome tab bar.
https://bugs.kde.org/show_bug.cgi?id=269744 Leonardo Lins changed: What|Removed |Added CC||leonn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 419874] Folder selection does not work in file picker dialog
https://bugs.kde.org/show_bug.cgi?id=419874 Leonardo Lins changed: What|Removed |Added CC||leonn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #37 from Leonardo --- (In reply to Nate Graham from comment #34) > (In reply to Szczepan Hołyszewski from comment #31) > > We literally want the code to STOP doing something that it currently > > ACTIVELY DOES. It is an extraordinary claim requiring extraordinary evidence > > to say that STOPPING doing something is any more complicated than, well, > > stopping. > Yes, that's the easy part, but then there's not enough of a visual highlight > for the hover or selected window, and implementing that proves to be > challenging. If we don't implement that, then the work is only half-finished > and we will get bug reports about *that*. :) > > > (In reply to Leonardo from comment #33) > > Nate, how about give support to Parachute project? It is an excellent > > project that fills the gap. Maybe put in KDE incubator. Is stable but there > > are few bugs and could be a KDE project. The project owner agree about > > incubator. I could put him in touch. > I reached out to the author last year and he said he didn't consider the > code to be in a good enough state to upstream. e told me about your interest. Now the software is more mature and stable. He changed his mind and is read for your idea. We tried with the brazilian KDE community but they are too resistant to new suggestions. Could you try again? Or if you prefer, he could reach you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #33 from Leonardo --- Yes, Just comment the code. Nate, how about give support to Parachute project? It is an excellent project that fills the gap. Maybe put in KDE incubator. Is stable but there are few bugs and could be a KDE project. The project owner agree about incubator. I could put him in touch. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 437465] kdialog erro
https://bugs.kde.org/show_bug.cgi?id=437465 --- Comment #1 from Leonardo Lins --- Created attachment 138644 --> https://bugs.kde.org/attachment.cgi?id=138644=edit xdg-desktop-portal-kde is great xdg-desktop-portal-kde works in firefox web-browser but dont works chrome,opera,microsoft-edge use kdialog please helpe this. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 437465] New: kdialog erro
https://bugs.kde.org/show_bug.cgi?id=437465 Bug ID: 437465 Summary: kdialog erro Product: kdialog Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: leonn...@gmail.com Target Milestone: --- Created attachment 138643 --> https://bugs.kde.org/attachment.cgi?id=138643=edit kdialog error save network address SUMMARY STEPS TO REPRODUCE 1. error save network address 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.
[kdialog] [Bug 437465] kdialog erro
https://bugs.kde.org/show_bug.cgi?id=437465 --- Comment #2 from Leonardo Lins --- i would like to apologize again this is my first post move to the right place and let me know where to post, i would just like to point out that kde desktop and the best linux desktop i just use it gnome is also good but kde has everything to be the desktop used in the world in all aspects. congratulations on the work of the kde team and the whole community long life peace and health to all. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 436733] New: Duplicating widget
https://bugs.kde.org/show_bug.cgi?id=436733 Bug ID: 436733 Summary: Duplicating widget Product: kdeplasma-addons Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- It would be great if we could duplicate panels when using 2 or more screens. It's annoying when working on second screen with a different panel. Maybe widgets too. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435740] New: Brightness/volume indicator flying around
https://bugs.kde.org/show_bug.cgi?id=435740 Bug ID: 435740 Summary: Brightness/volume indicator flying around Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- The new Brightness/volume indicator is beautiful and less intrusive. Great job! It's good not being in the middle of the screen like it was. But it's position should be more at the bottom for stetic reasons and will get LESS intrusive. (or have an option to choose its position) It's like its lost. When using two screens it pops in the screen 1 or 2. I can't understand its logic to choose which screen it will pop. Looks like it tries to follow the mouse but isn't consistent. Would be great if it follows the mouse, poping in the screen which the mouse cursor is. Thanks! Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-71-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 434853] Battery indicator for Bluetooth headset only shows up occasionally
https://bugs.kde.org/show_bug.cgi?id=434853 Leonardo changed: What|Removed |Added CC||leonei...@gmail.com --- Comment #2 from Leonardo --- Bluetooth Battery indicator? Where? I am running Plasma 5.21.3 and i have never seen the battery indicator. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427728] Minimum window height is too tall and does not scale with scale factor
https://bugs.kde.org/show_bug.cgi?id=427728 --- Comment #10 from Leonardo --- When i need a very small window i open the kWrite. See the comparison of KWrite and Kate attached. Both width are limited by tab name. I opened the bug but i think it is not too important. For me it can be closed. Its up to you. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427728] Minimum window height is too tall and does not scale with scale factor
https://bugs.kde.org/show_bug.cgi?id=427728 --- Comment #9 from Leonardo --- Created attachment 137339 --> https://bugs.kde.org/attachment.cgi?id=137339=edit Kate x KWrite -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434850] search
https://bugs.kde.org/show_bug.cgi?id=434850 Leonardo changed: What|Removed |Added Keywords||usability --- Comment #1 from Leonardo --- I realize that, when doing the search process, the program cannot find phrases that have words that are on different lines in the text. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434850] New: search
https://bugs.kde.org/show_bug.cgi?id=434850 Bug ID: 434850 Summary: search Product: okular Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: fede...@vivaldi.net Target Milestone: --- I realize that, when doing the search process, the program cannot find phrases that have words that are on different lines in the text. 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.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #30 from Leonardo --- (In reply to Szczepan Hołyszewski from comment #29) You are a warrior! Almost ten years fighting for what you want. Szczepan Hołyszewski 2012-07-12 20:55:01 UTC -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433695] Can't set the statistics refresh rate of system monitor widgets.
https://bugs.kde.org/show_bug.cgi?id=433695 Leonardo changed: What|Removed |Added CC||turbos...@pm.me --- Comment #1 from Leonardo --- Since Plasma 5.21 this seems to have been increased indeed and the widgets are very active, up to a point where they are quite annoying/disturbing for me. I would also appreciate an option to reduce this frequency or at least to have the previous frequency back -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #28 from Leonardo --- Great workaround. Problem solved! Just try this: https://store.kde.org/p/1370195/ More details here: https://github.com/tcorreabr/Parachute -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #27 from Leonardo --- (In reply to Nate Graham from comment #26) > There is every intention to change this, but it's simply not so simple due > to the very old fashioned code involved. Someone submitted a merge request > about a year ago, but abandoned it after being unable to address issues > found during testing. If this were an easy thing to do, it would have > already been done. Your patience is appreciated. :) Yes Nate we understand. Sometimes the things is harder than it look. But I have found a bug that eventually/maybe can help. "A good bug" When we have only one workspace the thumbnails dont dim. Of course i don't know if it is enough. So works perfectly with only one workspace. Easy to use. We appreciate the KDE team effort -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 411900] Tracking activity
https://bugs.kde.org/show_bug.cgi?id=411900 Leonardo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Leonardo --- I tried to write a software to track activities and it is working pretty well. I am closing this "request" Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432214] New: qdbus commands not working many times
https://bugs.kde.org/show_bug.cgi?id=432214 Bug ID: 432214 Summary: qdbus commands not working many times Product: kwin Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- SUMMARY Some times after turn on my laptop i can't execute some qdbus commands. It happens randomly. For example, right now i am trying keyboard shortcut, terminal command or widget action with some qdbus commands. Happens even after fresh installation. Not a problem specifically from my actual installation. NOT working right now: qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut Expose qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut ShowDesktopGrid qdbus org.kde.kglobalaccel /component/kwin invokeShortcut "Walk Through Windows" Working right now: qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "decrease_volume" qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "increase_volume" I have to restart my laptop one or two times to get everything working again. STEPS TO REPRODUCE 1. Execute some qdbus on terminal, keyboard shortcut or from some widget. 2. As it is randomly i need some instructions to generate some report to attach when it happens. 3. THANKS! SOperating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #24 from Leonardo --- Is there a workaround? Looks like it is too easy to fix. I'm not a C++ developer so i can't fix it as shown here: https://www.youtube.com/watch?v=QEHC43zMIMc Could someone attach some script or Solution here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431314] New: Usability Issue - Grid
https://bugs.kde.org/show_bug.cgi?id=431314 Bug ID: 431314 Summary: Usability Issue - Grid Product: kwin Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- Created attachment 134662 --> https://bugs.kde.org/attachment.cgi?id=134662=edit Windows Grid too dark SUMMARY When using window and desktop grid it is not easy to fast identify the window you want to pick. There is a effect that dims the thumbnail window. So if you use black theme or screen NOT too bright you will take 3 or 4 seconds to identify the windows you want to pick. For usabilitie purpose, i think this efect should not be present above the thumbnail windows. Should be removed. For example gnome grid is easy to pick your windows. There is no dim effect. I use desktop grip hundreds time every day and i spend some minutes every day to pick the choosen windows. STEPS TO REPRODUCE 1. Open a lot of windows 2. Run qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut Expose 3. Run qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut Expose OBSERVED RESULT Window thubnail is too dark. Not easy to fast find some window EXPECTED RESULT Brighter windows to fast find some window. Just remove the dim effect SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-36-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 THANKS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431313] New: Usability Issue - Grid
https://bugs.kde.org/show_bug.cgi?id=431313 Bug ID: 431313 Summary: Usability Issue - Grid Product: kwin Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- Created attachment 134661 --> https://bugs.kde.org/attachment.cgi?id=134661=edit Windows Grid too dark SUMMARY When using window and desktop grid it is not easy to fast identify the window you want to pick. There is a effect that dims the thumbnail window. So if you use black theme or screen NOT too bright you will take 3 or 4 seconds to identify the windows you want to pick. For usabilitie purpose, i think this efect should not be present above the thumbnail windows. Should be removed. For example gnome grid is easy to pick your windows. There is no dim effect. I use desktop grip hundreds time every day and i spend some minutes every day to pick the choosen windows. STEPS TO REPRODUCE 1. Open a lot of windows 2. Run qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut Expose 3. Run qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut Expose OBSERVED RESULT Window thubnail is too dark. Not easy to fast find some window EXPECTED RESULT Brighter windows to fast find some window. Just remove the dim effect SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-36-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 THANKS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411897] Option to configure what happens when scrolling on a screen edge
https://bugs.kde.org/show_bug.cgi?id=411897 Leonardo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411897] Option to configure what happens when scrolling on a screen edge
https://bugs.kde.org/show_bug.cgi?id=411897 --- Comment #2 from Leonardo --- Yes, maybe you are right. For me vollume is very usefull but there are few ways to have this feature using third softwares. Thanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 430459] New: Issue connecting to public Hotspot
https://bugs.kde.org/show_bug.cgi?id=430459 Bug ID: 430459 Summary: Issue connecting to public Hotspot Product: frameworks-networkmanager-qt Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: leonei...@gmail.com CC: lamar...@kde.org, lukas.ti...@merlin.cz Target Milestone: --- SUMMARY Of course public hotspot is an open network. I mean no password is required. But you have to authenticate on a secondary window. When you connect to public hotspot with Android or gnome(for example) it opens the secondary window for authentication. Generally is a facebook or twitter page you have to visit before to get acess to the internet. The problem is that Plasma doesn't open this authentication window. It's a kind confused to gain access to the internet using plasma on public hotspot. STEPS TO REPRODUCE 1. Connect to a public hotspot that you have to authenticate on a secondary window. 2. 3. OBSERVED RESULT The secondary window doesn't show up and you can't connect to the internet easily. EXPECTED RESULT The secondary window have to opens to authenticate as it happens on Android, Gnome, Windows etc... SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-33-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Thanks -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 411900] Tracking activity
https://bugs.kde.org/show_bug.cgi?id=411900 --- Comment #3 from Leonardo --- I have already tried doing some script but unsuccessful. The log wasn't that accurate. My knowledge is limited. It was something like that: qdbus org.kde.ActivityManager /ActivityManager/Activities SetCurrentActivity 20cddbba-d1b1-4e73-af18-8d84ef7980eb | python3 /home/username/.local/bin/utt hello | python3 /home/username/.local/bin/utt add ActivityNameLog -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 428086] New: Desktop widget positions and sizes getting messed up
https://bugs.kde.org/show_bug.cgi?id=428086 Bug ID: 428086 Summary: Desktop widget positions and sizes getting messed up Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: turbos...@pm.me Target Milestone: --- SUMMARY The widget size and positions are getting messed up when using screen extension, when the laptop's resolution (and screen) is smaller than the monitor that's being used to extend to. The laptop resolution is 720p, the monitor 1080p After booting, the widgets are messed up (or some gone) because they were positioned for the bigger monitor, but they are being repositioned every time for the small laptop monitor. This results me in having to reposition them almost every time after a reboot. STEPS TO REPRODUCE 1. position the widgets (hardware activity, ram, etc) for the big monitor and use extend to right screen extension (or even other modes) 2. reboot and login 3. see the widgets being moved, dissappeared OBSERVED RESULT as described EXPECTED RESULT keep the same position for the widgets, but just resize them to be smaller and fit in the same positions on the smaller resolution. But as soon as the bigger monitor is used, use the original sizes (and positions) SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE KDE (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: latest I guess Qt Version: ADDITIONAL INFORMATION Could be a duplicate of Bug 360478 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410845] Profile picture name error
https://bugs.kde.org/show_bug.cgi?id=410845 Leonardo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419757] Laptop HDMI screen can't keep as primary screen.
https://bugs.kde.org/show_bug.cgi?id=419757 Leonardo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427895] New: Volume control
https://bugs.kde.org/show_bug.cgi?id=427895 Bug ID: 427895 Summary: Volume control Product: systemsettings Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- I know plasma 5.20 comes with less obtrusive "on-screen displays". I would like to suggest some way to configure the display time. For example, a way to configure the "volume display" time when changing volume. For me 400ms is enough. Today the default time can't be changed and is about 2 seconds. if i'm not wrong it looks to be very simple to implement. Thanks for the great job! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427728] Window size
https://bugs.kde.org/show_bug.cgi?id=427728 --- Comment #2 from Leonardo --- i mean, i understand that the notepad concept is to have a fast, simple and flexible tool. i am the kind of user that uses notepad all the day. to take fast notes, annotate big things, to fast count things and of course codding. i am sure i'm not the only user that miss that "resize versatility". just fast drag to any corner and take notes from a bigger window. thanks -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427728] New: Window size
https://bugs.kde.org/show_bug.cgi?id=427728 Bug ID: 427728 Summary: Window size Product: kate Version: 20.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- Created attachment 132369 --> https://bugs.kde.org/attachment.cgi?id=132369=edit resizing kate SUMMARY Cant resize Kate window less than: W169 x H301 it is useful having a notepad window as a "single line height" or as a "single col width". Just see the attached image. Lost too much space. STEPS TO REPRODUCE 1. Just try to resize kate less than W169 x H301 OBSERVED RESULT There is a limit to resize. Kate window still big EXPECTED RESULT Resize less than width:169 or height:301 SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-23-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424561] Widgets don't have option to delay process
https://bugs.kde.org/show_bug.cgi?id=424561 Leonardo changed: What|Removed |Added Resolution|WAITINGFORINFO |INTENTIONAL Status|NEEDSINFO |RESOLVED --- Comment #7 from Leonardo --- Alright, in that case it should be fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422937] Widgets are broken; Widget graphs are unintuitive; Widget legends are unaligned
https://bugs.kde.org/show_bug.cgi?id=422937 --- Comment #2 from Leonardo --- Created attachment 130329 --> https://bugs.kde.org/attachment.cgi?id=130329=edit Pie chart is displaying wrong data I've added an attachment to also show the Pie chat, how it's displaying the graph and percentage wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422937] Widgets are broken; Widget graphs are unintuitive; Widget legends are unaligned
https://bugs.kde.org/show_bug.cgi?id=422937 Leonardo changed: What|Removed |Added CC||aard...@posteo.be --- Comment #1 from Leonardo --- I agree that the display of the legend is not optimal. It's shortened unnecessarily when there's enough horizontal space to show all the text. This is especially the case with the Network Activity and Memory Usage widgets -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424561] Widgets don't have option to delay process
https://bugs.kde.org/show_bug.cgi?id=424561 --- Comment #4 from Leonardo --- It was useful for me to reduce the load on the machine and because it wasn't necessary for me to have such frequent updates of the statistics. David Edmundson schreef op 23 juli 2020 11:05:53 CEST: >https://bugs.kde.org/show_bug.cgi?id=424561 > >David Edmundson changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||k...@davidedmundson.co.uk > >--- Comment #3 from David Edmundson --- >Yes it changed. > >Can you expand on why it was useful to set an interval? > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 --- Comment #27 from Leonardo --- Yes!!!, it is working!!! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421575] New: Paths in kis_paintoppresets.blacklist containing backward slashes are ignored
https://bugs.kde.org/show_bug.cgi?id=421575 Bug ID: 421575 Summary: Paths in kis_paintoppresets.blacklist containing backward slashes are ignored Product: krita Version: 4.3.0-beta1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tagging Assignee: krita-bugs-n...@kde.org Reporter: odraenco...@gmail.com Target Milestone: --- SUMMARY Paths in kis_paintoppresets.blacklist use / (forward slash) as directory separator, except that SOMETIMES the last directory separator becomes a \ (backward slash) instead. When this happens, Krita fails at blacklisting the path and overwritten brush presets, backups, etc. show up in the brush list. I'm not familiar with the code, but it's possible that somewhere Krita checks if a preset filepath matches the blacklist entries EXACTLY (e.g. filepath_a == filepath_b) and that fails, or some function to resolve paths into their canonical versions fails at resolving backward slashes on Windows, or something like that. Anyway, the simplest fix is to stop using backward slashes in blacklisted paths, or to replace "paintoppresets\" with "paintoppresets/" before comparing paths. STEPS TO REPRODUCE 1. Select the brush b)_Basic-2_Opacity. 2. On the brush settings editor, click "Save new brush preset..." and save as "Test". 3. Select the brush Test. 4. On the brush settings editor, change a setting. E.g. click on the "size" checkbox to change size with pressure. 5. Click "overwrite brush". OBSERVED RESULT ~/AppData/Roaming/krita/paintoppresets\Test_backup_2020-05-15-140459.kpp The "Test" preset shows twice on Krita because the backup isn't blacklisted. EXPECTED RESULT ~/AppData/Roaming/krita/paintoppresets/Test_backup_2020-05-15-140459.kpp The "Test" preset shows once on Krita as the backup is properly blacklisted. SOFTWARE/OS VERSIONS Windows 7 (64bit) Krita 4.3.0-beta1 (git 5149f63) ADDITIONAL INFORMATION Manually editing kis_paintoppresets.blacklist with Notepad++ and replacing \ with / fixes the issue. It seems that SOMETIMES blacklisted paths are added correctly, with /, while other times they were added incorrectly, with \. This suggests that the bug only happens under certain circumstances, and that the code to add entries to the blacklist has two different ways to generate paths, one with /, another with \, which alternate sometimes for some reason. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420987] New: Pedir para abrir
https://bugs.kde.org/show_bug.cgi?id=420987 Bug ID: 420987 Summary: Pedir para abrir Product: konqueror Version: 5.0.97 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: hlo...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.6.8-300.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (Thirty Two) -- Information about the crash: Pedir para abrir um website www.nostv.pt e ele dar a oportunidade de abrir em outros web browsers. Rejeitei e ele fechou inesperadamente. Por sinal... Porque o widgets "NAVEGADOR" não nos dá a oportinudade de escolher o browser que queremos, e é obrigado a utilizar o Konqueror? -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa3ecac4840 (LWP 4267))] Thread 6 (Thread 0x7fa3d6ffd700 (LWP 4276)): #0 0x7fa3ef844e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa3dda88d7b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7fa3dda8884b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7fa3ef83e432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fa3f2bba9d3 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fa3d77fe700 (LWP 4275)): #0 0x7fa3ef844e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa3dda88d7b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7fa3dda8884b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7fa3ef83e432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fa3f2bba9d3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fa3d7fff700 (LWP 4274)): #0 0x7fa3ef844e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa3dda88d7b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7fa3dda8884b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7fa3ef83e432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fa3f2bba9d3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fa3dcba4700 (LWP 4273)): #0 0x7fa3ef844e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa3dda88d7b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7fa3dda8884b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7fa3ef83e432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fa3f2bba9d3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fa3decb6700 (LWP 4271)): #0 0x7fa3f0f089a6 in socketNotifierSourceCheck(_GSource*) () from /lib64/libQt5Core.so.5 #1 0x7fa3eef0d4f9 in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7fa3eef0da95 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #3 0x7fa3eef0dc23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7fa3f0f08c23 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fa3f0ebc21b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fa3f0d30577 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7fa3f16bf4da in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7fa3f0d31846 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7fa3ef83e432 in start_thread () from /lib64/libpthread.so.0 #10 0x7fa3f2bba9d3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fa3ecac4840 (LWP 4267)): [KCrash Handler] #6 0x7fa3f2cc4c7a in KonqRun::foundMimeType(QString const&) [clone .cold] () from /lib64/libkdeinit5_konqueror.so #7 0x7fa3f25fecb6 in KRun::mimeTypeDetermined(QString const&) () from /lib64/libKF5KIOWidgets.so.5 #8 0x7fa3f279b23a in KParts::BrowserRun::slotBrowserMimetype(KIO::Job*, QString const&) () from /lib64/libKF5Parts.so.5 #9 0x7fa3f0ee3a60 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7fa3f249754b in KIO::TransferJob::mimetype(KIO::Job*, QString const&) () from /lib64/libKF5KIOCore.so.5 #11 0x7fa3f0ee3a60 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7fa3f2476c49 in KIO::SlaveInterface::mimeType(QString const&) () from /lib64/libKF5KIOCore.so.5 #13 0x7fa3f2478dbd in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #14 0x7fa3f247734d in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #15 0x7fa3f247ad32 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #16 0x7fa3f0ee3a60 in QMetaObject::activate(QObject*, int,
[KAccounts] [Bug 420878] Problems in KDE-Plasma Online Accounts in Fedora 32
https://bugs.kde.org/show_bug.cgi?id=420878 --- Comment #2 from Hugo Leonardo R. D. Lopes --- (In reply to Christoph Feck from comment #1) > Please don't add random people to the CC list, just because you believe they > are maintaining KDE software in Fedora. > > If you want attention of Fedora maintainers, user their bug tracker. I'm sorry for this! I believed that by sending more people the problem would be solved faster. I read some articles and I already understand how it works. Best regards and I'm sorry. Hugo Lopes. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 420878] Problems in KDE-Plasma Online Accounts in Fedora 32
https://bugs.kde.org/show_bug.cgi?id=420878 Hugo Leonardo R. D. Lopes changed: What|Removed |Added CC||64bit_fed...@comcast.net, ||aol...@redhat.com, ||b...@redhat.de, ||fedora.ru...@gmail.com, ||fedora...@bigorange.org, ||hlo...@gmail.com, ||jwrdego...@fedoraproject.or ||g, kde-bugzi...@plasma.cx, ||mschwe...@fedoraproject.org ||, ||nuell@mnredhat7.lethbridgec ||ollege.ab.ca, ||pga...@redhat.com, ||reveal@bungiesoft.org, ||yna...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 420878] New: Problems in KDE-Plasma Online Accounts in Fedora 32
https://bugs.kde.org/show_bug.cgi?id=420878 Bug ID: 420878 Summary: Problems in KDE-Plasma Online Accounts in Fedora 32 Product: KAccounts Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: hlo...@gmail.com Target Milestone: --- Created attachment 128088 --> https://bugs.kde.org/attachment.cgi?id=128088=edit Short video from Online Accounts < 1min. Problems in KDE-Plasma Online Accounts in Fedora 32 x86_64 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 420803] partitionmanager breaks ext4 partition
https://bugs.kde.org/show_bug.cgi?id=420803 --- Comment #4 from Leonardo --- (In reply to Andrius Štikonas from comment #3) > (In reply to Leonardo from comment #2) > > It didn't even took a second to output me a superblock error. > > > Hmm, so maybe it was found during initial file system check. Otherwise it > would have taken much longer (shrinking needs to move data). > > I just tried the steps you mentioned, it worked fine for me. > (everything was done in the right order File sytem check, shrink fs resize > partitition, fs check again) Well... I just tried in virtualbox here too and It did work fine :/ Probably It was already borked then... sorry about it -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 420803] partitionmanager breaks ext4 partition
https://bugs.kde.org/show_bug.cgi?id=420803 --- Comment #2 from Leonardo --- (In reply to Andrius Štikonas from comment #1) > What actually gave you an error about wrong superblocks. Was it KDE > Partition Manager while running after resize file system check? I don't get the second part of the answer. It was this: https://linux-cdn.softpedia.com/screenshots/KDE-Partition-Manager_1.png It didn't even took a second to output me a superblock error. > Were you resizing mounted partition? It should only be possible to grow ext4 > mounted partition not shrink... (Unless you do something illegal like open > partitionmanager, mount that partition using external tools, so that KPM is > not aware that partition is mounted and then shrink it) I resized it offline (used opensuse tw liveusb to do it) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 420803] New: partitionmanager breaks ext4 partition
https://bugs.kde.org/show_bug.cgi?id=420803 Bug ID: 420803 Summary: partitionmanager breaks ext4 partition Product: partitionmanager Version: 3.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: leonardosilvateod...@hotmail.com Target Milestone: --- SUMMARY I used kde partitionmanager today to resize my root ext4 partition on opensuse tw and It gave me an error saying something was wrong with superblocks, I thought It was fine, left the software and went back to my root (I was on opensuse tw kde liveusb) and It dropped me on a emergency shell. I went back to opensuse tw kde liveusb and figured out that It shrunk the partition (the same process cfdisk does) instead of check the filesystem firstly (with e2fsck), actually resizing (with resize2fs) and then use cfdisk to finalize. STEPS TO REPRODUCE 1. open partitionmanager 2. select the partition you want to shrink 3. right click it and select "resize/move" 4. put a value on "free space after", apply SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse tumbleweed (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 420803] partitionmanager breaks ext4 partition
https://bugs.kde.org/show_bug.cgi?id=420803 Leonardo changed: What|Removed |Added CC||leonardosilvateodoro@hotmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419757] New: Laptop HDMI screen can't keep as primary screen.
https://bugs.kde.org/show_bug.cgi?id=419757 Bug ID: 419757 Summary: Laptop HDMI screen can't keep as primary screen. Product: plasmashell Version: 5.18.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: leonei...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Using a second HDMI screen the KDE plasma can't remember the main screen after some actions. STEPS TO REPRODUCE 1. Connect a HDMI screen to the Notebook and set to use both screens to extended. 2. Open Screen configuration manager 3. Clck on HDMI screen image so select it. 4. Check primary/main checkbox. 5. Now the HDMI is working as primary screen and the "notebook screen" as secondary. 6. ... 6. Now using the keyboard shortcut(fn) select to use only one screen(any one). 7. Now again with fn shortcut set to use both screens to extended. OBSERVED RESULT The primary/main screen is not the HDMI screen previouly configured. It is like plasma had lost the configuration. EXPECTED RESULT Plasma should remember the primary screen always. One time the HDMI screen is the primary it should be every time we turn on the laptop or connect the screen. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-42-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7,7 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417662] Cant choose widget version
https://bugs.kde.org/show_bug.cgi?id=417662 Leonardo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Leonardo --- Just a mistake -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417662] New: Cant choose widget version
https://bugs.kde.org/show_bug.cgi?id=417662 Bug ID: 417662 Summary: Cant choose widget version Product: plasmashell Version: 5.18.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: leonei...@gmail.com Target Milestone: 1.0 SUMMARY Widget window doesnt allow to choose the widget version to install. Some widgets provide 2 or more versions. Try Win7 Show Desktop https://store.kde.org/p/1100895 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 5.18 backport (available in About System) KDE Plasma Version: 5.18 KDE Frameworks Version: 5.67 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417660] New: Cant install widget as file
https://bugs.kde.org/show_bug.cgi?id=417660 Bug ID: 417660 Summary: Cant install widget as file Product: plasmashell Version: 5.18.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: leonei...@gmail.com Target Milestone: 1.0 SUMMARY New Plasma 5.18 doesnt allow installing widget from local file. The main widget window closes by itself. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 5.18 backport (available in About System) KDE Plasma Version: 5.18 KDE Frameworks Version: 5.67 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416079] New: teamviewer 13 fecha
https://bugs.kde.org/show_bug.cgi?id=416079 Bug ID: 416079 Summary: teamviewer 13 fecha Product: kwin Version: 5.16.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leonn...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.4) Qt Version: 5.12.3 Frameworks Version: 5.61.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: toda vez usando teamviewer 13 quando aecsso uma area detrabalho remota por dentro de uma sessão teamviewer o mesmo fecha o aplicativo junto mais não mostra erro. simplesmente fecha. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb20e045880 (LWP 2546))] Thread 8 (Thread 0x7fb1e66d6700 (LWP 7116)): [KCrash Handler] #6 0x7fb1db2601b0 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #7 0x7fb1db14fdea in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #8 0x7fb1db154193 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #9 0x7fb1db1c18c3 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #10 0x7fb1db1c1a89 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #11 0x7fb1db1c4251 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #12 0x7fb1db1c492e in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #13 0x7fb1db159973 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #14 0x7fb1dad59f6b in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.50 #15 0x7fb205a6c848 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7fb205a72056 in QSGBatchRenderer::Renderer::render() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7fb205a62810 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7fb205a62cbb in QSGRenderer::renderScene(unsigned int) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7fb205a9f830 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7fb205b01a18 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7fb205aaae92 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7fb205aaeae8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7fb20acc9c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fb2069196db in start_thread (arg=0x7fb1e66d6700) at pthread_create.c:463 #25 0x7fb20d9b588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb1ecaac700 (LWP 7115)): #0 0x7fb20d9a8cf6 in __GI_ppoll (fds=0x7fb1e0013e88, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fb20aefbab1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb20aefd1be in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb20aea103a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb20acc84ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb205337115 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fb20acc9c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb2069196db in start_thread (arg=0x7fb1ecaac700) at pthread_create.c:463 #8 0x7fb20d9b588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fb1e4bb6700 (LWP 4046)): #0 0x7fb20691f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5631075b7b34) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb20691f9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5631075b7ae0, cond=0x5631075b7b08) at pthread_cond_wait.c:502 #2 0x7fb20691f9f3 in __pthread_cond_wait (cond=0x5631075b7b08, mutex=0x5631075b7ae0) at pthread_cond_wait.c:655 #3 0x7fb20acd0dbb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb20acd10c9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb205aae6f8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb205aaeb2a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fb20acc9c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb2069196db in start_thread (arg=0x7fb1e4bb6700) at pthread_create.c:463 #9
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Leonardo changed: What|Removed |Added CC||leonei...@gmail.com --- Comment #6 from Leonardo --- Same problem here. It was working in Kubuntu before formatting my HDD. Not working now I tried in Manjaro, KDE Neon and Kubuntu. Also i get some messages: "Access grant not present" "This browser or app is not safe, try another." "Sign in with Google is temporarily disabled for this app This app has not yet been verified by Google to use Google Login." and some white screens -- You are receiving this mail because: You are watching all bug changes.
