[plasmashell] [Bug 422708] System Monitor widgets show no sensors
https://bugs.kde.org/show_bug.cgi?id=422708 nather...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nather...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from nather...@gmail.com --- same as https://bugs.kde.org/show_bug.cgi?id=422673 I think *** This bug has been marked as a duplicate of bug 422673 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422710] Disk Quota and Network Quota widgets are not working anymore
https://bugs.kde.org/show_bug.cgi?id=422710 nather...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nather...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from nather...@gmail.com --- https://bugs.kde.org/show_bug.cgi?id=422673 *** This bug has been marked as a duplicate of bug 422673 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422673] Plasma monitor doesn't show anything.
https://bugs.kde.org/show_bug.cgi?id=422673 nather...@gmail.com changed: What|Removed |Added CC||matheusfillip...@gmail.com --- Comment #11 from nather...@gmail.com --- *** Bug 422710 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422708] System Monitor widgets show no sensors
https://bugs.kde.org/show_bug.cgi?id=422708 nather...@gmail.com changed: What|Removed |Added CC|nather...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422381] Make Krita's Windows Installer Translatable
https://bugs.kde.org/show_bug.cgi?id=422381 --- Comment #22 from Alvin Wong --- (In reply to Boudewijn Rempt from comment #21) > Okay, sure. And I guess when we can update to the version of nsis that has > the translations we should move to that? Yes, exactly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422673] Plasma monitor doesn't show anything.
https://bugs.kde.org/show_bug.cgi?id=422673 nather...@gmail.com changed: What|Removed |Added CC||tim.cli...@gmail.com --- Comment #10 from nather...@gmail.com --- *** Bug 422708 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422708] System Monitor widgets show no sensors
https://bugs.kde.org/show_bug.cgi?id=422708 nather...@gmail.com changed: What|Removed |Added CC||nather...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422658] Firefox and Brave windows become unresponsive under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=422658 nather...@gmail.com changed: What|Removed |Added CC||nather...@gmail.com --- Comment #1 from nather...@gmail.com --- Noticed this issue as well on arch running zen kernel. I did observe (before the widgets stopped working in last update today) that when this happens RAM usage of the system spikes and when it becomes responsive again it has released RAM. Looks like for whatever reason Firefox eats up all RAM and then it crashes -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Monkiki changed: What|Removed |Added CC||monk...@gmail.com --- Comment #36 from Monkiki --- In my opinion this is a very neccesary feature already present in others terminal applications like GNOME Terminal. And according to some Internet sites, it's also very solicited. In my case I make a strong use of the terminal and with some commands like "docker ps" the output width is quite large and, in short terminal size, the output get messed. Simply resizing the window can solve the problem in GNOME but with KDE I need to resize and execute the command again, which is not very pleasant nor productive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422705] Plasma crashes
https://bugs.kde.org/show_bug.cgi?id=422705 Sam Dyer changed: What|Removed |Added Summary|Plasma |Plasma crashes CC||samdyer...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 422716] New: using gcc10 as compiler while including crashes kdevelop
https://bugs.kde.org/show_bug.cgi?id=422716 Bug ID: 422716 Summary: using gcc10 as compiler while including crashes kdevelop Product: kdevelop Version: 5.4.6 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: kitanat...@gmail.com Target Milestone: --- Application: kdevelop (5.4.6) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.15-gentoo x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I went to Project->Open Configuration->Language Support->C/C++ parser and switch the "Compiler for path" option to GCC10 - Custom settings of the application: in Settings->Configure KDevelop->C/C++ Compilers I manually added an entry named GCC10 with "Compiler executable" set to gcc-10.1.0 This was in a project created from Project->New From Template...->Standard->Terminal->CMake C++ in which I just added the line #include The crash can be reproduced every time. -- Backtrace (Reduced): #5 0x7ff7329f3826 in isSameEntity(clang::NamedDecl*, clang::NamedDecl*) () from /usr/lib/llvm/10/lib64/libclang.so.10 #6 0x7ff732a20170 in clang::ASTDeclReader::findExisting(clang::NamedDecl*) () from /usr/lib/llvm/10/lib64/libclang.so.10 #7 0x7ff732a281d0 in void clang::ASTDeclReader::mergeRedeclarable(clang::Redeclarable*, clang::ASTDeclReader::RedeclarableResult&, unsigned int) () from /usr/lib/llvm/10/lib64/libclang.so.10 #8 0x7ff732a282cc in clang::ASTDeclReader::VisitRedeclarableTemplateDecl(clang::RedeclarableTemplateDecl*) () from /usr/lib/llvm/10/lib64/libclang.so.10 #9 0x7ff732a2913f in clang::ASTDeclReader::VisitFunctionTemplateDecl(clang::FunctionTemplateDecl*) () from /usr/lib/llvm/10/lib64/libclang.so.10 The reporter indicates this bug may be a duplicate of or related to bug 421704. Possible duplicates by query: bug 422533, bug 422509, bug 422200, bug 422009, bug 421930. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 422716] using gcc10 as compiler while including crashes kdevelop
https://bugs.kde.org/show_bug.cgi?id=422716 --- Comment #1 from Radu Benea --- Created attachment 129178 --> https://bugs.kde.org/attachment.cgi?id=129178&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420848] System Settings crashed when I clicked on some entry of the side bar
https://bugs.kde.org/show_bug.cgi?id=420848 JustWay2Fly2beAlive changed: What|Removed |Added CC||justfly1...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422715] valgrind 3.16.0 vex: the `impossible' happened: expr_is_guardable: unhandled expr
https://bugs.kde.org/show_bug.cgi?id=422715 --- Comment #2 from Julian Seward --- Err, ignore that last comment. I just discovered you attached a complete log file. /me gets some more coffee. Let me see if I can repro this locally. In principle this is easy to fix, but I'd like to be able to test the fix. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422030] Pkexec does not work with Dolphin service menus on 20.04
https://bugs.kde.org/show_bug.cgi?id=422030 --- Comment #9 from Don B. Cilly --- It means nothing. It works perfectly - on Neon/18.04. Removing the ;fi makes it work on 20.04 too. It was obviously a "leftover". And just as obviously, the fact that it *did* work on neon, made me overlook it. Sorry. Good job. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422715] valgrind 3.16.0 vex: the `impossible' happened: expr_is_guardable: unhandled expr
https://bugs.kde.org/show_bug.cgi?id=422715
--- Comment #1 from Julian Seward ---
This is the new &&-idiom-recovery machinery in 3.16.0. Looks like
I didn't test it well enough on x86_32 (sigh). It should be trivial
to fix.
You unfortunately cut off the most important bit of the failure message.
What was printed immediately prior to "valgrind fails with an internal error:"
?
That is to say: what was printed by the ppIRExpr call in
default:
vex_printf("\n"); ppIRExpr(e); vex_printf("\n");
vpanic("expr_is_guardable: unhandled expr");
in expr_is_guardable() ?
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 405648] Feature request: Tool for dividing into equal parts
https://bugs.kde.org/show_bug.cgi?id=405648 --- Comment #7 from Hector --- (In reply to Tymond from comment #6) > Some of the ideas here could even be implemented just in vector libraries Yes. So it can be done. You can come up with a lot of ideas to replace the missing features. But this should not go on forever. I'm not a fan of downloading a bunch of plugins and blanks. However, I have to make them. I want this to work out of the box. I want new users to immediately be able to use various chips, and not search the forums. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422715] valgrind 3.16.0 vex: the `impossible' happened: expr_is_guardable: unhandled expr
https://bugs.kde.org/show_bug.cgi?id=422715 William Bader changed: What|Removed |Added CC||williamba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422715] New: valgrind 3.16.0 vex: the `impossible' happened: expr_is_guardable: unhandled expr
https://bugs.kde.org/show_bug.cgi?id=422715 Bug ID: 422715 Summary: valgrind 3.16.0 vex: the `impossible' happened: expr_is_guardable: unhandled expr Product: valgrind Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: williamba...@hotmail.com Target Milestone: --- Created attachment 129177 --> https://bugs.kde.org/attachment.cgi?id=129177&action=edit log file SUMMARY valgrind fails with an internal error: vex: the `impossible' happened: expr_is_guardable: unhandled expr vex storage: T total 993007680 bytes allocated vex storage: P total 496 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==71737==at 0x5803FDC7: ??? (in /usr/libexec/valgrind/memcheck-x86-linux) ... ==71737==by 0x580FA469: ??? (in /usr/libexec/valgrind/memcheck-x86-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 71737) ==71737==at 0x83C6036: cnv_double_to_string (in /u/william/linux-dvl/cpag/cpag) client stack range: [0xFEC2C000 0xFEC37FFF] client SP: 0xFEC32320 valgrind stack range: [0x883AA000 0x884A9FFF] top usage: 6104 of 1048576 STEPS TO REPRODUCE 1. It happens every time when I run my application. OBSERVED RESULT Valgrind aborts with an 'impossible' error. EXPECTED RESULT Valgrind does not abort. SOFTWARE/OS VERSIONS Fedora 31, kernel 5.6.15-200.fc31.x86_64 It is a 64 bit OS, but my application is 32 bit. valgrind-3.16.0-1.fc31.i686 ADDITIONAL INFORMATION I have been using valgrind for years on this application, and it never gave an 'impossible' error before. Google and searching in bugzilla did not find 'expr_is_guardable', so this might be a new problem in valgrind 3.16.0. Is this a known problem? Should I try to make a small example? (The 'cnv_double_to_string' function just calls sprintf and hasn't been touched for years.) Should I try to do a bisection on valgrind? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422714] plasmashell: segfault in libKF5CoreAddons.so.5.70.0
https://bugs.kde.org/show_bug.cgi?id=422714 choc...@post.com changed: What|Removed |Added CC||choc...@post.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422714] New: plasmashell: segfault in libKF5CoreAddons.so.5.70.0
https://bugs.kde.org/show_bug.cgi?id=422714 Bug ID: 422714 Summary: plasmashell: segfault in libKF5CoreAddons.so.5.70.0 Product: plasmashell Version: 5.17.5 Platform: Debian testing OS: Other Status: REPORTED Severity: crash Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: choc...@post.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Desktop turns black (crash). Applications can be run using Alt+F2. That happened after the last update STEPS TO REPRODUCE 1. Boot Linux 2. Login OBSERVED RESULT The Desktop shows for 2 or 3 seconds and then turns black. EXPECTED RESULT Regular Desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: Parrot OS (rolling) based on Debian Testing Kernel: 5.6.0-2parrot1-amd64 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.12.5-2 ADDITIONAL INFORMATION Kernel message: plasmashell[1613]: segfault at 7fc3ad2c8808 ip 7fc3d074bc62 sp 7ffd0e4eccf0 error 7 in libKF5CoreAddons.so.5.70.0[7fc3d0728000+68000] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422713] New: Backtab should be named Tab
https://bugs.kde.org/show_bug.cgi?id=422713 Bug ID: 422713 Summary: Backtab should be named Tab Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- I noticed that in the window switching kcm in system settings the default keyboard shortcut for reverse window switching is "Alt+Shift+Backtab", whereas the keyboard shortcuts kcm always mentions "Tab" instead. It seems the name shown in the kcm is defined in line https://invent.kde.org/plasma/kwin/-/blob/master/tabbox/tabbox.cpp#L548 but I might be mistaken. To me it looks like it's trivial and the fix just requires renaming Qt::Key_Backtab to Qt::Key_Tab, but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422096] Right-click often performs the first action in the context menu on high-DPI displays
https://bugs.kde.org/show_bug.cgi?id=422096 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 420914] Version 3.8.2 When selecting file after folder open Event 1000 Faulting Module libstdc++-6.dll
https://bugs.kde.org/show_bug.cgi?id=420914 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 422067] Program stops responding when importing Quicken data
https://bugs.kde.org/show_bug.cgi?id=422067 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422712] New: Not able to use "Edit application" from right click menu from the search list.
https://bugs.kde.org/show_bug.cgi?id=422712 Bug ID: 422712 Summary: Not able to use "Edit application" from right click menu from the search list. Product: plasmashell Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: matheusfillip...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Not able to use "Edit application" from right click menu from the search list. STEPS TO REPRODUCE 1. Open the application launcher or application dashboard menu 2. Search for any app and right click on it 3. Click on "Edit application" from the popup menu. OBSERVED RESULT Nothing happens but that is not a problem with kmenuedit since it still launches and it also works if i just got to my app tab or recent and right click on them. The problem only happens for applications in the search results list. EXPECTED RESULT A window for editing the app should appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.19 KDE Frameworks Version: 5.70 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422711] New: kwin_wayland segmentation fault in KWin::LibInput::Connection::applyScreenToDevice when logging in
https://bugs.kde.org/show_bug.cgi?id=422711
Bug ID: 422711
Summary: kwin_wayland segmentation fault in
KWin::LibInput::Connection::applyScreenToDevice when
logging in
Product: kwin
Version: 5.18.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
SUMMARY
I booted the Fedora Rawhide KDE Plasma live spin
Fedora-KDE-Live-x86_64-Rawhide-20200603.n.0.iso which has Plasma 5.18.5, KF
5.70.0/1, Qt 5.14.2. I created a new user in System Settings with a password. I
installed kwin-wayland, plasma-workspace-wayland, and their dependencies. I
logged out of Plasma on X. I selected the user I created in sddm. I entered an
incorrect password and tried to login 3 times. The login was denied. I switched
the user to the liveuser and tried to log in to Plasma on Wayland. The screen
was briefly black then it went back to sddm. The next login to Plasma on
Wayland worked properly. coredumpctl showed that kwin_wayland had a
segmentation fault in KWin::LibInput::Connection::applyScreenToDevice at
/usr/src/debug/kwin-5.18.5-1.fc33.x86_64/libinput/../screens.h:220 which
occurred on the first login to Plasma on Wayland which didn't complete
properly. The full trace of all threads from coredumpctl was the following.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 KWin::LibInput::Connection::applyScreenToDevice
(this=this@entry=0x5635f74f4300, device=device@entry=0x5635f7605b60) at
/usr/src/debug/kwin-5.18.5-1.fc33.x86_64/libinput/../screens.h:220
220 return m_count;
[Current thread is 1 (Thread 0x7fc60d857e00 (LWP 10125))]
(gdb) thread apply all bt full
Thread 4 (Thread 0x7fc5f37fe680 (LWP 10128)):
#0 0x7fc60c941abf in poll () from /lib64/libc.so.6
No symbol table info available.
#1 0x7fc60a43dace in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#2 0x7fc60a43dc03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#3 0x7fc60cee1b73 in QEventDispatcherGlib::processEvents
(this=0x7fc5e4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
d = 0x7fc5e4000b80
canWait = true
savedFlags = {i = 0}
result =
#4 0x7fc60ce9491b in QEventLoop::exec (this=this@entry=0x7fc5f37fdc00,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
d = 0x7fc5e4003090
locker = {val = 94789782694168}
ref =
app =
#5 0x7fc60cd00427 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
d = 0x5635f75368c0
locker = {val = 94789782694168}
eventLoop = { = {_vptr.QObject = 0x7fc60d14d948 , static sta--Type for more, q to quit, c to continue
without paging--c
ticMetaObject = {d = {superdata = {direct = 0x0}, stringdata = 0x7fc60d0342e0
, data = 0x7fc60d0341c0 ,
static_metacall = 0x7fc60cec3350 , relatedMetaObjects = 0x0, extradata = 0x0}},
d_ptr = {d = 0x7fc5e4003090}, static staticQtMetaObject = {d = {superdata =
{direct = 0x0}, stringdata = 0x7fc60d037260 , data =
0x7fc60d034400 , static_metacall = 0x0, relatedMetaObjects =
0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = {direct =
0x7fc60d1452c0 }, stringdata = 0x7fc60d02e4e0
, data = 0x7fc60d02e480
, static_metacall = 0x7fc60ce94630
,
relatedMetaObjects = 0x0, extradata = 0x0}}}
returnCode =
#6 0x7fc60cd01690 in QThreadPrivate::start(void*) () at
thread/qthread_unix.cpp:342
currentThreadData = 0x5635f75370b0
current_thread_data_once = 2
current_thread_data_key = 3
(anonymous namespace)::destroy_current_thread_data_key_dtor_instance_ =
{}
#7 0x7fc60d994479 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#8 0x7fc60c94cb53 in clone () from /lib64/libc.so.6
No symbol table info available.
Thread 3 (Thread 0x7fc5f3fff680 (LWP 10127)):
#0 0x7fc60c941abf in poll () from /lib64/libc.so.6
No symbol table info available.
#1 0x7fc60a43dace in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#2 0x7fc60a43dc03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#3 0x7fc60cee1b73 in QEventDispatcherGlib::processEvents
(this=0x7fc5ec000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
d = 0x7fc5ec000b80
canWait = true
savedFlags = {i = 0}
result =
#4 0x7fc60ce9491b in QEventLoop::exec (this=this@entry=0x7fc5f3ffec00,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
d = 0x7fc5ec003890
locker
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #61 from TheRogueGrunt --- (In reply to Simon Redman from comment #58) > You should be able to build the .apk by going to the directory where the > branch is checked out and doing `./gradlew installDebug` without using > Android Studio (Assuming ADB is set up and your phone is connected) > > I am going to merge this latest patch in a day or so in any case, since it > at least seems to work as well as it previously did for all phones and it > has been reported to work on a few phones which didn't previously work. > Nobody with a Samsung device has been able to test which is the big one, but > I am hopeful that it will work in any case (and I have read online that it > should) That command has failed miserably so I'm just gonna wait for an apk I can just install. I'm not an app developer and I barely know enough to use Linux so all of this is WAY over my head and it honestly hurts to try to figure out -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #60 from TheRogueGrunt --- (In reply to Simon Redman from comment #58) > You should be able to build the .apk by going to the directory where the > branch is checked out and doing `./gradlew installDebug` without using > Android Studio (Assuming ADB is set up and your phone is connected) > > I am going to merge this latest patch in a day or so in any case, since it > at least seems to work as well as it previously did for all phones and it > has been reported to work on a few phones which didn't previously work. > Nobody with a Samsung device has been able to test which is the big one, but > I am hopeful that it will work in any case (and I have read online that it > should) This is why I'm trying so desperately to test it, I have a Samsung Note 8. I'll try this and if I can't figure it out I'll just wait for the merge. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Simon Redman changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-android/comm ||it/876d1fa3db9a7f9a136ae2ca ||be38bc81194b6dfd Resolution|--- |FIXED --- Comment #59 from Simon Redman --- Git commit 876d1fa3db9a7f9a136ae2cabe38bc81194b6dfd by Simon Redman. Committed on 10/06/2020 at 03:58. Pushed by sredman into branch 'master'. [SMS Helper] Use simple=true parameter for fetching the list of all conversations ## Summary Use `content://mms-sms/conversations?simple=true` instead of just `content://mms-sms/conversations` which should work for more devices (and is reported to work on Samsung devices) For some reason, this misses exactly one conversation on my phone and throws back one invalid thread ID -- I suspect this indicates that my message database is corrupt :shrug: ## Test Plan ### Before: Lots of devices were not able to retrieve conversations. See [bug 401677](https://bugs.kde.org/show_bug.cgi?id=401677) ### After: Hopefully all devices are able to retrieve conversations. At minimum, hopefully there are no regressions :) M +42 -17 src/org/kde/kdeconnect/Helpers/SMSHelper.java https://invent.kde.org/network/kdeconnect-android/commit/876d1fa3db9a7f9a136ae2cabe38bc81194b6dfd -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422710] New: Disk Quota and Network Quota widgets are not working anymore
https://bugs.kde.org/show_bug.cgi?id=422710 Bug ID: 422710 Summary: Disk Quota and Network Quota widgets are not working anymore Product: kdeplasma-addons Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disk Quota Assignee: plasma-b...@kde.org Reporter: matheusfillip...@gmail.com Target Milestone: --- SUMMARY After the 5.19 upgrade the system monitor applets/widgets are showing totally blank. They were working on 5.18.5. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.19 KDE Frameworks Version: 5.70 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #58 from Simon Redman --- You should be able to build the .apk by going to the directory where the branch is checked out and doing `./gradlew installDebug` without using Android Studio (Assuming ADB is set up and your phone is connected) I am going to merge this latest patch in a day or so in any case, since it at least seems to work as well as it previously did for all phones and it has been reported to work on a few phones which didn't previously work. Nobody with a Samsung device has been able to test which is the big one, but I am hopeful that it will work in any case (and I have read online that it should) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #57 from TheRogueGrunt --- (In reply to poperigby from comment #53) > (In reply to Simon Redman from comment #52) > > (In reply to poperigby from comment #51) > > > > > > I'm happy to test. How can I do it? > > > > If you already have Android Studio installed, you can build using that, > > otherwise you can install Android Studio or build using gradle > > https://developer.android.com/studio/build/building-cmdline > > > > I've had pretty much 0% success sharing .apks built from my development > > session, so I can't provide a pre-built one, sorry > > Ok. I'll do it soon when I have time. If you make the apk, can you share it? I've just tried to and I broke Android Studio so badly even a full reinstall didn't fix it. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 422709] New: drag & drop files for compare no longer works
https://bugs.kde.org/show_bug.cgi?id=422709 Bug ID: 422709 Summary: drag & drop files for compare no longer works Product: kompare Version: 4.1.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: s_chriscoll...@hotmail.com Target Milestone: --- Created attachment 129176 --> https://bugs.kde.org/attachment.cgi?id=129176&action=edit video showing the bug SUMMARY I used to be able to drag a file from dolphin into either the "Source" or "Destination" file path boxes and it would fill in the path to that file. Now, when I drag and drop a file in this manner, the file path becomes empty. At some point, either a system or application update appears to have broken this functionality. I attached a video showing the problem. SOFTWARE/OS VERSIONS OS: KDE Neon 5.19 User Edition Linux Kernel: 5.3.0-53-generic KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422708] New: System Monitor widgets show no sensors
https://bugs.kde.org/show_bug.cgi?id=422708 Bug ID: 422708 Summary: System Monitor widgets show no sensors Product: plasmashell Version: 5.19.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: tim.cli...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 129175 --> https://bugs.kde.org/attachment.cgi?id=129175&action=edit screenshot of empty widgets and no available sensors Just upgraded to Plasma 5.19, and my peviously working system monitor widgets are now blank. Apologize if this is a duplicate - I found a reddit thread describing this issue, and an Arch forum post, but no actual bug filed. Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19 KDE Frameworks Version: 5.70 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 422707] New: Click continuously to switch to the next song, and the lock screen will be forced to lock.
https://bugs.kde.org/show_bug.cgi?id=422707 Bug ID: 422707 Summary: Click continuously to switch to the next song, and the lock screen will be forced to lock. Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: logic...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When listening to music, use the control plug-in of the lock screen to switch the next song, and when you switch songs continuously, the lock screen will end forcefully. STEPS TO REPRODUCE 1. Lock the screen when listening to music 2. Use the control plug-in to switch songs and switch several songs in a row 3. The lock screen will be forced to end and re-lock. OBSERVED RESULT The lock screen will be forced to end and re-lock. EXPECTED RESULT The lock screen is delayed and locked in response to mouse operation. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.15-zen2-1-zencjk OS Type: 64-位 Processors: 8 × AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx Memory: 14.6 GiB Graphics Processor: AMD RAVEN ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387775] KWin touch screen edge creates a 1 pixel dead zone on that edge that doesn't accept mouse clicks or scrolls outside of full-screen mode
https://bugs.kde.org/show_bug.cgi?id=387775 Maciej Stanczew changed: What|Removed |Added CC||maciej.stancze...@gmail.com --- Comment #29 from Maciej Stanczew --- Regarding bug 422674: until Plasma 5.19, mouse clicks at X = 0 worked at least on title bars and bottom panels. Starting from 5.19 it seems that all mouse clicks at X = 0 do nothing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387775] KWin touch screen edge creates a 1 pixel dead zone on that edge that doesn't accept mouse clicks or scrolls outside of full-screen mode
https://bugs.kde.org/show_bug.cgi?id=387775 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415583] Global Themes with SDDM Themes fail to install if SDDM is not installed
https://bugs.kde.org/show_bug.cgi?id=415583 --- Comment #2 from The Feren OS Dev --- As for running the command normally: $~: kpackagetool5 -t Plasma/LookAndFeel -i /tmp/02-com.github.vinceliuice.McMojave-light.tar.xz already installed. already installed. already installed. already installed. already installed. couldn't find knsrc file for "sddmtheme.knsrc" Error: Installation of /tmp/02-com.github.vinceliuice.McMojave-light.tar.xz failed: Could not install dependency: 'kns://sddmtheme.knsrc/api.kde-look.org/1312086' -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415583] Global Themes with SDDM Themes fail to install if SDDM is not installed
https://bugs.kde.org/show_bug.cgi?id=415583 The Feren OS Dev changed: What|Removed |Added Summary|Global Themes with SDDM |Global Themes with SDDM |Themes do not get installed |Themes fail to install if |properly if SDDM is not |SDDM is not installed |installed | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415583] Global Themes with SDDM Themes do not get installed properly if SDDM is not installed
https://bugs.kde.org/show_bug.cgi?id=415583 The Feren OS Dev changed: What|Removed |Added Summary|Global Themes with SDDM |Global Themes with SDDM |Themes fail installation if |Themes do not get installed |SDDM is not installed |properly if SDDM is not ||installed --- Comment #1 from The Feren OS Dev --- Reproduced on Frameworks 5.70.0 on KDE neon 5.19.0 With the introduction of the error messages upon failure, this message is provided in the case of the McMojave Global Theme: An error occurred during the installation process: The installation failed with code 4 while attempting to run the command: kpackagetool5 -t Plasma/LookAndFeel -i /tmp/02-com.github.vinceliuice.McMojave-light.tar.xz The returned output was: Error: Installation of /tmp/02-com.github.vinceliuice.McMojave-light.tar.xz failed: Could not install dependency: 'kns://sddmtheme.knsrc/api.kde-look.org/1312086' -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415583] Global Themes with SDDM Themes fail installation if SDDM is not installed
https://bugs.kde.org/show_bug.cgi?id=415583 The Feren OS Dev changed: What|Removed |Added Summary|Global Themes with SDDM |Global Themes with SDDM |Themes do not get installed |Themes fail installation if |properly if SDDM is not |SDDM is not installed |installed | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422706] Separate translatable Original between channels2layers and karbonplugins
https://bugs.kde.org/show_bug.cgi?id=422706 Tyson Tan changed: What|Removed |Added Summary|Separate Original from |Separate translatable |channels2layers and |Original between |karbonplugins |channels2layers and ||karbonplugins -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422706] New: Separate Original from channels2layers and karbonplugins
https://bugs.kde.org/show_bug.cgi?id=422706 Bug ID: 422706 Summary: Separate Original from channels2layers and karbonplugins Product: krita Version: 4.3.0-beta2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Original #: plugins/python/channels2layers/channels2layers.py:1129 #: plugins/tools/karbonplugins/tools/KarbonPatternOptionsWidget.cpp:35 #, kde-format Please separate these two "Original", because in Chinese/Japanese we don't have a single noun in place of "Original", but must be very specific as "Original of what". So these two cannot share the same translation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422704] Add Sort by... to grouped instances. Search ?
https://bugs.kde.org/show_bug.cgi?id=422704 --- Comment #1 from Me --- BTW, would be really nice if TaskManager -> rightclick -> More Actions had a "Open" (Open All) function in the list. This would allow users to open all the instances at once, look through them and then manually close them one at a time. Would make searching for something much easier. As it is right now to do the same thing you'd have to manually open each instance by selecting it in the group list. By "Open" I mean open the instance as if you clicked it in the group instance list. The More Actions list has Maximize, Minimize and lots of other stuff, but no plain Open. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 416941] AVIF image support
https://bugs.kde.org/show_bug.cgi?id=416941 Matt Scheirer changed: What|Removed |Added CC||matt.schei...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416103] Adjusting Detailed Settings for Regional Settings breaks locale
https://bugs.kde.org/show_bug.cgi?id=416103 --- Comment #7 from Alexander --- Still have this problem on Kubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422705] New: Plasma
https://bugs.kde.org/show_bug.cgi?id=422705 Bug ID: 422705 Summary: Plasma Product: plasmashell Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: matheusfillip...@gmail.com Target Milestone: 1.0 Created attachment 129174 --> https://bugs.kde.org/attachment.cgi?id=129174&action=edit Crash dump SUMMARY Plasma randomly crashes. Not sure why, usually when opening an application but happened three times with me already with different applications so I can't quite see any pattern. Maybe the attached crash dump tells something useful I hope. SOFTWARE/OS VERSIONS Linux: Arch linux (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #10 from Johannes Zarl-Zierl --- I've just synced the KDE Neon branch with master. You should get the updated package soon. Please report back if this fixes the crash for you... Btw. thanks for taking the time to close your related bug report - this really makes a difference for us! Cheers, Johannes -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387775] KWin touch screen edge creates a 1 pixel dead zone on that edge that doesn't accept mouse clicks or scrolls outside of full-screen mode
https://bugs.kde.org/show_bug.cgi?id=387775 Patrick Silva changed: What|Removed |Added CC||32299...@gmail.com --- Comment #28 from Patrick Silva --- *** Bug 422674 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422674] Application launcher does not respond to clicks in the corner of display
https://bugs.kde.org/show_bug.cgi?id=422674 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 387775 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422704] New: Add Sort by... to grouped instances. Search ?
https://bugs.kde.org/show_bug.cgi?id=422704 Bug ID: 422704 Summary: Add Sort by... to grouped instances. Search ? Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: linuxguy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Add Sort by... and search to grouped instances. Allow a group of task instances (like Firefox instances) to be sorted alphabetically, by last used, my most used, etc. and to search for instances based on window title names. STEPS TO REPRODUCE 1. Add a panel with a task manager widget. Enable group by name, disable waiting for the task bar to be full. All tasks will be grouped all the time. 2. Open 20 to 50 instances of an app, like Firefox 3. Use them over the course of a week. 4. Reboot. OBSERVED RESULT When Linux reboots, task manager adds instances to the group as they launch. Ie without a pre determined order. If you need to open a specific instance from the list, you have to search through the list and find it. Very time consuming. Would be better to be able to search the instance list for a window title keyword or sort the instances alphabetically. Would also be great to be able to "star" a specific instance (gmail, for example) and keep it at the bottom or top of the task list, so it is always available. Would also be great to be able to sort the list by last used, most frequently used, etc. EXPECTED RESULT No have to manually search through an arbitrarily ordered list to find the instance that is needed. Give the power users some power tools. SOFTWARE/OS VERSIONS Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.13.2 Kernel Version: 5.6.16-300.fc32.x86_64 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 62.8 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #19 from Nate Graham --- Scratch that. It's only working for XWayland apps. Full Wayland apps are still broken in the way described here. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 422681] Icons of non-selected folders in GTK3 file open/save dialogs are barely visible with Breeze global theme
https://bugs.kde.org/show_bug.cgi?id=422681 Nate Graham changed: What|Removed |Added Keywords||triaged Assignee|visual-des...@kde.org |uhh...@gmail.com Component|Icons |gtk theme CC||n...@kde.org --- Comment #1 from Nate Graham --- Cannot reproduce; the icons are correctly colored for me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411114] Some touchpad settings get lost after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=44 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Nate Graham --- I just had this happen recently after installing or removing some packages on openSUSE TUmbleweed but I can't remember that they were. :( -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 422703] New: Skrooge Crash on first click.
https://bugs.kde.org/show_bug.cgi?id=422703 Bug ID: 422703 Summary: Skrooge Crash on first click. Product: skrooge Version: unspecified Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: js...@jstub.com CC: steph...@mankowski.fr Target Milestone: --- Application: skrooge (2.21.1) Qt Version: 5.13.0 Frameworks Version: 5.62.0 Operating System: FreeBSD 12.1-RELEASE-p5 i386 Distribution (Platform): FreeBSD Ports -- Information about the crash: - What I was doing when the application crashed: Just started skrooge. Clicked on "new file". Crash ensued. Now I will replicate... $ uname -a FreeBSD deemon 12.1-RELEASE-p5 FreeBSD 12.1-RELEASE-p5 GENERIC i386 $ Just finished upgrading from 11.3 to 12.1 yesterday and this morning. Most applications are from 'pkg' system. Also upgraded all ports. The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generated Possible duplicates by query: bug 422588, bug 422568, bug 422533, bug 422433, bug 422374. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422702] New: Virtual keyboard stopped working since the last update, wayland
https://bugs.kde.org/show_bug.cgi?id=422702 Bug ID: 422702 Summary: Virtual keyboard stopped working since the last update, wayland Product: kwin Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: keziolio...@gmail.com Target Milestone: --- SUMMARY Virtual keyboard closes itself after pressing a key, after the new 5.19 update STEPS TO REPRODUCE 1. start kde on wayland in a touchscreen device without a physical keyboard 2. press on a text box 3. try to write in the text box with the virtual keyboard OBSERVED RESULT The keyboard closes itself EXPECTED RESULT The keyboard should write stuff in the text box SOFTWARE/OS VERSIONS Everything up to date on Archlinux -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 422701] New: Falkon browser does not support webauthn (public key credentials)
https://bugs.kde.org/show_bug.cgi?id=422701 Bug ID: 422701 Summary: Falkon browser does not support webauthn (public key credentials) Product: Falkon Version: 3.1.0 Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kanwar.pl...@gmail.com Target Milestone: --- SUMMARY I have noticed the user agent in Falkon browser does not allow public key credentials. In fact, it was working but shows the error "Uncaught (in promise) DOMException: The user agent does not support public key credentials." when accessing a corporate 2FA login (webauthn)? This happens only on KaOS Linux. It seems to work on Kubuntu and Manjaro (with KDE/Plasma). STEPS TO REPRODUCE 1. Run Falkon on KaOS 2. Access a site that requires webauthn 3. Page does not load 4. When viewed in developer tools, the error "Uncaught (in promise) DOMException: The user agent does not support public key credentials." is reported. OBSERVED RESULT "Uncaught (in promise) DOMException: The user agent does not support public key credentials." EXPECTED RESULT Login page loads SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KaOS Linux / KDE 5.70.0 / Plasma 5.19.0 (available in About System) KDE Plasma Version: Plasma 5.19.0 KDE Frameworks Version: KDE 5.70.0 Qt Version: 5.15.0-1 ADDITIONAL INFORMATION Works under KDE Neon / Kubuntu / Manjaro -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422680] [Wayland] Notifications Timer Animation Is Not Showing
https://bugs.kde.org/show_bug.cgi?id=422680 Nate Graham changed: What|Removed |Added Keywords||triaged Resolution|WAITINGFORINFO |--- Flags|X11?, Brainstorm-, |Wayland+, X11- |Translation_missing-, | |Usability-, VisualDesign- | Status|NEEDSINFO |REPORTED --- Comment #4 from Nate Graham --- Thanks! That's strange. Cannot reproduce in my Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 Nate Graham changed: What|Removed |Added Version Fixed In||5.19.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #18 from Nate Graham --- Yep, this was fixed in 5.19! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422574] File Open requires .pdf suffix to display in "All Supported Files"
https://bugs.kde.org/show_bug.cgi?id=422574 --- Comment #4 from Albert Astals Cid --- oh, seems like gtk, supports adding mimetypes to the file dialog, Qt just supports adding file extionsions. There's nothing Okular can really do here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401012] keyboard indicator text is barely visible in system tray settings when using a dark theme for Plasma
https://bugs.kde.org/show_bug.cgi?id=401012 Nate Graham changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419221] Presentation toolbar: Checkmarks in drawing tool buttons blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=419221 --- Comment #9 from Nate Graham --- Haha! I love the hippo. In that screenshot, you can see: > Request to merge davidhurka:make-presentation-toolbar-checkboxes-sharp > into master" So it would have landed on the master branch after merging. The actual commit page (https://invent.kde.org/graphics/okular/-/commit/e667143ef10913960d16adb672260ba3edb5c605) is not very clear about what branch it's on though, that's true. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 177856] move "switch application language" from "help" to "settings"
https://bugs.kde.org/show_bug.cgi?id=177856 Nate Graham changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|kdelibs-b...@kde.org|n...@kde.org --- Comment #4 from Nate Graham --- Dunno why I didn't do this years ago. ago Here's merge request that will fix it: https://invent.kde.org/frameworks/kxmlgui/-/merge_requests/4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366823] Consistent direction for changing zoom and changing brush size
https://bugs.kde.org/show_bug.cgi?id=366823 --- Comment #6 from Tymond --- I guess I agree with @Nick in comment 5. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 422661] Extra newline at the end of cmake build type
https://bugs.kde.org/show_bug.cgi?id=422661 --- Comment #1 from Yavuz Mert --- I browsed the code to see if I can easily fix it, it seem that it is already fixed on master on Feb 9th but somehow is not applied on 5.5.1 version, or even 5.5.2 version. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 339077] Circle and Rectangle tools Rotation.
https://bugs.kde.org/show_bug.cgi?id=339077 --- Comment #7 from Tymond --- If it would work the way Houdini manipulator works, it couldn't work like other paint tools. I think it should be designed more carefully to be done in one movement, the way it is now - you create a rectangle and it's done and cannot be changed. Alternatively, those tools could work like Transform Tool - before committing, you only see a preview. That would be a tiny bit more difficult, easier to design, but I'm not sure if it would improve UX all that much considering the committing part. I think the first option would be better. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 422488] Hidded items in GUI translation tree
https://bugs.kde.org/show_bug.cgi?id=422488 --- Comment #8 from Antoni Bella --- I build lokalize 19.12.3-0ubuntu1bella1 for Qt suitable version. All work fine! Thank you :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395558] KWIN Suddent crash
https://bugs.kde.org/show_bug.cgi?id=395558 --- Comment #4 from Oussama --- Created attachment 129173 --> https://bugs.kde.org/attachment.cgi?id=129173&action=edit New crash information added by DrKonqi kwin_x11 (5.19.0) using Qt 5.14.2 Kwin crashes whene I close a maximazed windwos. I'm using both "MACsimize" and "Dynamic Virtual Desktop". Sorry for my poor english. -- Backtrace (Reduced): #4 0x7f1143447a19 in KWin::FocusChain::getForActivation(unsigned int, int) const (this=0x558ae60c5e40, desktop=, desktop@entry=2, screen=0) at ./focuschain.cpp:77 #5 0x7f1143447a9c in KWin::FocusChain::getForActivation(unsigned int) const (this=, desktop=desktop@entry=2) at ./focuschain.cpp:64 #6 0x7f114352f2a2 in KWin::Workspace::findClientToActivateOnDesktop(unsigned int) (this=0x558ae5fb5ce0, desktop=2) at ./workspace.cpp:1036 #7 0x7f114352f43d in KWin::Workspace::activateClientOnNewDesktop(unsigned int) (this=0x558ae5fb5ce0, desktop=2) at ./workspace.cpp:986 #8 0x7f1143530180 in KWin::Workspace::slotCurrentDesktopChanged(unsigned int, unsigned int) (this=0x558ae5fb5ce0, oldDesktop=3, newDesktop=2) at ./workspace.cpp:944 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422698] HDMI Audio output setting lost, device not saved, goes to default screen.
https://bugs.kde.org/show_bug.cgi?id=422698 Me changed: What|Removed |Added Version|5.10.3 |5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422700] New: Rotated non primary display has to be reset after reboot.
https://bugs.kde.org/show_bug.cgi?id=422700 Bug ID: 422700 Summary: Rotated non primary display has to be reset after reboot. Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: linuxguy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Rotated non primary display non functional after reboot and has to be reset to use. STEPS TO REPRODUCE 1. Set up KDE with 2 screens. Primary screen is on the right. Other screen is on the left, rotated. 2. Reboot. OBSERVED RESULT First off, the login on the non primary screen is rotated sideways. On login the system doesn't recognize that the monitor is rotated and doesn't compensate. Secondly, after login the non primary screen is black, but not operating. The mouse will operate on the screen but KDE isn't operating on it and things like mouse clicks, etc. aren't acted upon. To get the non primary screen to operate, one needs to System Settings -> Display Configuration, unclick the rotated button and click the non rotated button and press apply. At this point KDE starts displaying and working on the monitor. Then press the rotated orientation button and Apply and everything works again. EXPECTED RESULT The screen should function properly after a reboot without any fiddling. SOFTWARE/OS VERSIONS Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.13.2 Kernel Version: 5.6.16-300.fc32.x86_64 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 62.8 GiB of RAM ADDITIONAL INFORMATION Does this with both Intel and NVidia display adapters. Does it with both Nouveau and NVidia drivers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405648] Feature request: Tool for dividing into equal parts
https://bugs.kde.org/show_bug.cgi?id=405648 --- Comment #6 from Tymond --- Some of the ideas here could even be implemented just in vector libraries templates like here: https://krita-artists.org/t/vector-library-drawing-templates/6686 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 422699] New: Application Categories Can't List Packages after Performing an Update Using Discover
https://bugs.kde.org/show_bug.cgi?id=422699 Bug ID: 422699 Summary: Application Categories Can't List Packages after Performing an Update Using Discover Product: Discover Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: k...@startport.com CC: aleix...@kde.org Target Milestone: --- In Kubuntu 20.04, after installing updates via Discover, if I try to navigate applications in left pane, upon clicking each application-category, it says "Sorry, nothing found...". I easily resolved this by closing Discover after the update, and then I was able to see the apps by clicking on the categories. This is minor issue, but I thought I should report it. I'm using Discover 5.18.5, so maybe you've already addressed this issue 15.19.0. I wouldn't know. To reproduce, you'll need a to test a system that actually needs updates, and just install those update using Discover and then try to navigate the Application categories. Merely checking for updates doesn't cause this issue; it only happens after installing update using Discover. You'll find that you have to close and reopen discover before you'll be able to navigate those application categories. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422698] HDMI Audio output setting lost, device not saved, goes to default screen.
https://bugs.kde.org/show_bug.cgi?id=422698 Me changed: What|Removed |Added Summary|HDMI Audio output device|HDMI Audio output setting |not saved, goes to default. |lost, device not saved, ||goes to default screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422698] New: HDMI Audio output device not saved, goes to default.
https://bugs.kde.org/show_bug.cgi?id=422698 Bug ID: 422698 Summary: HDMI Audio output device not saved, goes to default. Product: plasmashell Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: linuxguy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Set up KDE to operate on 2 screens. Primary screen is screen #2, on the right. Secondary screen is to the left, rotated 90 degrees. Login is to occur on the primary screen. Sound should come out of the primary screen. 2. Set up sound to use HDMI output. Use PulseAudio Volume Control to select HDMI out and the primary screen for output. OBSERVED RESULT Half the time there is no sound and one has to go to the sound widget in panel and select HDMI as the Default Device. (The Default Device icon is messed up as well.) Every time the computer is rebooted the sound will default back to screen #1. The user must open PulseAudio Volume Control and reset the audio to come out of the primary screen. Sometimes this happens every time the computer goes to sleep and/or every time you log out. Thus every reboot or sleep you have to go in and reset and fiddle with the HDMI audio settings. EXPECTED RESULT 1) The HDMI output device should be retained across reboots, sleep, logouts, etc. 2) The selection of HDMI audio as the default should be retained across reboots, sleep, logouts, etc. SOFTWARE/OS VERSIONS Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.13.2 Kernel Version: 5.6.16-300.fc32.x86_64 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 62.8 GiB of RAM ADDITIONAL INFORMATION Video card and driver independent. Happens with both Intel and NVidia display adapters and Intel, nouveau and Nvidia drivers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415106] Popup palette colour history is not updated if paint stroke is started soon after closure
https://bugs.kde.org/show_bug.cgi?id=415106 Lynx3d changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/17e6e2841 |hics/krita/commit/a43a239a6 |c245aa16eeb000f62f3e5717db7 |a342a2d8e179bee1d8c57bdb1af |b657|d89a --- Comment #5 from Lynx3d --- Git commit a43a239a6a342a2d8e179bee1d8c57bdb1afd89a by Mathias Wein. Committed on 09/06/2020 at 21:42. Pushed by mwein into branch 'krita/4.3'. Remove old workaround for popup palette hiding Commit 591684144731c0e8516bfd065fa812ff3e5f9c00 and Commit ae734675be9f92173a9c44516a205edefb19ee97 added this to prevent picking up the new foreground color as used by closing the palette with a left-click on the canvas. The paint tools however have been refactored since then and the "TODO" is no longer present in kis_tool_freehand.cc, so remove the remains of this workaround. (cherry picked from commit 17e6e2841c245aa16eeb000f62f3e5717db7b657) M +1-7libs/ui/kis_canvas_resource_provider.cpp M +0-15 libs/ui/kis_canvas_resource_provider.h M +0-7libs/ui/kis_favorite_resource_manager.h M +0-1libs/ui/kis_paintop_box.cc M +0-23 libs/ui/kis_popup_palette.cpp M +0-12 libs/ui/kis_popup_palette.h https://invent.kde.org/graphics/krita/commit/a43a239a6a342a2d8e179bee1d8c57bdb1afd89a -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 416382] Yakuake will not toggle on screen directly left of main screen
https://bugs.kde.org/show_bug.cgi?id=416382 --- Comment #5 from Maximilian Schiller --- whoops linked the wrong report https://bugs.kde.org/show_bug.cgi?id=396697 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422673] Plasma monitor doesn't show anything.
https://bugs.kde.org/show_bug.cgi?id=422673 Nate Graham changed: What|Removed |Added Severity|minor |grave CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 416382] Yakuake will not toggle on screen directly left of main screen
https://bugs.kde.org/show_bug.cgi?id=416382 Maximilian Schiller changed: What|Removed |Added CC||manim...@outlook.de --- Comment #4 from Maximilian Schiller --- I think this is the same issue as in https://bugs.kde.org/show_bug.cgi?id=39669 should be fixed in the next release -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422697] Task manager doesn't group Firefox instances after reboot.
https://bugs.kde.org/show_bug.cgi?id=422697 Me changed: What|Removed |Added Summary|Task manager doesn't group |Task manager doesn't group |Firefox after reboot. |Firefox instances after ||reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422697] New: Task manager doesn't group Firefox after reboot.
https://bugs.kde.org/show_bug.cgi?id=422697 Bug ID: 422697 Summary: Task manager doesn't group Firefox after reboot. Product: plasmashell Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: linuxguy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Task manager doesn't group Firefox after reboot. STEPS TO REPRODUCE 1. Add a panel. Add a task manager widget. Behavior -> Group by program name, open groups in popup. Disable Group only when task manager is full. Sort manually. Keep launchers separate. Show only tasks from current desktop. Show only tasks from current activity. 2. Open 20 to 50 Firefox instances. Observe that they group properly in task manager. 3. sudo reboot OBSERVED RESULT The workstation reboots properly. The Firefox instances all restart and appear as individual items in Task Manager. Task Manager does not group them at all. To get them to regroup, one must manually open every instance on the desktop and then minimize it. This is a very time consuming process if you have a large number of instances open. When you minimize the instances, Task Manager groups them properly. It appears that Task Manager must group upon a window minimize event. I think on startup after a reboot it will need to group on something else. EXPECTED RESULT After reboot all the Firefox instances should be grouped into one Task Manager item for Firefox. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32. (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.13.2 $ uname -a Linux bigboy 5.6.16-300.fc32.x86_64 #1 SMP Thu Jun 4 18:08:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ADDITIONAL INFORMATION Plasma rocks! Keep up the excellent work. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 416382] Yakuake will not toggle on screen directly left of main screen
https://bugs.kde.org/show_bug.cgi?id=416382 --- Comment #3 from daniel-other+kde...@dadosch.de --- (In reply to daniel-other+kdebug from comment #2) > for me, it now works with 5.19. Does it work now for you @Hamish? now it doesn't work again... strange. Do you have a second panel on a screen other than the main screen? Because I had removed that panel earlier and then it worked. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372912] Usability improvements for layer selection tool (R+click)
https://bugs.kde.org/show_bug.cgi?id=372912 Tymond changed: What|Removed |Added Summary|Wish - Usability|Usability improvements for |improvements for layer |layer selection tool |selection tool (R+click)|(R+click) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372912] Wish - Usability improvements for layer selection tool (R+click)
https://bugs.kde.org/show_bug.cgi?id=372912 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #3 from Tymond --- It's not really a tool, so there will be a problem where to put the setting. Also I'm not sure if comment 2 describes a proper behaviour... There is also a shortcut that selects *all* layers that result in a specific pixel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 petrk changed: What|Removed |Added Version|5.18.90 |5.19.0 --- Comment #1 from petrk --- Still an issue after 5.19 shipped on arch. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 422696] New: "Enable Bluetooth" checkbox not clickable if Bluetooth is disabled
https://bugs.kde.org/show_bug.cgi?id=422696 Bug ID: 422696 Summary: "Enable Bluetooth" checkbox not clickable if Bluetooth is disabled Product: Bluedevil Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: system tray Assignee: now...@gmail.com Reporter: sfr6...@t-online.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 129172 --> https://bugs.kde.org/attachment.cgi?id=129172&action=edit Screenshot SUMMARY In the Bluetooth system tray popup, the "Enable/Disable Bluetooth" checkbox (in the header area of the popup) is not clickable when Bluetooth is disabled. STEPS TO REPRODUCE 1. Open the Bluetooth System Tray Popup 2. Ensure that Bluetooth is disabled OBSERVED RESULT The "Enable Bluetooth" checkbox is grayed-out and not clickable (see attachment). EXPECTED RESULT The checkbox is clickable and toggling the checkbox enables Bluetooth. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.15-arch1-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415106] Popup palette colour history is not updated if paint stroke is started soon after closure
https://bugs.kde.org/show_bug.cgi?id=415106 Lynx3d changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/17e6e2841 ||c245aa16eeb000f62f3e5717db7 ||b657 Status|CONFIRMED |RESOLVED --- Comment #4 from Lynx3d --- Git commit 17e6e2841c245aa16eeb000f62f3e5717db7b657 by Mathias Wein. Committed on 09/06/2020 at 21:31. Pushed by mwein into branch 'master'. Remove old workaround for popup palette hiding Commit 591684144731c0e8516bfd065fa812ff3e5f9c00 and Commit ae734675be9f92173a9c44516a205edefb19ee97 added this to prevent picking up the new foreground color as used by closing the palette with a left-click on the canvas. The paint tools however have been refactored since then and the "TODO" is no longer present in kis_tool_freehand.cc, so remove the remains of this workaround. M +1-7libs/ui/kis_canvas_resource_provider.cpp M +0-15 libs/ui/kis_canvas_resource_provider.h M +0-7libs/ui/kis_favorite_resource_manager.h M +0-1libs/ui/kis_paintop_box.cc M +0-23 libs/ui/kis_popup_palette.cpp M +0-12 libs/ui/kis_popup_palette.h https://invent.kde.org/graphics/krita/commit/17e6e2841c245aa16eeb000f62f3e5717db7b657 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 422695] New: [Wayland] Windows Previews Disappear When An Application Has Multiple Instances Opened
https://bugs.kde.org/show_bug.cgi?id=422695 Bug ID: 422695 Summary: [Wayland] Windows Previews Disappear When An Application Has Multiple Instances Opened Product: lattedock Version: 0.9.11 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- Flags: Backport-, Brainstorm-, corner_case-, Translation_missing- SUMMARY When you're under Wayland session and got more than 1 open instance of any application, go to the icon at the icon-only task manager, left click on it, it shows for about 1 second, then disappear almost instantly, not allowing either close it with the mouse cursor, nor selecting and changing between the opened instances. STEPS TO REPRODUCE 1. Login to the Wayland session. 2. Open 2 windows of Firefox (for example). 3. Move the cursor to the icon, click on it. OBSERVED RESULT The preview of the two windows/instances, is showed for about half second or a second, then disappears with no option to be interacted with. EXPECTED RESULT The previews should be accessible and interactive with, when you click on them, they should be there until you move the cursor out of the space or you click on other part. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.6.15 (available in About System) KDE Plasma Version: 5.19 KDE Frameworks Version: 5.70 Qt Version: 5.15 ADDITIONAL INFORMATION This bug has been present since the update to Plasma 5.18 LTS. Sorry for the delay in the report :(. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 422694] New: Allow changing IP range for shared connections
https://bugs.kde.org/show_bug.cgi?id=422694 Bug ID: 422694 Summary: Allow changing IP range for shared connections Product: plasma-nm Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: k...@markuspi.de Target Milestone: --- SUMMARY nmcli allows specifying custom IP ranges for shared connections. plasma-nm does not support this and will overwrite these settings STEPS TO REPRODUCE 1. Create a new shared ethernet or wifi connection using cli or gui 2. Change ip range using cli: `nmcli connection modify $ID +ipv4.addresses 192.168.5.1/24` 4. Observe change took place: `nmcli connection show $ID | grep ipv4.adresses` yields `ipv4.addresses: 192.168.5.1/24` 3. Activate connection using cli or gui 4. Observe dnsmasq is launched with correct ip: `ps aux | grep dnsmasq` yields ... "--listen-address=192.168.5.1" ... TRIGGER BUG: 5. Perform any modification in the gui (eg renaming the connection) and press apply OBSERVED RESULT: 6. `nmcli connection show $ID | grep ipv4.adresses` yields "ipv4.addresses: --" 7. dnsmasq uses default IP range of 10.42.0.1 EXPECTED RESULT: plasma-nm should not delete ipv4.addresses 6. `nmcli connection show $ID | grep ipv4.adresses` yields "ipv4.addresses: 192.168.5.1/24" 7. dnsmasq still uses the specified range SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION NetworkManager version: 1.22.10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417052] The default size of the window to be opened when opening a file in window mode is too small.
https://bugs.kde.org/show_bug.cgi?id=417052 --- Comment #2 from ferweer --- (In reply to Tymond from comment #1) > It is a bit small, but on the other hand, if it's too big to fit on the > screen, it would be difficult to make it smaller... and with fullHD devices > with 150% UI scaling, and the new Android tablets, it might be better to > leave it as it is. > > > I wish this information could be easily copied by pressing a button or > > something. > > Go to Help -> Show system information for bug reports. hi. just bit? im don't think so. umm but maybe, im think it is only im think. but therefore im suggested option for this method. 200px,500px,1024px,etc. yes you said right, now krita action 257-210px. for easy file use? only small devices and big display user. why option = that is krita can take free line of flow for extensive user. im think. and thanks! im don't knew before for this is option dialog! yes, im can easy copy for system infomation. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 422693] New: minify hover text in systray by removing "connected to"
https://bugs.kde.org/show_bug.cgi?id=422693 Bug ID: 422693 Summary: minify hover text in systray by removing "connected to" Product: plasma-nm Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: daniel-other+kde...@dadosch.de Target Milestone: --- SUMMARY Currently, the hover text of the nm applet in the systray shows strings in this format: : Connected to (see https://invent.kde.org/plasma/plasma-nm/-/blob/master/libs/declarative/networkstatus.cpp#L220 I suggest removing the word "Connected to" to make the hover text smaller and look nicer with longer SSIDs. The "normal" state of networks is "connected," so IMHO those words aren't needed in this normal state. What do you think? (If there is a consent to do this, I can quickly do a MR) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 420887] Available connections are mixed with saved connections without order
https://bugs.kde.org/show_bug.cgi?id=420887 daniel-other+kde...@dadosch.de changed: What|Removed |Added CC||daniel-other+kdebug@dadosch ||.de --- Comment #1 from daniel-other+kde...@dadosch.de --- possible duplicate of https://bugs.kde.org/show_bug.cgi?id=419288 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 380901] Place visibility-toggling menu items under the View menu, when present
https://bugs.kde.org/show_bug.cgi?id=380901 Nate Graham changed: What|Removed |Added Resolution|--- |MOVED Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #5 from Nate Graham --- I agree with your original proposal. Putting all actions that save their state in the Settings menu is a fairly implementation-centric UI. I think a user-focused UI of location actions based on function makes more sense and this is in fact what we already generally do. However I'm afraid there's nothing actionable in this bug report at the KXMLGui level. View actions that are common to many KDE apps are already all in the View menu; everything you're proposing will require changes to the individual apps themselves, as those items are specific to those apps. You'll want to open a new bug report for each app. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422680] [Wayland] Notifications Timer Animation Is Not Showing
https://bugs.kde.org/show_bug.cgi?id=422680 --- Comment #3 from Alberto Díaz López --- Created attachment 129171 --> https://bugs.kde.org/attachment.cgi?id=129171&action=edit Plasma 5.19 Notifications' Animation Timer Not Showing Screenshot showing the issue of not showing the animation timer at the notifications on Plasma 5.19, since 5.18 LTS is like this, sorry for the delay reporting the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401012] keyboard indicator text is barely visible in system tray settings when using a dark theme for Plasma
https://bugs.kde.org/show_bug.cgi?id=401012 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #7 from Patrick Silva --- This issue is still reproducible on X11 when Breeze global theme and Breeze Dark plasma style are used. Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422680] [Wayland] Notifications Timer Animation Is Not Showing
https://bugs.kde.org/show_bug.cgi?id=422680 --- Comment #2 from Alberto Díaz López --- (In reply to Nate Graham from comment #1) > Are you using a non-default icon and/or plasma theme? Can you share a > screensoht of how it looks? You can generate a notification by running > `notify-send foo bar`. Nope, I'm using Breeze Dark, I've never used a non-default icon or Plasma theme. I add a screenshot so you can see and figure it out better. Thank you very much for the quick response :). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410829] [krita-sprint-2019 bug/discussions] Annoying autosave on-canvas notifications while in canvas-only mode
https://bugs.kde.org/show_bug.cgi?id=410829 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #4 from Tymond --- I agree with comment 2. We could first make the change in notifications and add the checkbox Boud mentioned in comment 1, and then check if there is anything more needed. -- You are receiving this mail because: You are watching all bug changes.
