[kwin] [Bug 429843] New: Jarring black bars while changing desktops with a tall screen
https://bugs.kde.org/show_bug.cgi?id=429843 Bug ID: 429843 Summary: Jarring black bars while changing desktops with a tall screen Product: kwin Version: 5.20.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: emi...@diademiemi.me Target Milestone: --- Created attachment 133746 --> https://bugs.kde.org/attachment.cgi?id=133746=edit Video of all screens while changing desktops. SUMMARY Changing desktops with the Slide effect creates jarring black bars if one screen is vertical. STEPS TO REPRODUCE 1. Have one vertical screen, taller than the other screens 2. Change desktop with the Slide animation 3. OBSERVED RESULT The horizontal screens have black bars which are very jarring. EXPECTED RESULT I would expect the horizontal screens to slide slower than the tall one. I understand why it currently does this, the black bars are there to make the screens "taller" so the animation can be in sync, but it looks very distracting. Operating System: Gentoo Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.11-gentoo OS Type: 64-bit Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics ADDITIONAL INFORMATION See attachment for a recording of this in action. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418602] plasmashell aborted when logging in to Plasma on Wayland with the message "The Wayland connection experienced a fatal error: Protocol error"
https://bugs.kde.org/show_bug.cgi?id=418602 torokat...@gmail.com changed: What|Removed |Added CC||torokat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429836] Unable To Open Krita File After Importing Jpeg Into Pattern Section of Fill Layer
https://bugs.kde.org/show_bug.cgi?id=429836 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- This sounds like a crash. Can you find the crash log at: C:\Users\(your-username)\AppData\Local\kritacrash.log and post the content here? If it's quite large then a link to a Pastebin store may be more convenient. I've tested this situation with the 4.4.1 Linux appimage and the 4.4.1 Windows installed package and I don't get a crash. With both .png and .jpg files imported as patterns during selection of Pattern fill of a Fill Layer, the result looks normal but after Saving as .kra and then opening in a new session of krita, the Fill layer shows no pattern. The reason for this to do with the reference pointer for the pattern file in the .filterconfig file of the layer data inside the .kra file. That may need a separate bug report for the failure of layer content aspect. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429103] Digikam 7.1.0 does not start up, when using macos big sur
https://bugs.kde.org/show_bug.cgi?id=429103 --- Comment #20 from Martin Neuß --- Thank you very much for your committment to digigkam. one question: is it possible to direct some funds directly to you? (you are working for us, at least there should be some compensation) martin -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 429815] #8831937ffe4 broke compatiblity with older Qt5 versions
https://bugs.kde.org/show_bug.cgi?id=429815 --- Comment #2 from RJVB --- I don't think we have to be concerned with the potential additional overhead of creating a copy of the string as `toString()` appears to do? I don't see anything about a new cast operator in the Qt 5.15 documentation for QStringRef nor any new overloads of QVersionNumber::fromString() that would be used here so it's a bit of a mystery to me why the code builds as is. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416257] mailto feature does not work anymore
https://bugs.kde.org/show_bug.cgi?id=416257 Kai Uwe Broulik changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||7da3e583cab231b7505acb3dbc6 ||ee63c6d557929 --- Comment #4 from Kai Uwe Broulik --- Git commit 7da3e583cab231b7505acb3dbc6ee63c6d557929 by Kai Uwe Broulik. Committed on 30/11/2020 at 10:50. Pushed by broulik into branch 'master'. [Location Runner] Also explicitly look for URL scheme handlers KProtocolInfo handles only protocols KIO knows but apps can also register to be a URL scheme handler independently of this. This patch makes the location runner also query for the preferred URL scheme handler when no known protocol is found. It also prefers the scheme handler over the helper protocol since a service has a name. While at it, also format the protocol "exec" using DesktopExecParser to avoid showing placeholders like '%u' to the user. Also use PreferLocalFile for "go to". M +22 -9runners/locations/locationrunner.cpp https://invent.kde.org/plasma/plasma-workspace/commit/7da3e583cab231b7505acb3dbc6ee63c6d557929 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429666] Unresponsive Timeline
https://bugs.kde.org/show_bug.cgi?id=429666 --- Comment #5 from Jean-Baptiste Mardelle --- In git master and 20.12, there is a warning when trying to play timeline if project monitor is hidden -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429666] Unresponsive Timeline
https://bugs.kde.org/show_bug.cgi?id=429666 --- Comment #4 from Jean-Baptiste Mardelle --- Created attachment 133745 --> https://bugs.kde.org/attachment.cgi?id=133745=edit monitor-missing user info on hidden project monitor -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 429803] Import Audio File Metadata does not work since version 3.3
https://bugs.kde.org/show_bug.cgi?id=429803 --- Comment #1 from jolu4...@gmail.com --- Does not work with Tellico 3.3.4 on a fresh installation of openSUSE Tumbleweed as well. KDE Frameworks 5.76.0 Qt 5.15.2 Linux 5.9.10-1-default -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 429815] #8831937ffe4 broke compatiblity with older Qt5 versions
https://bugs.kde.org/show_bug.cgi?id=429815 --- Comment #1 from Milian Wolff --- please fix it then -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 429842] New: Crash resizing Elisa on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=429842 Bug ID: 429842 Summary: Crash resizing Elisa on kwin_wayland Product: elisa Version: 20.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: elisa (20.08.3) Qt Version: 5.15.1 Frameworks Version: 5.76.0 Operating System: Linux 5.4.0-54-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.20 -- Information about the crash: Multiple times after starting Elisa, resizing the window caused a crash. The, "Scanning music" notification was displaying; The view was on a selected song ready to play, but not playing yet; The playlist was populated with 25 tracks and overflowing the view, producing a scrollbar; There was album art correctly displayed in the central view and as the background of the "header" view. After a third attempt, waiting for the, "Scanning music" notification to finish and resizing the window did not cause another crash. The crash can be reproduced sometimes. -- Backtrace: Application: Elisa (elisa), signal: Aborted [New LWP 502974] [New LWP 502975] [New LWP 502976] [New LWP 502977] [New LWP 502978] [New LWP 502979] [New LWP 502980] [New LWP 502981] [New LWP 502982] [New LWP 502983] [New LWP 502984] [New LWP 502985] [New LWP 502990] [New LWP 502992] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x555b21e8d554) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7f3a0f315880 (LWP 502971))] Thread 15 (Thread 0x7f39ceffd700 (LWP 502992)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f3a141c9859 in __GI_abort () at abort.c:79 #6 0x7f3a1460bbe7 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7f39ceffc9b0, msg=msg@entry=0x7f3a0e7ba0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #8 0x7f3a0e6fecd5 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlogging.h:90 #9 QtWaylandClient::QWaylandDisplay::checkError (this=) at qwaylanddisplay.cpp:204 #10 0x7f3a0e70f671 in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) (this=0x555b2127a220, queue=0x555b216412d0, condition=..., timeout=timeout@entry=100) at qwaylanddisplay.cpp:260 #11 0x7f3a0e716628 in QtWaylandClient::QWaylandWindow::waitForFrameSync (this=0x555b219e7af0, timeout=100) at /usr/include/c++/9/new:174 #12 0x7f3a070fbdda in QtWaylandClient::QWaylandGLContext::swapBuffers (this=0x555b21afe290, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:492 #13 0x7f3a15105a51 in QOpenGLContext::swapBuffers (this=0x555b21b96fa0, surface=) at kernel/qopenglcontext.cpp:1120 #14 0x7f3a1338ae2c in QSGRenderThread::syncAndRender (this=0x555b21e76ac0, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:870 #15 0x7f3a1338eba7 in QSGRenderThread::run (this=0x555b21e76ac0) at scenegraph/qsgthreadedrenderloop.cpp:1043 #16 0x7f3a14646b1c in QThreadPrivate::start (arg=0x555b21e76ac0) at thread/qthread_unix.cpp:329 #17 0x7f3a12c44609 in start_thread (arg=) at pthread_create.c:477 #18 0x7f3a142c6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f39cf7fe700 (LWP 502990)): #0 __GI___libc_read (nbytes=10, buf=0x7f39cf7fdb5e, fd=30) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=30, buf=0x7f39cf7fdb5e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f3a0fb78975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f3a122bb416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f3a122bbeb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f3a122bbf70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f3a122ca11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f3a0fba772c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f3a12c44609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3a142c6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f39e27fc700 (LWP 502985)): #0 0x7f3a1233c095 in g_source_ref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3a1233c168 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3a1233daff in g_main_context_check () from
[Breeze] [Bug 369016] Remove pixel on top of tab bar when menubar is off
https://bugs.kde.org/show_bug.cgi?id=369016 Friedrich W. H. Kossebau changed: What|Removed |Added Product|konversation|Breeze Version|unspecified |5.20.3 Component|general |QStyle CC||kosse...@kde.org Assignee|konversation-de...@kde.org |unassigned-b...@kde.org --- Comment #2 from Friedrich W. H. Kossebau --- This is an issue with the Breeze style it seems. That one calculates a region for the tab bar element in a QTabWidget which has a margin of 1 to the border: see Style::tabWidgetTabBarRect() at https://invent.kde.org/plasma/breeze/-/blob/master/kstyle/breezestyle.cpp#L1893 And thus as result also means that a with a tabbar placed next to the screen border we do not get the infinite tabs which allow throwing the mouse against the screen edge and clicking the tab easily, but instead enforces to properly target them instead (something with Fitt's law and stuff). With styles like Plastique, Windows or QtCurve that is not an issue. I do not think we should try to workaround this in Konversation. Instead this is a principle issue with the Breeze style. That 1 pixel margin seems wanted for design issues, to not blend the outshape lines with that of neighbouring elements I guess. Yet to help with that case of screen edges, the active tab range should still include also that margin pixels IMHO. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 359280] Parts of a link get hidden by line break
https://bugs.kde.org/show_bug.cgi?id=359280 Christian Boltz changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Christian Boltz --- Testing with the latest Konversation (1.7.7) shows that this bug has indeed been accidently ;-) fixed in the meantime. Whoever did the fix - thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429629] Crash on clicking at an item in Resources Manager
https://bugs.kde.org/show_bug.cgi?id=429629 --- Comment #6 from Vladimir Savic --- (In reply to Tymond from comment #5) > Could you please elaborate on this: > > > What is that everything that you "nuked" (I guess removed :) )? The whole > resource folder? The bundle? The cache database? Sorry. I was a bit more poetic (in my very limited artistic sense) than precise here. :) By "nuking" I meant removing: .local/share/krita/ .config/kritadisplayrc .config/kritarc .local/share/krita.log .local/share/krita-sysinfo.log > And what is it that you > reimported - just the bundle, I guess? In which way, through the GUI (in > which version, still master?) or...? I didn't even know it is possible to import bundles the other way than GUI. Is there? It is still the master. I'm compiling it daily. Right now I'm at "Version: 5.0.0-prealpha (git 379ace5)". -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 428909] helgrind: need to intercept duplicate libc definitions for Fedora 33
https://bugs.kde.org/show_bug.cgi?id=428909
--- Comment #17 from Paul Floyd ---
> Please change this into configure tests that verify whether pthreads
> functions exist in libpthread, libc or in both.
Hi Bart
That's a good idea, but the devil is in the details. I have two fairly big
questions.
1) which functions to test and
2) how to test for them
For point 1, for the platforms that I know of at the moment
Fedora 33
There are 34 pthread functions in libc and 72 in libpthread (28 only in libc,
66 only in libpthread and 6 in both).
(To count these I used
nm /lib64/libc.so.6 | grep " T " | grep " pthread" | sed 's/@.*// | awk '{print
$3}' | sort -u > c
and
nm /lib64/libpthread.so.0 | grep " T " | grep " pthread" | sed 's/@.*// | awk
'{print $3}' | sort -u > p
to generate two text file lists c and p for libc and libpthread respectively,
then I used combinations of
comm c p -2 -3 | wc
comm c p -1 -3 | wc
comm c p -1 -2 | wc
to count libc, libpthread and both.
This is a bit simplistic as I'm not counting W symbols).
For comparison, openSuSE Leap 15.2 which uses glibc 2.26 has 7 only in libc 70
only in libpthread and 24 in both
Linux MUSL, everything is in /lib/ld-musl-x86_64.so.1. libc is a symlink to
this and there is no libpthread.
macOS I don't quite understand what is where, on my old macbook there is some
stuff in /usr/lib/libSystem.B.dylib and /usr/lib/libpthread.dylib is just a
symlink to this.
Solaris, libc contains everything and libpthread exists but just contains
absolute symbols.
FreeBSD, pthread functions are in libpthread but sem functions are in libc.
Next, question b) how to test this? I'm no expert in autoconf. It seems to me
that the AC_CHECK_LIB and AC_SEARCH_LIBS are not suitable since they don't
exclude libc, so this would require full AC_LINK_IFELSE style tests using
-nostlib and then either -lc or -lpthread, for each required platform
variation.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 429298] No window decoration is highlighted in Window Decorations KCM
https://bugs.kde.org/show_bug.cgi?id=429298 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/492 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 429829] no tooltip on PC3 ToolButton
https://bugs.kde.org/show_bug.cgi?id=429829 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403432] [RFE] systemd password agent for KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=403432 Stefan Schmid changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Stefan Schmid --- (In reply to Justin Zobel from comment #6) > I believe this is fixed. I run systemctl stop ssh in my konsole and it pops > up asking me to authenticate. > > If I understand correctly this is what you want? No, this is a polkit action. Please have a look at the website which is linked in the field "URL", it explains what it is about. When a service unit starts (for whatever reason) and the service it contains expects an input, systemd asks for this input via the available Password Agent and then passes it on to the service. Gnome has its own Password Agent integrated in the desktop environment, only KDE Plasma does not have one. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420598] kendlive crashes upon start on Ubuntu 20.4
https://bugs.kde.org/show_bug.cgi?id=420598 --- Comment #7 from Olof Andersson --- (In reply to emohr from comment #3) > Delete kdenlive-appimagerc: https://community.kde.org/Kdenlive/Configuration > > Please try with the current Kdenlive AppImage version 20.08.2 to see if > there are any packaging issues > https://download.kde.org/stable/kdenlive/20.08/linux/ > > If the problem/issue doesn't occur when using the AppImage, then it's your > configuration or packaging. Ahh, first I didn't see that you pointed out an earlier version. Now I tested with 20.08.2 instead of 20.08.3. 20.08.2 seems to work without crashing! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420598] kendlive crashes upon start on Ubuntu 20.4
https://bugs.kde.org/show_bug.cgi?id=420598 --- Comment #6 from Olof Andersson --- Comment on attachment 133744 --> https://bugs.kde.org/attachment.cgi?id=133744 kdenlive crash log I still get the same crash after deleting kdenlive-appimagerc and downloading kdenlive-20.08.3-x86_64.appimage wget https://download.kde.org/stable/kdenlive/20.08/linux/kdenlive-20.08.3-x86_64.appimage chmod +x kdenlive-20.08.3-x86_64.appimage rm ~/.config/kdenlive-appimagerc ./kdenlive-20.08.3-x86_64.appimage see attached crash log -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420598] kendlive crashes upon start on Ubuntu 20.4
https://bugs.kde.org/show_bug.cgi?id=420598 --- Comment #5 from Olof Andersson --- Created attachment 133744 --> https://bugs.kde.org/attachment.cgi?id=133744=edit kdenlive crash log -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 391698] Command line arguments ignored
https://bugs.kde.org/show_bug.cgi?id=391698 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/konversation/-/merge_requests/34 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429841] New: Spectacle takes screenshot automatically when "On Click" is set
https://bugs.kde.org/show_bug.cgi?id=429841 Bug ID: 429841 Summary: Spectacle takes screenshot automatically when "On Click" is set Product: Spectacle Version: 20.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: gudv...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When you open Spectacle app it takes screenshot even if "On Click" is set so whenever I try to change its configuration it takes screenshot and I need to delete it after. STEPS TO REPRODUCE 1. Launch spectacle 2. Set Delay: "On Click" = true 3. Close spectacle 4. Launch spectacle OBSERVED RESULT Screenshot of the whole screen space is taken EXPECTED RESULT No screenshot SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.4.79-1-lts OS Type: 64-bit ADDITIONAL INFORMATION It may be related to #427205 because it seems that spectacle ignores settings from previous launch. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 429799] kdoctools build if using zsh, antigen and zsh-autosuggestions
https://bugs.kde.org/show_bug.cgi?id=429799 --- Comment #2 from Srevin Saju --- I have attached the build.log and cmake.log for your reference. It seems like CMAKE searches my $PATH for DocBookXSL; my $PATH includes ~/.antigen/.../zsh-autosuggestions which might be a pointer. I am not sure why it selects ~/.antigen/.../zsh-autosuggestions. I can clean build it, if I pop ~/.antigen/.../zsh-autosuggestions from $PATH, but it might imply that some checks or the path to DocBookXSL is to be refined perhaps https://people.sugarlabs.org/~srevinsaju/dl/cmake-2020-11-30.log https://people.sugarlabs.org/~srevinsaju/dl/build-2020-11-30.log -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 429840] New: Old resource assingments not removed for rescheduled tasks
https://bugs.kde.org/show_bug.cgi?id=429840 Bug ID: 429840 Summary: Old resource assingments not removed for rescheduled tasks Product: calligraplan Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dag.ander...@kdemail.net Reporter: dag.ander...@kdemail.net Target Milestone: --- SUMMARY When recalculating started projects and tasks is rescheduled to start later, the old resource assignments are not removed. 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.
[kdevelop] [Bug 426070] Deadlock in ~QQmlEngine() inside ~WelcomePageWidget() when exiting KDevelop right after starting it - before Welcome Page is loaded
https://bugs.kde.org/show_bug.cgi?id=426070 Kevin Funk changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-75777 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 408201] Enhancement: Text tool: Allow marking of text
https://bugs.kde.org/show_bug.cgi?id=408201 DarkTrick changed: What|Removed |Added Version|19.04 |20.08 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 403646] Enable "Select None" through click on non canvas area
https://bugs.kde.org/show_bug.cgi?id=403646 DarkTrick changed: What|Removed |Added Status|REPORTED|RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408200 Resolution|--- |DUPLICATE --- Comment #1 from DarkTrick --- For whatever reasons I reported this twice: https://bugs.kde.org/show_bug.cgi?id=408200 I'll close this one and keep the other. *** This bug has been marked as a duplicate of bug 408200 *** -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 408200] Enhancement: Unselect selection, if clicked outside the canvas (in the grey area)
https://bugs.kde.org/show_bug.cgi?id=408200 DarkTrick changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=403646 --- Comment #1 from DarkTrick --- *** Bug 403646 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 408200] Enhancement: Unselect selection, if clicked outside the canvas (in the grey area)
https://bugs.kde.org/show_bug.cgi?id=408200 DarkTrick changed: What|Removed |Added Version|19.04 |20.08 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 403646] Enable "Select None" through click on non canvas area
https://bugs.kde.org/show_bug.cgi?id=403646 DarkTrick changed: What|Removed |Added Version|unspecified |20.08 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 199326] System Settings should write default application changes for non-KDE apps
https://bugs.kde.org/show_bug.cgi?id=199326 Bohdan Danylchenko changed: What|Removed |Added CC||exp@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429382] black icon with dark theme for Windows build.
https://bugs.kde.org/show_bug.cgi?id=429382 --- Comment #1 from Gary Wang --- Reinstalled craft with windows-msvc2019_64-cl ABI, and now I'm able to get Kate build under Windows. Adding `QIcon::setThemeName()` call to set `breeze-dark` icon theme is not enough to fix this bug. There are still two other steps need to be done: 1. Since current windows package doesn't contains breeze-dark icon theme like what Kdenlive did (`bin\data\icons\` folder doesn't exist at all), we also need to package the breeze and breeze-dark icon theme to the installer and install them to the right place so we can use it. 2. In kateapp.cpp or somewhere else, we also need to tell the program to load the icon theme files (.rcc files) like what Kdenlive did in https://github.com/KDE/kdenlive/blob/93a40647ad91fc8f7f606f642cd000cfa074b2d5/src/main.cpp#L110 . After doing these three steps, Kate will be able to use breeze-dark icon theme when the breeze-dark application theme applied. I'd like to send a patch but I'm not quite sure about how to make the installer package these icon theme assets, btw, the output of cl.exe is not readable when building under non-English environment (eg. `error C2248: ��QString::QString��: �� private ��Ա(�ڡ�QString��)`), so sorry I couldn't provide a patch to fix this issue, but let me know if you need any additional information, I'd love to help you fix this issue. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397873] Regional Settings are not easy to configure and language gets changed by accident
https://bugs.kde.org/show_bug.cgi?id=397873 britalme...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from britalme...@gmail.com --- Isn't it easier if whomever designed this workflow verifies it? This is a design issue that should be present for anyone with a fresh install of kde5, it's not platform dependent. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 428957] Elisa constantly emitting org.mpris.MediaPlayer2.Player.Seeked
https://bugs.kde.org/show_bug.cgi?id=428957 --- Comment #5 from David Redondo --- Yes, optimally we would only emit Seeked if the playback position is manually changed and not during normal playback, see the quoted spec. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429762] cannot paste files/folders via context menu
https://bugs.kde.org/show_bug.cgi?id=429762 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/129 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429839] Running JavaScript files leads to an error
https://bugs.kde.org/show_bug.cgi?id=429839 --- Comment #1 from Kai Uwe Broulik --- Seems to happen because the file is marked +x but that didn't cause problems earlier. I don't get why JS files are treated as "executable" anyway. What is it supposed to do? Spawn a NodeJS instance with them? -- You are receiving this mail because: You are watching all bug changes.
