[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #16 from Philippe Waroquiers --- (In reply to Stas Sergeev from comment #15) > (In reply to Philippe Waroquiers from comment #14) > > So, IMO, the easiest is to use the client requests > > Which ones? > I did all the modifications you asked for, they > all in my latest test-case. > > > (the downside of this is that this implies modification of the code). > > No, that downside is that you didn't suggest > any further modifications. :) Here is the new part of the doc describing these false positives: As explained above, Memcheck maintains 8 V bits for each byte in your process, including for bytes that are in shared memory. However, the same piece of shared memory can be mapped multiple times, by several processes or even by the same process (for example, if the process wants a read-only and a read-write mapping of the same page). For such multiple mappings, Memcheck tracks the V bits for each mapping independently. This can lead to false positive errors, as the shared memory can be initialised via a first mapping, and accessed via another mapping. The access via this other mapping will have its own V bits, which have not been changed when the memory was initialised via the first mapping. The bypass for these false positives is to use Memcheck's client requests VALGRIND_MAKE_MEM_DEFINED and VALGRIND_MAKE_MEM_UNDEFINED to inform Memcheck about what your program does (or what another process does) to these shared memory mappings. Alternatively, you can also use VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE. So, the easiest is to use VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE. If you still want to have proper error detection, then you must ensure that whenever your program initialises (or uninitialises) a byte, that the equivalent V bits are modified the same way via VALGRIND_MAKE_MEM_*DEFINED in the other(s) mapping. For example, if you have a read mapping and a write mapping of a page, after each modification via the "write" mapping, you have to 'copy' the V bits from the write mapping to the read mapping. That might not be straightforward to do, in particular if you have multiple threads (you probably need a critical section around the write operations) or processes (this will even be more complex, as you will probably need a side channel to inform all other processes about what was done). This logic is of course application dependent. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387393] akonadiserver 17.08.03 crashed during idle
https://bugs.kde.org/show_bug.cgi?id=387393 --- Comment #6 from Maarten ter Huurne --- Created attachment 114970 --> https://bugs.kde.org/attachment.cgi?id=114970=edit New crash information added by DrKonqi akonadiserver (5.7.3) using Qt 5.9.4 - What I was doing when the application crashed: I wasn't interacting with akonadi at all when it crashed. It might have been fetching mail in the background. Kontact was open. I never had this problem until I few days ago, but now there are two crashes. I wonder if this is a coincidence or a recent change increased the chance of this crash occurring. The last system (openSUSE Leap 15) update on 2018-09-12 installed the following packages: nvidia-gfxG04-kmp-default|390.87_k4.12.14_lp150.11-lp150.10.1|x86_64 nvidia-glG04|390.87-lp150.10.1|x86_64 nvidia-computeG04|390.87-lp150.10.1|x86_64 x11-video-nvidiaG04|390.87-lp150.10.1|x86_64 discover|5.12.6-lp150.2.3.1|x86_64 kde-user-manager|5.12.6-lp150.2.3.1|x86_64 kinfocenter5|5.12.6-lp150.3.3.1|x86_64 kscreen5|5.12.6-lp150.2.3.1|x86_64 kscreenlocker|5.12.6-lp150.2.3.1|x86_64 libKScreenLocker5|5.12.6-lp150.2.3.1|x86_64 libksysguard5|5.12.6-lp150.2.3.1|x86_64 libksysguard5-helper|5.12.6-lp150.2.3.1|x86_64 metatheme-breeze-common|5.12.6-lp150.2.3.1|x86_64 milou5|5.12.6-lp150.2.3.1|x86_64 plasma-nm5|5.12.6-lp150.3.3.1|x86_64 plasma5-addons|5.12.6-lp150.2.3.1|x86_64 plasma5-integration-plugin|5.12.6-lp150.2.3.1|x86_64 discover-lang|5.12.6-lp150.2.3.1|noarch kde-user-manager-lang|5.12.6-lp150.2.3.1|noarch kinfocenter5-lang|5.12.6-lp150.3.3.1|noarch kscreen5-lang|5.12.6-lp150.2.3.1|noarch kscreenlocker-lang|5.12.6-lp150.2.3.1|noarch kwin5|5.12.6-lp150.2.3.1|x86_64 libksysguard5-lang|5.12.6-lp150.2.3.1|noarch gtk3-metatheme-breeze|5.12.6-lp150.2.3.1|noarch milou5-lang|5.12.6-lp150.2.3.1|noarch plasma-nm5-lang|5.12.6-lp150.3.3.1|noarch plasma5-addons-lang|5.12.6-lp150.2.3.1|noarch plasma5-integration-plugin-lang|5.12.6-lp150.2.3.1|noarch kwin5-lang|5.12.6-lp150.2.3.1|noarch plasma5-workspace-libs|5.12.6-lp150.2.3.1|x86_64 ksysguard5|5.12.6-lp150.2.3.1|x86_64 gtk2-metatheme-breeze|5.12.6-lp150.2.3.1|noarch plasma-nm5-pptp|5.12.6-lp150.3.3.1|x86_64 plasma-nm5-openvpn|5.12.6-lp150.3.3.1|x86_64 plasma-nm5-openconnect|5.12.6-lp150.3.3.1|x86_64 plasma5-workspace|5.12.6-lp150.2.3.1|x86_64 khotkeys5|5.12.6-lp150.2.3.1|x86_64 ksysguard5-lang|5.12.6-lp150.2.3.1|noarch plasma5-workspace-lang|5.12.6-lp150.2.3.1|noarch khotkeys5-lang|5.12.6-lp150.2.3.1|noarch plasma5-desktop|5.12.6-lp150.3.3.1|x86_64 plasma5-desktop-lang|5.12.6-lp150.3.3.1|noarch plasma5-session|5.12.6-lp150.2.3.1|noarch plasma5-session-wayland|5.12.6-lp150.2.3.1|noarch While there are several KDE packages in that list, I don't think akonadiserver would depends on the listed packages. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f30d3ea26c1 in __GI_abort () at abort.c:79 [...] #9 0x7f30d3eeac43 in malloc_printerr (action=, str=0x7f30d3fed5d8 "double free or corruption (!prev)", ptr=, ar_ptr=) at malloc.c:5428 #10 0x7f30d3eec549 in _int_free (av=av@entry=0x7f30d421fc20 , p=, p@entry=0x564dce831ce0, have_lock=have_lock@entry=1) at malloc.c:4170 #11 0x7f30d3eef250 in _int_realloc (av=av@entry=0x7f30d421fc20 , oldp=oldp@entry=0x564dce831ce0, oldsize=oldsize@entry=4128, nb=8208) at malloc.c:4676 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398652] New: Add possibility to change the order of opened tabs if only two tabs are opened
https://bugs.kde.org/show_bug.cgi?id=398652 Bug ID: 398652 Summary: Add possibility to change the order of opened tabs if only two tabs are opened Product: kate Version: 18.08.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: aryan100jan...@gmail.com Target Milestone: --- When more than 2 tabs are open, it is possible to change the order, but it is not possible in case of 2 tabs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396179] Krita crashing randomly
https://bugs.kde.org/show_bug.cgi?id=396179 --- Comment #25 from Mohammad --- I made a new user on my laptop (same laptop that crashes) and Krita runs just fine on it. No crashes, bugs or anything. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398412] Discover crashes at startup with memory corruption ("corrupted size vs. prev_size")
https://bugs.kde.org/show_bug.cgi?id=398412 Dr. Chapatin changed: What|Removed |Added CC||sibbe.ra...@gmail.com --- Comment #20 from Dr. Chapatin --- *** Bug 398639 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398639] Discover crash on Launch
https://bugs.kde.org/show_bug.cgi?id=398639 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 398412 *** -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 398651] New: Drop down to select an user account is vertically bigger than normal
https://bugs.kde.org/show_bug.cgi?id=398651 Bug ID: 398651 Summary: Drop down to select an user account is vertically bigger than normal Product: policykit-kde-agent-1 Version: 5.13.90 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: polkit-kde-authentication-agent-1 Assignee: jrez...@redhat.com Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 114969 --> https://bugs.kde.org/attachment.cgi?id=114969=edit screenshot See the screenshot taken on Arch Linux running plasma 5.14 beta. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398650] New: shifting to different part of the timeline crashes kdenlive
https://bugs.kde.org/show_bug.cgi?id=398650 Bug ID: 398650 Summary: shifting to different part of the timeline crashes kdenlive Product: kdenlive Version: 17.08.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: profetik...@outlook.com Target Milestone: --- Left app open overnightcame back to it and when I move to a different part of the timeline, the preview video has funky colors/bars that come on the preview screen...Here is an example using a screen share vid software. https://drive.google.com/file/d/1OutzIx24mFBzNfHlCq4BUU1l9clqhgBs/view Application: kdenlive (17.08.3) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: KDE neon LTS User Edition 5.12 -- Information about the crash: The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generated Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398649] New: New s390x z13 support doesn't build with older gcc/binutils
https://bugs.kde.org/show_bug.cgi?id=398649 Bug ID: 398649 Summary: New s390x z13 support doesn't build with older gcc/binutils Product: valgrind Version: 3.14 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- Fairly old gcc/binutils might not have z13 support. But there are no configure checks for this. This impacts the code in s390x_dirtyhelper_vec_binop: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../include -I../VEX/pub -I../VEX/pub -DVGA_s390x=1 -DVGO_linux=1 -DVGP_s390x_linux=1 -DVGPV_s390x_linux_vanilla=1 -Ipriv -m64 -O2 -finline-functions -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wold-style-declaration -fno-stack-protector -fno-strict-aliasing -fno-builtin -fomit-frame-pointer -Wbad-function-cast -fstrict-aliasing -g -pipe -Wall --param=ssp-buffer-size=4 -march=z9-109 -mtune=z10 -MT priv/libvex_s390x_linux_a-guest_s390_helpers.o -MD -MP -MF priv/.deps/libvex_s390x_linux_a-guest_s390_helpers.Tpo -c -o priv/libvex_s390x_linux_a-guest_s390_helpers.o `test -f 'priv/guest_s390_helpers.c' || echo './'`priv/guest_s390_helpers.c priv/guest_s390_helpers.c: In function 's390x_dirtyhelper_vec_binop': priv/guest_s390_helpers.c:2505: error: unknown register name 'v18' in 'asm' priv/guest_s390_helpers.c:2505: error: unknown register name 'v17' in 'asm' priv/guest_s390_helpers.c:2505: error: unknown register name 'v16' in 'asm' And the new testcases vector, lsc2 and ppno. When those are behind some configure check (I haven't figured out which one yet, but just disabled that code) things seem to work fine (for any non z13 code of course, but it is not expected any z13 code runs on such old setups). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398612] freefilesystem polling rate too high for !file URI?
https://bugs.kde.org/show_bug.cgi?id=398612 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398648] New: Magic Lamp minimize doesn't apply Blur
https://bugs.kde.org/show_bug.cgi?id=398648 Bug ID: 398648 Summary: Magic Lamp minimize doesn't apply Blur Product: kwin Version: 5.13.90 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: kristopher.i...@gmail.com Target Milestone: --- When using Magic Lamp minimize effect the Blur effect disappears during the animation in Konsole. How to reproduce bug: 1. Enable Magic Lamp minimize effect 2. Enable Blur desktop effect 3. Use Breeze with Blur option 4. Open Konsole 5. Minimize Konsole What happens: Blur goes away. What should happen: Blur should stay while the Magic Lamp minimize animation plays. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 313050] Icon size displayed in Information Panel inconsistent
https://bugs.kde.org/show_bug.cgi?id=313050 --- Comment #7 from Dr. Chapatin --- Still valid for dolphin 18.08.1 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395262] Transparency/blur is corrupted on context menu of desktop files
https://bugs.kde.org/show_bug.cgi?id=395262 --- Comment #27 from Dr. Chapatin --- Under Wayland the bug occurs with the context menu of window decoration. Both neon dev unstable and Arch Linux (plasma 5.14 beta) are affected. Under X11 the bug occurs with the context menu of plasma notification. For example, press printscreen to open spectacle and save the screenshot. Right click the notification and you can see the bug in the context menu. Can we reopen this report or we need new reports? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388885] Pointer does not unfreeze after closing an app that locks it
https://bugs.kde.org/show_bug.cgi?id=35 Roman Gilg changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Roman Gilg --- Closing again. The other bug report is on 5.13. The patch lands in 5.14. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398615] crash exiting kdevelop [OutputWidget::findFilteredView]
https://bugs.kde.org/show_bug.cgi?id=398615 Anton Anikin changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kde ||velop/f856a9a63910a7e9f2fbc ||bcd63f85100599805ae Resolution|--- |FIXED --- Comment #2 from Anton Anikin --- Git commit f856a9a63910a7e9f2fbcbcd63f85100599805ae by Anton Anikin. Committed on 15/09/2018 at 00:26. Pushed by antonanikin into branch 'master'. Fix segfaults in OutputWidget Summary: This patch fixes regressions provided by D14931. Steps to reproduce (my system is neon/bionic with Qt 5.11.1 and KDevelop/master): 1) Start KDevelop and load some project 2) Start project build 3) Close KDevelop 4) Segfault happens Main problems: 1) Incorrect signal processing. `OutputWidget::updateFilter()` slot is called from parent's destructor when `m_tabwidget`/`m_stackwidget` is deleted so we have destroyed `m_views` hash and segfault as a result. 2) Incorrect `QSharedPointer` usage. All handled objects have `QWidget` as a parent so we have double-free problem and and segfault as a result. Test Plan: Tested on different output widgets (`KDevelop::IOutputView::OneView/HistoryView/MultipleView`) with no segfaults. All our `QTreeView`/`QSortFilterProxyModel` objects are deleted (no memory leaks). Reviewers: #kdevelop, kossebau Reviewed By: #kdevelop, kossebau Subscribers: kfunk, kossebau, vkorneev, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D15326 M +35 -26 plugins/standardoutputview/outputwidget.cpp M +5-4plugins/standardoutputview/outputwidget.h https://commits.kde.org/kdevelop/f856a9a63910a7e9f2fbcbcd63f85100599805ae -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398647] New: krita 4.1.1 crashing and slow
https://bugs.kde.org/show_bug.cgi?id=398647 Bug ID: 398647 Summary: krita 4.1.1 crashing and slow Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: sequelh...@gmail.com Target Milestone: --- Krita worked fine when first installed but now it is crashing as soon as it is opened and it is also slow and laggy. If I zoom in it will not do the command immediately and larger brush strokes don't appear on the canvas right away either. Krita often freezes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 Roman Gilg changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |UPSTREAM CC||subd...@gmail.com --- Comment #17 from Roman Gilg --- This is likely an upstream bug. If they say something differently, pls reopen. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398646] New: Moving files from Fat32 to NTFS partition, permission error crash.
https://bugs.kde.org/show_bug.cgi?id=398646 Bug ID: 398646 Summary: Moving files from Fat32 to NTFS partition, permission error crash. Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: myccl...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: Moving files from a FAT32 formated USB to an internal NTFS drive. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d73caa6c0 (LWP 20315))] Thread 4 (Thread 0x7f2d4a923700 (LWP 20319)): #0 0x7f2d664c6cf9 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2d66480b81 in g_main_context_query () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2d664813b7 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2d6648154c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2d6d73e90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2d6d6e39ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2d6d50222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2d6d50716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2d685f26db in start_thread (arg=0x7f2d4a923700) at pthread_create.c:463 #9 0x7f2d7353788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2d562cd700 (LWP 20318)): #0 0x7f2d735260b4 in __GI___libc_read (fd=7, buf=0x7f2d562ccb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f2d664c5980 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2d66480f27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2d664813e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2d6648154c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2d6d73e90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2d6d6e39ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2d6d50222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2d6dbbbd45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f2d6d50716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2d685f26db in start_thread (arg=0x7f2d562cd700) at pthread_create.c:463 #11 0x7f2d7353788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2d5cb6d700 (LWP 20317)): #0 0x7f2d7352abf9 in __GI___poll (fds=0x7f2d5cb6cca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2d65dc2747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2d65dc436a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2d5f91a2a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f2d6d50716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2d685f26db in start_thread (arg=0x7f2d5cb6d700) at pthread_create.c:463 #6 0x7f2d7353788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2d73caa6c0 (LWP 20315)): [KCrash Handler] #6 0x7f2d6d6e8d41 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2d71a842f9 in KIO::FileCopyJob::slotResult(KJob*) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #8 0x7f2d6d7146cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2d6f096fdc in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #10 0x7f2d6f097b11 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7f2d71a93628 in KIO::SimpleJob::slotFinished() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x7f2d71a919db in KIO::SimpleJob::slotError(int, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7f2d6d7146cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2d71a69186 in KIO::SlaveInterface::error(int, QString const&) ()
[krunner] [Bug 398645] krunner is not working on Fedora 28
https://bugs.kde.org/show_bug.cgi?id=398645 --- Comment #1 from Jose Arthur Benetasso Villanova --- >From konsole: KCrash: Attempting to start /usr/bin/krunner from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... [1] Exit 253krunner [2]+ Stopped krunner -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 398645] New: krunner is not working on Fedora 28
https://bugs.kde.org/show_bug.cgi?id=398645 Bug ID: 398645 Summary: krunner is not working on Fedora 28 Product: krunner Version: 5.13.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: jose.art...@gmail.com Target Milestone: --- Application: krunner (5.13.4) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.18.5-200.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: I opened konsole typed "krunner" typed "ALT+SPACE" (Hot Key to open krunner prompt) typed "tes" and just waited. Every time krunner crashes. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 28return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7f1eb8e1b940 (LWP 24560))] Thread 12 (Thread 0x7f1e73fff700 (LWP 24572)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55af79bea254) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55af79bea200, cond=0x55af79bea228) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55af79bea228, mutex=0x55af79bea200) at pthread_cond_wait.c:655 #3 0x7f1ec7e89183 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #4 0x7f1e99eeb730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f1e99eef86c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f1e99eea7c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f1e99eef8ca in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #8 0x7f1e99eea7c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #9 0x7f1e99eef8ca in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #10 0x7f1e99eea7c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #11 0x7f1e99eed751 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #12 0x7f1ec7e88b4b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #13 0x7f1ec3893594 in start_thread (arg=) at pthread_create.c:463 #14 0x7f1ec71bee6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f1e80b66700 (LWP 24571)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55af79bea254) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55af79bea200, cond=0x55af79bea228) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55af79bea228, mutex=0x55af79bea200) at pthread_cond_wait.c:655 #3 0x7f1ec7e89183 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #4 0x7f1e99eeb730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f1e99eef86c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f1e99eea7c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f1e99eef8ca in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #8 0x7f1e99eea7c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #9 0x7f1e99eed751 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #10 0x7f1ec7e88b4b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #11 0x7f1ec3893594 in start_thread (arg=) at pthread_create.c:463 #12 0x7f1ec71bee6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f1e81367700 (LWP 24570)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55af79bea254) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55af79bea200, cond=0x55af79bea228) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55af79bea228, mutex=0x55af79bea200) at pthread_cond_wait.c:655 #3 0x7f1ec7e89183 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #4
[plasmashell] [Bug 398636] Extra padding on items under Wayland
https://bugs.kde.org/show_bug.cgi?id=398636 David Edmundson changed: What|Removed |Added Product|kwin|plasmashell CC||k...@davidedmundson.co.uk, ||plasma-b...@kde.org Assignee|kwin-bugs-n...@kde.org |k...@davidedmundson.co.uk Component|wayland-generic |Application Launcher ||(Kickoff) Target Milestone|--- |1.0 Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from David Edmundson --- Does clearing the plasma svg cache make a different? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398634] Keyboard repeat setting not respected under Wayland
https://bugs.kde.org/show_bug.cgi?id=398634 Dr. Chapatin changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED CC||bugsefor...@gmx.com URL||https://bugreports.qt.io/br ||owse/QTBUG-55615 --- Comment #1 from Dr. Chapatin --- Qt bug https://bugreports.qt.io/browse/QTBUG-55615 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398630] There is probably a line missing between tabs and the content (see screenshot)
https://bugs.kde.org/show_bug.cgi?id=398630 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398626] Media controls became invisible but still work
https://bugs.kde.org/show_bug.cgi?id=398626 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- yes, buttons to control the player are invisible here too. I also use plasma 5.14 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 398390] Use icon for "Configure" menu item
https://bugs.kde.org/show_bug.cgi?id=398390 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Summary|Unify "Configure" and |Use icon for "Configure" |Application Icons in|menu item |Dolphin | Status|NEEDSINFO |CONFIRMED --- Comment #3 from Nate Graham --- Makes sense now, thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398619] Wrong subcategory selected in the sidebar after clearing search bar
https://bugs.kde.org/show_bug.cgi?id=398619 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 398574] KIO SFTP doesn't connect to some (ecdsa-sha2-nistp256 key) hosts with libssh 0.8
https://bugs.kde.org/show_bug.cgi?id=398574 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Nate Graham --- Thanks! Let me know if you need a hand, and please mention the URL for your patch here once you've submitted it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #15 from Stas Sergeev --- (In reply to Philippe Waroquiers from comment #14) > So, IMO, the easiest is to use the client requests Which ones? I did all the modifications you asked for, they all in my latest test-case. > (the downside of this is that this implies modification of the code). No, that downside is that you didn't suggest any further modifications. :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397894] System Settings crashes when "Launch Feedback" pane is open
https://bugs.kde.org/show_bug.cgi?id=397894 --- Comment #3 from Martin --- Created attachment 114968 --> https://bugs.kde.org/attachment.cgi?id=114968=edit New crash information added by DrKonqi systemsettings5 (5.13.4) using Qt 5.11.1 - What I was doing when the application crashed: Open "Launch feedback" - Unusual behavior I noticed: Titlebar was flashing with "*". When I clicked in the Back button, it crash -- Backtrace (Reduced): #6 KQuickAddons::ConfigModule::needsSave (this=0x676e69636e756f42) at /usr/src/debug/kdeclarative-5.49.0-1.1.x86_64/src/quickaddons/configmodule.cpp:336 #7 0x7f7fb23394bb in KCModuleQmloperator() (__closure=) at /usr/src/debug/kcmutils-5.49.0-2.1.x86_64/src/kcmoduleqml.cpp:72 #10 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:421 #11 0x7f7fb09e1760 in QtPrivate::QSlotObjectBase::call (a=0x7fff384e93b0, r=0x55dfc507cc50, this=0x55dfc50a9f40) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 [...] #13 0x7f7f8e7d2f23 in LaunchFeedback::updateNeedsSave (this=0x55dfc507cc50) at /usr/src/debug/plasma5-desktop-5.13.4-1.1.x86_64/kcms/launch/launchfeedback.cpp:199 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397894] System Settings crashes when "Launch Feedback" pane is open
https://bugs.kde.org/show_bug.cgi?id=397894 Martin changed: What|Removed |Added CC||emtorr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398606] Okular 'Help > What's this' doesn't work on toolbar items
https://bugs.kde.org/show_bug.cgi?id=398606 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 396630] Unable to rename files via kio_smb
https://bugs.kde.org/show_bug.cgi?id=396630 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396701] Regression: New tab not put after current tab
https://bugs.kde.org/show_bug.cgi?id=396701 --- Comment #5 from Nate Graham --- What's the URL for the patch? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398644] New: Add support to "\z" escape character support in Lua
https://bugs.kde.org/show_bug.cgi?id=398644 Bug ID: 398644 Summary: Add support to "\z" escape character support in Lua Product: kdevelop Version: 5.2.4 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: pentest...@airmail.cc Target Milestone: --- Lua allows to use the escape character "\z" to continue a string on the next line ignoring the newline and indentation, but Kdevelop doesn't display it correctly, any code that is ahead of a string that uses "\z" is highlighted as if it were a string. Sorry for my bad English. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398643] Selection tool shouldn't automatically turn into move selection tool
https://bugs.kde.org/show_bug.cgi?id=398643 --- Comment #1 from Storm Engineer --- To see how the current behavior can go real bad create a complex selection, eg. by selecting on-continuous color ranges. This can result in a complex map of areas inside and outside the selection outline. Now if you mover your cursor around your tool will perform a magic act: Now I'm selection tool... no wait, I'm move tool... no wait, I'm selection tool again! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398643] New: Selection tool shouldn't automatically turn into move selection tool
https://bugs.kde.org/show_bug.cgi?id=398643 Bug ID: 398643 Summary: Selection tool shouldn't automatically turn into move selection tool Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Recently the selection tool behavior changed. Expected behavior: The selection tool is always the selection tool. Actual behavior: The selection tool automatically turns into move selection tool when over an existing selection. The user is forced to hold down the modifier key of the respective selection mode (replace, Add, etc.) just to stop this automatic behavior. This is a reversed logic: A tool changing into another tool on its own as we move it around, and having to hold down a key just to stop this and preserve the behavior we set it to. Moreover I have to hold a different key to preserve its behavior based on which mode I was in. This is confusing, inconsistent and counter-intuitive. Suggestion: Changing into a move selection tool should be invoked by holding a modifier key instead. This is more predictable and consistent behavior for both the selection and the move selection tools. Note: I understand the demand for an easy way to move selections, but automatically changing tools based on if the cursor is inside or outside the selection outline makes much less sense (esp. in case of complex selections) than changing them precisely when we want, and only if we want, via holding down a key. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398642] New: The menu bar is gone from Kate under Wayland
https://bugs.kde.org/show_bug.cgi?id=398642 Bug ID: 398642 Summary: The menu bar is gone from Kate under Wayland Product: kate Version: 18.08.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- Created attachment 114967 --> https://bugs.kde.org/attachment.cgi?id=114967=edit Kate without the menu bar Kate seems to be working properly, but the menu bar and thus the menu seems to be missing. I can't bring it back with Ctrl+M, and katerc says "Show Menu Bar=true". The same issue is affecting KWrite. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398580] Critically important notifications should be shown in fullscreen
https://bugs.kde.org/show_bug.cgi?id=398580 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398641] New: Resizing windows causes color changes and colorful blocks to appear
https://bugs.kde.org/show_bug.cgi?id=398641 Bug ID: 398641 Summary: Resizing windows causes color changes and colorful blocks to appear Product: kwin Version: 5.12.6 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: cantf...@gmail.com Target Milestone: --- Resizing a window causes artifacts, as seen in this video: https://streamable.com/ityc8 video card info: GL_RENDERER = AMD JUNIPER (DRM 2.50.0 / 4.15.0-29-generic, LLVM 6.0.0) GL_VERSION= 3.0 Mesa 18.0.5 GL_VENDOR = X.Org This is a clean install of Kubuntu 18.04, live version also exhibited the same artifacts. moving the windows works fine, watching videos works fine, glxgears works fine. Only resizing of any window causes weird artifacts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398541] Minimize animation to wrong place after changing place of Icons-only Task Manager desktop widget on Wayland
https://bugs.kde.org/show_bug.cgi?id=398541 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Dr. Chapatin --- Same bug in plasma 5.14 beta, Arch Linux. Both Wayland and X11 sessions are affected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398220] Invisible windows appear randomly on wayland
https://bugs.kde.org/show_bug.cgi?id=398220 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #4 from Dr. Chapatin --- Today I noticed the same problem in plasma 5.14 on Arch Linux. I can confirm Wayland session crash when I close the hidden window while "present windows" effect is active. In my case only xWayland apps (Firefox and Opera browsers) were affected. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 398539] Application Dashboard isn't clickable after adding widgets to desktop on Wayland
https://bugs.kde.org/show_bug.cgi?id=398539 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- I can not even add a widget to my desktop because plasma crashes immediately when I start to drag the widget. Plasma 5.14 beta, Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 398536] Switching from Apps & Docs to Widgets top section is taking delay
https://bugs.kde.org/show_bug.cgi?id=398536 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398535] Plasma crashed upon dragging Power / Session items in Widgets page of Application Dashboard on Wayland
https://bugs.kde.org/show_bug.cgi?id=398535 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Dr. Chapatin --- crash also occurs in plasma 5.14 beta, Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 180268] Search by specific metadata as Artist, Byline, Location, City, Country, etc... [patch]
https://bugs.kde.org/show_bug.cgi?id=180268 --- Comment #19 from Maik Qualmann --- Git commit 2d199f612c4c428cedee0d4c3a8c647aba790f17 by Maik Qualmann. Committed on 14/09/2018 at 21:11. Pushed by mqualmann into branch 'master'. apply patch #114952 from Johannes to add search by creator M +9-0core/libs/database/item/imagequerybuilder.cpp M +7-1core/utilities/searchwindow/searchfields.cpp M +1-0core/utilities/searchwindow/searchgroup.cpp https://commits.kde.org/digikam/2d199f612c4c428cedee0d4c3a8c647aba790f17 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398533] Plasma crashed upon dragging favorites item in Application Dashboard on Wayland
https://bugs.kde.org/show_bug.cgi?id=398533 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- crash also occurs in plasma 5.14 beta, Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #15 from Dr. Chapatin --- Right. Thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 397611] [ERR-5]: Format de date non pris en charge importation boobank
https://bugs.kde.org/show_bug.cgi?id=397611 --- Comment #15 from Stephane MANKOWSKI --- Je viens de faire une beta: https://launchpad.net/~s-mankowski/+archive/ubuntu/beta-kf5 Franchement, tu peux utiliser sans crainte. La seule chose qui peut arriver, ce sont des parties non encore traduites. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398504] Ekos: plate solving never gets closer to target
https://bugs.kde.org/show_bug.cgi?id=398504 --- Comment #3 from Jasem Mutlaq --- There was an issue I just resolved and merged to master as mount module was reporting ERROR since it wasn't processing EQUATORIAL_COORD So hopefully this is resolved after our rework on scheduler module it's done. If you try it now it's probably going to be broken since work is not yet complete. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #14 from Wolfgang Bauer --- (In reply to Dr. Chapatin from comment #13) > Created attachment 114966 [details] > cursor drop down in plasma 5.13.5 > > Sorting must be case-insensitive. I agree that it should be case-insensitive, but let's summarize the current state to avoid confusion. So, as I see it: The icon and cursor themes list are sorted now (not in 5.14 beta because the fix got "lost", that's fixed in 5.14 branch too meanwhile). But they are sorted case-sensitive (i.e. 'a' comes after 'Z', not before 'B'), it should rather be case-insensitive. The GTK2/3 themes lists are apparently still not sorted and appear in the order they are in the directory list. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398503] Ekos: Mount control doesn't see the mount move
https://bugs.kde.org/show_bug.cgi?id=398503 --- Comment #9 from Cedric Raguenaud --- Is there anything I can do? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 398500] Switching between Apps & Docs and Widgets top sections can be made by hover over them
https://bugs.kde.org/show_bug.cgi?id=398500 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- We can already switch between categories on the right side on mouseover. I think that the same behavior with the entries on top would be nice. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398635] When capture suspends because of guiding deviation, and capture is stopped, UI is in invalid state
https://bugs.kde.org/show_bug.cgi?id=398635 --- Comment #1 from Jasem Mutlaq --- Are you sure it's not CAPTURE_SUSPENDED? The logs should indicate why it was stopped (stopped, aborted, or suspended) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 sibbe.ra...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||sibbe.ra...@gmail.com --- Comment #20 from sibbe.ra...@gmail.com --- This is still an issue in Plasma 5.13.90. I have tested it with KDE Neon Dev Unstable. The cursor is way too big and only on window decorations normally sized. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391082] Menu Bar is landing on the wrong monitor. Primary monitor not defined.
https://bugs.kde.org/show_bug.cgi?id=391082 sibbe.ra...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Version|5.12.2 |5.13.90 CC||sibbe.ra...@gmail.com --- Comment #1 from sibbe.ra...@gmail.com --- I have the same issue with Plasma 5.13.90. There is no option to set an primary output in the wayland session and the settings under X11 dont get honored in Wayland. This renders The Plasma Wayland Session unusable on my System. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398640] New: System Settings crashes after enabling Night Color
https://bugs.kde.org/show_bug.cgi?id=398640 Bug ID: 398640 Summary: System Settings crashes after enabling Night Color Product: systemsettings Version: 5.13.90 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sibbe.ra...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.90) Qt Version: 5.11.1 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: System settings crashed after i enabled the night color feature in the display settings. Even though it crashed, night colors got enabled. The crash just happend once. Enabling and disabling that function after the crash didnt trigger the crash again. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8891a0e940 (LWP 3974))] Thread 19 (Thread 0x7f883264a700 (LWP 4037)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f887365c70b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7f887365c427 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7f7fd6ba in start_thread (arg=0x7f883264a700) at pthread_create.c:333 #4 0x7f888d06a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f8838d7a700 (LWP 4006)): #0 0x7f888d05a27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f88867be6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f888677ae74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f888677b330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f888677b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f888d9760bb in QEventDispatcherGlib::processEvents (this=0x7f88280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f888d91d5ba in QEventLoop::exec (this=this@entry=0x7f8838d79c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7f888d7525e4 in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7f888d75d727 in QThreadPrivate::start (arg=0x1d31340) at thread/qthread_unix.cpp:367 #9 0x7f7fd6ba in start_thread (arg=0x7f8838d7a700) at pthread_create.c:333 #10 0x7f888d06a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f883a162700 (LWP 4005)): #0 0x7f888d05e74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f888677b38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f888677b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f888d9760bb in QEventDispatcherGlib::processEvents (this=0x7f882c000f80, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f888d91d5ba in QEventLoop::exec (this=this@entry=0x7f883a161c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f888d7525e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f888d75d727 in QThreadPrivate::start (arg=0x1995940) at thread/qthread_unix.cpp:367 #7 0x7f7fd6ba in start_thread (arg=0x7f883a162700) at pthread_create.c:333 #8 0x7f888d06a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f883bfff700 (LWP 3991)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7f888d05e742 in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x7f888677b38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f888677b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f888d9760bb in QEventDispatcherGlib::processEvents (this=0x7f88340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f888d91d5ba in QEventLoop::exec (this=this@entry=0x7f883bffec50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f888d7525e4 in QThread::exec (this=this@entry=0x19b68a0) at thread/qthread.cpp:525 #7 0x7f888b469195 in QQmlThreadPrivate::run (this=0x19b68a0) at qml/ftw/qqmlthread.cpp:148 #8 0x7f888d75d727 in QThreadPrivate::start (arg=0x19b68a0) at thread/qthread_unix.cpp:367 #9 0x7f7fd6ba in start_thread (arg=0x7f883bfff700) at pthread_create.c:333 #10 0x7f888d06a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f8849506700 (LWP 3990)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f887365c70b in ?? () from
[systemsettings] [Bug 398493] Incorrect behavior of formats preview
https://bugs.kde.org/show_bug.cgi?id=398493 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398636] Extra padding on items under Wayland
https://bugs.kde.org/show_bug.cgi?id=398636 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #14 from Philippe Waroquiers --- (In reply to Stas Sergeev from comment #13) > Will it help to print an additional warning when > the uninitialized mem is copied to the shared region? > The chances are very high this will result in a false-positives > later, so maybe catching it at that stage would be better? > If such warning is printed, valgrind may just consider > them initialized from now on, to avoid the false-positive > error later. > What do you think about such strategy? Giving errors/warnings when uninitialised memory is copied will as far as I can see slow down valgrind (as it means that each copy operation must contain a check) and will cause many false positive. So, IMO, the easiest is to use the client requests (the downside of this is that this implies modification of the code). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 398425] Shortcut ctrl-shift-q does not end Yakuake but only hides it
https://bugs.kde.org/show_bug.cgi?id=398425 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398639] New: Discover crash on Launch
https://bugs.kde.org/show_bug.cgi?id=398639 Bug ID: 398639 Summary: Discover crash on Launch Product: Discover Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sibbe.ra...@gmail.com Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: With the latest Edition of KDE Neon Dev Unstable, Discover crashes on Launch -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdc591508c0 (LWP 3126))] Thread 12 (Thread 0x7fdc1b9c8700 (LWP 3140)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fdc54df7355 in QBasicMutex::lockInternal() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fdc54df73b7 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fdc54ff4a1f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdc1ad80ee4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer/libqgenericbearer.so #5 0x7fdc54fd4719 in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc54fd98f7 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdc522f0836 in QNetworkConfigurationManagerPrivate::pollEngines() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7fdc5237870d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7fdc54ff4f79 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdc55001b07 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fdc55001e08 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fdc54ff5f73 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fdc54fc821b in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fdc5501e47e in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fdc5501ed01 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fdc4f03d197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fdc4f03d3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fdc4f03d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fdc5501f09f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fdc54fc65ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fdc54dfb5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fdc54e06727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fdc50ea26ba in start_thread (arg=0x7fdc1b9c8700) at pthread_create.c:333 #24 0x7fdc5440a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fdc254b2700 (LWP 3139)): #0 0x7fdc543fe74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdc4f03d38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc4f03d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc5501f0bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdc54fc65ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdc54dfb5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc5824cf86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fdc54e06727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdc50ea26ba in start_thread (arg=0x7fdc254b2700) at pthread_create.c:333 #9 0x7fdc5440a41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #13 from Dr. Chapatin --- Created attachment 114966 --> https://bugs.kde.org/attachment.cgi?id=114966=edit cursor drop down in plasma 5.13.5 Sorting must be case-insensitive. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 Tobias Roeser changed: What|Removed |Added CC||le.petit@web.de -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 398638] New: Paste hex data into Okteta
https://bugs.kde.org/show_bug.cgi?id=398638 Bug ID: 398638 Summary: Paste hex data into Okteta Product: okteta Version: 0.25.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kosse...@kde.org Reporter: ro...@protonmail.com Target Milestone: --- Apologies if this is trivial, but I cannot seem to find the option (neither in the program's menu's or the documentation) to paste hex data directly into Okteta without it being considered as actual data. Am I missing the obvious or is this feature missing? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398503] Ekos: Mount control doesn't see the mount move
https://bugs.kde.org/show_bug.cgi?id=398503 --- Comment #8 from TallFurryMan --- That's what I thought: Scheduler is not seeing the mount slew, and request the slew operation again: "Warning: job 'Deneb' found not slewing, restarting.". You don't get the same behavior with kstars because it is not checking whether the request is actually operated. Now we must find why the status returned by the mount interface is not the right state. This is probably in the wINDI interface, or the mount interface talking with wINDI. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #12 from Wolfgang Bauer --- (In reply to Dr. Chapatin from comment #11) > Plasma 5.13.5 had the same bug shown in the screenshot from comment 7. All right, that's the (GTK2) theme list though. I only looked at the cursors and icon-themes list as the title of this bug report says, and the commit from comment#4 was supposed to fix. Although, the themes lists seem to be correctly sorted here too (even case-insensitive), may be just "luck" though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398637] New: Present windows makes everything too shaded - provide option for shading?
https://bugs.kde.org/show_bug.cgi?id=398637 Bug ID: 398637 Summary: Present windows makes everything too shaded - provide option for shading? Product: plasmashell Version: 5.13.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: mank...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 In KDE when I select "present windows", everything appears shaded and is so dark it is hard to see the windows. If there are multiple similar windows (e.g. Konsole's) it is important to see their contents to know which one to mouse over and raise. Is there a way to disable this? If I mouse over a window it moves forward a bit and lightens, but I would like to be able to see the displayed windows without mousing over them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368707] Seekbar stops working after skipping to different parts of media
https://bugs.kde.org/show_bug.cgi?id=368707 --- Comment #4 from Neousr --- This seems to be a duplicate of recent closed Bug #397591 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #11 from Dr. Chapatin --- Plasma 5.13.5 had the same bug shown in the screenshot from comment 7. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398636] New: Extra padding on items under Wayland
https://bugs.kde.org/show_bug.cgi?id=398636 Bug ID: 398636 Summary: Extra padding on items under Wayland Product: kwin Version: 5.13.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- Created attachment 114965 --> https://bugs.kde.org/attachment.cgi?id=114965=edit Application Menu under Wayland (with 2x scaling) There's extra padding on certain items under Wayland. I've attached a picture of the Application Menu, which looks quite differently from how it does under X11. Should be noted that I run 2x scaling, if that might matter. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #10 from Wolfgang Bauer --- (In reply to Dr. Chapatin from comment #9) > Plasma 5.13.5 had the same bug. Which one? On your screenshot from 5.13.3 the only problem that can be seen is that the search is case-sensitive.(O->P->e) And that's what I see here with 5.13.5 too. In 5.14 beta it probably is completely unsorted though, but current 5.14 branch should be in the same state as 5.13.5. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398635] New: When capture suspends because of guiding deviation, and capture is stopped, UI is in invalid state
https://bugs.kde.org/show_bug.cgi?id=398635 Bug ID: 398635 Summary: When capture suspends because of guiding deviation, and capture is stopped, UI is in invalid state Product: kstars Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: eric.dejouha...@gmail.com Target Milestone: --- When capturing a target, it may happen than guiding deviation suspends the capture until the guide star is repositioned to the lock position. If the Capture module is stopped by the Scheduler at that moment (programmatically as opposed to through the UI), the Capture module enters a weird state where the start/stop icon expectedly displays as a "start", but where it is not possible to load a new sequence or request a preview. Clicking the "start" button at that moment reveals that the state of the module is actually still "capturing" although no capture is taking place or can take place anymore. After clicking, the "start" button remains in state "start", but suddenly features are working again. This seems to be a side-effect or regression of the introduction of the suspend state. Stopping the capture programmatically doesn't restore the initial configuration. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385342] Segmentation fault when switching between look and feel themes
https://bugs.kde.org/show_bug.cgi?id=385342 --- Comment #5 from Andrius Štikonas --- (In reply to Lucas from comment #4) > I can't reproduce it anymore, so closing for now I can still reproduce my issue #390092. Should I reopen that bug (which was marked as duplicate of this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #9 from Dr. Chapatin --- Plasma 5.13.5 had the same bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395148] Double-click text selection
https://bugs.kde.org/show_bug.cgi?id=395148 --- Comment #3 from Alexander Potashev --- Sven, are you talking to the topic starter or me? I couldn't reproduce with these words pasted into the KDevelop editor window: // afdasf // привет // 이야기 Can't read Hangul so no idea here how words may be delimited :( -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #8 from Wolfgang Bauer --- (In reply to Dr. Chapatin from comment #7) > Created attachment 114964 [details] > R comes before O in plasma 5.14 beta, Arch Linux That's likely because the fix never was merged to master, it only was in the 5.13 branch. Has been fixed an hour ago though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #7 from Dr. Chapatin --- Created attachment 114964 --> https://bugs.kde.org/attachment.cgi?id=114964=edit R comes before O in plasma 5.14 beta, Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398634] New: Keyboard repeat setting not respected under Wayland
https://bugs.kde.org/show_bug.cgi?id=398634 Bug ID: 398634 Summary: Keyboard repeat setting not respected under Wayland Product: kwin Version: 5.13.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- Nothing much to it. I have the keyboard repeat rate set to 200ms in Plasma when running X11. Booted into Wayland now to try it out, and noticed that the keyboard repeat setting -- both delay and rate -- doesn't have any effect. No matter the values set to it, it still runs on the defaults. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398617] Project/Configure Selection does not take qmake extra arguments into account
https://bugs.kde.org/show_bug.cgi?id=398617 Kevin Funk changed: What|Removed |Added Summary|Project/Configure Selection |Project/Configure Selection |does not take qmake extra |does not take qmake extra |arguments into acount |arguments into account -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397640] Installing a snap package never ends
https://bugs.kde.org/show_bug.cgi?id=397640 --- Comment #6 from S. Christian Collins --- Just confirmed that this bug happens in recent git as well, tested using the Bionic preview version of KDE neon Developer Edition Git-Unstable (plasma 5.14.80, frameworks 5.51.0, Qt 5.11.1, kernel 4.15.0-34-generic). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397585] Discover crashes when configuring Snap permissions
https://bugs.kde.org/show_bug.cgi?id=397585 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398278] Input box with text Type to search is displayed a little bit higher after clicking on Type to search text
https://bugs.kde.org/show_bug.cgi?id=398278 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395148] Double-click text selection
https://bugs.kde.org/show_bug.cgi?id=395148 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #2 from Sven Brauch --- Your name suggests that you use some non-latin1 text. Can you provide a sample text and where you double-click? For English language text or similar, this definitely works, and has worked for 20 years. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #6 from Wolfgang Bauer --- (In reply to Dr. Chapatin from comment #5) > Created attachment 113891 [details] > screenshot taken on Arch, plasma 5.13.3 > > unfortunately it's not fixed in plasma 5.13.3, Arch Linux. It actually is sorted, but the sorting is case-sensitive, i.e. 'a' comes after 'Z'. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398276] Esc key or click on empty space could dismiss search input field in Kickoff menu
https://bugs.kde.org/show_bug.cgi?id=398276 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398222] 100% CPU usage when trying to open a mailto link
https://bugs.kde.org/show_bug.cgi?id=398222 --- Comment #3 from Walter Lapchynski --- I can confirm with e0d1175dd107 that if I have an email client installed, it Just Works™, but if there's no email client installed, it produces the same results. And indeed xdg-open wants to open falkon for mailtos, so I guess that explains things. The question is now: which commit fixed the problem? Is this unknown? Or maybe approaching this from a different direction: when's the next release? I'd really love to see this fixed before 18.10 is released. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398503] Ekos: Mount control doesn't see the mount move
https://bugs.kde.org/show_bug.cgi?id=398503 --- Comment #6 from Cedric Raguenaud --- Created attachment 114962 --> https://bugs.kde.org/attachment.cgi?id=114962=edit Ekos log -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398503] Ekos: Mount control doesn't see the mount move
https://bugs.kde.org/show_bug.cgi?id=398503 --- Comment #7 from Cedric Raguenaud --- Created attachment 114963 --> https://bugs.kde.org/attachment.cgi?id=114963=edit wINDI log -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398503] Ekos: Mount control doesn't see the mount move
https://bugs.kde.org/show_bug.cgi?id=398503 --- Comment #5 from Cedric Raguenaud --- Created attachment 114961 --> https://bugs.kde.org/attachment.cgi?id=114961=edit EQMod log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398266] Desktop icon isn't removing in Wayland
https://bugs.kde.org/show_bug.cgi?id=398266 --- Comment #2 from Dr. Chapatin --- Created attachment 114960 --> https://bugs.kde.org/attachment.cgi?id=114960=edit icon removed from desktop under Wayland is back after relogin and overlaps another icon Sorry, my mistake. I can reproduce, the icon removed from desktop before logout is back after relogin and can overlap another icon as we can see on my screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395900] No Audio When Playing Clips Frame by Frame
https://bugs.kde.org/show_bug.cgi?id=395900 --- Comment #3 from mickyrosenl...@tuta.io --- The problem is experienced by my friend on his windows computer. Ill get him to try the new version and report back thanks ;) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395148] Double-click text selection
https://bugs.kde.org/show_bug.cgi?id=395148 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398266] Desktop icon isn't removing in Wayland
https://bugs.kde.org/show_bug.cgi?id=398266 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- cannot reproduce on Arch Linux, plasma 5.14 beta. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379901] Default Email Application is ignored
https://bugs.kde.org/show_bug.cgi?id=379901 Dr. Chapatin changed: What|Removed |Added CC||m.w...@web.de --- Comment #3 from Dr. Chapatin --- *** Bug 398246 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 398246] Purpose Email functionality ignores mail client setting in systemsettings
https://bugs.kde.org/show_bug.cgi?id=398246 Dr. Chapatin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 379901 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398617] Project/Configure Selection does not take qmake extra arguments into acount
https://bugs.kde.org/show_bug.cgi?id=398617 --- Comment #3 from RJVB --- > not meant to RJVB directly. Didn't take it that way (but I'd have figured out a fix if I used QMake projects more often). (And thanks for correcting the subject. Usually I notice when my sh*tty notebook keyboard didn't register a stroke...) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398358] News widget cannot get news on Windows
https://bugs.kde.org/show_bug.cgi?id=398358 --- Comment #5 from Jaime Torres --- What I've seen using wireshark is that there is no connection at all when the news enabled check button is checked in the windows build, in linux it works at the first attempt. I've also noticed that krita is not enabled as an app that can connect to the internet in the default windows firewall, but after enabling it twice (that's windows), it still doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398105] Searching for "torrent" in Discover brought up unrelated and vulgar app names
https://bugs.kde.org/show_bug.cgi?id=398105 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 398633] New: Feature request add tests for qt containers and qobjects
https://bugs.kde.org/show_bug.cgi?id=398633 Bug ID: 398633 Summary: Feature request add tests for qt containers and qobjects Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mike.a.har...@outlook.com CC: smart...@kde.org Target Milestone: --- I have a very simple example that refuses to be flagged by either clang, clang-tidy, clazy, or Krazy2. QVector myVec; myVec.push_back(1); myVec.push_back(2); int third = myVec.at(3); int otherThird =myVec[3]; obviously this segfaults because there was never a third element. The issue is that no single IDE or plugin will flag this. It'll ASSERT in Qt Creator debug build run but that's after it compiles. there has to be some intellisense like thing in the editor or any static analysis tool that can read Qt Containers. "Just add the Qt source to your code model" you might say well compiling every single part of Qt takes many days so not an option. Another example is QCheckBox *myCheckbox = new QCheckBox(); QListView *myListView = qobject_cast(myCheckBox); //will equal null QSize size = myListView->gridSize(); //myListView is null so crashes with segfault again This leads to deep bugs that aren't flagged with any static analysis tool. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 398632] New: Entries are missing Icons
https://bugs.kde.org/show_bug.cgi?id=398632 Bug ID: 398632 Summary: Entries are missing Icons Product: frameworks-knewstuff Version: 5.48.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: rahul.vit2...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- In the attached screenshot you can see an icon is shown beside Gparted and Filelight only and not for others like KDE Partition Manager etc. https://imgur.com/jIn3kDr I think it would be better to show icons for all the suggested applications or for none. -- You are receiving this mail because: You are watching all bug changes.
