[kmymoney4] [Bug 384903] Lost data
https://bugs.kde.org/show_bug.cgi?id=384903 Jack changed: What|Removed |Added CC|ostroffjh@users.sourceforge | |.net| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385055] PPC VEX temporary storage exhausted
https://bugs.kde.org/show_bug.cgi?id=385055 --- Comment #2 from Carl Love --- The second workload that hits the same issue is a GCC instruction test. The test runs a whole bunch of float 128-bit instructions to test the code generation. In this case, there are several instructions: xsmulqp, xsmaddqp, xssubqp, xsdivqp, xsaddqp which all call the function generate_store_FPRF( Ity_F128, vT ); to set the condition code for the instruction. The function expands into: t125 = Or32(8Uto32(GET:I8(1342)),Shl32(8Uto32(GET:I8(1344)),0xC:I8)) t124 = And32(t125,0x3:I32) t122 = GET:F128(896) t121 = GET:F128(912) t123 = AddF128(Xor32(t124,And32(Shl32(t124,0x1:I8),0x2:I32)),t121,t122) t134 = 64HLtoV128(ReinterpF64asI64(F128HItoF64(t123)),ReinterpF64asI64(F128LOtoF64(t123))) t133 = 64to1(And64(Shr64(V128HIto64(t134),0x3F:I8),0x1:I64)) t136 = 0x7FFF:I64 t135 = 0x:I64 t137 = 0x0:I64 t126 = 32to1(And32(1Uto32(CmpEQ64(And64(V128HIto64(t134),t136),t136)),1Uto32(Not1(CmpEQ64(Or64(And64(V128HIto64(t134),t135),V128to64(t134)),t137) t139 = 0x7FFF:I64 t138 = 0x:I64 t140 = 0x0:I64 t127 = 32to1(And32(1Uto32(CmpEQ64(And64(V128HIto64(t134),t139),t139)),1Uto32(CmpEQ64(Or64(And64(V128HIto64(t134),t138),V128to64(t134)),t140 t142 = 0x7FFF:I64 t141 = 0x:I64 t143 = 0x0:I64 t132 = 32to1(And32(1Uto32(CmpEQ64(And64(V128HIto64(t134),t142),t143)),1Uto32(CmpEQ64(Or64(And64(V128HIto64(t134),t141),V128to64(t134)),t143 t144 = 0x7FFF:I64 t145 = 0x0:I64 t129 = 32to1(And32(1Uto32(Not1(CmpEQ64(And64(V128HIto64(t134),t144),t145))),1Uto32(Not1(CmpEQ64(And64(V128HIto64(t134),t144),t144) t147 = 0x7FFF:I64 t146 = 0x:I64 t148 = 0x0:I64 t128 = 32to1(And32(1Uto32(CmpEQ64(And64(V128HIto64(t134),t147),t148)),1Uto32(Not1(CmpEQ64(Or64(And64(V128HIto64(t134),t146),V128to64(t134)),t148) t130 = 32to1(And32(1Uto32(32to1(Not32(1Uto32(t133,1Uto32(1:I1))) t131 = 32to1(And32(1Uto32(t133),1Uto32(1:I1))) PUT(1344) = 32to8(Or32(And32(0xF:I32,8Uto32(GET:I8(1344))),Shl32(And32(0x1:I32,1Uto32(32to1(Or32(1Uto32(32to1(Or32(1Uto32(t126),1Uto32(32to1(And32(1Uto32(t131)\ ,1Uto32(t128))),1Uto32(32to1(Or32(1Uto32(32to1(And32(1Uto32(t131),1Uto32(t132,1Uto32(32to1(And32(1Uto32(t130),1Uto32(t128))),0x4:I8))) PUT(1344) = 32to8(Or32(And32(0x10:I32,8Uto32(GET:I8(1344))),And32(0xF:I32,Or32(Or32(1Uto32(32to1(Or32(1Uto32(t126),1Uto32(t127,Shl32(1Uto32(32to1(And32(1Ut\ o32(32to1(Not32(1Uto32(t126,1Uto32(t132,0x1:I8)),Or32(Shl32(1Uto32(32to1(And32(1Uto32(32to1(Not32(1Uto32(t126,1Uto32(32to1(And32(1Uto32(32to1(Or32(1Uto32(32to1(O\ r32(1Uto32(32to1(And32(1Uto32(t130),1Uto32(t128,1Uto32(32to1(And32(1Uto32(t130),1Uto32(t129))),1Uto32(32to1(And32(1Uto32(t130),1Uto32(t127))),1Uto32(32to1(And32(\ 1Uto32(32to1(Not32(1Uto32(t132,1Uto32(32to1(Not32(1Uto32(t126),0x2:I8),Shl32(1Uto32(32to1(And32(1Uto32(32to1(Not32(1Uto32(t126,1Uto32(32to1(And32(1Uto32(\ 32to1(Or32(1Uto32(32to1(Or32(1Uto32(32to1(And32(1Uto32(t131),1Uto32(t128,1Uto32(32to1(And32(1Uto32(t131),1Uto32(t129))),1Uto32(32to1(And32(1Uto32(t131),1Uto32(t127))\ ),1Uto32(32to1(And32(1Uto32(32to1(Not32(1Uto32(t132,1Uto32(32to1(Not32(1Uto32(t126),0x3:I8)) PUT(784) = t123 PUT(1296) = 0x4157DB0:I64 The basic block again seems to have about 30 instructions, with 6 of the instructions having the above expansion for generate_store_FPRF(). This with the added dres->hint = Dis_HintVerbose on each of these instructions. The generate_store_FPRF() stores a condition code, which for this application is not used so I commented out the body of the function to avoid calculating the code and storing it. Once it is removed, the workload runs normally. So, we either need to get the dres->hint to limit the BB more, perhaps end the BB once it sees an instruction with the hint or perhaps use a C-code handler in place of the generate_store_FPRF() function. Other thoughts? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 385060] Could not enter receiver if not enabled as payee
https://bugs.kde.org/show_bug.cgi?id=385060 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #2 from Jack --- A standard payment transaction is a transfer of money to a payee. If the recipient of the funds is not a payee, how can KMM create a balanced transaction? The money has to go somewhere. The only way not to need a payee is to make a transfer, and that needs another account to transfer to. Also, from my attempts, saying "no" to add the payee, just blanks out the payee field, and advances the cursor to the category field. It also changes the transaction type from withdrawal or deposit to transfer, and the category dropdown is populated with accounts. I have never had it immediately enter an empty transaction. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385063] New: won't accept password
https://bugs.kde.org/show_bug.cgi?id=385063 Bug ID: 385063 Summary: won't accept password Product: Discover Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: j...@gretton-dann.org.uk Target Milestone: --- Can't install programs using gui program because it won't accept my password, even though it works in konsole with same password -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 385062] New: Cannot build snaps locally
https://bugs.kde.org/show_bug.cgi?id=385062 Bug ID: 385062 Summary: Cannot build snaps locally Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: aleix...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Tried to build this one: https://packaging.neon.kde.org/applications/kate.git/?h=Neon/unstable apol@oliver:~/devel/snaps/kate (Neon/unstable)$ snapcraft cleanbuild Cannot find the definition for part 'kde-frameworks-5-dev'. It may be a remote part, run `snapcraft update` to refresh the remote parts cache. Unsure how to solve it. -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 385061] New: :(
https://bugs.kde.org/show_bug.cgi?id=385061 Bug ID: 385061 Summary: :( Product: abakus Version: unspecified Platform: Other OS: Windows CE Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k.h...@gmx.de Reporter: musli...@hackermail.com Target Milestone: --- Created attachment 108021 --> https://bugs.kde.org/attachment.cgi?id=108021&action=edit Ane Tamvan gan B) Ane Tamvan gan B) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385032] Impossible to set meta key to open kicker/kickoff
https://bugs.kde.org/show_bug.cgi?id=385032 --- Comment #8 from Martin Flöser --- All right I understand the problem: the X11Filter in TabBox is created prior to the one in XInputIntegration and due to that the events are filtered out by TabBox before XInputIntegration gets them. The good news is that this is quite easy to fix: the creation of the X11Filter in TabBox can be delayed till the TabBox gets shown and also can be destroyed when TabBox gets closed. That's also how it's done in e.g. Effects. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385055] PPC VEX temporary storage exhausted
https://bugs.kde.org/show_bug.cgi?id=385055
Carl Love changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Carl Love ---
The first workload is a video workload. When Run with the trace-flags, the
issue seems to be with the expansion of the xxperm instruction.I added
vex_printf("CARLL, set dres->hint\n");
dres->hint = Dis_HintVerbose;
to the code for the xxperm instruction. I verified that the hint was being
set. The expansion.
With the hint, we get a basic block with 32 instructions. There are four
xxperm instructions in the basic block. The expansion is:
0x10076664: xxperm v38,v32,v37
CARLL, set dres->hint
-- IMark(0x10076664, 4, 0) --
t66 = GET:V128(784)
t67 = GET:V128(864)
t65 = GET:V128(880)
t70 = 64HLtoV128(0x0:I64,0x0:I64)
t68 = 64HLtoV128(0x0:I64,0x1F:I64)
t69 = 64HLtoV128(0x0:I64,0xFF:I64)
t72 = ShrV128(AndV128(t67,ShlV128(t68,0x78:I8)),0x78:I8)
t71 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t72,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t72,0x4:I8)
t73 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t72),0xF:I64))),0x8:I32))
t74 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t71),ShlV128(t69,t73))),AndV128(t65,AndV128(t71,ShlV128(t69,t73,t73),0x78:I8)
t75 = OrV128(t74,t70)
t77 = ShrV128(AndV128(t67,ShlV128(t68,0x70:I8)),0x70:I8)
t76 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t77,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t77,0x4:I8)
t78 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t77),0xF:I64))),0x8:I32))
t79 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t76),ShlV128(t69,t78))),AndV128(t65,AndV128(t76,ShlV128(t69,t78,t78),0x70:I8)
t80 = OrV128(t79,t75)
t82 = ShrV128(AndV128(t67,ShlV128(t68,0x68:I8)),0x68:I8)
t81 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t82,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t82,0x4:I8)
t83 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t82),0xF:I64))),0x8:I32))
t84 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t81),ShlV128(t69,t83))),AndV128(t65,AndV128(t81,ShlV128(t69,t83,t83),0x68:I8)
t85 = OrV128(t84,t80)
t87 = ShrV128(AndV128(t67,ShlV128(t68,0x60:I8)),0x60:I8)
t86 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t87,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t87,0x4:I8)
t88 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t87),0xF:I64))),0x8:I32))
t89 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t86),ShlV128(t69,t88))),AndV128(t65,AndV128(t86,ShlV128(t69,t88,t88),0x60:I8)
t90 = OrV128(t89,t85)
t92 = ShrV128(AndV128(t67,ShlV128(t68,0x58:I8)),0x58:I8)
t91 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t92,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t92,0x4:I8)
t93 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t92),0xF:I64))),0x8:I32))
t94 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t91),ShlV128(t69,t93))),AndV128(t65,AndV128(t91,ShlV128(t69,t93,t93),0x58:I8)
t95 = OrV128(t94,t90)
t97 = ShrV128(AndV128(t67,ShlV128(t68,0x50:I8)),0x50:I8)
t96 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t97,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t97,0x4:I8)
t98 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t97),0xF:I64))),0x8:I32))
t99 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t96),ShlV128(t69,t98))),AndV128(t65,AndV128(t96,ShlV128(t69,t98,t98),0x50:I8)
t100 = OrV128(t99,t95)
t102 = ShrV128(AndV128(t67,ShlV128(t68,0x48:I8)),0x48:I8)
t101 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t102,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t102,0x4:I8)
t103 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t102),0xF:I64))),0x8:I32))
t104 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t101),ShlV128(t69,t103))),AndV128(t65,AndV128(t101,ShlV128(t69,t103,t103),0x48:I8)
t105 = OrV128(t104,t100)
t107 = ShrV128(AndV128(t67,ShlV128(t68,0x40:I8)),0x40:I8)
t106 =
64HLtoV128(1Sto64(64to1(V128to64(ShrV128(t107,0x4:I8,1Sto64(64to1(V128to64(ShrV128(t107,0x4:I8)
t108 =
32to8(Mul32(Sub32(0xF:I32,64to32(And64(V128to64(t107),0xF:I64))),0x8:I32))
t109 =
ShlV128(ShrV128(OrV128(AndV128(t66,AndV128(NotV128(t106),ShlV128(t69,t108))),AndV128(t65,AndV128(t106,ShlV128(t69,t108,t108),0x40:I8)
t110 =
[KBibTeX] [Bug 384741] Wrong ID Reported in Duplicate Dialog
https://bugs.kde.org/show_bug.cgi?id=384741 Thomas Fischer changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kbi ||btex/1f8a4d7577185c9c7028f9 ||356cdc7526ea106236 Status|ASSIGNED|RESOLVED --- Comment #4 from Thomas Fischer --- Git commit 1f8a4d7577185c9c7028f9356cdc7526ea106236 by Thomas Fischer. Committed on 23/09/2017 at 19:24. Pushed by thomasfischer into branch 'master'. Handling of empty or duplicate entry ids or macro keys Improving the handling of empty entry ids or macro keys, respectively, or entry ids or macro keys, respectively, that are duplicates of existing entries' ids or macros' keys, respectively. For empty ids/keys, a warning is shown and the original (hopefully valid) id/key is restored. For duplicate ids/keys, the user is asked to choose between restoring the original id/key or keeping the new-but-duplicate id/key. M +56 -19 src/gui/element/elementeditor.cpp M +2-3src/gui/element/elementwidgets.cpp M +7-1src/gui/element/elementwidgets.h https://commits.kde.org/kbibtex/1f8a4d7577185c9c7028f9356cdc7526ea106236 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385032] Impossible to set meta key to open kicker/kickoff
https://bugs.kde.org/show_bug.cgi?id=385032 Martin Flöser changed: What|Removed |Added Keywords||regression Flags||Wayland-, X11+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385032] Impossible to set meta key to open kicker/kickoff
https://bugs.kde.org/show_bug.cgi?id=385032 Martin Flöser changed: What|Removed |Added Assignee|h...@kde.org|kwin-bugs-n...@kde.org Component|Application Menu (Kicker) |platform-x11-standalone Target Milestone|1.0 |--- Product|plasmashell |kwin Version|master |5.10.95 --- Comment #7 from Martin Flöser --- (In reply to Dr. Chapatin from comment #6) > Meta key stops working when I press alt+tab. We had this in the past and back then created: http://commits.kde.org/kwin/66d1a0cc7a03b5f0e9f7a2fd3bda90c24844fdda I fear that one of the X11 refactoring broke this special handling which I hadn't on the radar any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385026] Pointer lock interferes with games
https://bugs.kde.org/show_bug.cgi?id=385026 --- Comment #2 from Sandeep --- Well, when I say menu, it's not the usual context menu that you get when you use the right mouse button click. It's more like a separate screen that shows game menu with options like settings, resume, quit etc. Is there any way for me to capture these requests? If I build KWin debug build, are there any logs I can enable to find out if the app is requesting it a second time? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 385060] Could not enter receiver if not enabled as payee
https://bugs.kde.org/show_bug.cgi?id=385060 --- Comment #1 from Ralf Habacker --- Furthermore pressing 'no' adds a new empty transation without been able to enter receiver, category/account and amount. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 385060] New: Could not enter receiver if not enabled as payee
https://bugs.kde.org/show_bug.cgi?id=385060 Bug ID: 385060 Summary: Could not enter receiver if not enabled as payee Product: kmymoney4 Version: 4.8.0 Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- It is not possible to add a receiver without adding as payee. How to reproduce ? 1. start kmymoney 2. load present file or create a new file 3. open ledger 4. Add a new transaction by pressing STRG-Insert or press 'new' button 5. Enter a receiver 6. Select 'No' on the request to add the receiver as payee What happens ? The entered receiver is deleted. There is no way to add it without adding as payee What is expected ? The receiver should not be deleted -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 RJVB changed: What|Removed |Added Attachment #108017|0 |1 is obsolete|| --- Comment #10 from RJVB --- Created attachment 108020 --> https://bugs.kde.org/attachment.cgi?id=108020&action=edit on-demand set-up of dir-only dirwatching -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381428] Crash in svg parser when loading svg symbols
https://bugs.kde.org/show_bug.cgi?id=381428 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED CC||dimul...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #8 from Dmitry Kazakov --- I have just pushed the proposed patch: https://commits.kde.org/krita/d5418bb57535a3719e4de8565e439e03fd0f6002 It is almost correct, except that it reorders the shapes, which doesn't conform to the standard -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 384903] Lost data
https://bugs.kde.org/show_bug.cgi?id=384903 --- Comment #7 from aper...@gmail.com --- I have about 38 accounts including savings, investment, checking, retirement,assets, credit card, etc Could it be the problem? Ive just reopen the file I really sure that was saved including reconciled accounts and even reconcliliations are not there!!! It is very frustationg! 2017-09-25 15:41 GMT-03:00 Alexandre Perali : > Forgot to mention that another occurrency was after an update stock and > currency prices kmm frozen again and i forced close it loosing previous > data even with 0 auto save. > > > 2017-09-25 15:25 GMT-03:00 Alexandre Perali : > >> Today I was entering new transactions and it seems ok. Then, I try to >> import an ofx file and it imported fine but when I was editing the imported >> transactions it stopped to work while the saving bar below of the screen >> was on 100% and KMM freeze stopping to work. I force close kmm and started >> again but all my previous saving (0sec automatic saving) was not there! >> I noticed that KMM created a file with the "ne.kmyBO8040.new" extension. >> This is the unique clue I have. >> >> >> 2017-09-25 3:05 GMT-03:00 Thomas Baumgart : >> >>> https://bugs.kde.org/show_bug.cgi?id=384903 >>> >>> --- Comment #4 from Thomas Baumgart --- >>> Please make sure, that the number of automatic backups is set to 10 or >>> above so >>> you can always go back a step in case something goes really crazy. >>> >>> -- >>> You are receiving this mail because: >>> You reported the bug. >>> >> >> >> >> -- >> Atc, >> Perali >> > > > > -- > Atc, > Perali > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384511] New project window does not fit to laptop screen (1366x768)
https://bugs.kde.org/show_bug.cgi?id=384511 Sten J. Pettersen changed: What|Removed |Added CC||sten.retroga...@gmail.com --- Comment #1 from Sten J. Pettersen --- This bug affects me too (Debian 9/Gnome 3.26) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384998] I am stuck on the pan tool
https://bugs.kde.org/show_bug.cgi?id=384998 --- Comment #14 from Mika L --- I can't find that anywhere... Although I opened the settings and it says Windows 10 so maybe that's it?(In reply to Alvin Wong from comment #13) > Have you enabled the Windows 8 Pointer Input API in the settings and > restarted krita before testing? > > Also... try to uninstall your current tablet driver, install the latest > version, then clear the tablet driver configuration and try again... -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384750] Progress bars don't work when I save a project to an ISO file
https://bugs.kde.org/show_bug.cgi?id=384750 --- Comment #6 from Dr. Chapatin --- On Arch the progess bars dont work with k3b-git from AUR nor with k3b 17.08.1 from oficial repositories. With k3b 17.08.1 I can test only data project, it does not create dvd-video ISO because a bug not fixed in this release. I cant reproduce this bug on neon dev unstable. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 384864] Oxygen cursors have some reversed symlinks
https://bugs.kde.org/show_bug.cgi?id=384864 Arthur Țițeică changed: What|Removed |Added CC||arthur+...@cloud.titeica.ro -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 384903] Lost data
https://bugs.kde.org/show_bug.cgi?id=384903 --- Comment #6 from aper...@gmail.com --- Forgot to mention that another occurrency was after an update stock and currency prices kmm frozen again and i forced close it loosing previous data even with 0 auto save. 2017-09-25 15:25 GMT-03:00 Alexandre Perali : > Today I was entering new transactions and it seems ok. Then, I try to > import an ofx file and it imported fine but when I was editing the imported > transactions it stopped to work while the saving bar below of the screen > was on 100% and KMM freeze stopping to work. I force close kmm and started > again but all my previous saving (0sec automatic saving) was not there! > I noticed that KMM created a file with the "ne.kmyBO8040.new" extension. > This is the unique clue I have. > > > 2017-09-25 3:05 GMT-03:00 Thomas Baumgart : > >> https://bugs.kde.org/show_bug.cgi?id=384903 >> >> --- Comment #4 from Thomas Baumgart --- >> Please make sure, that the number of automatic backups is set to 10 or >> above so >> you can always go back a step in case something goes really crazy. >> >> -- >> You are receiving this mail because: >> You reported the bug. >> > > > > -- > Atc, > Perali > -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384880] Dirwatcher inefficiency when using QFileSystemWatcher
https://bugs.kde.org/show_bug.cgi?id=384880 --- Comment #9 from RJVB --- Created attachment 108017 --> https://bugs.kde.org/attachment.cgi?id=108017&action=edit on-demand set-up of dir-only dirwatching This is a PoC implementation of my idea of deferring the dirwatcher feeding to the worker that does the actual project directory traversal (the FileManagerListJob class), for now coupled with the possibility to disable dirwatching for my own convenience. Initial tests show that - big project import is a *lot* faster - dirwatching actually works on Mac. I've used a QSet to avoid repetitive calls to KDirWatch::contains(). I haven't timed it, but judging from the latter's implementation the former should be considerably faster. I hope I haven't missed a place or two where entries have to be removed from the dirwatcher. Let me know if this is mature enough to phab it? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 384481] mapviewer (qtlocation), minuet, kalgebra-mobile segfault at startup
https://bugs.kde.org/show_bug.cgi?id=384481 Antonio Rojas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-integration/1781d60b230 |sma-integration/059369d6b6a |c32977c078e2943d94c506d7ee6 |9a99538c175a3c53058cbb54e8a |45 |bc --- Comment #5 from Antonio Rojas --- Git commit 059369d6b6a9a99538c175a3c53058cbb54e8abc by Antonio Rojas. Committed on 25/09/2017 at 18:27. Pushed by arojas into branch 'Plasma/5.11'. Use QQuickStyle to set the QQC2 style Use QQuickStyle::setStyle instead of an environment variable to set the QQC2 desktop style. This prevent the style from being inherited by plasmashell (or krunner) child processes, which makes QGuiApplications crash. The QQC1 style still needs to be set via an environment variable, so we explicitely unset it for non-QApplications to prevent them from crashing. Differential Revision: https://phabricator.kde.org/D7953 M +1-1CMakeLists.txt M +1-0src/platformtheme/CMakeLists.txt M +10 -5src/platformtheme/kdeplatformtheme.cpp https://commits.kde.org/plasma-integration/059369d6b6a9a99538c175a3c53058cbb54e8abc -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 384903] Lost data
https://bugs.kde.org/show_bug.cgi?id=384903 --- Comment #5 from aper...@gmail.com --- Today I was entering new transactions and it seems ok. Then, I try to import an ofx file and it imported fine but when I was editing the imported transactions it stopped to work while the saving bar below of the screen was on 100% and KMM freeze stopping to work. I force close kmm and started again but all my previous saving (0sec automatic saving) was not there! I noticed that KMM created a file with the "ne.kmyBO8040.new" extension. This is the unique clue I have. 2017-09-25 3:05 GMT-03:00 Thomas Baumgart : > https://bugs.kde.org/show_bug.cgi?id=384903 > > --- Comment #4 from Thomas Baumgart --- > Please make sure, that the number of automatic backups is set to 10 or > above so > you can always go back a step in case something goes really crazy. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 385024] Scroll the apps list using a touch screen is not intuitive
https://bugs.kde.org/show_bug.cgi?id=385024 Aleix Pol changed: What|Removed |Added Component|discover|general Assignee|aleix...@kde.org|notm...@gmail.com CC||k...@davidedmundson.co.uk Product|Discover|frameworks-qqc2-desktop-sty ||le --- Comment #1 from Aleix Pol --- No, swiping should scroll the list. Assigning to qqc2-desktop-style. I'm pretty sure it works on the phone, so assigning to the qqc2 style. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385018] top bar is broken when the package has a long name
https://bugs.kde.org/show_bug.cgi?id=385018 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dis ||cover/2c5f7ac09bd5ecb499247 ||824c175f7bf802dab4f --- Comment #1 from Aleix Pol --- Git commit 2c5f7ac09bd5ecb499247824c175f7bf802dab4f by Aleix Pol. Committed on 25/09/2017 at 18:03. Pushed by apol into branch 'master'. Make sure the application name doesn't overflow Instead of using several lines, just elide. M +1-0discover/qml/ApplicationPage.qml https://commits.kde.org/discover/2c5f7ac09bd5ecb499247824c175f7bf802dab4f -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385038] Discover uses hidden breeze-styled main scrollbar, when using the Oxygen theme
https://bugs.kde.org/show_bug.cgi?id=385038 Aleix Pol changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from Aleix Pol --- Please make sure you have qqc2-desktop-style installed. Ask your distribution what's the steps to take. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385038] Discover uses hidden breeze-styled main scrollbar, when using the Oxygen theme
https://bugs.kde.org/show_bug.cgi?id=385038 --- Comment #1 from Aleix Pol --- Created attachment 108015 --> https://bugs.kde.org/attachment.cgi?id=108015&action=edit Working -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384849] Database dropped when network collection not mounted
https://bugs.kde.org/show_bug.cgi?id=384849 --- Comment #6 from tpg --- makes sense. What is the right order to fix it? +- or -+? Theo -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385059] crash plasma
https://bugs.kde.org/show_bug.cgi?id=385059 David Edmundson changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Component|general |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384849] Database dropped when network collection not mounted
https://bugs.kde.org/show_bug.cgi?id=384849 --- Comment #5 from Maik Qualmann --- If the collection is established under network, digiKam assumes that it is not always available. The thumbnails are retained when the network connection is lost. When trying to open an image, comes a tooltip that the connection to the network must be reconnected. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385059] New: crash plasma
https://bugs.kde.org/show_bug.cgi?id=385059 Bug ID: 385059 Summary: crash plasma Product: plasmashell Version: 5.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: wodd...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.13.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I crash it every time I make updates on Opensuse Tumbleweed via the applet in the panel. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb1ed3dd900 (LWP 1737))] Thread 19 (Thread 0x7fb0c60e8700 (LWP 3796)): #0 0x7fb1e69cbcc8 in read () at /lib64/libc.so.6 #1 0x7fb1dc7ab751 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-11.0.so #2 0x7fb1dd789dde in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7fb1dd78a850 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7fb1dd78a910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7fb1dd798779 in () at /usr/lib64/libpulse.so.0 #6 0x7fb1dc7da438 in () at /usr/lib64/pulseaudio/libpulsecommon-11.0.so #7 0x7fb1e628b2f8 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb1e69da5ef in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fb0e7fff700 (LWP 3795)): #0 0x7fb1e1a05474 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb1e19bf548 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb1e19bff4b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb1e19c012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb1e72fb6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb1e72a435a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb1e70d431a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fb1ea220705 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fb1e70d8d2e in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb1e628b2f8 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb1e69da5ef in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fb0ecc98700 (LWP 1886)): #0 0x7fb1e19e79e3 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb1e19c011d in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb1e72fb6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb1e72a435a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb1e70d431a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7fb0ef53af37 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #6 0x7fb1e70d8d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb1e628b2f8 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb1e69da5ef in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fb0f4f56700 (LWP 1881)): #0 0x7fb1e69d012b in poll () at /lib64/libc.so.6 #1 0x7fb1e19c0019 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb1e19c012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb1e72fb6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb1e72a435a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb1e70d431a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb1e70d8d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb1e628b2f8 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb1e69da5ef in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fb107a42700 (LWP 1871)): #0 0x7fb1e629159d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb1c0d16beb in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fb1c0d16b07 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fb1e628b2f8 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb1e69da5ef in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fb12cff9700 (LWP 1869)): #0 0x7fb1e69d012b in poll () at /lib64/libc.so.6 #1 0x7fb1e19c0019 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb1e19c012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb1e72fb6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb1e72a435a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb1e70d431a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb1eadc7342 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7fb1e70d8d2e in () at /usr/lib64/libQt5Core
[kdevelop] [Bug 385058] New: A file search result becomes unreadable.
https://bugs.kde.org/show_bug.cgi?id=385058 Bug ID: 385058 Summary: A file search result becomes unreadable. Product: kdevelop Version: 5.1.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: markus.elfr...@web.de Target Milestone: --- Created attachment 108014 --> https://bugs.kde.org/attachment.cgi?id=108014&action=edit excerpt from a screenshot with a questionable text display I selected an entry in the view of file search results by the program “KDevelop 5.1.2-32.1”. Unfortunately, the text selection can become unreadable in my graphical configuration after a double-click there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384849] Database dropped when network collection not mounted
https://bugs.kde.org/show_bug.cgi?id=384849 --- Comment #4 from tpg --- Good question, Maik, No it isn't. It's a local collection. When version 5 came, it seemed to have lost everything in use until that moment. So I reconfigured. I may have thought it made no difference. The file browsing menus are identical anyway, asking for the mount point. Come to think of it, the mount point is also a local directory, but when nothing mounted there, empty. I will add a collection on removable shares, and when next remove the local collection. Or should I remove it first and next add the network share? Theo Vriendelijke groet, Theo Groen 2017-09-23 23:08 GMT+02:00 Maik Qualmann : > https://bugs.kde.org/show_bug.cgi?id=384849 > > Maik Qualmann changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > > --- Comment #3 from Maik Qualmann --- > Problem is not reproducible here. The mount point has also been added as a > network collection under digiKam? > > Maik > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput
https://bugs.kde.org/show_bug.cgi?id=383379 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #12 from Nate Graham --- Fantastic work, guys! Here's some documentation on how to develop a KCM: https://techbase.kde.org/Development/Tutorials/KCM_HowTo Probably the best option would be to modify the existing touchpad KCM to present a different set of settings and user interface elements when it detects that libinput is being used. But if you want to developer a new, separate KCM that only handles libinput, that's okay too, since synaptics isn't supported with Wayland and eventually everyone will have to use libinput anyway. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 384835] Crash on a feed with superfluous whitespace
https://bugs.kde.org/show_bug.cgi?id=384835 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #1 from Allen Winter --- 5.2.3 is pretty old. In the current version I don't get a crash. I get a popup saying the feed doesn't exist when trying to add http://wp.rac.ca/feed/ -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 385057] New: unable to operate and/or configurate kadress book; as soon as click to open, it's krash...
https://bugs.kde.org/show_bug.cgi?id=385057 Bug ID: 385057 Summary: unable to operate and/or configurate kadress book; as soon as click to open, it's krash... Product: kdebugsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: camillei...@videotron.ca Target Milestone: --- Created attachment 108012 --> https://bugs.kde.org/attachment.cgi?id=108012&action=edit unable to config adress book Unable to config. KDEadress book; ( see file ...I am working with Linux MInt sarah and KDE 5.6 i AM ALSO TRYING TO config and OPERATE kmail AND Kadresse book Many thanks to allow us to have ''free internet'' Camille Chabot -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput
https://bugs.kde.org/show_bug.cgi?id=383379 slimbook changed: What|Removed |Added CC||s...@slimbook.es --- Comment #11 from slimbook --- Hello, We are SLIMBOOK TEAM, and we want to join this bug. We have developed a small application to change the configuration of libinput, and we tell you a little how it works to see if you can solve it. It is best that you can change the touchpad settings without installing third-party applications. Image of options of our app: https://slimbook.es/images/imagetuto/touchpadevdev.png We have never developed for Plasma, but I think it should be another "kcm" when it is not a Synaptics touchpad (the synclient status service) or in our case the Unique ID: AH6Q.bGO0sOimOM3 - To get touchpad hardware id: hwinfo --mouse *Previous command returns the line: 'Unique ID: AH6Q.bGO0sOimOM3' and line 'Model: "ImExPS/2 Generic Explorer Mouse"' (model name used later for setting properties using 'xinput') - To get touchpad properties we can modify: xinput --list-props "ImExPS/2 Generic Explorer Mouse" *We can use model name (like previous line) or number id related with model name obtained when running command 'xinput': xinput --list-props 11 - To modify values of properties 'libinput Accel Speed' and 'libinput Natural Scrolling Enabled': xinput --set-prop "ImExPS/2 Generic Explorer Mouse" "libinput Accel Speed" 1 xinput --set-prop "ImExPS/2 Generic Explorer Mouse" "libinput Natural Scrolling Enabled" 1 *Like in previous step, we can use number id instead of model name. Propertie "libinput Natural Scrolling Enabled" accepts values 0 or 1. Propertie "libinput Accel Speed" accepts values between -1 and 1. More information in our app: https://github.com/slimbook/slimbook-touchpad Thanks, -- You are receiving this mail because: You are watching all bug changes.
[kdepimlibs] [Bug 199530] Closing Kontact (and other situations) causes a crash [QCoreApplication::notifyInternal, ..., KMessageBox::createKMessageBox, ..., KABC::GuiErrorHandler::error]
https://bugs.kde.org/show_bug.cgi?id=199530 Camille Chabot changed: What|Removed |Added CC||camillei...@videotron.ca -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 380429] Install prompt asks the user to pick one of two choices, but gives a yes/no set of buttons
https://bugs.kde.org/show_bug.cgi?id=380429 p.sonalipa...@gmail.com changed: What|Removed |Added CC||p.sonalipa...@gmail.com --- Comment #1 from p.sonalipa...@gmail.com --- I would like to work on this bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384156] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0x6B 0x6A
https://bugs.kde.org/show_bug.cgi?id=384156 Alex Henrie changed: What|Removed |Added CC||alexhenri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360541] HiDPI option in Qt also scales the canvas widget
https://bugs.kde.org/show_bug.cgi?id=360541 Alvin Wong changed: What|Removed |Added OS|MS Windows |All Platform|MS Windows |unspecified -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 385056] New: Baloo crash on delete a lots files on my home
https://bugs.kde.org/show_bug.cgi?id=385056 Bug ID: 385056 Summary: Baloo crash on delete a lots files on my home Product: frameworks-baloo Version: 5.38.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: leviat...@gmx.com Target Milestone: --- Application: baloo_file (5.38.0) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-35-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: I was deleting a lot of files from my personal folder. It was completely deleted (pushing keys Control + Delete), didn't move to the recycling bin. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f650ca368c0 (LWP 1559))] Thread 2 (Thread 0x7f6501e0c700 (LWP 1588)): #0 0x7f6507d33a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6507cee929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6507cef2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6507cef49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f650b6d594b in QEventDispatcherGlib::processEvents (this=0x7f64fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f650b67e7ca in QEventLoop::exec (this=this@entry=0x7f6501e0bcd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f650b4a7cd4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f650cb4db75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f650b4ac989 in QThreadPrivate::start (arg=0x7f650cbc3da0) at thread/qthread_unix.cpp:368 #9 0x7f650a1366ba in start_thread (arg=0x7f6501e0c700) at pthread_create.c:333 #10 0x7f650aab03dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f650ca368c0 (LWP 1559)): [KCrash Handler] #6 0x7f650a9de428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f650a9e002a in __GI_abort () at abort.c:89 #8 0x7f650aa207ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f650ab39e98 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f650aa2937a in malloc_printerr (ar_ptr=, ptr=, str=0x7f650ab39f88 "double free or corruption (top)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7f650aa2d53c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7f650b4add91 in QArrayData::deallocate (data=, objectSize=objectSize@entry=2, alignment=alignment@entry=8) at tools/qarraydata.cpp:167 #13 0x00421f00 in QTypedArrayData::deallocate (data=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:237 #14 QString::~QString (this=0x7fff4684aa70, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1084 #15 Baloo::PendingFileQueue::enqueue (this=0xb162f0, file=...) at /workspace/build/src/file/pendingfilequeue.cpp:66 #16 0x0041fc16 in Baloo::FileWatch::slotFileDeleted (this=0x7fff4684b2f0, urlString=..., isDir=) at /workspace/build/src/file/filewatch.cpp:116 #17 0x7f650b6acf46 in QtPrivate::QSlotObjectBase::call (a=0x7fff4684ad30, r=0x7fff4684b2f0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #18 QMetaObject::activate (sender=sender@entry=0xb12540, signalOffset=, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7fff4684ad30) at kernel/qobject.cpp:3749 #19 0x7f650b6ad527 in QMetaObject::activate (sender=sender@entry=0xb12540, m=m@entry=0x641be0 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7fff4684ad30) at kernel/qobject.cpp:3628 #20 0x00426a04 in KInotify::deleted (_t2=true, _t1=..., this=0xb12540) at /workspace/build/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330 #21 KInotify::slotEvent (this=, socket=) at /workspace/build/src/file/kinotify.cpp:381 #22 0x7f650b6acf46 in QtPrivate::QSlotObjectBase::call (a=0x7fff4684aeb0, r=0xb12540, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #23 QMetaObject::activate (sender=sender@entry=0xb360b0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4684aeb0) at kernel/qobject.cpp:3749 #24 0x7f650b6ad527 in QMetaObject::activate (sender=sender@entry=0xb360b0, m=m@entry=0x7f650b937cc0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4684aeb0) at kernel/qobject.cpp:3628 #25 0x7f650b6b8ec8 in QSocketNotifier::activated (this=this@entry=0xb360b0, _t1=14, _t2=...) at .moc/moc_qsocketnotifier.cpp:13
[valgrind] [Bug 385055] New: PPC VEX temporary storage exhausted
https://bugs.kde.org/show_bug.cgi?id=385055
Bug ID: 385055
Summary: PPC VEX temporary storage exhausted
Product: valgrind
Version: 3.14 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: c...@us.ibm.com
Target Milestone: ---
Power 9 application is receiving the error
Pool = TEMP, start 0x5861af28 curr 0x58adfa48 end 0x58adfa67 (size
500)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
I increased the N_TEMPORARY_BYTES and N_PERMANENT_BYTES #defines as
given below.
--- a/VEX/priv/main_util.c
+++ b/VEX/priv/main_util.c
@@ -55,10 +55,10 @@
#if defined(ENABLE_INNER)
/* 5 times more memory to be on the safe side: consider each
allocation is
8 bytes, and we need 16 bytes redzone before and after. */
-#define N_TEMPORARY_BYTES (5*500)
+#define N_TEMPORARY_BYTES (5*20)
static Bool mempools_created = False;
#else
-#define N_TEMPORARY_BYTES 500
+#define N_TEMPORARY_BYTES 20
#endif
static HChar temporary[N_TEMPORARY_BYTES]
__attribute__((aligned(REQ_ALIGN)));
@@ -70,9 +70,9 @@ static ULong temporary_bytes_allocd_TOT = 0;
#if defined(ENABLE_INNER)
/* See N_TEMPORARY_BYTES */
-#define N_PERMANENT_BYTES (5*1)
+#define N_PERMANENT_BYTES (5*10)
#else
-#define N_PERMANENT_BYTES 1
+#define N_PERMANENT_BYTES 10
Once these were increased both workloads then hit the error:
x264 [info]: profile High, level 3.1
vex: priv/host_generic_reg_alloc3.c:470 (doRegisterAllocation_v3):
Assertion `instrs_in->arr_used <= 15000' failed.
vex storage: T total 373013384 bytes allocated
vex storage: P total 192 bytes allocated
The issue appears to be the same issue seen on arm64 in bugzilla
https://bugs.kde.org/show_bug.cgi?id=375839
Per this bugzill, it was found that using the command line option
--vex-guest-max-insns=2 allowed the application to run but does appear to run
with a significant performance hit.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 384998] I am stuck on the pan tool
https://bugs.kde.org/show_bug.cgi?id=384998 --- Comment #13 from Alvin Wong --- Have you enabled the Windows 8 Pointer Input API in the settings and restarted krita before testing? Also... try to uninstall your current tablet driver, install the latest version, then clear the tablet driver configuration and try again... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383042] Cursor Offset
https://bugs.kde.org/show_bug.cgi?id=383042 --- Comment #4 from Alvin Wong --- (In reply to kumercxi from comment #3) > Created attachment 107996 [details] > I dont know if I did it correctely Did you tried drawing on the canvas with the stylus after enabling tablet logging? You need to do that in order to have the events captured in the log. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385032] Impossible to set meta key to open kicker/kickoff
https://bugs.kde.org/show_bug.cgi?id=385032 --- Comment #6 from Dr. Chapatin --- Meta key stops working when I press alt+tab. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385032] Impossible to set meta key to open kicker/kickoff
https://bugs.kde.org/show_bug.cgi?id=385032 --- Comment #5 from Dr. Chapatin --- I'm on neon dev unstable now, but I noticed this problem some days ago on Arch running plasma 5.11 beta. I just noticed here that the meta key stops working randomly and works again after restart my session.. On Arch with 5.11 beta I never saw the meta key to work. Informação de suporte do KWin: A seguinte informação deve ser usada ao pedir suporte, p.ex., no http://forum.kde.org. Ela fornece informações sobre a instância atualmente em execução, quais as opções usadas, qual o driver de OpenGL e os efeitos em execução. Envie a informação fornecida após este texto introdutório para um serviço de área de transferência remoto, como o http://paste.kde.org, em vez de colar o texto nos tópicos de suporte. == Version === KWin version: 5.11.90 Qt Version: 5.9.1 Qt compile version: 5.9.1 XCB compile version: 1.11.1 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11903000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 1, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 101 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: LVDS-1 Geometry: 0,0,1366x768 Refresh Rate: 59.989 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL version string: 3.0 Mesa 17.0.7 OpenGL platform interface: GLX OpenGL shading language version string: 1.30 Driver: Intel GPU class: IvyBridge OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 17.0.7 X server version: 1.19.3 Linux kernel version: 4.10 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom slidingpopups kwin4_effect_logout kwin4_effect_login kwin4_effect_windowaperture slide screenshot minimizeanimation desktopgrid kwin4_effect_translucency colorpicker kwin4_effect_maximize kwin4_effect_frozenapp kwin4_effect_fade kwin4_effect_morphingpopups kwin4_effect_dialogparent presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTrackin
[frameworks-kglobalaccel] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0
https://bugs.kde.org/show_bug.cgi?id=384597 Martin Flöser changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kgl ||obalaccel/68e35f234ca7d866b ||cb54442d22892450d871848 Status|CONFIRMED |RESOLVED --- Comment #27 from Martin Flöser --- Git commit 68e35f234ca7d866bcb54442d22892450d871848 by Martin Flöser. Committed on 25/09/2017 at 15:30. Pushed by graesslin into branch 'master'. Revert "KGlobalAccel: port to KKeyServer's new method symXModXToKeyQt, to fix numpad keys" This reverts commit 2c20ddff034e4958bf0536ca91ae9e444955305d. I'm reverting as we don't have a fix yet and the next release is too close to risk any changes. As explained in the original review request for this feature: touching this code base is dangerous. The code is extremely fragile. A month of living in master was not enough to spot the severe regressions we had. As we are now only a few days away from next release we cannot expect to discover regressions any fix would cause. I don't really see a solution to this problem: any change might cause issues especially in KWin, KScreenLocker and KGlobalAccel. All of them have the problem that the maintainer of those components is not running X11 and won't spot the regressions. Futhermore we don't have any test cases for the complete key handing stack on X11. We won't find the regressions. My personal recommendation would be to no longer change the X11 side and instead all together work on Wayland and get it ready. There the world looks better: we have a sane input stack which is completly unit tested. The first regression caused by the changes here was discovered by a KWin test case for Wayland. That's the world where we can change and improve the stack. Let X die, long live Wayland! If someone wants to take on the task to improve the X11 stack here I expect some serious work on the testability of this fragile stack. If we see that the shortcuts will still match I would be way more confident to accept a change. CCMAIL: kde-frameworks-de...@kde.org M +45 -7src/runtime/plugins/xcb/kglobalaccel_x11.cpp https://commits.kde.org/kglobalaccel/68e35f234ca7d866bcb54442d22892450d871848 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381724] Switching windows for the current application broken
https://bugs.kde.org/show_bug.cgi?id=381724 --- Comment #10 from Franco Pellegrini --- I sure will, is there any additional package I can install for giving you debug information or something like that? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342326] window contents freeze
https://bugs.kde.org/show_bug.cgi?id=342326 JKAbrams changed: What|Removed |Added CC||j...@jkabrams.se --- Comment #31 from JKAbrams --- I've had this issue a few years and it is still there. This is the only major annoyance I run into repeatedly with KDE, it happens on average ~2-3 times a week (while working full time). Mostly it happens to Firefox and VirtualBox. I've also seen it happen on Libreoffice, Audacious and Eclipse, but it can seemingly happen on any application in heavy use. It also happens to Plasma itself where the taskbar stops updating (opening/switching windows lags one window behind), hover will not redraw it but clicking on the taskbar will. I've had the problem happen on two different machines (both with nVidia graphics but it happens with both the proprietary driver and nouveau) from early versions of KF5 up until present Plasma 5.8.7, Frameworks 5.36.0, QT 5.6.1, Kernel 4.11.0-14. Arch Linux and Linux Mint 18.2. I currently runt compositing on OpenGL 3.1, but OpenGL 2.0 also had the problem. Others (#330424) report that Xrender is also affected. >From my user perspective these are possible duplicates as they describe the same symptoms: https://bugs.kde.org/show_bug.cgi?id=330424 https://bugs.kde.org/show_bug.cgi?id=366651 https://bugs.kde.org/show_bug.cgi?id=353983 https://bugs.kde.org/show_bug.cgi?id=342500 https://bugs.kde.org/show_bug.cgi?id=343661 https://www.reddit.com/r/kde/comments/6ggjx8/windows_sometimes_stop_updating_content_kwin/ https://forum.kde.org/viewtopic.php?t=101313 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385032] Impossible to set meta key to open kicker/kickoff
https://bugs.kde.org/show_bug.cgi?id=385032 --- Comment #4 from Martin Flöser --- Please provide the output of: qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381724] Switching windows for the current application broken
https://bugs.kde.org/show_bug.cgi?id=381724 --- Comment #9 from Martin Flöser --- Please monitor whether that happens again and whether there is a pattern. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385051] kwin crash on alt+tab switching
https://bugs.kde.org/show_bug.cgi?id=385051 Martin Flöser changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- Crash happens in OpenGL driver. Please note that you use swrast which means software emulation. It looks like the driver is not installed. Best check your installation. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 385044] Add weather informations into KCalendar
https://bugs.kde.org/show_bug.cgi?id=385044 Allen Winter changed: What|Removed |Added Platform|Kubuntu Packages|unspecified Product|kontact |korganizer CC||win...@kde.org OS|Linux |All Component|calendar|agendaview (weekview) Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[sweeper] [Bug 338526] Clearing of Run Command History failed
https://bugs.kde.org/show_bug.cgi?id=338526 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Burkhard Lueck --- Works using sweeper master in kf5 build from sources and in neon git unstable. This issue was obviously fixed with https://cgit.kde.org/sweeper.git/commit/?id=28b1d032edef6e7e934749aabe0fe382fac26a5c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385054] Drag and drop with multiple monitors location is incorrect
https://bugs.kde.org/show_bug.cgi?id=385054 --- Comment #1 from Kenneth Ingham --- It submitted when I hit enter after attaching the screen shot and before I had typed everything. Here is what I intended to submit. When using two monitors, drag and drop has an incorrect cursor or icon location. In the attached screen shot, the cursor is on the selected image. The icon for the drag and drop file is off to the right. This always occurs with a second monitor attached, and never occurs when using just the laptop internal display. This problem occurs with all apps such as Digikam, dolphin, browsers, etc. I am running OpenSUSE Tumbleweed, current as of 2017-09-24. Hardware is an x86_64 architecture. Laptop display is 3480x2160, external monitor is wide aspect ratio 2560x1080. $ rpm -qa '*plasma*' plasma5-addons-5.10.5-1.2.x86_64 plasma5-session-wayland-5.10.5-1.1.noarch plasma5-workspace-branding-openSUSE-42.1.1-23.1.noarch plasma-nm5-5.10.5-1.2.x86_64 plasma-nm5-pptp-5.10.5-1.2.x86_64 patterns-kde-kde_plasma-20170319-9.1.noarch plasma-framework-private-5.37.0-1.1.x86_64 plasma5-workspace-libs-5.10.5-2.1.x86_64 plasma5-workspace-5.10.5-2.1.x86_64 plasma-framework-components-5.37.0-1.1.x86_64 plasma5-pk-updates-0.2-7.4.x86_64 plasma-nm5-vpnc-5.10.5-1.2.x86_64 plasma5-session-5.10.5-1.1.noarch plasma5-pa-5.10.5-1.2.x86_64 plasma5-defaults-openSUSE-42.1.1-23.1.noarch plasma-framework-5.37.0-1.1.x86_64 plasma5-integration-plugin-5.10.5-1.1.x86_64 plasma-nm5-openvpn-5.10.5-1.2.x86_64 plasma5-theme-openSUSE-42.1.1-23.1.noarch plasma5-desktop-5.10.5-1.2.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385054] New: Drag and drop with multiple monitors location is incorrect
https://bugs.kde.org/show_bug.cgi?id=385054 Bug ID: 385054 Summary: Drag and drop with multiple monitors location is incorrect Product: plasmashell Version: 5.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: kdeb...@i-pi.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 108011 --> https://bugs.kde.org/attachment.cgi?id=108011&action=edit Mouse location and icon+drag and drop location offset When using two monitors, drag and drop has an incorrect cursor location. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381724] Switching windows for the current application broken
https://bugs.kde.org/show_bug.cgi?id=381724 Franco Pellegrini changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WORKSFORME |--- --- Comment #8 from Franco Pellegrini --- Hey Martin, this manifested again this morning, however in this case, the Alt + ` was working fine, until at some point it stopped working. After I kill the kglobalaccel5 PID and started it again with kglobalaccel5& I have the switching windows working again, and did not have any more issues yet. KDE Neon 5.10 KDE Plasma 5.10.5 KDE Frameworks 5.38.0 QT 5.9.1 Kernel 4.4.0-96-generic OS: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 Lukasz changed: What|Removed |Added CC|dolo...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385053] New: Kmail crash
https://bugs.kde.org/show_bug.cgi?id=385053 Bug ID: 385053 Summary: Kmail crash Product: kmail2 Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m.fa...@yahoo.fr Target Milestone: --- Application: kmail (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.87-25-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: I started kmail.Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef5732b940 (LWP 17334))] Thread 22 (Thread 0x7feeef7f5700 (LWP 17366)): #0 0x7fef4a1e50bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fef4117dd10 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fef4116b7bb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fef4116ba35 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fef41168327 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fef42a431ca in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fef42a434e1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fef42a435d2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fef4130bc12 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7fef412f76b5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7fef413234f0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7fef4131fece in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7fef4a1e0744 in start_thread () from /lib64/libpthread.so.0 #13 0x7fef5446eaad in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7feeefff6700 (LWP 17365)): #0 0x7fef4a1e50bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fef41322189 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fef4132294d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fef41323170 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fef4131fece in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fef4a1e0744 in start_thread () from /lib64/libpthread.so.0 #6 0x7fef5446eaad in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7feef87f8700 (LWP 17364)): #0 0x7fef5446620d in poll () from /lib64/libc.so.6 #1 0x7fef3993b0a1 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7fef3992c76c in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7fef3992cdde in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7fef3992ce90 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7fef3993b006 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7fef34699408 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7fef4a1e0744 in start_thread () from /lib64/libpthread.so.0 #8 0x7fef5446eaad in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7feef8ff9700 (LWP 17363)): #0 0x7fef4a1e50bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fef41318cbf in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fef41318d94 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fef412fb62b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fef4130bc12 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fef412f76b5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fef413234f0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fef4131fece in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fef4a1e0744 in start_thread () from /lib64/libpthread.so.0 #9 0x7fef5446eaad in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7feef97fa700 (LWP 17362)): #0 0x7fef4a1e50bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fef40d1e979 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fef41323170 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fef4131fece in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fef4a1e0744 in start_thread () from /lib64/libpthread.so.0 #5 0x7fef5446eaad in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7feef9ffb700 (LWP 17361)): #0 0x7fef5447aeab in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7fef5447ca46 in __fprintf_chk () from /lib64/libc.so.6 #2 0x7fef38377fdf in ?? () from /usr/lib64/libevent-2.0.so.5 #3 0x7fef383781b7 in event_warn () from /usr/lib64/libevent-2.0.so.5 #4 0x7fef3837c468 in ?? () from /usr/lib64/libevent-2.0.so.5 #5 0x7fef38368477 in event_base_loop () from /usr/lib64/libevent-2.0.so.5 #6 0x7fef412d884e in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fef4130bc12 i
[krunner] [Bug 383389] Krunner crash
https://bugs.kde.org/show_bug.cgi?id=383389 Kishore Gopalakrishnan changed: What|Removed |Added Attachment #107208|0 |1 is obsolete|| --- Comment #3 from Kishore Gopalakrishnan --- Created attachment 108010 --> https://bugs.kde.org/attachment.cgi?id=108010&action=edit Backtrace with additional debug symbols I have finally been able to catch another crash. This one is with debug symbols for glibc, k1i8n, and sqlite installed. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 385052] New: Cannot connect to the Akonadi service
https://bugs.kde.org/show_bug.cgi?id=385052 Bug ID: 385052 Summary: Cannot connect to the Akonadi service Product: Akonadi Version: 5.6.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: a...@mpe.mpg.de Target Milestone: --- Since 17.08 I often get: Cannot connect to the Akonadi service When moving msg or marking as spam. In error log I see: Sep 25 13:21:41 allee plasma5[5194]: org.kde.pim.imapresource: Called item() while state holds multiple items! Sep 25 13:21:43 allee plasma5[5194]: org.kde.pim.akonadicore: Invalid command, the world is going to end! Sep 25 13:21:43 allee plasma5[5194]: QIODevice::read (QLocalSocket): device not open Sep 25 13:21:43 allee plasma5[5194]: org.kde.pim.akonadicore: "Cannot connect to the Akonadi service." Sep 25 13:21:43 allee plasma5[5194]: org.kde.pim.akonadiserver: Invalid command: no such handler for 10 Sep 25 13:21:43 allee plasma5[5194]: org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/user/20334/akonadi-ach.mpbfwB/akonadiserver-cmd.socket" Sep 25 13:21:43 allee plasma5[5194]: org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket: Remote closed" Sep 25 13:21:43 allee plasma5[5194]: org.kde.pim.akonadicore: Error during ItemSync: "Cannot connect to the Akonadi service." Sep 25 13:21:43 allee plasma5[5194]: org.kde.pim.akonadicore: Protocol Exception: "Failed to write data to stream" Sep 25 13:21:43 allee plasma5[5194]: QIODevice::read (QLocalSocket): device not open Since 17.08 this happens more or less several times per day even on weekends, when I don't touch my computer at work. I have this problem on all three KDE neon user systems, that I use. Unfortunately I've not notices/found a rule how to trigger the bug. Any hint appreciated. Achim -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385051] New: kwin crash on alt+tab switching
https://bugs.kde.org/show_bug.cgi?id=385051 Bug ID: 385051 Summary: kwin crash on alt+tab switching Product: kwin Version: 5.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: lari.ka...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.33.0 Operating System: Linux 4.10.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: browsing the web, watching video, listening to spotify web player... if I would switch widows, it would crash on alt+tab The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2a87ec5900 (LWP 8426))] Thread 13 (Thread 0x7f2a3a20e700 (LWP 8455)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a83dc88e4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f2a83dc8929 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f2a4f45e700 (LWP 8452)): #0 0x7f2a8784f8ab in ppoll () at /lib64/libc.so.6 #1 0x7f2a84e73649 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f2a84e74c26 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f2a84e2035a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2a84c5031a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f2a7f560705 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f2a84c54d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f2a50e9c700 (LWP 8451)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2a64a88227 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f2a5169d700 (LWP 8450)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2a64a88227 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f2a51e9e700 (LWP 8449)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2a64a88227 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f2a5269f700 (LWP 8448)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2a64a88227 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f2a52ea0700 (LWP 8447)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2a64a88227 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f2a536a1700 (LWP 8446)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2a64a88227 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f2a53ea2700 (LWP 8445)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2a64a88227 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2a80a71537 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2a8785904f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f2a546a3700 (LWP 8444)): #0 0x7f2a80a779a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2a64a883ab in () at /u
[krita] [Bug 385050] New: workflow improvement: create a group when several layers are selected and that user clicks on "add layer"
https://bugs.kde.org/show_bug.cgi?id=385050 Bug ID: 385050 Summary: workflow improvement: create a group when several layers are selected and that user clicks on "add layer" Product: krita Version: 3.1.2 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: gordie.lachance+...@gmail.com Target Milestone: --- Hi ! Small idea here that could be great: When the user selects several layers in the layers stack and clicks on the "add layer" (+) icon; it would be great to automatically create a layer group and move the selected layers inside that new group. What do you think of it ? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384885] Crash in the SVN plugin [svn::pool_create]
https://bugs.kde.org/show_bug.cgi?id=384885 Andreas Pakulat changed: What|Removed |Added CC|ap...@gmx.de| -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #16 from Jochen Trumpf --- Oh, and I forgot to say, obviously one needs to fix existing iCal resources by hand or discard them and start from scratch. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #15 from Jochen Trumpf --- The above two patches against 17.08.1 fix this issue for me. My calendar setup is rather basic with everything in a single timezone and I have not tested if the patches would work with multiple timezones. But at least they give a pointer to where to start. The approach taken in the patches is to make this change seamless for the user. Everything looks and behaves the same from their perspective but what gets written to the iCal resource changes. The current korganizer GUI is limited compared to the full KCalCore API for recurrence. I have tried to map the existing limitations in the GUI best possible to the KCalCore API (except for the currently naive handling of timezones). This would break if the korganizer GUI would ever allow sub-daily recurrence. But for now we can write DATE entries for all day recurrences and DATE-TIME entries otherwise. I am unsure how to properly merge the exception dates from the GUI into the exDateTimes in the case of different timezones. There is probably an API for that in KCalCore but I did not check. The patches are not doing anything fancy so properly porting to Qt5 should be straightforward. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #14 from Jochen Trumpf --- Created attachment 108009 --> https://bugs.kde.org/attachment.cgi?id=108009&action=edit patch for korganizer -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #13 from Jochen Trumpf --- Created attachment 108008 --> https://bugs.kde.org/attachment.cgi?id=108008&action=edit patch for incidenceeditor -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 385049] New: Opening large CJK blocks crashes kcharselect
https://bugs.kde.org/show_bug.cgi?id=385049 Bug ID: 385049 Summary: Opening large CJK blocks crashes kcharselect Product: kcharselect Version: 1.12 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: cf...@kde.org Reporter: exab...@3mhz.net Target Milestone: --- Application: kcharselect (1.12) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.0-3-amd64 x86_64 Distribution: Debian GNU/Linux 9.1 (stretch) -- Information about the crash: - What I was doing when the application crashed: Opening any large CJK character block crashes KCharSelect, for example Hangul Syllables or CJK Unified Ideographs. May be related to crash 374933, but I'm not sure - I'm explicitly saying it here, because I selected it as a likely duplicated in the reporting tool, but I'm not sure that it was marked: Similar crash happens when searching for “small...”. Backtraces look similar, but are too long for me to be sure. -- Backtrace: Application: KCharSelect (kcharselect), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fde593648c0 (LWP 28624))] Thread 4 (Thread 0x7fde41430700 (LWP 28633)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fde424ad75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fde424ad487 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fde620cc494 in start_thread (arg=0x7fde41430700) at pthread_create.c:333 #4 0x7fde63c88aff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 3 (Thread 0x7fde4a9d7700 (LWP 28628)): #0 QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:147 #1 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:141 #2 QThreadData::canWaitLocked (this=0x55d45b959210) at ../../include/QtCore/5.7.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253 #3 postEventSourcePrepare (s=0x7fde440012d0, timeout=0x7fde4a9d6b04) at kernel/qeventdispatcher_glib.cpp:259 #4 0x7fde601e6edd in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fde601e791b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fde601e7b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fde6459406b in QEventDispatcherGlib::processEvents (this=0x7fde440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7fde6453d9ca in QEventLoop::exec (this=this@entry=0x7fde4a9d6cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #9 0x7fde6436b0f3 in QThread::exec (this=) at thread/qthread.cpp:507 #10 0x7fde665eb6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7fde6436fda8 in QThreadPrivate::start (arg=0x7fde0d60) at thread/qthread_unix.cpp:368 #12 0x7fde620cc494 in start_thread (arg=0x7fde4a9d7700) at pthread_create.c:333 #13 0x7fde63c88aff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7fde56b6a700 (LWP 28625)): #0 0x7fde63c7f6ad in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fde5f100150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fde5f101ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fde590c8b69 in QXcbEventReader::run (this=0x55d45b7ab210) at qxcbconnection.cpp:1343 #4 0x7fde6436fda8 in QThreadPrivate::start (arg=0x55d45b7ab210) at thread/qthread_unix.cpp:368 #5 0x7fde620cc494 in start_thread (arg=0x7fde56b6a700) at pthread_create.c:333 #6 0x7fde63c88aff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7fde593648c0 (LWP 28624)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x554354515f5f7163) at /usr/include/c++/6/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x554354515f5f7163) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:99 #9 QWeakPointer::data (this=0x55d45bae9598) at ../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:604 #10 QPointer::data (this=0x55d45bae9598) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:86 #11 QPointer::operator QAbstractItemView* (this=0x55d45bae9598) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:92 #12 QAccessibleTableCell::rect (this=0x55d45bae9580) at accessible/itemviews.cpp:1038 #13 0x7fde652eee5c in QAccessibleTableCell::state (this=0x55d45bae9580) at accessible/itemviews.cpp:1002 #14 0x7fde5911c3a6 in AtSpiAdaptor::notify (this=0x55d45bba4d80,
[kdevelop] [Bug 384885] Crash in the SVN plugin [svn::pool_create]
https://bugs.kde.org/show_bug.cgi?id=384885 RJVB changed: What|Removed |Added CC||ap...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #36 from CnZhx --- I also tried the situation suggested in comment #32 and comment #33. And I found that if both "Start time" and "End time" were set for an entry, it's no problem to add the to-do list to the widget. However, after some time, maybe when the date passes the "Start time", the "Start time" is removed from that entry. After this, if the calendar widget is clicked to elevate, `plasmashell` will consume all the memory then crash. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385048] New: GNU Octave svg logo looks ugly, please use official one.
https://bugs.kde.org/show_bug.cgi?id=385048 Bug ID: 385048 Summary: GNU Octave svg logo looks ugly, please use official one. Product: Breeze Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: k.ohl...@gmail.com CC: kain...@gmail.com Target Milestone: --- Created attachment 108007 --> https://bugs.kde.org/attachment.cgi?id=108007&action=edit Official GNU Octave icon. Dear maintainers, The breeze and breeze-dark logos for GNU Octave look ugly, maybe due to some transformation process. https://cgit.kde.org/breeze-icons.git/tree/icons/apps/48/octave.svg Would you consider to replace that one with the official SVG, here as URL http://hg.savannah.gnu.org/hgweb/octave/file/8f3db1ac7877/etc/icons/octave-logo.svg or see file attached to this report. Thank you very much for your help, Kai -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 --- Comment #14 from Philippe ROUBACH --- i tried to get a bt but no true success Start it from the beginning? (y or n) y Starting program: /usr/bin/kaddressbook [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffd49d4700 (LWP 16106)] [New Thread 0x7fffc9a63700 (LWP 16107)] [New Thread 0x7fffc28c5700 (LWP 16108)] [New Thread 0x7fffb999a700 (LWP 16110)] org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Subtree: 25 QSet(28, 31, 30, 32, 25, 27, 26, 29) org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/2c2c0176895df900"; org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/e"; org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/d"; org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/f"; org.kde.akonadi.ETM: collection: "episteme.promen...@gmail.com" org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/1e2d34f48c32ef6f"; org.kde.akonadi.ETM: collection: "Autres contacts" org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/5835b2ea0c54d438"; org.kde.akonadi.ETM: Subtree: 8 QSet(8) org.kde.akonadi.ETM: collection: "Contacts personnels" org.kde.akonadi.ETM: Fetch job took 138 msec org.kde.akonadi.ETM: was collection fetch job: collections: 9 org.kde.akonadi.ETM: first fetched collection: "Contacts personnels" org.kde.akonadi.ETM: Fetch job took 72 msec org.kde.akonadi.ETM: was item fetch job: items: 16 org.kde.akonadi.ETM: Fetch job took 75 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 77 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 78 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 112 msec org.kde.akonadi.ETM: was item fetch job: items: 174 org.kde.akonadi.ETM: Fetch job took 119 msec org.kde.akonadi.ETM: was item fetch job: items: 8 org.kde.akonadi.ETM: Fetch job took 122 msec org.kde.akonadi.ETM: was item fetch job: items: 0 QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified org.kde.akonadi.ETM: Fetch job took 170 msec org.kde.akonadi.ETM: was item fetch job: items: 21 org.kde.akonadi.ETM: Fetch job took 120 msec org.kde.akonadi.ETM: was item fetch job: items: 0 QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No
[kdevelop] [Bug 384885] Crash in the SVN plugin [svn::pool_create]
https://bugs.kde.org/show_bug.cgi?id=384885
--- Comment #5 from RJVB ---
The only explanation I can find is that the compiler (clang 4.0.1) miscompiles
the svncpp code in KDevelop (but not the comparable code in kdesvn, from which
I copied certain things for testing). Compiler and/or linker don't generate the
proper address for the apr_pool_initialize() function:
(lldb) l 40
40 if (!s_initialized)
41 {
42 if (apr_pool_initialize() == APR_SUCCESS) {
43 s_initialized = true;
44 }
45 }
46
47 return svn_pool_create(parent);
48 }
49
(lldb) dis -l
kdevsubversion.so`svn::Pool::Pool:
-> 0x11e0c3be4 <+36>: callq 0x11e0c5f90 ; symbol stub for:
apr_pool_initialize
(lldb) l apr_pool_initialize
File:
/Volumes/VMs/MPbuild/_Volumes_Debian_MP9_var_macports_sources_rsync.macports.org_release_ports_devel_apr/apr/work/apr-1.6.2/memory/unix/apr_pools.c
642 * Local functions
643 */
644
645 static void run_cleanups(cleanup_t **c);
646 static void free_proc_chain(struct process_chain *procs);
647
648 #if APR_POOL_DEBUG
649 static void pool_destroy_debug(apr_pool_t *pool, const char
*file_line);
650 #endif
651
652 #if !APR_POOL_DEBUG
(lldb) l 661
661 if (apr_pools_initialized++)
662 return APR_SUCCESS;
663
664 #if HAVE_VALGRIND
665 apr_running_on_valgrind = RUNNING_ON_VALGRIND;
666 #endif
667
668 #if APR_ALLOCATOR_USES_MMAP && defined(_SC_PAGESIZE)
669 boundary_size = sysconf(_SC_PAGESIZE);
670 boundary_index = 12;
(lldb) p apr_pool_initialize()
(apr_status_t) $1 = 0
(lldb) p apr_pools_initialized
(apr_byte_t) $2 = '\0'
(lldb) p apr_pool_initialize
(apr_status_t (*)()) $3 = 0x00011e33cc9e
(libapr-1.0.dylib`apr_pool_initialize)
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 383991] Akonadi 17.08.0 / 5.6.0 with MariaDB 10.2.8 - Plugin pvio_socket could not be loaded: not initialized
https://bugs.kde.org/show_bug.cgi?id=383991 --- Comment #6 from Kevin Kofler --- Ah, looks like Daniel Vrátil already did that: https://codereview.qt-project.org/#/c/205874/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 383991] Akonadi 17.08.0 / 5.6.0 with MariaDB 10.2.8 - Plugin pvio_socket could not be loaded: not initialized
https://bugs.kde.org/show_bug.cgi?id=383991 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #5 from Kevin Kofler --- How about fixing the issue in Qt instead, where it actually lies? -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 Philippe ROUBACH changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #13 from Philippe ROUBACH --- i reopen this report because there is something new opensuse leap 42.2 kdeapplications 17.0.8.1 kde framework5 5.38 plasma 5.10.95 again there is a crash but no dr konqui report. here is the log in konsole roubach@linux-bmy3:~> kaddressbook org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Subtree: 8 QSet(8) org.kde.akonadi.ETM: collection: "Contacts personnels" org.kde.akonadi.ETM: Subtree: 25 QSet(32, 30, 31, 28, 29, 26, 27, 25) org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/f"; org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/d"; org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/e"; org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/2c2c0176895df900"; org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/5835b2ea0c54d438"; org.kde.akonadi.ETM: collection: "Autres contacts" org.kde.akonadi.ETM: collection: "http://www.google.com/m8/feeds/groups/episteme.promeneur%40gmail.com/base/1e2d34f48c32ef6f"; org.kde.akonadi.ETM: collection: "episteme.promen...@gmail.com" org.kde.akonadi.ETM: Fetch job took 135 msec org.kde.akonadi.ETM: was collection fetch job: collections: 9 org.kde.akonadi.ETM: first fetched collection: "Contacts personnels" org.kde.akonadi.ETM: Fetch job took 9 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 11 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 12 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 14 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 37 msec org.kde.akonadi.ETM: was item fetch job: items: 16 org.kde.akonadi.ETM: Fetch job took 42 msec org.kde.akonadi.ETM: was item fetch job: items: 21 org.kde.akonadi.ETM: Fetch job took 44 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 46 msec org.kde.akonadi.ETM: was item fetch job: items: 8 org.kde.akonadi.ETM: Fetch job took 66 msec org.kde.akonadi.ETM: was item fetch job: items: 174 QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified sonnet.core: deleting 0x1def010 for "fr_FR" sonnet.core: deleting 0x1d74078 for "fr_FR" sonnet.core: Loading trigrams from "/usr/share/kf5/sonnet/trigrams.map" sonnet.core: deleting 0x1d72360 for "fr" sonnet.core: deleting 0x19edde8 for "fr_FR" QXcbConnection: XCB error: 3 (BadWindow), sequence: 2171, resource id: 46491381, major code: 40 (TranslateCoords), minor code: 0 Erreur de segmentation (core dumped) roubach@linux-bmy3:~> -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346335] System Settings crash while editting Global Keyboard Shortcuts
https://bugs.kde.org/show_bug.cgi?id=346335 Sander changed: What|Removed |Added CC||san...@dmafsu.nl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346335] System Settings crash while editting Global Keyboard Shortcuts
https://bugs.kde.org/show_bug.cgi?id=346335 --- Comment #6 from Sander --- Created attachment 108006 --> https://bugs.kde.org/attachment.cgi?id=108006&action=edit New crash information added by DrKonqi kcmshell5 (5.10.5) using Qt 5.9.1 - What I was doing when the application crashed: I opened up Global Shortcuts by searching this through the start menu. Following that I clicked on the component System Settings Module and here I selected Log out, clicked on None and entered the key combination Meta+L after which the crash occured. - Custom settings of the application: Log Out was already set to Custom without a key combination (None). I think I crashed before but cannot seem to reproduce it after crashing. - Extra info: After the crash the new key combination seemed to have been set up. The key combination was set in the System Settings Module. -- Backtrace (Reduced): #6 0x7fb88ad2e0b0 in QLabel::text() const () from /usr/lib64/libQt5Widgets.so.5 #7 0x7fb8893552d6 in ShortcutEditWidget::setKeySequence (this=0x55732d913eb0, activeSeq=...) at /usr/src/debug/kxmlgui-5.37.0/src/kshortcuteditwidget.cpp:192 [...] #9 0x7fb8841ad544 in KGlobalAccel::globalShortcutChanged (this=this@entry=0x7fb8843c7590 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, _t1=, _t1@entry=0x55732d7a7a50, _t2=...) at /usr/src/debug/kglobalaccel-5.37.0/build/src/KF5GlobalAccel_autogen/include/moc_kglobalaccel.cpp:162 #10 0x7fb8841affa7 in KGlobalAccelPrivate::_k_shortcutGotChanged (this=, actionId=..., keys=...) at /usr/src/debug/kglobalaccel-5.37.0/src/kglobalaccel.cpp:480 [...] #12 0x7fb8841bb4ce in OrgKdeKGlobalAccelInterface::yourShortcutGotChanged (_t2=..., _t1=..., this=) at /usr/src/debug/kglobalaccel-5.37.0/build/src/kglobalaccel_interface.moc:267 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 Peter changed: What|Removed |Added CC||peter.lad...@mailbox.org --- Comment #73 from Peter --- Same her on KDE Neon devoloper stable KDE-Plasma 5.10.95 KDE-Frameworks-Version 5.39.0 Kernel 4.4.0-096 generic 64-bit OS Bug: while creating a caldav-ressource connecting https://dav.mailbox.org/ korganizer-collection of folders is successful fist item (job) successful created in korganizer pointing to caldav-server first job successful transmitted to caldav-Server, is visible there after this, every try to read the caldav-server fails Output akonadictl restart --verbose rg.kde.pim.davresource: Error when uploading item: 400 "There was a problem with the request. The item has not been created on the server.\nDie Datei oder der Ordner dav.mailbox.org existiert nicht. (0)." Output korganizer $ korganizer KServiceTypeTrader: serviceType "KOrganizer/Part" not found org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Subtree: 11 QSet(11) org.kde.akonadi.ETM: collection: "akonadi_ical_resource_0" org.kde.akonadi.ETM: Subtree: 1 QSet(48, 49, 1) org.kde.akonadi.ETM: collection: "OpenInvitations" org.kde.akonadi.ETM: collection: "DeclinedInvitations" org.kde.akonadi.ETM: Subtree: 2 QSet(2) org.kde.akonadi.ETM: collection: "Geburtstage und Jahrestage" org.kde.akonadi.ETM: Fetch job took 56 msec org.kde.akonadi.ETM: was collection fetch job: collections: 5 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 13 msec org.kde.akonadi.ETM: was item fetch job: items: 1 org.kde.akonadi.ETM: Fetch job took 17 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 20 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 32 msec org.kde.akonadi.ETM: was item fetch job: items: 0 pError loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." Error loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." "syntax error, unexpected MONTH" "syntax error, unexpected MONTH" Error loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." Error loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." Error loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." Error loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." Error loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." KServiceTypeTrader: serviceType "KOrganizer/Part" not found Error loading plugin: "Die dynamische Bibliothek konnte nicht gefunden werden." org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Subtree: 11 QSet(11) org.kde.akonadi.ETM: Subtree: 1 QSet(48, 49, 1) org.kde.akonadi.ETM: Subtree: 2 QSet(2) org.kde.akonadi.ETM: Fetch job took 41 msec org.kde.akonadi.ETM: was collection fetch job: collections: 5 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: collection: "https://dav.mailbox.org/caldav/31/"; org.kde.akonadi.ETM: collection: "https://dav.mailbox.org/caldav/33/"; org.kde.akonadi.ETM: collection: "https://dav.mailbox.org/caldav/46/"; org.kde.akonadi.ETM: collection: "https://dav.mailbox.org/caldav/43/"; org.kde.akonadi.ETM: collection: "https://dav.mailbox.org/caldav/45/"; org.kde.akonadi.ETM: Fetch job took 0 msec org.kde.akonadi.ETM: was collection fetch job: collections: 1 org.kde.akonadi.ETM: first fetched collection: "akonadi_davgroupware_resource_8" org.kde.akonadi.ETM: Fetch job took 0 msec org.kde.akonadi.ETM: was collection fetch job: collections: 1 org.kde.akonadi.ETM: first fetched collection: "akonadi_davgroupware_resource_8" org.kde.akonadi.ETM: Fetch job took 58 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: collection: "https://dav.mailbox.org/caldav/47/"; org.kde.akonadi.ETM: Fetch job took 64 msec org.kde.akonadi.ETM: was item fetch job: items: 0 org.kde.akonadi.ETM: Fetch job took 64 msec org.kde.akonadi.ETM:
[Oxygen] [Bug 384864] Oxygen cursors have some reversed symlinks
https://bugs.kde.org/show_bug.cgi?id=384864 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com --- Comment #1 from andreas.sturmlech...@gmail.com --- (In reply to Jack from comment #0) > (originally reported to Gentoo bug list: https://bugs.gentoo.org/629550. > (I'm not sure if any of this is Gentoo specific Gentoo installs a vanilla oxygen, no downstream patching going on. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385047] New: no folder appears when browsing the root of disk c:/
https://bugs.kde.org/show_bug.cgi?id=385047 Bug ID: 385047 Summary: no folder appears when browsing the root of disk c:/ Product: kdenlive Version: 17.08.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jean-louis.pastu...@orange.fr Target Milestone: --- Created attachment 108005 --> https://bugs.kde.org/attachment.cgi?id=108005&action=edit Emty panel folders when browsing from disk root Windows 10 kdenlive 17.08.1 no folder appears when browsing the root of disk c:/ See attachement -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385046] New: Bug at starting du to a bad position of melt.exe
https://bugs.kde.org/show_bug.cgi?id=385046 Bug ID: 385046 Summary: Bug at starting du to a bad position of melt.exe Product: kdenlive Version: 17.08.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: jean-louis.pastu...@orange.fr Target Milestone: --- Created attachment 108004 --> https://bugs.kde.org/attachment.cgi?id=108004&action=edit Shows screenshot and solution for the bug In this version 17.08.01 melt.exe is located on the root directory and raise a bug. Copying it into share directory solve the issue. See pdf attachment. This bug may be closed and certainly fixed soon on 7z archive ;-) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 385045] New: Falkon doesn't know about printers in KDE
https://bugs.kde.org/show_bug.cgi?id=385045 Bug ID: 385045 Summary: Falkon doesn't know about printers in KDE Product: Falkon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: now...@gmail.com Reporter: t.ki...@gmail.com Target Milestone: --- Falkon doesn't know about printers in KDE (probably because of being snap). The only option is to print into PDF. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 385044] New: Add weather informations into KCalendar
https://bugs.kde.org/show_bug.cgi?id=385044 Bug ID: 385044 Summary: Add weather informations into KCalendar Product: kontact Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: madshey...@gmail.com Target Milestone: --- This feature would inform user about the evet day weather. Something like this is in outlook and I really like it. Think it's not a hard work to do, so this would be a nice addition to kcalendar ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 --- Comment #3 from Christian Ohrfandl --- (In reply to David Edmundson from comment #2) > ~/.local/share/sddm/wayland-session.log > > Please set this back to unconfirmed when you have this Thanky you for the information! Unfortunately, I will be able to analyse further not until Friday, 29th September. I'll keep you posted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from David Edmundson --- Are there any logs I may view in order to resolve the issue after turning the PC off and on again? ~/.local/share/sddm/wayland-session.log Please set this back to unconfirmed when you have this -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 385043] New: Ark : after extraction, clicking on the notification button re-opens the archive instead of target directory
https://bugs.kde.org/show_bug.cgi?id=385043 Bug ID: 385043 Summary: Ark : after extraction, clicking on the notification button re-opens the archive instead of target directory Product: ark Version: 17.08.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: ma...@free.fr CC: rthoms...@gmail.com Target Milestone: --- After extracting an archive, an interactive notification asks whether one would like to open the target directory in Dolphin. Clicking on the button re-opens the archive in Ark instead of opening the target directory. Bug reproduced under both KDE Neon (latest) + Arch Linux. Latest KDE apps 17.08.1 but it used to occur with former versions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 384500] kioexec: Spurious prompt to re-upload, when a temporary file has been used
https://bugs.kde.org/show_bug.cgi?id=384500 Jonathan Marten changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kio ||/c76c1486ec79e8a16329207e9b ||293eed1244adfb --- Comment #4 from Jonathan Marten --- Git commit c76c1486ec79e8a16329207e9b293eed1244adfb by Jonathan Marten. Committed on 25/09/2017 at 07:56. Pushed by marten into branch 'master'. kioexec: Watch the file when it has finished copying To eliminate a spurious "The file has changed, do you want to upload it?" dialogue. Differential Revision: https://phabricator.kde.org/D7841 M +27 -22 src/kioexec/main.cpp https://commits.kde.org/kio/c76c1486ec79e8a16329207e9b293eed1244adfb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385042] Plasma crashes when I click the desktop after clicking on the menu.
https://bugs.kde.org/show_bug.cgi?id=385042 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 381630 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction
https://bugs.kde.org/show_bug.cgi?id=381630 David Edmundson changed: What|Removed |Added CC||articula...@icloud.com --- Comment #23 from David Edmundson --- *** Bug 385042 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384789] Wrong screen size reported with qemu and virtio
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #14 from David Edmundson --- Git commit 2b869e687d775ab072ef87c96c665f461df3580f by David Edmundson. Committed on 25/09/2017 at 07:47. Pushed by davidedmundson into branch 'Plasma/5.11'. Don't auto scale outputs where we don't know the physical size Summary: We don't have enough data to calculate the DPI properly and the current code effectively ends up switching based purely on resolution. Reviewers: #plasma, fvogt Reviewed By: fvogt Subscribers: plasma-devel, fvogt Tags: #plasma Differential Revision: https://phabricator.kde.org/D7980 M +4-0kded/generator.cpp https://commits.kde.org/kscreen/2b869e687d775ab072ef87c96c665f461df3580f -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 382042] Incorrect german translation for 'mount point'
https://bugs.kde.org/show_bug.cgi?id=382042 --- Comment #4 from Burkhard Lueck --- SVN commit 1498545 by lueck: translation update, change Mount-Punkt to Einhängepunkt M +26 -26kmymoney.po WebSVN link: http://websvn.kde.org/?view=rev&revision=1498545 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385036] Upon connecting to Cisco VPN, the Nameserver info for the VPN is not configured
https://bugs.kde.org/show_bug.cgi?id=385036 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Jan Grulich --- This is unfortunately not a problem in plasma-nm, which is just an UI backend for NetworkManager. You will have to report this problem in NetworkManager bugzilla, which you can find here https://bugzilla.gnome.org/page.cgi?id=browse.html&product=NetworkManager. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 375765] KIO-gdrive dies unexpectedly when downloading larger files
https://bugs.kde.org/show_bug.cgi?id=375765 idmresettrial changed: What|Removed |Added CC||idmresettr...@gmail.com --- Comment #4 from idmresettrial --- Any news about this bug? My machine always freezes when try downloading/uploading a ~80mb file, I have to hold the power button to force shutdown it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385034] Cannot click on brush preset ondocker
https://bugs.kde.org/show_bug.cgi?id=385034 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |INVALID CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Why do you think reinstalling would make any difference? You can try to reset your configuration to default (https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration), but what happens here i the presets docker is already visible in any case, I can just see it behind the menu. It might be locked, so it cannot be removed, but that's impossible to see from the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385029] Krita segfaults when saving krita documents sometimes crashes x11
https://bugs.kde.org/show_bug.cgi?id=385029 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- I'd need a gdb backtrace to be sure, but I'm pretty sure that this is, like I said on the forum, a crash caused by the deepin qimageio plugins. Please provide a backtrace so we can make sure. -- You are receiving this mail because: You are watching all bug changes.
