[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 --- Comment #7 from Hugo Pereira Da Costa --- Can you check with oxygen-demo5 if the mdi-window tab is responsive there ? It is, here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379829] Krita display unresponsive
https://bugs.kde.org/show_bug.cgi?id=379829 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- You'll have to update your intel display driver or disable opengl: https://docs.krita.org/KritaFAQ#Krita_starts_with_a_black_or_blank_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_or_blank_screen_on_my_Windows_system_with_an_Intel_GPU *** This bug has been marked as a duplicate of bug 360601 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360601] [INTEL] Canvas doesn't update but is not black either
https://bugs.kde.org/show_bug.cgi?id=360601 Boudewijn Rempt changed: What|Removed |Added CC||toastzombi...@gmail.com --- Comment #36 from Boudewijn Rempt --- *** Bug 379829 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 --- Comment #8 from Hugo Pereira Da Costa --- Created attachment 105543 --> https://bugs.kde.org/attachment.cgi?id=105543&action=edit another ui file with mdi windows, that work Can you test this ui locally (it has mdi windows, no stylesheet) Here nothing is frozen (which is why I reported that I cannot reproduce in the first place) If confirmed that neither oxygen-demo5 nor this ui are frozen, it means that there is something specific to the ui you sent that makes the freeze happen. That could be a good base for further investigations -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 Hugo Pereira Da Costa changed: What|Removed |Added Priority|VLO |HI -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 --- Comment #9 from Hugo Pereira Da Costa --- Here at least it seems setting the stylesheet creates the freeze. Removing it on your ui file unfreezes things Adding it on mine freezes things. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379838] New: disAMode(x86): not an addr!
https://bugs.kde.org/show_bug.cgi?id=379838 Bug ID: 379838 Summary: disAMode(x86): not an addr! Product: valgrind Version: 3.13 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: iv...@ivosh.net Target Milestone: --- Running DRD or Helgrind on test case helgrind/tests/tc12_rwl_trivial compiled in 32-bit mode (X86) produces the following crash: $ ./vg-in-place --tool=helgrind helgrind/tests/tc12_rwl_trivial ==29388== Helgrind, a thread error detector ==29388== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al. ==29388== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info ==29388== Command: helgrind/tests/tc12_rwl_trivial ==29388== ==29388== ---Thread-Announcement-- ==29388== ==29388== Thread #1 is the program's root thread ==29388== ==29388== ==29388== ==29388== Thread #1 unlocked a not-locked lock at 0xFEA5ADEC ==29388==at 0x48333AB: pthread_rwlock_unlock_WRK (hg_intercepts.c:2540) ==29388==by 0x4834D7C: pthread_rwlock_unlock (hg_intercepts.c:2559) ==29388==by 0x10891F: safe_pthread_rwlock_unlock (safe-pthread.h:58) ==29388==by 0x108AF9: main (tc12_rwl_trivial.c:29) ==29388== Lock at 0xFEA5ADEC was first observed ==29388==at 0x4832D45: pthread_rwlock_init_WRK (hg_intercepts.c:2027) ==29388==by 0x4834D2E: pthread_rwlock_init (hg_intercepts.c:2042) ==29388==by 0x10898D: main (tc12_rwl_trivial.c:18) ==29388== Address 0xfea5adec is on thread #1's stack ==29388== in frame #3, created by main (tc12_rwl_trivial.c:14) ==29388== ==29388== vex: the `impossible' happened: disAMode(x86): not an addr! vex storage: T total 32739272 bytes allocated vex storage: P total 384 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==29388==at 0x5802918B: show_sched_status_wrk (m_libcassert.c:355) ==29388==by 0x580292BD: report_and_quit (m_libcassert.c:426) ==29388==by 0x5802946C: panic (m_libcassert.c:502) ==29388==by 0x5802946C: vgPlain_core_panic_at (m_libcassert.c:507) ==29388==by 0x5802948A: vgPlain_core_panic (m_libcassert.c:512) ==29388==by 0x580449FC: failure_exit (m_translate.c:740) ==29388==by 0x581062F3: vpanic (main_util.c:231) ==29388==by 0x5812886B: disAMode (guest_x86_toIR.c:1564) ==29388==by 0x58148B0C: disInstr_X86_WRK (guest_x86_toIR.c:15322) ==29388==by 0x5814A3A1: disInstr_X86 (guest_x86_toIR.c:15456) ==29388==by 0x5811D570: bb_to_IR (guest_generic_bb_to_IR.c:365) ==29388==by 0x5810370F: LibVEX_FrontEnd (main_main.c:558) ==29388==by 0x58103F42: LibVEX_Translate (main_main.c:1173) ==29388==by 0x580472B7: vgPlain_translate (m_translate.c:1791) ==29388==by 0x58082558: handle_chain_me (scheduler.c:1084) ==29388==by 0x58084257: vgPlain_scheduler (scheduler.c:1428) ==29388==by 0x58094FA7: thread_wrapper (syswrap-linux.c:103) ==29388==by 0x58094FA7: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 29388) ==29388==at 0x4873818: _xend (pthread_rwlock_unlock.c:38) ==29388==by 0x4873818: pthread_rwlock_unlock (pthread_rwlock_unlock.c:38) ==29388==by 0x48333DA: pthread_rwlock_unlock_WRK (hg_intercepts.c:2543) ==29388==by 0x4834D7C: pthread_rwlock_unlock (hg_intercepts.c:2559) ==29388==by 0x10891F: safe_pthread_rwlock_unlock (safe-pthread.h:58) ==29388==by 0x108AF9: main (tc12_rwl_trivial.c:29) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. $ file helgrind/tests/tc12_rwl_trivial helgrind/tests/tc12_rwl_trivial: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=f5d2b09e348834b0a9c00c65487771d10f9bbc1f, not stripped $ gcc --version gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406 Copyright (C) 2016 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ ./vg-in-place --version -v valgrind-3.13.0.SVN-16373M-vex-3369 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379838] disAMode(x86): not an addr!
https://bugs.kde.org/show_bug.cgi?id=379838 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #1 from Ivo Raisr --- The problem is reproducible even with 'none' tool: $ ./vg-in-place --tool=none helgrind/tests/tc12_rwl_trivial ==29554== Nulgrind, the minimal Valgrind tool ==29554== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. ==29554== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info ==29554== Command: helgrind/tests/tc12_rwl_trivial ==29554== vex: the `impossible' happened: disAMode(x86): not an addr! vex storage: T total 26363116 bytes allocated vex storage: P total 384 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==29554==at 0x580A62CB: show_sched_status_wrk (m_libcassert.c:355) ==29554==by 0x580A63FD: report_and_quit (m_libcassert.c:426) ==29554==by 0x580A65AC: vgPlain_core_panic_at (m_libcassert.c:502) ==29554==by 0x580A65CA: vgPlain_core_panic (m_libcassert.c:512) ==29554==by 0x58019F6C: failure_exit (m_translate.c:740) ==29554==by 0x580E76B3: vpanic (main_util.c:231) ==29554==by 0x58109C2B: disAMode (guest_x86_toIR.c:1564) ==29554==by 0x58129ECC: disInstr_X86_WRK (guest_x86_toIR.c:15322) ==29554==by 0x5812B761: disInstr_X86 (guest_x86_toIR.c:15456) ==29554==by 0x580FE930: bb_to_IR (guest_generic_bb_to_IR.c:365) ==29554==by 0x580E4ACF: LibVEX_FrontEnd (main_main.c:558) ==29554==by 0x580E5302: LibVEX_Translate (main_main.c:1173) ==29554==by 0x5801C827: vgPlain_translate (m_translate.c:1791) ==29554==by 0x58053368: handle_chain_me (scheduler.c:1084) ==29554==by 0x58055067: vgPlain_scheduler (scheduler.c:1428) ==29554==by 0x58065DB7: run_a_thread_NORETURN (syswrap-linux.c:103) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 29554) ==29554==at 0x485F818: pthread_rwlock_unlock (pthread_rwlock_unlock.c:38) ==29554==by 0x10891F: safe_pthread_rwlock_unlock (safe-pthread.h:58) ==29554==by 0x108AF9: main (tc12_rwl_trivial.c:29) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379838] disAMode(x86): not an addr!
https://bugs.kde.org/show_bug.cgi?id=379838 --- Comment #2 from Julian Seward --- (In reply to Ivo Raisr from comment #1) That's weird. I have never seen the x86 front end fail in that way before, nor for that matter the amd64 front end (it has basically identical logic.) disAMode should never be called with a modrm byte that indicates in fact a register. Do you have any local modifications? Or is there some inconsistent compilation problem? I can't imagine what through, given that disAMode and all its callers are in the same source file. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379838] disAMode(x86): not an addr!
https://bugs.kde.org/show_bug.cgi?id=379838 --- Comment #3 from Julian Seward --- Whoa! Reproduced. Investigating. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379838] disAMode(x86): not an addr!
https://bugs.kde.org/show_bug.cgi?id=379838 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Ivo Raisr --- Seems like the offending instruction is 'xend' from __pthread_rwlock_unlock(). -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 299375] Improper handling of nested \input commands by the project tree view
https://bugs.kde.org/show_bug.cgi?id=299375
Moritz Augustin changed:
What|Removed |Added
CC||softw...@moritz-augustin.de
--- Comment #2 from Moritz Augustin ---
I can confirm this wrong behaviour in the current version, i.e., kile 2.1.3-7
as packaged in arch linux. Particularly I see the annoying Case 1 where kile
shows non-root files (of the same project) that are included using
\input{subfolder/file} incorrectly as root documents although they should be
rather subfiles.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 374963] increase valgrind's load address to prevent mmap failure
https://bugs.kde.org/show_bug.cgi?id=374963 --- Comment #4 from Ivo Raisr --- Created attachment 105544 --> https://bugs.kde.org/attachment.cgi?id=105544&action=edit patch to increase load address for almost all platforms to 0x5800 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374963] increase valgrind's load address to prevent mmap failure
https://bugs.kde.org/show_bug.cgi?id=374963 --- Comment #5 from Ivo Raisr --- Please test the attached patch [1] which increases the load address for almost all platforms to 0x5800 (from 0x3800). This gives another 512 MB for executable without changing linkage model (which is different on every platform). I've tested on x86/Linux, amd64/Linux, x86/Solaris, amd64/Solaris. 32-bit only, 64-bit only, mix and outer/inner setup. [1] https://bugs.kde.org/attachment.cgi?id=105544 -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #9 from RJVB --- A bit of both. I ran into this issue rebuilding the previous digiKam release (why is not relevant here). Applications that use boost are not a theoretical concern, they exist. The ECM are supposed to be a collection of convenience macros and modules, allowing among others to write more readable CMake files that are easier to maintain. As such I think they shouldn't oblige software to use rarely used constructs (and a bit alien to CMake's principle too, IIUC). If there is really no other solution here, the least that could be done is provide something that hides the syntax and offloads the obligation for developers to be aware of a rarely used compiler argument. Ideally that would be a *documented* mechanism with the effect that the compiler argument is never added to CXXFLAGS but it could also be a macro of the form `ECM_PROJECT_USES_NAMED_LOGICAL_OPERATORS`. I'm not very well versed in writing CMake code but I could put a simple prototype up on Phabricator and see what we can come up with. Maybe a sort of attribute system where you can declare specific, less common needs of the project before including the ECM modules that set up the build environment (= the SET_PROJECT_PROPERTIES feature CMake forgot to implement ;)). --- To be very honest, I wasn't even aware that the C/C++ standard define named logical operators. So I googled a bit and came across a number of good arguments why one might prefer them. Not compelling enough to change my own practice but I can very well understand why complex projects like boost use them - and I doubt that boost has any anti-MSVC agenda (didn't check, though :)). What I think the ECM should do is set the options required to make software compile on all supported/major platforms. Setting things up so that software fails to build everywhere because there exists a platform where certain practices cause build failure feels like caressing the proverbial cat against its fur. Esp. if it happens in a minor release, possibly even without documentation other than a commit message. No matter how big MS Windows is compared to all other platforms it's still a platform that's very different from KDE's main platform (Unix/Linux and derivatives). It would be much more in line with the other ECM features to figure out how to get all platforms to accept what they should be accepting in the first place. FWIW, should getting MSVC to accept named logical operators not be feasible, isn't this something that should be implemented as a CMake policy? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379839] New: adding multiple attachments via "actions - send as kmail attachment" in plasma only adds first item to new message
https://bugs.kde.org/show_bug.cgi?id=379839 Bug ID: 379839 Summary: adding multiple attachments via "actions - send as kmail attachment" in plasma only adds first item to new message Product: kmail2 Version: 5.5.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: martin.tlus...@gmail.com Target Milestone: --- When trying to add several documents (by selecting them with CTRL-click) via the "actions - send as kmail attachment" in the plasme right-click menu, only the first item gets added to the new message window. This probably is a plasma bug, but I could not find where to file it... -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 321863] Krusader crasher during synchronization of directory with tons of sub-dirs
https://bugs.kde.org/show_bug.cgi?id=321863 --- Comment #4 from shlom...@gmail.com --- Hi, I don't remember. It was long ago... Thanks, Shlomi On Sun, May 14, 2017 at 6:40 PM, Alex Bikadorov wrote: > https://bugs.kde.org/show_bug.cgi?id=321863 > > Alex Bikadorov changed: > >What|Removed |Added > > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #3 from Alex Bikadorov --- > Was the "Compare by content" setting checked? If so, does it crash when > unchecked? > > (I know this is an old report.) > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379838] disAMode(x86): not an addr!
https://bugs.kde.org/show_bug.cgi?id=379838 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Ivo Raisr --- VEX SVN commit r3370. Valgrind SVN commit 16375. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 378430] www: update Valgrind alias mirrors
https://bugs.kde.org/show_bug.cgi?id=378430 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Ivo Raisr --- Commited in Valgrind www SVN as r520. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379795] Konsole crashed on double right click
https://bugs.kde.org/show_bug.cgi?id=379795 --- Comment #2 from rооt --- Created attachment 105546 --> https://bugs.kde.org/attachment.cgi?id=105546&action=edit New crash information added by DrKonqi konsole (17.07.70) using Qt 5.7.1 I had 2 tabs on a konsole window. When i right clicked on first tab crash happen. -- Backtrace (Reduced): #6 QWidget::actions (this=this@entry=0x0) at kernel/qwidget.cpp:3387 #7 0x7fe7d233f96f in QMenu::clear (this=0x0) at widgets/qmenu.cpp:2060 #8 0x7fe7d491f239 in Konsole::SessionController::updateWebSearchMenu (this=this@entry=0x562fd55e3730) at ./src/SessionController.cpp:380 #9 0x7fe7d49259bb in Konsole::SessionController::showDisplayContextMenu (this=0x562fd55e3730, position=...) at ./src/SessionController.cpp:1544 #10 0x7fe7d129081e in QtPrivate::QSlotObjectBase::call (a=0x7ffdfbb830a0, r=0x562fd55e3730, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379795] Konsole crashed on double right click
https://bugs.kde.org/show_bug.cgi?id=379795 rооt changed: What|Removed |Added CC||cerebel...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379828] Unable to render after updating codecs. 'freeze -p' not allowed
https://bugs.kde.org/show_bug.cgi?id=379828 --- Comment #2 from James A. Jaworski --- Created attachment 105547 --> https://bugs.kde.org/attachment.cgi?id=105547&action=edit Screenshot of error msg. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes
https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #6 from Julian Seward --- Created attachment 105548 --> https://bugs.kde.org/attachment.cgi?id=105548&action=edit test case (allocgig.c) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379828] Unable to render after updating codecs. Arg. 'freeze -p' not allowed
https://bugs.kde.org/show_bug.cgi?id=379828 James A. Jaworski changed: What|Removed |Added Summary|Unable to render after |Unable to render after |updating codecs. 'freeze|updating codecs. Arg. |-p' not allowed |'freeze -p' not allowed -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes
https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #7 from Julian Seward --- Created attachment 105549 --> https://bugs.kde.org/attachment.cgi?id=105549&action=edit Proposed fix (so far, Linux only) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379839] adding multiple attachments via "actions - send as kmail attachment" in plasma only adds first item to new message
https://bugs.kde.org/show_bug.cgi?id=379839 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- fixed in 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #10 from Kevin Funk --- I really don't like having to spend my time defending a change which actually helps us developers writing better code, but here we go... If there are some compiler switches that help us ensuring we're writing cross-platform code, then there are good reasons to use it. We've come across this problem: some Linux dev accidentally (freudian slip most of time) uses one of the operator keywords, and then just later we've noticed it broke the MSVC build. So this is addressing some real world issues. > Applications that use boost are not a theoretical concern, they exist. The > ECM are supposed to be a collection of convenience macros and modules, > allowing among others to write more readable CMake files that are easier to > maintain. > (...) Yes, and also to ensure we write proper C++ code, by enabling several compiler warnings, etc. pp. > To be very honest, I wasn't even aware that the C/C++ standard define named > logical operators. So I googled a bit and came across a number of good > arguments why one might prefer them. Not compelling enough to change my own > practice but I can very well understand why complex projects like boost use > them - and I doubt that boost has any anti-MSVC agenda (didn't check, though > :)). I just grepped the Boost source code (for 'not' and 'and') from the 15+ Boost libraries I have installed and it looks like there's indeed just occurrences of them in 'transitive_reduction.hpp', which looks to me like a freudian slip as well (all other files in that subdir use '!' and '&&' as usual). > What I think the ECM should do is set the options required to make software > compile on all supported/major platforms. Setting things up so that software > fails to build everywhere because there exists a platform where certain > practices cause build failure feels like caressing the proverbial cat against > its fur. Not really. If we can enable compiler warnings/error in a way it helps us writing cross-platform code, that's good. Please see this from a developer perspective. > Esp. if it happens in a minor release, possibly even without documentation > other than a commit message. And a review, and with a discussion on the review... > No matter how big MS Windows is compared to all other platforms it's still a > platform that's very different from KDE's main platform (Unix/Linux and > derivatives). And b/c it's different we shouldn't make it easier to develop for it? > It would be much more in line with the other ECM features to figure out how > to get all platforms to accept what they should be accepting in the first > place. Not sure what you mean here. > FWIW, should getting MSVC to accept named logical operators not be feasible, > isn't this something that should be implemented as a CMake policy? There's really no need to touch CMake here. There's an option to make MSVC adhere more to compiler standards (/Za) but I do not know the side effects of it. Please, let's not waste time discussing this change if there are no real world issues with it. The two or three individual problems with this patch have been sorted out, and since then no developer complained. We're really better off spending our time elsewhere. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 --- Comment #1 from Jarosław Staniek --- Created attachment 105551 --> https://bugs.kde.org/attachment.cgi?id=105551&action=edit Photo of the Old and New sizes (from bug #379072) -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379072] The Bar Size/Font size of the Menu Bar, the Properties Box and the Bottom Bar are too small.
https://bugs.kde.org/show_bug.cgi?id=379072 --- Comment #4 from Jarosław Staniek --- Created attachment 105550 --> https://bugs.kde.org/attachment.cgi?id=105550&action=edit Photo of the Old and New sizes (from bug #379072) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 379840] New: Akregator crashes at start (metakit backend)
https://bugs.kde.org/show_bug.cgi?id=379840 Bug ID: 379840 Summary: Akregator crashes at start (metakit backend) Product: akregator Version: 5.5.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ansl...@yahoo.com Target Milestone: --- Application: akregator (5.5.1) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.11.0-gentoo x86_64 Distribution: "Gentoo Base System release 2.3" -- Information about the crash: - What I was doing when the application crashed: Just started Akregator and while syncing the feeds it crashed. This is an old bug with the metakit backend, but since the reports for the old versions have been closed I'm logging a new one to be aware it still exists. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f06a4568880 (LWP 17577))] Thread 28 (Thread 0x7f062e642700 (LWP 17966)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f069f4d7461 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f069f4d7ab9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f069f4d7c70 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f069f4d485c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f06a3e2a352 in start_thread (arg=0x7f062e642700) at pthread_create.c:333 #6 0x7f06a50f0a7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 27 (Thread 0x7f062fffa700 (LWP 17928)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f069cd667a4 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f069ce4df20 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f069cd667e9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f06a3e2a352 in start_thread (arg=0x7f062fffa700) at pthread_create.c:333 #4 0x7f06a50f0a7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 26 (Thread 0x7f0640c1a700 (LWP 17778)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f069f0a7770 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f069f090950 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f069f090cbb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f069f08c9ca in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f06a01b28fe in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f06a01b4be4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f06a01b4c35 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f06a01b4cf9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f069f4c095a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f069f4ab765 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f069f4d822a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f069f4d485c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7f06a3e2a352 in start_thread (arg=0x7f0640c1a700) at pthread_create.c:333 #14 0x7f06a50f0a7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 25 (Thread 0x7f06417fa700 (LWP 17739)): #0 0x7f06a300c9c8 in g_main_context_iterate (context=context@entry=0x7f060c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3879 #1 0x7f06a300cc24 in g_main_context_iteration (context=0x7f060c000990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #2 0x7f06a5836abb in QEventDispatcherGlib::processEvents (this=0x7f060c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f06a57e964a in QEventLoop::exec (this=this@entry=0x7f06417f9d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #4 0x7f06a5654f4b in QThread::exec (this=) at thread/qthread.cpp:507 #5 0x7f06a565914b in QThreadPrivate::start (arg=0x104ce80) at thread/qthread_unix.cpp:368 #6 0x7f06a3e2a352 in start_thread (arg=0x7f06417fa700) at pthread_create.c:333 #7 0x7f06a50f0a7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 24 (Thread 0x7f0641ffb700 (LWP 17731)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f069f4d7461 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f069f4d7ab9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x00
[kexi] [Bug 379072] The Bar Size/Font size of the Menu Bar, the Properties Box and the Bottom Bar are too small.
https://bugs.kde.org/show_bug.cgi?id=379072 Jarosław Staniek changed: What|Removed |Added Attachment #105550|0 |1 is obsolete|| Attachment #105550|Photo of the Old and New|- description|sizes | -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379072] The size of local menu/property editor is too small
https://bugs.kde.org/show_bug.cgi?id=379072 Jarosław Staniek changed: What|Removed |Added Summary|The Bar Size/Font size of |The size of local |the Menu Bar, the |menu/property editor is too |Properties Box and the |small |Bottom Bar are too small. | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379827] Dolphin crashed moving files to a NTFS partition
https://bugs.kde.org/show_bug.cgi?id=379827 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 364039 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364039] Dolphin crashed on file transfer
https://bugs.kde.org/show_bug.cgi?id=364039 Elvis Angelaccio changed: What|Removed |Added CC||ivan.rinco...@gmail.com --- Comment #36 from Elvis Angelaccio --- *** Bug 379827 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 Jarosław Staniek changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Jarosław Staniek --- Technical note: the issue appear when for given widget style height of a horizontal scrollbar is too small. The section of navigator buttons are added using QAbstractScrollArea::addScrollBarWidget(QWidget *widget, Qt::Alignment alignment). The docs say "The height of the widget will be set to match the height of the scroll bar" -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes
https://bugs.kde.org/show_bug.cgi?id=368507 --- Comment #8 from Tom Hughes --- Fails at 32Gb without patch: trying for 31 GB .. ==12078== Warning: set address range perms: large range [0x3960c040, 0x7f960c040) (defined) .. OK ==12078== Warning: set address range perms: large range [0x3960c028, 0x7f960c058) (noaccess) trying for 32 GB .. allocgig: allocgig.c:15: main: Assertion `p' failed. ==12078== ==12078== Process terminating with default action of signal 6 (SIGABRT) ==12078==at 0x4E6E428: raise (raise.c:54) ==12078==by 0x4E70029: abort (abort.c:89) ==12078==by 0x4E66BD6: __assert_fail_base (assert.c:92) ==12078==by 0x4E66C81: __assert_fail (assert.c:101) ==12078==by 0x400700: main (in /home/tomh/allocgig) and at 64Gb with the patch: trying for 63 GB .. ==14020== Warning: set address range perms: large range [0x10060c4040, 0x1fc60c4040) (defined) .. OK ==14020== Warning: set address range perms: large range [0x10060c4028, 0x1fc60c4058) (noaccess) trying for 64 GB .. allocgig: allocgig.c:15: main: Assertion `p' failed. ==14020== ==14020== Process terminating with default action of signal 6 (SIGABRT) ==14020==at 0x4E6E428: raise (raise.c:54) ==14020==by 0x4E70029: abort (abort.c:89) ==14020==by 0x4E66BD6: __assert_fail_base (assert.c:92) ==14020==by 0x4E66C81: __assert_fail (assert.c:101) ==14020==by 0x400700: main (in /home/tomh/allocgig) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX
https://bugs.kde.org/show_bug.cgi?id=360415 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #16 from Ivo Raisr --- Running the latest Valgrind on regression test fb_test_amd64 built with gcc 5.4.0 gives the following crash: vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xC5 0x9C 0x58 0x48 0x83 vex amd64->IR: REX=1 REX.W=1 REX.R=1 REX.X=0 REX.B=1 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F38 vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==1119== valgrind: Unrecognised instruction at address 0x409768. ==1119==at 0x409768: exec_adcx (fb_test_amd64.h:69) ==1119==by 0x409806: test_adcx (fb_test_amd64.h:166) ==1119==by 0x411652: main (fb_test_amd64.c:1201) Disassembly indeed shows it is adcx: 0x00409767 <+405>: popfq => 0x00409768 <+406>: adcx %r13,%r8 0x0040976e <+412>: pushfq (gdb) x/16xb 0x409768 0x409768 : 0x660x4d0x0f0x380xf60xc5 0x9c0x58 0x409770 : 0x480x830xec0x080x250xd5 0x080x00 ./vg-in-place --version -v valgrind-3.13.0.SVN-16374-vex-3369 Is it possible that some paths in adcx decoding are not handled properly? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378700] There is gap on the right of every invoked tray icon
https://bugs.kde.org/show_bug.cgi?id=378700 q...@e.amav.ro changed: What|Removed |Added CC||q...@e.amav.ro --- Comment #3 from q...@e.amav.ro --- On today's KF 5.34 update the gap is still presented -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX
https://bugs.kde.org/show_bug.cgi?id=360415 --- Comment #17 from Julian Seward --- Ah yes, I remembered about this and then forgot it again. The test case uses ADOX etc, and runs unconditionally, but the fix only decodes them on AVX2 capable machines and above. So the test case needs to be conditionalised to only run on AVX2. I'll fix it. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 Jarosław Staniek changed: What|Removed |Added CC||whitfi...@telkomsa.net -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 --- Comment #3 from Jarosław Staniek --- @whitfi...@telkomsa.net Could you please provide screenshot for the new size when the scrollbar is displayed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379841] New: Application menu button missing in programs started at login
https://bugs.kde.org/show_bug.cgi?id=379841 Bug ID: 379841 Summary: Application menu button missing in programs started at login Product: kwin Version: 5.9.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: karsten.fleisc...@gmail.com Target Milestone: --- Hi, I'm using the "Application menu button", hiding the typical Program menu (File, Tools, Help,...) within the titlebar to save vertical space. I'm very happy with the feature! So thanks for that one first. I did notice a bug/inconvenience, at least on the Opensuse rpm (running Leap 42.2, Plasma 5.9.5, Frameworks 5.33, QT 5.8.0): After a login any application started initially (in my case kontact and amarok) do not have the appropriate titlebar icon. If I close these programs and reopen them the button appears. Not sure if it is related to an older bug (309958) as both programs are configured to start minimised in the systray. Kind Regards -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 --- Comment #4 from Jarosław Staniek --- Note: the AppImage version uses Fusion widget style and navigator buttons are of the same vertical size as the scrollbar's buttons. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 --- Comment #5 from Jarosław Staniek --- Possible solution: users demanding larger buttons could switch to different widget style. This is hard for AppImage versions of Kexi so special option could be a better choice. I requested Breeze as default for AppImage: https://github.com/appimage-packages/kexi/issues/12 -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 --- Comment #6 from Jarosław Staniek --- Created attachment 105552 --> https://bugs.kde.org/attachment.cgi?id=105552&action=edit 2.9.11 and 3.1.0 Record navigator in 2.9.11 on the top, 3.1.0 on the bottom. Please note that 3.1.0 has no smaller geometry. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 379817] Behaviour change: JPEG image preview scaled to widget size
https://bugs.kde.org/show_bug.cgi?id=379817 Alexander Volkov changed: What|Removed |Added CC||a.vol...@rusbitech.ru --- Comment #1 from Alexander Volkov --- It should be fixed by https://git.reviewboard.kde.org/r/130129/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334798] Mouse cursor appearence does not change when hovering
https://bugs.kde.org/show_bug.cgi?id=334798 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375905] [HUION] Incorrect pressure information with Huion WH1409
https://bugs.kde.org/show_bug.cgi?id=375905 Boudewijn Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #3 from Boudewijn Rempt --- Thanks for the info! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379842] New: DAV resource: calendar vanishes and looses settings after akonadi restart
https://bugs.kde.org/show_bug.cgi?id=379842 Bug ID: 379842 Summary: DAV resource: calendar vanishes and looses settings after akonadi restart Product: Akonadi Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Sometimes one of my calendars of the DAV resource vanishes from a list of different calendars. It is my only writable calendar that does so. Restarting the calendar afterwards brings the calendar back, but not its settings. I.e. all calendar properties, such as calendar color or reminder settings are lost. THi especially happens after keeping akonadi running for a longer time (i.e. 2 or 3 days) This bug may be related to Bug 341998, but it is back since i have upgraded to 5.5.0 and is still reproducible for 5.5.1. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379843] New: Include calligra flow
https://bugs.kde.org/show_bug.cgi?id=379843 Bug ID: 379843 Summary: Include calligra flow Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: martin.tlus...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I'd like to see calligraflow being added to KDE NEON. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379844] New: Misaligned elements of the record navigator
https://bugs.kde.org/show_bug.cgi?id=379844 Bug ID: 379844 Summary: Misaligned elements of the record navigator Product: kexi Version: 3.1 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: kexi-b...@kde.org Reporter: stan...@kde.org CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- Misaligned elements of the record navigator (vertically): record number and record count. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379844] Misaligned elements of the record navigator
https://bugs.kde.org/show_bug.cgi?id=379844 Jarosław Staniek changed: What|Removed |Added Severity|normal |minor Target Milestone|--- |3.0.2 CC||whitfi...@telkomsa.net Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379844] Misaligned elements of the record navigator
https://bugs.kde.org/show_bug.cgi?id=379844 --- Comment #1 from Jarosław Staniek --- Created attachment 105553 --> https://bugs.kde.org/attachment.cgi?id=105553&action=edit Position of elements (fusion style) -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379844] Misaligned elements of the record navigator
https://bugs.kde.org/show_bug.cgi?id=379844 Jarosław Staniek changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379844] Misaligned elements of the record navigator
https://bugs.kde.org/show_bug.cgi?id=379844 --- Comment #2 from Jarosław Staniek --- For breeze/gtk+ widget style there's no issue. There's issue e.g. for fusion, oxygen... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms
https://bugs.kde.org/show_bug.cgi?id=370028 --- Comment #41 from Tamara Vlahovic --- Created attachment 105554 --> https://bugs.kde.org/attachment.cgi?id=105554&action=edit Patch 2/4 fix I noticed today that my update of a Patch 2/4 have a mistake that causes build to crash on 64BE architectures. This patch fixes it. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 379817] Behaviour change: JPEG image preview scaled to widget size
https://bugs.kde.org/show_bug.cgi?id=379817 --- Comment #2 from Alex Bikadorov --- Thanks for the fast response. I don't have permission to view the review request. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379843] Include calligra flow
https://bugs.kde.org/show_bug.cgi?id=379843 Jonathan Riddell changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jonathan Riddell --- we build the components of calligra that are enabled by calligra developers. it's up to them which get built. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms
https://bugs.kde.org/show_bug.cgi?id=370028 --- Comment #42 from Ivo Raisr --- (In reply to Tamara Vlahovic from comment #41) Indeed, thank you for spotting it. I think it was caused by a mismerge from TileGX port removal. Commited as SVN r16377. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 379821] Exponent button (x*10y) only works with numbers entered immediately previously
https://bugs.kde.org/show_bug.cgi?id=379821 Christoph Feck changed: What|Removed |Added Severity|major |wishlist --- Comment #2 from Christoph Feck --- I just checked my CASIO fx calculator, and it also allows this 'EXP' key only when entering numbers, it does not work with previous results. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 165491] Kleopatra: Bugs in process for create new certificates.
https://bugs.kde.org/show_bug.cgi?id=165491 elitelif...@gmail.com changed: What|Removed |Added CC||elitelif...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #11 from RJVB --- > helps us developers writing better code That's a bit the point, using named logical operators can easily be defended as "helping write better code". "not" is more visible than "!", and confusion/mistakes between the logical and bitwise versions become much less likely and probably easier to spot. > There's an option to make MSVC adhere more to compiler standards (/Za) but I > do not know the side effects of it. That too is one of the points: there appear to be side-effects. If that is not the case, then the ECM should add that option when MSVC is used instead of using -fno-operator-names everywhere else. Actually, q quick read of the /Za description suggests that might be a good idea anyway: https://msdn.microsoft.com/en-us/library/aa278577(v=vs.60).aspx Sadly I cannot test it. > The two or three individual problems with this patch have been sorted out, > and since then no developer complained. We're really better off spending our > time elsewhere. No wonder no developer has complained about a fix that was made for them. Look, this doesn't have to be a drawn-out discussion. I've brought it up because I saw you have been hesitating yourself. Let me just say 1 more thing: KDE_ENABLE_EXCEPTIONS and I'll work on an equivalent and put it up for review after testing it (hopefully with MSVC too). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379845] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=379845 Bug ID: 379845 Summary: plasma crash Product: plasmashell Version: 5.9.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dinamic6...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.95) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.8.0-51-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: closing the "task manager" options crashes the plasma, i think. i see the desktop restarting, black screen and then wallpaper and task manager bar apearing (new to kde) The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb17fbf48c0 (LWP 13242))] Thread 13 (Thread 0x7fb09bdff700 (LWP 14357)): #0 0x7fb17a52bb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb175cc138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb175cc149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb17ae4b75b in QEventDispatcherGlib::processEvents (this=0x7f7090032a10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fb17adf60ba in QEventLoop::exec (this=this@entry=0x7fb09bdfece0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fb17ac25f64 in QThread::exec (this=this@entry=0x5fcd600) at thread/qthread.cpp:507 #6 0x7fb17d256bf5 in QQmlThreadPrivate::run (this=0x5fcd600) at qml/ftw/qqmlthread.cpp:147 #7 0x7fb17ac2ab48 in QThreadPrivate::start (arg=0x5fcd600) at thread/qthread_unix.cpp:368 #8 0x7fb179ad06ba in start_thread (arg=0x7fb09bdff700) at pthread_create.c:333 #9 0x7fb17a53782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fb0a95c9700 (LWP 14347)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb17ac2b9fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x54bc730) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x54f22d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fb0c3bde07f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fb0c3be2078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fb0c3bdd26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fb0c3be20d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fb0c3bdd26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fb0c3bdfbf0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fb17ac2ab48 in QThreadPrivate::start (arg=0x2168a50) at thread/qthread_unix.cpp:368 #10 0x7fb179ad06ba in start_thread (arg=0x7fb0a95c9700) at pthread_create.c:333 #11 0x7fb17a53782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fb0a9dca700 (LWP 14346)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb17ac2b9fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x54bc730) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x54f22d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fb0c3bde07f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fb0c3be2078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fb0c3bdd26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fb0c3be20d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fb0c3bdd26d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fb0c3bdfbf0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fb17ac2ab48 in QThreadPrivate::start (arg=0x7fb0a40033e0) at thread/qthread_unix.cpp:368 #10 0x7fb179ad06ba in start_thread (arg=0x7fb0a9dca700) at pthread_create.c:333 #1
[kexi] [Bug 379071] Improve support for searching content from first/last record
https://bugs.kde.org/show_bug.cgi?id=379071 --- Comment #2 from Ian Whitfield --- Seems to be working now in AppImage 24 Apr. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379078] Deleting or renaming a table crashes the program
https://bugs.kde.org/show_bug.cgi?id=379078 --- Comment #7 from Ian Whitfield --- Working now OK in AppImage 24 Apr -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379079] Properties Box for a Photo Object only brings up two options
https://bugs.kde.org/show_bug.cgi?id=379079 --- Comment #2 from Ian Whitfield --- Still the same in AppImage 24 Apr. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #12 from Kevin Funk --- > That's a bit the point, using named logical operators can easily be defended > as "helping write better code". "not" is more visible than "!", and > confusion/mistakes between the logical and bitwise versions become much less > likely and probably easier to spot. That's off-topic/orthogonal. Or do you plan to port all code of KDE/Qt to named operators? We've never used them in KDE projects, nor will we in any near future. s/better/cross-platform/ if you prefer. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #13 from Kevin Funk --- > Look, this doesn't have to be a drawn-out discussion. I've brought it up > because I saw you have been hesitating yourself. Let me just say 1 more thing: > KDE_ENABLE_EXCEPTIONS Sorry, forgot: +1 on that one. Patches welcome :) -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #14 from RJVB --- > We've never used them in KDE projects, nor will we in any near future. Define "we"? ;) > Sorry, forgot: +1 on that one. Patches welcome :) Whew... :) -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #15 from Kevin Funk --- > Define "we"? ;) ... you asked for it: "All but you?" But I'll stop filling the bug tracker with useless spam now. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379846] New: Please show current DNS server
https://bugs.kde.org/show_bug.cgi?id=379846 Bug ID: 379846 Summary: Please show current DNS server Product: plasma-nm Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: vy...@baka.sk Target Milestone: --- The "Active Connections" / "Details" tab is really helpful. Could it be improved so that it will show more information about the connection - most importantly, the current DNS server? Currently it only show IP, speed and mac address. This helps fixing connection-related issues. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 379847] New: Plasma crash at startup
https://bugs.kde.org/show_bug.cgi?id=379847 Bug ID: 379847 Summary: Plasma crash at startup Product: ksmserver Version: 5.9.5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: alexandrpa...@gmail.com Target Milestone: --- Created attachment 10 --> https://bugs.kde.org/attachment.cgi?id=10&action=edit xterm output after plasma crash Gentoo ~amd64. X server works fine and I can start it with "startx" from a regular user. Then, I try to "startkde" from one of it's terminals. I see KDE loading splash screen, but then it fades away and in terminal I see several KCrash lines (attachment). Then KDE crash reporter tool pops out, and here is info it provides: Application: ksmserver (ksmserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fea8cfb2200 (LWP 2621))] Thread 2 (Thread 0x7fea75e0c700 (LWP 2623)): #0 0x7fea8ca8b1dd in poll () from /lib64/libc.so.6 #1 0x7fea813f071c in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fea813f082c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fea88629f3b in QEventDispatcherGlib::processEvents (this=0x7fea680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fea885d00e2 in QEventLoop::exec (this=this@entry=0x7fea75e0bd50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fea88416dae in QThread::exec (this=this@entry=0x7fea8d15bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x7fea8d0d7a25 in QDBusConnectionManager::run (this=0x7fea8d15bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7fea8841c6cd in QThreadPrivate::start (arg=0x7fea8d15bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #8 0x7fea8310b3a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fea8ca945af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fea8cfb2200 (LWP 2621)): [KCrash Handler] #5 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x6175747269763d43) at /usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/include/g++-v6/bits/atomic_base.h:396 #6 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #7 QBasicAtomicInteger::load (this=0x6175747269763d43) at /usr/include/qt5/QtCore/qbasicatomic.h:99 #8 QtPrivate::RefCount::ref (this=0x6175747269763d43) at /usr/include/qt5/QtCore/qrefcount.h:55 #9 QList::QList (this=this@entry=0x7ffc5354b570, l=...) at /usr/include/qt5/QtCore/qlist.h:805 #10 0x7fea89c2c506 in QStringList::QStringList (this=0x7ffc5354b570) at /usr/include/qt5/QtCore/qstringlist.h:100 #11 KProcess::program (this=) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.34.0/work/kcoreaddons-5.34.0/src/lib/io/kprocess.cpp:253 #12 0x7fea8cd64871 in KSMServeroperator() (exitCode=9, __closure=0x14ccc60) at /var/tmp/portage/kde-plasma/plasma-workspace-5.9.5.1-r1/work/plasma-workspace-5.9.5.1/ksmserver/startup.cpp:691 #13 QtPrivate::FunctorCall, QtPrivate::List, void, KSMServer::slotAutoStart():: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:135 #14 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:192 #15 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1, this_=0x14ccc50, r=, a=, ret=) at /usr/include/qt5/QtCore/qobject_impl.h:169 #16 0x7fea885ff8f3 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5354b740, r=0x14c9c40, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #17 QMetaObject::activate (sender=sender@entry=0x14c9c40, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc5354b740) at kernel/qobject.cpp:3723 #18 0x7fea885ffe37 in QMetaObject::activate (sender=sender@entry=0x14c9c40, m=m@entry=0x7fea8882b1c0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc5354b740) at kernel/qobject.cpp:3602 #19 0x7fea88516611 in QProcess::finished (this=this@entry=0x14c9c40, _t1=) at .moc/moc_qprocess.cpp:326 #20 0x7fea8851d6bf in QProcessPrivate::_q_processDied (this=this@entry=0x1517df0) at io/qprocess.cpp:1178 #21 0x7fea8856f704 in QProcessPrivate::waitForFinished (this=this@entry=0x1517df0, msecs=msecs@entry=3) at io/qprocess_unix.cpp:895 #22 0x7fea885172fb in QProcess::waitForFinished (this=this@entry=0x14c9c40, msecs=msecs@entry=3) at io/qprocess.cpp:1922 #23 0x7fea88517a2c in QProcess::~QProcess (this=0x14c9c40, __in_chrg=) at io/qprocess.cpp:1261 #24 0x7fea89c2c259 in KProcess::~KProcess (this=0x14c9c40, __in_chrg=) at /var/tmp/port
[okular] [Bug 365161] Can't select which pages to print
https://bugs.kde.org/show_bug.cgi?id=365161 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- As I understand it this not Okular's fault. Okular uses the standard Qt print dialog, and that one is missing the required feature. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379848] New: When there is a lot of WiFi connections, the VPN connection is not shown in the list
https://bugs.kde.org/show_bug.cgi?id=379848 Bug ID: 379848 Summary: When there is a lot of WiFi connections, the VPN connection is not shown in the list Product: plasma-nm Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: vy...@baka.sk Target Milestone: --- If there is a lot of available WiFi connections, my VPN connection won't show. It seems as if the list of connections to connect tops at around 20 or so, pushing my VPN connection below until it "falls off" the list. Once I disable the WiFi checkbox in nm-widget, the VPN will appear immediately and I can then connect to it. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled
https://bugs.kde.org/show_bug.cgi?id=379719 beojan changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #7 from beojan --- Here's the new backtrace with debug symbols enabled: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd1fa627c0 (LWP 26324))] Thread 3 (Thread 0x7fccfe73a700 (LWP 26327)): #0 0x7fcd1b72937d in read () from /usr/lib/libc.so.6 #1 0x7fcd13b4de20 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fcd13b0947e in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fcd13b09954 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fcd13b09acc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fcd1c05610b in QEventDispatcherGlib::processEvents (this=0x7fccf80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fcd1bfff93a in QEventLoop::exec (this=this@entry=0x7fccfe739dc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fcd1be21ae3 in QThread::exec (this=this@entry=0x7fcd1cbe0d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #8 0x7fcd1c96c835 in QDBusConnectionManager::run (this=0x7fcd1cbe0d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:170 #9 0x7fcd1be26748 in QThreadPrivate::start (arg=0x7fcd1cbe0d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #10 0x7fcd177662e7 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fcd1b73754f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fcd0cb75700 (LWP 26326)): #0 0x7fcd1b72d67d in poll () from /usr/lib/libc.so.6 #1 0x7fcd17fea8e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fcd17fec679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fcd0f70b9f9 in QXcbEventReader::run (this=0x12bb020) at qxcbconnection.cpp:1345 #4 0x7fcd1be26748 in QThreadPrivate::start (arg=0x12bb020) at thread/qthread_unix.cpp:368 #5 0x7fcd177662e7 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fcd1b73754f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fcd1fa627c0 (LWP 26324)): [KCrash Handler] #6 0x7fcd1d403764 in QFlags::operator& (f=, this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:142 #7 QWindow::type (this=this@entry=0x1ad92e0) at kernel/qwindow.cpp:826 #8 0x7fcd1d408dd2 in QWindow::winId (this=0x1ad92e0) at kernel/qwindow.cpp:599 #9 0x7fcd0756dfd3 in QDBusMenuBar::unregisterMenuBar (this=0x1ad8f00) at /home/beojan/SRC/ABS/extra/plasma-integration/src/plasma-integration-5.9.5/src/platformtheme/qdbusmenubar.cpp:222 #10 0x7fcd0756d989 in QDBusMenuBar::handleReparent (this=0x1ad8f00, newParentWindow=0x17c6df0) at /home/beojan/SRC/ABS/extra/plasma-integration/src/plasma-integration-5.9.5/src/platformtheme/qdbusmenubar.cpp:171 #11 0x7fcd1dd14dbc in QMenuBarPrivate::handleReparent (this=this@entry=0x1ad8b00) at widgets/qmenubar.cpp:1362 #12 0x7fcd1dd15a95 in QMenuBar::eventFilter (this=0x1ad87f0, object=0x1abdf70, event=0x7fffd5e18b00) at widgets/qmenubar.cpp:1462 #13 0x7fcd1c001241 in QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x1abdf70, event=event@entry=0x7fffd5e18b00) at kernel/qcoreapplication.cpp:1099 #14 0x7fcd1db983b5 in QApplicationPrivate::notify_helper (this=, receiver=0x1abdf70, e=0x7fffd5e18b00) at kernel/qapplication.cpp:3741 #15 0x7fcd1db9fbf1 in QApplication::notify (this=0x7fffd5e1acb0, receiver=0x1abdf70, e=0x7fffd5e18b00) at kernel/qapplication.cpp:3502 #16 0x7fcd1c0014e0 in QCoreApplication::notifyInternal2 (receiver=receiver@entry=0x1abdf70, event=event@entry=0x7fffd5e18b00) at kernel/qcoreapplication.cpp:988 #17 0x7fcd1dbe0eb6 in QCoreApplication::sendEvent (event=0x7fffd5e18b00, receiver=0x1abdf70) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #18 QWidget::setParent (this=this@entry=0x1abdf70, parent=parent@entry=0x1b21cb0, f=...) at kernel/qwidget.cpp:10597 #19 0x7fcd1dbe1c4c in QWidget::setParent (this=this@entry=0x1abdf70, parent=parent@entry=0x1b21cb0) at kernel/qwidget.cpp:10451 #20 0x7fcd1dbbb9b6 in QLayout::addChildWidget (this=this@entry=0x1b195e0, w=w@entry=0x1abdf70) at kernel/qlayout.cpp:926 #21 0x7fcd1dbbba2f in QLayout::addWidget (this=0x1b195e0, w=0x1abdf70) at kernel/qlayout.cpp:226 #22 0x7fcd1dcfb7bc in QMdiSubWindow::setWidget (this=this@entry=0x1b21cb0, widget=widget@entry=0x1abdf70) at widgets/qmdisubwindow.cpp:2330 #23 0x7fcd1dcef8e3 in QMdiArea::addSubWindow (this=, widget=0x1abdf70, windowFlags=...) at widgets/qmdiarea.cpp:1989 #24 0x7fccf487af4
[plasmashell] [Bug 378376] Crash in Plasma::FrameSvgPrivate::alphaMask
https://bugs.kde.org/show_bug.cgi?id=378376 David Edmundson changed: What|Removed |Added CC||dinamic6...@yahoo.com --- Comment #10 from David Edmundson --- *** Bug 379845 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 379847] Plasma crash at startup
https://bugs.kde.org/show_bug.cgi?id=379847 --- Comment #1 from Alexandr Paliy --- Created attachment 105556 --> https://bugs.kde.org/attachment.cgi?id=105556&action=edit Installed versions of qt libs and kde packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379845] plasma crash
https://bugs.kde.org/show_bug.cgi?id=379845 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 378376 *** -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379078] Deleting or renaming a table crashes the program
https://bugs.kde.org/show_bug.cgi?id=379078 --- Comment #8 from Jarosław Staniek --- Thanks Ian -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdbusaddons] [Bug 379830] All kde binaries crash in QDBusConnectionPrivate::closeConnection() when exiting without opening a window
https://bugs.kde.org/show_bug.cgi?id=379830 --- Comment #2 from Rex Dieter --- While I was able to initially reproduce this, I no longer can after restarting my plasma session. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334798] Mouse cursor appearence does not change when hovering
https://bugs.kde.org/show_bug.cgi?id=334798 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- Confirmed with current git master on Debian testing. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379844] Misaligned elements of the record navigator
https://bugs.kde.org/show_bug.cgi?id=379844 Jarosław Staniek changed: What|Removed |Added Latest Commit||https://commits.kde.org/kex ||i/dc7cc8c61b4bdad0d9022ad7d ||af29e1229d9a230 Status|ASSIGNED|RESOLVED Version Fixed In||3.0.2 Resolution|--- |FIXED --- Comment #3 from Jarosław Staniek --- Git commit dc7cc8c61b4bdad0d9022ad7daf29e1229d9a230 by Jaroslaw Staniek. Committed on 15/05/2017 at 12:52. Pushed by staniek into branch '3.0'. Fix vertical alignment of the record navigator - record number, count, "of" label - don't overpaint the top border in some widget styles such as fusion FIXED-IN:3.0.2 M +101 -36 src/widget/utils/kexirecordnavigator.cpp M +1-1src/widget/utils/kexirecordnavigator.h https://commits.kde.org/kexi/dc7cc8c61b4bdad0d9022ad7daf29e1229d9a230 -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379844] Misaligned elements of the record navigator
https://bugs.kde.org/show_bug.cgi?id=379844 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 379849] New: Rip fails to start when using clone mode and target exsists
https://bugs.kde.org/show_bug.cgi?id=379849 Bug ID: 379849 Summary: Rip fails to start when using clone mode and target exsists Product: k3b Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Copying Assignee: k...@kde.org Reporter: sithlor...@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- When copying a CD in CLONE mode if the target files exsist the copy process never starts. The overwrite prompt is shown then the job just never starts . If you delete the toc and iso that exsist the job will then start as expected. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379190] Strikeout/underline not available in font dialogs
https://bugs.kde.org/show_bug.cgi?id=379190 --- Comment #1 from Jarosław Staniek --- Side note: In the future font properties would be displayed in the property pane directly so the font dialog would not be necessary to change font properties. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379850] New: Konsole right click crash !!!
https://bugs.kde.org/show_bug.cgi?id=379850 Bug ID: 379850 Summary: Konsole right click crash !!! Product: konsole Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: peyli...@riseup.net Target Milestone: --- Application: konsole (17.04.1) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.10.0-20-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: some times when i right click to paste something to the konsole it will be crash ... The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fce9e24a3c0 (LWP 24230))] Thread 3 (Thread 0x7fce823d7700 (LWP 24232)): #0 0x7fce9dbf018d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fce93ddb576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fce93ddb68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fce9a1faf2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fce9a1a488a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fce99fd1fe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fce983615c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fce99fd6c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fce95cc06da in start_thread (arg=0x7fce823d7700) at pthread_create.c:456 #9 0x7fce9dbfc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fce8948b700 (LWP 24231)): #0 0x7fce9dbf018d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fce960e3c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fce960e58d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fce8b9e2ed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fce99fd6c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fce95cc06da in start_thread (arg=0x7fce8948b700) at pthread_create.c:456 #6 0x7fce9dbfc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fce9e24a3c0 (LWP 24230)): [KCrash Handler] #6 0x7fce9b148721 in QWidget::actions() const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fce9b28196f in QMenu::clear() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fce9d860dd9 in Konsole::SessionController::updateWebSearchMenu() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.17 #9 0x7fce9d86760b in Konsole::SessionController::showDisplayContextMenu(QPoint const&) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.17 #10 0x7fce9a1d281e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fce9d8a2345 in Konsole::TerminalDisplay::configureRequest(QPoint const&) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.17 #12 0x7fce9d883ae2 in Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.17 #13 0x7fce9b1593ef in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fce9d88451a in Konsole::TerminalDisplay::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.17 #15 0x7fce9b11135c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fce9b1199cd in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fce9a1a68a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fce9b11807d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fce9b1730f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fce9b175b03 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fce9b11135c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fce9b118b11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fce9a1a68a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fce9a97d723 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivat
[kexi] [Bug 277973] Add option to change the behaviour when double clicking an object in the project navigator
https://bugs.kde.org/show_bug.cgi?id=277973 Jarosław Staniek changed: What|Removed |Added Priority|NOR |LO --- Comment #4 from Jarosław Staniek --- Most suitable approach: though a plugin or an internal about:config-like option so users that don't need such specific setting won't be confused when it's in Kexi options. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379793] Record navigator's buttons shall be bigger
https://bugs.kde.org/show_bug.cgi?id=379793 Jarosław Staniek changed: What|Removed |Added Target Milestone|3.0.2 |--- -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379318] CSI S escape sequence (SU, scroll up) ignored if number of lines to scroll bigger than scrollable lines
https://bugs.kde.org/show_bug.cgi?id=379318 Markus Trippelsdorf changed: What|Removed |Added CC||octopl...@yandex.com -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379190] Strikeout/underline not available in font dialogs on some desktops
https://bugs.kde.org/show_bug.cgi?id=379190 Jarosław Staniek changed: What|Removed |Added Summary|Strikeout/underline not |Strikeout/underline not |available in font dialogs |available in font dialogs ||on some desktops -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379851] New: Having the task bar between two monitors makes windows disappear when moved past it
https://bugs.kde.org/show_bug.cgi?id=379851 Bug ID: 379851 Summary: Having the task bar between two monitors makes windows disappear when moved past it Product: kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: dualhead Assignee: unassigned-b...@kde.org Reporter: torg...@posteo.de Target Milestone: --- I use two monitors and the task bar is configured to be on the right side of the left monitor, so it is basically in the middle --- --- | |T | | | | |A | | | |2560x1440 |S | | 2560x1440 | | |K | | | | |B | | | --- --- When I move a window past the taskbar from the left monitor to the right, it suddenly disapears. This does not happen if I configure the taskbar to be at any other edge. I assume this is some false assumption that behind the taskbar no drawing needs to be done and rendering of the window is switched off. But whatever it is, it is annoying... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379851] Having the task bar between two monitors makes windows disappear when moved past it
https://bugs.kde.org/show_bug.cgi?id=379851 --- Comment #1 from Torge --- I could fix this behavior by changing visibility from "Immer sichtbar" (Always visible) to "Fenster rutschen unter die kontrolleiste" (Windows slide under taskbar) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379562] Calendar widget disappears when clicking away
https://bugs.kde.org/show_bug.cgi?id=379562 ska...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |INVALID --- Comment #2 from ska...@gmail.com --- actually, you're right. Haven't noticed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379079] Properties Box for a Photo Object only brings up two options
https://bugs.kde.org/show_bug.cgi?id=379079 Jarosław Staniek changed: What|Removed |Added Target Milestone|3.1 |3.0.2 Platform|unspecified |Appimage -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379306] Zero values not showing up
https://bugs.kde.org/show_bug.cgi?id=379306 --- Comment #14 from Ian Whitfield --- Created attachment 105557 --> https://bugs.kde.org/attachment.cgi?id=105557&action=edit No Zero shows in Table and Query -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379306] Zero values not showing up
https://bugs.kde.org/show_bug.cgi?id=379306 --- Comment #15 from Ian Whitfield --- Created attachment 105558 --> https://bugs.kde.org/attachment.cgi?id=105558&action=edit No Zeros in Report -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 379852] New: ksshaskpass does not store passwords in kwallet, neither use them if they already existed
https://bugs.kde.org/show_bug.cgi?id=379852 Bug ID: 379852 Summary: ksshaskpass does not store passwords in kwallet, neither use them if they already existed Product: ksshaskpass Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- ksshaskpass does not store passwords in kwallet, neither use them if they already existed. I used to use this feature for my ssh connections, but it stopped working few months ago. Today I decided to report the issue. Please let me know if I could be of any help to get this issue fixed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379853] New: Plasmashell crashed while opening Eclipse from folder widget
https://bugs.kde.org/show_bug.cgi?id=379853 Bug ID: 379853 Summary: Plasmashell crashed while opening Eclipse from folder widget Product: plasmashell Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sudd...@gmx.at CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.6) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.11.0-1.g1b516a5-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I started the Eclipse IDE from a folder widget on my desktop and then plasmashell crashed. The next time I opened it, it worked. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc353fe5900 (LWP 1802))] Thread 19 (Thread 0x7fc270411700 (LWP 3475)): #0 0x7fc34cd1f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc34dc0c65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc2a6e5f42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc2a6e62dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc2a6e5d45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc2a6e62e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc2a6e5d45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fc2a6e60a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fc34dc0b9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc34cd1a744 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc34d519d3d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fc270c12700 (LWP 3474)): #0 0x7fc34cd1f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc34dc0c65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc2a6e5f42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc2a6e62dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc2a6e5d45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc2a6e62e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc2a6e5d45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fc2a6e62e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fc2a6e5d45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7fc2a6e60a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7fc34dc0b9e9 in () at /usr/lib64/libQt5Core.so.5 #11 0x7fc34cd1a744 in start_thread () at /lib64/libpthread.so.0 #12 0x7fc34d519d3d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fc271413700 (LWP 3473)): #0 0x7fc34cd1f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc34dc0c65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc2a6e5f42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc2a6e62dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc2a6e5d45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc2a6e62e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc2a6e5d45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fc2a6e60a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fc34dc0b9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc34cd1a744 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc34d519d3d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fc271c14700 (LWP 3472)): #0 0x7fc34cd1f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc34dc0c65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc2a6e5f42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
[konsole] [Bug 379850] Konsole right click crash !!!
https://bugs.kde.org/show_bug.cgi?id=379850 Dimiter "Arruor" Nikov changed: What|Removed |Added CC||arr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] New: kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 Bug ID: 379854 Summary: kdevelop crashes after closing splitview Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- kdevelop crashes if you close splitview in a specific order. steps to recreate: 1. open a file 2. splitview the file 3. close the original (left or top) 4. close the split view. crashes 100% of the time. -- You are receiving this mail because: You are watching all bug changes.
