[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #14 from Friedrich W. H. Kossebau --- Thanks again for testing. (In reply to Duncan from comment #10) > (In reply to Friedrich W. H. Kossebau from comment #9) > > https://invent.kde.org/games/libkdegames/-/merge_requests/20.diff > > Good and bad news: > Good: The relative style ksudokurc theme entry works with that patch. Okay :) > Bad: The full-path style does not. > > If there hasn't been a release with the now-existing code that creates the > full-path entry I imagine the bad news can be ignored (unless we want to > give people hand-editing their ksudokurc files the choice of doing full > paths, too). No release of ksudoko using the new code yet, though sadly 22.08.0 release is currently prepared for tomorrow release and would be the first version of ksudoko with the new code path. libkdegames has seen a quite some releases with the id screwing logic (was added in 2014). I would agree that the most simple thing would be to just fallback to the default theme if the config holds a theme id that cannot be resolved. Most places also already do that, so those games can at least be used for gaming. Though ksudoku needs a fix-up for handling that situation, blame on me here, no idea why I failed to consider bad config entries. Local patch already prepared and tested, landing next. Will see to have the prepared 22.08.0 tarballs updated in time for tomorrow now. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #9 from Friedrich W. H. Kossebau --- Thanks for getting and showing that log. Okay, that should back up the working theory about the cause :) If you like to help more, please give the meanwhile created bug fix proposal as reported before by the bot a test. It should also apply to current master (I assume). You can download the patch itself by blue "Code" button (choose "Plain diff" in the popup menu) or using this link directly: https://invent.kde.org/games/libkdegames/-/merge_requests/20.diff -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #6 from Friedrich W. H. Kossebau --- Please try the attached patch for libkdegames: apply, build, install. then start ksudoku on the commandline. Interesting will be all the log output starting with "THEMELOADING", should be something like (in my case having double installation in system and user self-built location): --- 8< --- THEMELOADING considering locations ([lots of paths], "/usr/share/ksudoku") THEMELOADING considering desktop file "/home/some/path/share/ksudoku/themes/abstraction.desktop" THEMELOADING canonical path "/home/some/path/share/ksudoku/themes/abstraction.desktop" THEMELOADING id "themes/abstraction.desktop" THEMELOADING considering desktop file "/home/some/path/share/ksudoku/themes/default.desktop" THEMELOADING canonical path "/home/some/path/share/ksudoku/themes/default.desktop" THEMELOADING id "themes/default.desktop" THEMELOADING considering desktop file "/home/some/path/share/ksudoku/themes/ksudoku_scrible.desktop" THEMELOADING canonical path "/home/some/path/share/ksudoku/themes/ksudoku_scrible.desktop" THEMELOADING id "themes/ksudoku_scrible.desktop" THEMELOADING considering desktop file "/usr/share/ksudoku/themes/abstraction.desktop" THEMELOADING considering desktop file "/usr/share/ksudoku/themes/default.desktop" THEMELOADING considering desktop file "/usr/share/ksudoku/themes/ksudoku_scrible.desktop" --- 8< --- -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #5 from Friedrich W. H. Kossebau --- Created attachment 151355 --> https://bugs.kde.org/attachment.cgi?id=151355&action=edit Debug logging patch for libkdegames master (c5848c0d673cebc67eb280d54081ca69efeb28b0) -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #3 from Friedrich W. H. Kossebau --- >From a first look for potential culprit code, it seems the issue is how the theme id is generated in the libkdegames classes used in the new code (KgThemeProvider): `KgThemeProvider::rediscoverThemes()` goes over all `QStandardPaths::locateAll(QStandardPaths::AppDataLocation, "themes", QStandardPaths::LocateDirectory)` and collects the full path to the desktop files. Then it generates the theme id by first turning the desktop file path to a canonical version by `QFileInfo(file).canonicalFilePath()` and going once more over all `QStandardPaths::standardLocations(QStandardPaths::AppDataLocation)` and, if any of the latter path is a prefix to the canonical desktop file path, subtracts that prefix from the path to get the id. ((oh dear, how random people porting convoluted that logic :) )). See https://invent.kde.org/games/libkdegames/-/blob/master/src/kgthemeprovider.cpp#L185 and https://invent.kde.org/games/libkdegames/-/blob/master/src/kgthemeprovider.cpp#L174 My theory is that the logic of that code seems to miss out some constellation on your system, where QStandardPaths calls deliver some paths which would be turned to something else by the idea of QFileInfo about what the canonical version is. Are you capable to add some fprint debug lines to libkdegames yourself to get insight into the respective values used there? -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #2 from Friedrich W. H. Kossebau --- Hi, thanks for reporting the issue. Cannot remember I ran into such errors (though been some time) when I tested the change, and trying locally right now I also only get relative path with the new code when changing themes, like theme=themes/abstraction.desktop Will have a look in the code to see what condition might result in a full path later today. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 314798] There is no obvious way to copy (for pasting) data from defined structure
https://bugs.kde.org/show_bug.cgi?id=314798 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||0.26.9 Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/92a5d54 ||d3034f375f75d0f78be51ec6429 ||575f49 Status|REPORTED|RESOLVED --- Comment #2 from Friedrich W. H. Kossebau --- Git commit 92a5d54d3034f375f75d0f78be51ec6429575f49 by Friedrich W. H. Kossebau. Committed on 03/06/2022 at 16:27. Pushed by kossebau into branch '0.26'. Structures tool: add context menu to copy data & display string to clipboard FIXED-IN: 0.26.9 M +23 -8kasten/controllers/view/structures/structurestool.cpp M +4-1kasten/controllers/view/structures/structurestool.hpp M +48 -0kasten/controllers/view/structures/structureview.cpp M +2-0kasten/controllers/view/structures/structureview.hpp https://invent.kde.org/utilities/okteta/commit/92a5d54d3034f375f75d0f78be51ec6429575f49 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 337652] Edit flag and enum fields using literals from a structure definition
https://bugs.kde.org/show_bug.cgi?id=337652 --- Comment #1 from Friedrich W. H. Kossebau --- Git commit 29d529e7cc4be8ca5370bef20d8971a9e79ac941 by Friedrich W. H. Kossebau. Committed on 31/05/2022 at 14:13. Pushed by kossebau into branch '0.26'. Structures tool: use combobox editor for enums with defined values M +21 -0 kasten/controllers/view/structures/datatypes/primitive/basicprimitivedatainformation.hpp M +16 -0 kasten/controllers/view/structures/datatypes/primitive/bitfield/boolbitfielddatainformation.cpp M +4-0 kasten/controllers/view/structures/datatypes/primitive/bitfield/boolbitfielddatainformation.hpp M +16 -0 kasten/controllers/view/structures/datatypes/primitive/bitfield/signedbitfielddatainformation.cpp M +4-0 kasten/controllers/view/structures/datatypes/primitive/bitfield/signedbitfielddatainformation.hpp M +16 -0 kasten/controllers/view/structures/datatypes/primitive/bitfield/unsignedbitfielddatainformation.cpp M +4-0 kasten/controllers/view/structures/datatypes/primitive/bitfield/unsignedbitfielddatainformation.hpp M +7-0 kasten/controllers/view/structures/datatypes/primitive/booldatainformation.hpp M +6-0 kasten/controllers/view/structures/datatypes/primitive/chardatainformation.hpp M +6-0 kasten/controllers/view/structures/datatypes/primitive/doubledatainformation.hpp M +40 -0 kasten/controllers/view/structures/datatypes/primitive/enumdatainformation.cpp M +4-0 kasten/controllers/view/structures/datatypes/primitive/enumdatainformation.hpp M +6-0 kasten/controllers/view/structures/datatypes/primitive/floatdatainformation.hpp M +15 -0 kasten/controllers/view/structures/datatypes/primitive/primitivedatainformation.cpp M +9-0 kasten/controllers/view/structures/datatypes/primitive/primitivedatainformation.hpp M +8-0 kasten/controllers/view/structures/datatypes/primitive/sintdatainformation.hpp M +8-0 kasten/controllers/view/structures/datatypes/primitive/uintdatainformation.hpp https://invent.kde.org/utilities/okteta/commit/29d529e7cc4be8ca5370bef20d8971a9e79ac941 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 453759] KSyntaxHighlighting does not build with a C++20 compiler on Windows
https://bugs.kde.org/show_bug.cgi?id=453759 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/syntax-highlighting/ ||commit/8664e6eb1d3b45805abf ||fef91fe212d253750bc0 Version Fixed In||5.95.0 Status|ASSIGNED|RESOLVED --- Comment #14 from Friedrich W. H. Kossebau --- Git commit 8664e6eb1d3b45805abffef91fe212d253750bc0 by Friedrich W. H. Kossebau. Committed on 01/06/2022 at 19:53. Pushed by kossebau into branch 'master'. Avoid unprefixed CamelCase headers generated directly in build dir The removal of the PREFIX argument from ecm_generate_headers() call in 42a061b04c507de11b0fb240808fc65a7528d946 resulted in the headers being directly generated in the build dir, thus no longer only being visible via an explicit prefixed include. FIXED-IN: 5.95.0 M +6-0src/lib/CMakeLists.txt https://invent.kde.org/frameworks/syntax-highlighting/commit/8664e6eb1d3b45805abffef91fe212d253750bc0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 453759] KSyntaxHighlighting does not build with a C++20 compiler on Windows
https://bugs.kde.org/show_bug.cgi?id=453759 --- Comment #12 from Friedrich W. H. Kossebau --- Ah, right, yes, I only thought about building KSyntaxHighlighting itself, as the bug report talks about in title and initial description. Once it itself is built (if that works) and you build against the build artifacts in its build dir, we are back at the problem, I see, -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 453759] KSyntaxHighlighting does not build with a C++20 compiler on Windows
https://bugs.kde.org/show_bug.cgi?id=453759 --- Comment #10 from Friedrich W. H. Kossebau --- So a work-around for you might be to set the CMake C++ standard explicitly to C++17 for that subdirectory with ksyntaxhighligting, to match what is officially supported. Building the code with C++20 only works by chance, so there might be future issues. )s your code open visible somewhere, to get a better idea of your use-case? Still we want to fix ksyntaxhighlighting from the regression to have the unprefixed headers in the build include dir, that is not that ideal in any case, just wondering how urgent it is. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 453759] KSyntaxHighlighting does not build with a C++20 compiler on Windows
https://bugs.kde.org/show_bug.cgi?id=453759 --- Comment #8 from Friedrich W. H. Kossebau --- Nicolas: I am curious: given ksyntaxhighlighting itself is set to use C++17 during its build, does MSVC fail to react to that and still make C++20 headers visible or even use them? Or, when you say "Compile KSyntaxHighlighting with Visual Studio 2022 in C++20 mode" you mean, you modified the normal build and actually enforce C++20 instead? So anyone else should not be really affected for now? And in that case, why would you build with C++20 and not just the default C++17? Does that affect the output in any way? And should it perhaps be an option supported by upstream (in case this is also interesting for others)? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 453759] KSyntaxHighlighting does not build with a C++20 compiler on Windows
https://bugs.kde.org/show_bug.cgi?id=453759 --- Comment #7 from Friedrich W. H. Kossebau --- Thanks to a shower thought I guess the problem is rather that the current buildsystem setup for KSyntaxHighlighting generates the forward camelcase headers directly in the build directory of the library, which also is part of the include directories set up for the build, and before any system directories. So the preprocessor on searching to resolve #include will simply first come across the "Format" file in the library build dir, and then things go boom. So the generated headers need to be placed outside of the include directories, or, in this case due to other planned usages like from the examples referencing the generated forward headers, be placed into a subdir matching the prefix dir as used in the installed case. So the part of https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/313 which adds the "OUTPUT_DIR" argument to the ecm_generate_headers call should improve things and avoid the name collision. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 453759] KSyntaxHighlighting does not build with a C++20 compiler on Windows
https://bugs.kde.org/show_bug.cgi?id=453759 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org --- Comment #6 from Friedrich W. H. Kossebau --- The problem is not the header named "Format", but when include directories are set up to also have the very subdirectory of the "Format" file as part of it. Which is not by design, instead only the prefix "KSyntaxHighlighting" directoy should be found in the include directories. So that only #include will work. My question would be: can you tell which include actually triggers the wrong header to be used? I saw no include statement in KSyntaxHighlighting itself that uses a plain "format"/"Format" of any kind? So curious how exactly the wrong pick by the compiler is triggered here? -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 450826] Add additional decoding of 16, 32, and 64-bits on left-side
https://bugs.kde.org/show_bug.cgi?id=450826 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Friedrich W. H. Kossebau --- > It would be nice if the data could be displayed as groups of 16, 32, or > 64-bits on the left-hand side rather than clicking on the right to see the > decoding table with options for little or big endian. With "left-hand side", you mean the byte value display (with the options binary, octal, decimal, hexadecimal)? And with "right" the character display? What do you mean exactly by "clicking on the right"? After all the decoding table also adapts to the cursor when placed/moved in the byte values view part? What exactly do you mean by "groups of 16, 32, or 64-bits" or "32 or 64-bit values"? Integer values? If so, curious what use-case there is to combine view of 8-bit character set with mult-byte integer values? Would one not rather want to combine the single byte value (as the most common notation/interpretaion of the 8 bits of a byte) with whatever special data type those bytes are used for to encode? Can you give a visual mockup how you would like to see the display done, and perhaps give a sample of the use-case you have? So far I understand your request is a variant of bug 214131, just with multi-byte integer values instead of float or double? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454372] Proposal: switch to the cherry-pick backwards workflow
https://bugs.kde.org/show_bug.cgi?id=454372 Friedrich W. H. Kossebau changed: What|Removed |Added CC|kosse...@kde.org| --- Comment #2 from Friedrich W. H. Kossebau --- As I got cc::ed I have at least to say: fix bugs in the current product version,. Only then integrate those changes also into the development version, by whatever way. Backports to the product version instead come with increased risks of regressions and thus lower quality. Not involved with Elisa otherwise, so unsubscribing -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 337653] Changed a value in a structure view isn't shown after submitting
https://bugs.kde.org/show_bug.cgi?id=337653 Friedrich W. H. Kossebau changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Version Fixed In||0.26.9 Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/e86a5b4 ||59f6ea3b43d94223183e4a60695 ||b31a62 --- Comment #5 from Friedrich W. H. Kossebau --- Git commit e86a5b459f6ea3b43d94223183e4a60695b31a62 by Friedrich W. H. Kossebau. Committed on 23/05/2022 at 14:23. Pushed by kossebau into branch '0.26'. Structures tool: properly update tree view after committing a change FIXED-IN: 0.26.9 M +9-4kasten/controllers/view/structures/structurestool.cpp M +1-0kasten/controllers/view/structures/structurestool.hpp https://invent.kde.org/utilities/okteta/commit/e86a5b459f6ea3b43d94223183e4a60695b31a62 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 421357] Support for variable-length strings w/o terminator
https://bugs.kde.org/show_bug.cgi?id=421357
--- Comment #1 from Friedrich W. H. Kossebau ---
Alex, would you remember a reason besides no spare time resources that
maxCharCount and maxByteCount could not be also optionally scripted properties?
Would look into this otherwise in the next weeks.
FTR, as another work-around (though resulting in data reparsing) one can use
the updateFunc, starting with maxCharCount or maxByteCount set to 0 and then
have the value updated from that type-wide generic function.
E.g. with JS:
var obj = struct({
length: uint16(),
data: string("utf-8").set({
maxByteCount: 0,
updateFunc: function() { this.maxByteCount =
this.parent.length.value; }
})
});
or with XML
--
You are receiving this mail because:
You are watching all bug changes.
[okteta] [Bug 396057] Pascal-style RLE strings not working properly for length 1, both JS and OSD
https://bugs.kde.org/show_bug.cgi?id=396057 Friedrich W. H. Kossebau changed: What|Removed |Added Version Fixed In||0.26.9 Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/4c95f98 ||a3ce12b8517ea10058e59016336 ||165b17 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Friedrich W. H. Kossebau --- Git commit 4c95f98a3ce12b8517ea10058e59016336165b17 by Friedrich W. H. Kossebau. Committed on 23/05/2022 at 09:37. Pushed by kossebau into branch '0.26'. Structures tool: fix condition for string maxBytes meaning empty string FIXED-IN: 0.26.9 M +1-1 kasten/controllers/view/structures/datatypes/strings/utf32stringdata.cpp M +1-1 kasten/controllers/view/structures/datatypes/strings/utf8stringdata.cpp https://invent.kde.org/utilities/okteta/commit/4c95f98a3ce12b8517ea10058e59016336165b17 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 396057] Pascal-style RLE strings not working properly for length 1, both JS and OSD
https://bugs.kde.org/show_bug.cgi?id=396057 --- Comment #1 from Friedrich W. H. Kossebau --- Git commit aaea006c23cf1bb4471d11e7d3cc8cf45e1184ca by Friedrich W. H. Kossebau. Committed on 23/05/2022 at 09:32. Pushed by kossebau into branch '0.26'. Structures tool: clear any existing string data on reading zero-byres string M +1-0 kasten/controllers/view/structures/datatypes/strings/utf16stringdata.cpp M +1-0 kasten/controllers/view/structures/datatypes/strings/utf32stringdata.cpp M +1-0 kasten/controllers/view/structures/datatypes/strings/utf8stringdata.cpp https://invent.kde.org/utilities/okteta/commit/aaea006c23cf1bb4471d11e7d3cc8cf45e1184ca -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 454083] not working
https://bugs.kde.org/show_bug.cgi?id=454083 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|NEEDSINFO --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for your feedback. Do I understand correctly that with "Linux Mint 20.3" 'sudo apt install okteta' you got the version 0.26.3? > when i try to open a file nothing happens. You tried to open a file via the menu entry or the toolbar? Sounds like you hit bug 441802, too bad Qt still does not have that fixed. When it comes to no double byte support in the char table, different issue, interest for it though noted. In some future that might be added, other undone things more priority, so nothing to bet on short term sadly. *** This bug has been marked as a duplicate of bug 441802 *** -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 441802] Can't open file via menu / Ctrl+O but can via drag-and-drop / recent files
https://bugs.kde.org/show_bug.cgi?id=441802 Friedrich W. H. Kossebau changed: What|Removed |Added CC||msmalik...@gmail.com --- Comment #15 from Friedrich W. H. Kossebau --- *** Bug 454083 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 452362] Structure for PNG file header uses wrong endianess
https://bugs.kde.org/show_bug.cgi?id=452362 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/b8abb13 ||b01374b2d57f5e31fec16d3eb82 ||1233d2 Version Fixed In||0.26.8 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Friedrich W. H. Kossebau --- Git commit b8abb13b01374b2d57f5e31fec16d3eb821233d2 by Friedrich W. H. Kossebau. Committed on 16/05/2022 at 11:02. Pushed by kossebau into branch '0.26'. PNG structure definition: always use network byte order (big endian) FIXED-IN:0.26.8 M +1-1 kasten/controllers/view/structures/examples/okteta/structures/png/main.osd https://invent.kde.org/utilities/okteta/commit/b8abb13b01374b2d57f5e31fec16d3eb821233d2 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 453819] Edit negative float number and dot as separator
https://bugs.kde.org/show_bug.cgi?id=453819 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/0d6ae65 ||eae3eb184b8a5d223e5f40180fc ||4878a0 Version Fixed In||0.26.8 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Friedrich W. H. Kossebau --- Git commit 0d6ae65eae3eb184b8a5d223e5f40180fc4878a0 by Friedrich W. H. Kossebau. Committed on 16/05/2022 at 10:56. Pushed by kossebau into branch '0.26'. POD decoder: fix float-32bit editor with negative values & decimal places FIXED-IN:0.26.8 M +3-3kasten/controllers/view/poddecoder/typeeditors/float32editor.cpp https://invent.kde.org/utilities/okteta/commit/0d6ae65eae3eb184b8a5d223e5f40180fc4878a0 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 453819] Edit negative float number and dot as separator
https://bugs.kde.org/show_bug.cgi?id=453819 --- Comment #2 from Friedrich W. H. Kossebau --- Though using localized data might want to be a config option rather, same as done in the Structures tool. So that part will not be touched, besides fixing the float editors to follow the non-locale value style. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 453819] Edit negative float number and dot as separator
https://bugs.kde.org/show_bug.cgi?id=453819 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Friedrich W. H. Kossebau --- This is only about 32-bit float, right? Thanks for reporting the bug, this seems to have been broken since the editing feature was added in 2009, either you are the first to actually use that or the first do care to report :) And I might have missed to properly test this when I added the edit code for float-32bit initially, and never looked at it again Looking at details I learn even at my age that in C/C++ for float data types "min" actually has another meaning than what would transfer from integer data types, and instead some "lowest" is what to use here. Also spotted the cause why post-decimal-points digits are not possible. So fix already sketched, will see to turn into working code the next days. Related question: while looking at the feature (not used myself for some time) I see that values are not displayed localized. Any opinion against changing that to feature localized versions? -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 452943] Opening a file does not work
https://bugs.kde.org/show_bug.cgi?id=452943 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|WORKSFORME |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #5 from Friedrich W. H. Kossebau --- All things heard point to the same cause, so closing as duplicate. *** This bug has been marked as a duplicate of bug 441802 *** -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 441802] Can't open file via menu / Ctrl+O but can via drag-and-drop / recent files
https://bugs.kde.org/show_bug.cgi?id=441802 Friedrich W. H. Kossebau changed: What|Removed |Added CC||aar...@doofus.org --- Comment #14 from Friedrich W. H. Kossebau --- *** Bug 452943 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 452943] Opening a file does not work
https://bugs.kde.org/show_bug.cgi?id=452943 --- Comment #4 from Friedrich W. H. Kossebau --- I now remember that a similar issue had been reported in bug 441802, can we assume your issues seen have the same cause? -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 452943] Opening a file does not work
https://bugs.kde.org/show_bug.cgi?id=452943 --- Comment #3 from Friedrich W. H. Kossebau --- What workspace are you using? For now I would suspect the platformtheme integration plugin has a broken file dialog implementation, as the QFileDialog is the main difference here in the code paths when loading a file via the file picking UI or from the commandline. The actual file dialog itself is provided by the platform theme integration plugin, and Okteta relies on the public API with the signal QFileDialog::urlsSelected to properly provide the selected files as list of QUrls. If that is broken, if will also be broken for others, so nothing to work-around in Okteta. No idea right now how to find out which platformtheme integration plugin is actually used/picked. But can you please try and manually enforce a certain one and try loading files for comparison, e.g. by starting okteta via the extra args "okteta --platformtheme gtk2" (see also other options in /usr/lib64/qt5/plugins/platformthemes). What workspace/desktop environment are you using, and which Linux flavour/distribution (and version)? -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 452943] Opening a file does not work
https://bugs.kde.org/show_bug.cgi?id=452943 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Though works here (openSUSE TW, KF 5.93, Qt 5.15.2, Plasma env). To find what special case might trigger things for you, please give more detail, for a start where the selected file is stored, local filesystem or not, any special filesystem mount, which file picker dialog is used (Plasma/KDE or something else). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 451963] MySQL backend stores timestamps without adapting timezone
https://bugs.kde.org/show_bug.cgi?id=451963 --- Comment #1 from Friedrich W. H. Kossebau --- For comparison, the postgresql backend seems to not have that issue: For one a comment on #opensuse-kde was: "Eh, using postgresql here, was awake and at my laptop . No issues seen at all. " And looking at the sources of the Qt postgresql driver: https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/psql/qsql_psql.cpp?h=5.15#n1477 The value is explicitly stored converted relative to UTC. So only the timezone info is lost on a round-trip., but the absolute time stays correct. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 451963] New: MySQL backend stores timestamps without adapting timezone
https://bugs.kde.org/show_bug.cgi?id=451963
Bug ID: 451963
Summary: MySQL backend stores timestamps without adapting
timezone
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: kosse...@kde.org
Target Milestone: ---
PROBLEM:
On my CET/CEST timezone system, tonight when there was the daylight saving time
hour adaption, Akonadi reported some errors for a while. Here the extract from
systemd log (sorry, german local, but most should be obvious):
--- 8< ---
Mär 27 04:00:45 klaplax akonadi_pop3_resource[2955]: org.kde.pim.pop3resource:
"Fehler beim Speichern heruntergeladener E-Mails.\nFailed to append item"
Mär 27 04:00:45 klaplax akonadi_pop3_resource[2955]: org.kde.pim.pop3resource:
== ERROR DURING POP3 SYNC ==
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver: Error
while handling command CreateItem on connection akonadi_pop3_resource_0
(0x55e58e538930)
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver: Error
during insertion into table "PimItemTable" "Incorrect datetime value:
'2022-03-27 02:00:45.979000' for column `akonadi`.`pimitemtable`.`datetime` at
row 1 QMYSQL3: Der Befehl konnte nicht ausgeführt werden"
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver:
Query: "INSERT INTO PimItemTable (rev, remoteRevision, gid, collectionId,
mimeTypeId, datetime, atime, dirty, size) VALUES (:0, :1, :2, :3, :4, :5, :6,
:7, :8)"
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver:
Values: QMap((":0", QVariant(int, 0))(":1", QVariant(QString, ""))(":2",
QVariant(QString, ""))(":3", QVariant(qlonglong, 13))(":4", QVariant(qlonglong,
7))(":5", QVariant(QDateTime, QDateTime(2022-03-27 02:00:45.979 UTC
Qt::UTC)))(":6", QVariant(QDateTime, QDateTime(2022-03-27 02:00:45.979 UTC
Qt::UTC)))(":7", QVariant(bool, true))(":8", QVariant(qlonglong, 0)))
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver: Error
text: "Incorrect datetime value: '2022-03-27 02:00:45.979000' for column
`akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL3: Der Befehl konnte nicht
ausgeführt werden"
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver: DB
error: "Incorrect datetime value: '2022-03-27 02:00:45.979000' for column
`akonadi`.`pimitemtable`.`datetime` at row 1"
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver: Error
code: "1292"
Mär 27 04:00:45 klaplax akonadiserver[2593]: org.kde.pim.akonadiserver:
DATABASE ERROR:
--- 8< ---
It seems those errors appeared during 4 am & 5 am in my (now) CEST timezone,
whereas the timestamps used in the data were in the 2 am - 3 am range, which
obviously this night would not exist in my timezone, given the 2 am -> 3 am
time jump for the daylight saving time switch.
So there might be a mismatch in the timezones used for interpreting the
timestamps by the mysql/mariadb server and akonadi.
>From https://mariadb.com/kb/en/datetime/#time-zones:
"If a column uses the DATETIME data type, then any inserted values are stored
as-is, so no automatic time zone conversions are performed."
Looking at Akonadi code, e.g. for creating PimItems, often
QDateTime::currentDateTimeUtc() is used, so the QDateTime instances would be
based on UTC if values are directly queried.
From
https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/mysql/qsql_mysql.cpp?h=5.15:
Qt's MySQL driver stores only the current date & time values of a QDateTime
instance, without any conversion of the timezone to match the timezone
configured for the database, using QVariant::toDate() & QVariant::toTime() and
QDate::year()/month()/day() & QTime::hour()/minute()/second()/msec(). And reads
the value via QDateTime::fromString(MMddhhmmssString, Qt::ISODate).
So a QDateTime::currentDateTimeUtc() generated at 4:00:45 am CEST would be
turned into a string "02:00:45" by the current code, which then is rejected by
mariadb due to matching that against the system timezone which is CEST and that
very day does not have such a timestamp.
Similar issues with any other QDateTime instances used for PimItem::datetime &
PimItem::atime and being based on a timezone different from the one used for
the db.
SOLUTION:
?
I guess the mysql akonadi backend would need to know what timezone is used for
the database and adjust/normalize the QDateTime instances accordingly before
passing things over to the Qt db driver.
Then there is also the issue of migrating existing databases once this is
fixed. Even more as one cannot be sure that the current stored values are all
based on UTC or perhaps something else, depending on what the resources use.
--
You are receiving this mail because:
You are watching
[kwalletmanager] [Bug 451881] Dbus activation in desktop file breaks starting minimized in system tray
https://bugs.kde.org/show_bug.cgi?id=451881 --- Comment #2 from Friedrich W. H. Kossebau --- Going now for konversation & Co. to see if there is a fix possible, or if DBusActivatable behaviour pattern is not compatible with existing config options. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 451881] Dbus activation in desktop file breaks starting minimized in system tray
https://bugs.kde.org/show_bug.cgi?id=451881 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/kwalletmanager/commit ||/e1391cb3ab7eaf929989e79541 ||80daff3b9c7566 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Git commit e1391cb3ab7eaf929989e7954180daff3b9c7566 by Friedrich W. H. Kossebau. Committed on 26/03/2022 at 21:09. Pushed by kossebau into branch 'release/22.04'. kwalletmanager: do not show window on activation if not already shown M +8-3src/manager/kwalletmanager.cpp https://invent.kde.org/utilities/kwalletmanager/commit/e1391cb3ab7eaf929989e7954180daff3b9c7566 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 451856] kdevelop crashes while parsing /usr/lib64/python3.6/html/entities.py or /usr/lib64/python3.6/email/message.py
https://bugs.kde.org/show_bug.cgi?id=451856 Friedrich W. H. Kossebau changed: What|Removed |Added CC|kosse...@kde.org| -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 450704] Please support Ruby 3.1
https://bugs.kde.org/show_bug.cgi?id=450704 --- Comment #1 from Friedrich W. H. Kossebau --- FWIW, I tried simply adding "3.1.0" to the list of versions and did the Okteta 0.26.7 release with that, which seems to have worked by what I tested/checked in the generated artifacts. Yet no clue about the dragons in ruby land, so just mentioned "for the record". -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 450704] New: Please support Ruby 3.1
https://bugs.kde.org/show_bug.cgi?id=450704 Bug ID: 450704 Summary: Please support Ruby 3.1 Product: releaseme Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kosse...@kde.org CC: sit...@kde.org Target Milestone: --- Trying to use releaseme on current openSUSE TW got me: " - Ruby 2.4.0 or 2.5.0 or 2.6.0 or 2.7.0 or 3.0.0 required. Currently using: 3.1.0 " Given the warning about potential breakages with language changes with newer Ruby versions and having 0 clue about ruby myself, I have to default to file a request only :) -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 442007] Decoding table tool doesn't save preferences upon exit
https://bugs.kde.org/show_bug.cgi?id=442007 Friedrich W. H. Kossebau changed: What|Removed |Added Version Fixed In||0.26.7 Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/6f7c812 ||58b0bda11bdc99fabce22430c82 ||dd7069 --- Comment #1 from Friedrich W. H. Kossebau --- Git commit 6f7c81258b0bda11bdc99fabce22430c82dd7069 by Friedrich W. H. Kossebau. Committed on 21/02/2022 at 19:33. Pushed by kossebau into branch '0.26'. Tools: store used settings in the config FIXED-IN: 0.26.7 M +21 -2kasten/controllers/view/bytetable/bytetableview.cpp M +1-0kasten/controllers/view/bytetable/bytetableview.hpp M +99 -2 kasten/controllers/view/charsetconversion/charsetconversiontool.cpp M +40 -1kasten/controllers/view/checksum/checksumtool.cpp M +1-0kasten/controllers/view/checksum/checksumtool.hpp M +28 -16 kasten/controllers/view/checksum/checksumview.cpp M +2-1kasten/controllers/view/checksum/checksumview.hpp M +52 -2kasten/controllers/view/filter/filtertool.cpp M +11 -1kasten/controllers/view/filter/filtertool.hpp M +29 -5kasten/controllers/view/filter/filterview.cpp M +2-0kasten/controllers/view/filter/filterview.hpp M +22 -7 kasten/controllers/view/libbytearraychecksum/abstractbytearraychecksumalgorithm.cpp M +6-2 kasten/controllers/view/libbytearraychecksum/abstractbytearraychecksumalgorithm.hpp M +3-1 kasten/controllers/view/libbytearraychecksum/algorithm/adler32bytearraychecksumalgorithm.cpp M +3-1 kasten/controllers/view/libbytearraychecksum/algorithm/crc32bytearraychecksumalgorithm.cpp M +21 -1 kasten/controllers/view/libbytearraychecksum/algorithm/crc64bytearraychecksumalgorithm.cpp M +2-0 kasten/controllers/view/libbytearraychecksum/algorithm/crc64bytearraychecksumalgorithm.hpp M +38 -0 kasten/controllers/view/libbytearraychecksum/algorithm/crc64bytearraychecksumparameterset.cpp M +6-0 kasten/controllers/view/libbytearraychecksum/algorithm/crc64bytearraychecksumparameterset.hpp M +21 -2 kasten/controllers/view/libbytearraychecksum/algorithm/modsum16bytearraychecksumalgorithm.cpp M +2-0 kasten/controllers/view/libbytearraychecksum/algorithm/modsum16bytearraychecksumalgorithm.hpp M +21 -2 kasten/controllers/view/libbytearraychecksum/algorithm/modsum32bytearraychecksumalgorithm.cpp M +2-0 kasten/controllers/view/libbytearraychecksum/algorithm/modsum32bytearraychecksumalgorithm.hpp M +21 -2 kasten/controllers/view/libbytearraychecksum/algorithm/modsum64bytearraychecksumalgorithm.cpp M +2-0 kasten/controllers/view/libbytearraychecksum/algorithm/modsum64bytearraychecksumalgorithm.hpp M +3-1 kasten/controllers/view/libbytearraychecksum/algorithm/modsum8bytearraychecksumalgorithm.cpp M +38 -1 kasten/controllers/view/libbytearraychecksum/algorithm/modsumbytearraychecksumparameterset.cpp M +6-0 kasten/controllers/view/libbytearraychecksum/algorithm/modsumbytearraychecksumparameterset.hpp M +2-2 kasten/controllers/view/libbytearraychecksum/algorithm/qca2bytearraychecksumalgorithm.cpp M +1-1 kasten/controllers/view/libbytearraychecksum/algorithm/qca2bytearraychecksumalgorithm.hpp M +3-1 kasten/controllers/view/libbytearraychecksum/algorithm/template/template_bytearraychecksumalgorithm.cpp M +24 -13 kasten/controllers/view/libbytearraychecksum/bytearraychecksumalgorithmfactory.cpp M +22 -7 kasten/controllers/view/libbytearrayfilter/abstractbytearrayfilter.cpp M +6-2 kasten/controllers/view/libbytearrayfilter/abstractbytearrayfilter.hpp M +1-0 kasten/controllers/view/libbytearrayfilter/abstractbytearrayfilterparametersetedit.hpp M +21 -2 kasten/controllers/view/libbytearrayfilter/filter/andbytearrayfilter.cpp M +2-0 kasten/controllers/view/libbytearrayfilter/filter/andbytearrayfilter.hpp M +3-1 kasten/controllers/view/libbytearrayfilter/filter/invertbytearrayfilter.cpp M +75 -3 kasten/controllers/view/libbytearrayfilter/filter/operandbytearrayfilterparameterset.cpp M +23 -3 kasten/controllers/view/libbytearrayfilter/filter/operandbytearrayfilterparameterset.hpp M +10 -3 kasten/controllers/view/libbytearrayfilter/filter/operandbytearrayfilterparametersetedit.cpp M +21 -2 kasten/controllers/view/libbytearrayfilter/filter/orbytearrayfilter.cpp M +2-0 kasten/controllers/view/libbytearrayfilter/filter/orbytearrayfilter.hpp M +22 -2 kasten/controllers/view/libbytea
[okteta] [Bug 444453] The last character encoding combobox entries are unreachable by scrolling
https://bugs.kde.org/show_bug.cgi?id=53 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/95c1bdb ||937e06130b2a4c97f8981aef4d4 ||96e0bf Version Fixed In||0.26.7 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Friedrich W. H. Kossebau --- Git commit 95c1bdb937e06130b2a4c97f8981aef4d496e0bf by Friedrich W. H. Kossebau. Committed on 21/02/2022 at 19:33. Pushed by kossebau into branch '0.26'. Implement own IBM874 codec, as Qt with ICU uses instead TIS-620 FIXED-IN: 0.26.7 M +1-0core/CMakeLists.txt M +5-1core/codecs/charcodec.cpp A +88 -0core/codecs/ibm874charcodec.cpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +40 -0core/codecs/ibm874charcodec.hpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] M +1-1core/codecs/textcharcodec.cpp https://invent.kde.org/utilities/okteta/commit/95c1bdb937e06130b2a4c97f8981aef4d496e0bf -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 398047] Ability to display unread count on Task Manager icon
https://bugs.kde.org/show_bug.cgi?id=398047 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/konversation/commit/a4e ||c8102853c51adadd9a534e01318 ||a7b0381b52 Status|ASSIGNED|RESOLVED Version Fixed In||1.9.22040 Resolution|--- |FIXED --- Comment #6 from Friedrich W. H. Kossebau --- Git commit a4ec8102853c51adadd9a534e01318a7b0381b52 by Friedrich W. H. Kossebau. Committed on 18/02/2022 at 22:32. Pushed by kossebau into branch 'master'. Show number of unseen nick mentions & query messages on launcher entry FIXED-IN: 1.9.22040 M +1-1CMakeLists.txt M +3-0src/CMakeLists.txt M +3-0src/application.cpp M +3-0src/application.h M +61 -0src/config/konversation.kcfg A +41 -0src/config/launcherentry_config.cpp [License: GPL(v2.0+)] A +33 -0src/config/launcherentry_config.h [License: GPL(v2.0+)] A +190 -0src/config/launcherentry_config.ui M +48 -0src/config/preferences.cpp M +20 -0src/config/preferences.h M +7-0src/config/settingsdialog.cpp M +2-0src/config/settingsdialog.h A +118 -0src/launcherentryhandler.cpp [License: GPL(v2.0+)] A +46 -0src/launcherentryhandler.h [License: GPL(v2.0+)] M +5-0src/mainwindow.cpp M +1-0src/mainwindow.h M +63 -0src/viewer/chatwindow.cpp M +10 -1src/viewer/chatwindow.h M +44 -0src/viewer/viewcontainer.cpp M +3-0src/viewer/viewcontainer.h https://invent.kde.org/network/konversation/commit/a4ec8102853c51adadd9a534e01318a7b0381b52 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 447373] Okteta (Snap) cannot open file on removable media
https://bugs.kde.org/show_bug.cgi?id=447373 Friedrich W. H. Kossebau changed: What|Removed |Added CC||neon-b...@kde.org Assignee|kosse...@kde.org|neon-b...@kde.org Version|0.26.6 |unspecified Component|general |Snaps Product|okteta |neon -- You are receiving this mail because: You are watching all bug changes.
[kodaskanna] [Bug 449742] Doesn't recognize QR codes
https://bugs.kde.org/show_bug.cgi?id=449742 Friedrich W. H. Kossebau changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Friedrich W. H. Kossebau --- Thanks for the samples, could reproduce on openSUSE TW. Some other ZXing-based decoder had no issues on a quick try, so the guess for now is kodaskanna needs improvements in who it uses XZing, put on my todo list for next release. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 398047] Ability to display unread count on Task Manager icon
https://bugs.kde.org/show_bug.cgi?id=398047 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Assignee|peter.simons...@gmail.com |kosse...@kde.org --- Comment #3 from Friedrich W. H. Kossebau --- Did a first working draft to implement this. Question for now would be: given we sadly only have a single number to show, without further context, how to deal with both mentions as well as direct queries? For now I would go to simply summarize both numbers, given I assume in most cases one simply wants to know how many unread messages there are that addressed one, either directly or indirectly. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 398047] Ability to display unread count on Task Manager icon
https://bugs.kde.org/show_bug.cgi?id=398047 Friedrich W. H. Kossebau changed: What|Removed |Added CC||oleksa...@natalenko.name --- Comment #2 from Friedrich W. H. Kossebau --- *** Bug 439021 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 439021] [RFE] Make use of com.canonical.Unity.LauncherEntry
https://bugs.kde.org/show_bug.cgi?id=439021 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||kosse...@kde.org --- Comment #1 from Friedrich W. H. Kossebau --- *** This bug has been marked as a duplicate of bug 398047 *** -- You are receiving this mail because: You are watching all bug changes.
[kodaskanna] [Bug 449168] New: Support standard Quit action (at least as shortcut) in stand-alone mode
https://bugs.kde.org/show_bug.cgi?id=449168 Bug ID: 449168 Summary: Support standard Quit action (at least as shortcut) in stand-alone mode Product: kodaskanna Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kosse...@kde.org Reporter: kosse...@kde.org Target Milestone: --- People's muscle memory expects the usual shortcuts to work. At least in stand-alone mode, like when launched via the shell menu by the user without any arguments, the standard Quit action should be available, at least by shortcut, but perhaps also by menu entry when there is a fitting place. To be used: KStandard* classes -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 447803] New: Wanted: option to have notification actions register as activation/start calls to window system
https://bugs.kde.org/show_bug.cgi?id=447803
Bug ID: 447803
Summary: Wanted: option to have notification actions register
as activation/start calls to window system
Product: frameworks-knotifications
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: kosse...@kde.org
CC: kdelibs-b...@kde.org
Target Milestone: ---
Use case:
In a chat application when showing a notification about a new message, the
default action is to "Open" the respective view which holds the new message:
auto *msg = KNotification::event(...);
msg->setDefaultAction(i18n("Open"));
connect(msg, &KNotification::defaultActivated, window, [] {
window->show();
window->raise();
KWindowSystem::activateWindow(window->winId());
});
If the window is currently on another virtual desktop, given the intent of the
user to open/see the new message when activating the action, one would expect
that the window system/shell switches the virtual desktop as needed to show the
window.
Instead at least with KWin/Plasma on these calls only the window is highlighted
on the taskbar, but the virtual desktop not switched. So the user has to do a
further action (e.g. click the highlighted window entry) to finally get to the
window.
Assumption: this might be related to focus stealing handling? So there needs to
be some way for the notification system to tell the window system that the
window activation requested by the application is due to a start/activation
like event from the notification. Possibly something with X11 startup
id/Wayland activation token?
Seen in Konversation & NeoChat.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-knotifyconfig] [Bug 367753] notifications do not play sound
https://bugs.kde.org/show_bug.cgi?id=367753 Friedrich W. H. Kossebau changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Product|konversation|frameworks-knotifyconfig Assignee|konversation-de...@kde.org |k...@davidedmundson.co.uk Component|notifications |general Resolution|--- |WAITINGFORINFO CC||kdelibs-b...@kde.org, ||kosse...@kde.org Version|1.6 |5.68.0 --- Comment #5 from Friedrich W. H. Kossebau --- Works here on openSUSE TW in a Plasma session as well a Gnome session. What are the other apps you are testing with? Any other KF/Qt-based apps where you could test things in the notification dialog for comparison? In general, this would be a bug with the respective library providing the dialog though, thus already reassigning to that product. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 394432] Hide window on startup option doesn't work
https://bugs.kde.org/show_bug.cgi?id=394432 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||kosse...@kde.org --- Comment #3 from Friedrich W. H. Kossebau --- I suspect that next to Konversation having been added to autostart, it was also covered by session management. And as both are sadly not integrated, this resulted in Konversation being started 2x, once by session restore as well as autostart later on. And any second start is always interpreted as activation, which is handled by ensuring the window is shown. Next to that, session management support in Konversation had a bug in not remembering the window state properly. This was fixed for upcoming 1.8.21121. So plain session management should now ensure that if the Konversation window was hidden on session end, it will also be restored as hidden on session restore on the next login now. Without session management, when registering Konversation for Autostart, at least with current 1.8.21120 it respects the flag and starts hidden. So closing as UPSTREAM issue, as this is an design flaw in the desktop environments when it comes to missing integration of autostart and session management. Current behaviour is the same as also seen with other single instance applications like KMail. So use autostart only if session management is disabled. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 387572] Konversation always starts at top-left corner
https://bugs.kde.org/show_bug.cgi?id=387572 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||kosse...@kde.org --- Comment #3 from Friedrich W. H. Kossebau --- Cannot reproduce with Plasma 5.23 & Konversation 1.8.21120 I configured "Centered" window placement and unchecked the "Allow windows to restore their position if they remember", worked as expected. For now assuming something has fixed this. Please reopen if that bug is still experienced, so we can narrow down what the conditions are where this happens. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 382056] Empty space on tabbar after disabling 'Show a close button on the right side of the tab bar' option
https://bugs.kde.org/show_bug.cgi?id=382056 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||1.8.21121 Latest Commit||https://invent.kde.org/netw ||ork/konversation/commit/b5c ||741d20e9b7862d3e4b237ce7423 ||2ccd58faa9 Resolution|--- |FIXED --- Comment #1 from Friedrich W. H. Kossebau --- Git commit b5c741d20e9b7862d3e4b237ce74232ccd58faa9 by Friedrich W. H. Kossebau. Committed on 30/12/2021 at 22:38. Pushed by kossebau into branch 'release/21.12'. Fix unused empty space on tabbar if separate tab close button is disabled FIXED-IN: 1.8.21121 M +23 -9src/viewer/viewcontainer.cpp M +2-0src/viewer/viewcontainer.h https://invent.kde.org/network/konversation/commit/b5c741d20e9b7862d3e4b237ce74232ccd58faa9 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 444440] Konversation exits without warning when "Enable System Tray" is toggled
https://bugs.kde.org/show_bug.cgi?id=40 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/konversation/commit/4e5 ||f1ed454ef395ca1513243df6d7d ||ce76ef46f5 Resolution|--- |FIXED Version Fixed In||1.8.21121 Status|REPORTED|RESOLVED --- Comment #1 from Friedrich W. H. Kossebau --- Git commit 4e5f1ed454ef395ca1513243df6d7dce76ef46f5 by Friedrich W. H. Kossebau. Committed on 30/12/2021 at 21:29. Pushed by kossebau into branch 'release/21.12'. Fix quitting app without confirm dialog after previous canceling of quit FIXED-IN: 1.8.21121 M +6-5src/mainwindow.cpp M +1-1src/mainwindow.h https://invent.kde.org/network/konversation/commit/4e5f1ed454ef395ca1513243df6d7dce76ef46f5 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 397931] Windows download link on main site 404s
https://bugs.kde.org/show_bug.cgi?id=397931 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Friedrich W. H. Kossebau --- https://konversation.kde.org/download.html now links both stable & unstable windows builds, no longer any 404. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 354263] It moves to different area on desktop every time I click on it in system tray
https://bugs.kde.org/show_bug.cgi?id=354263 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Friedrich W. H. Kossebau --- I cannot reproduce right now with Plasma 5.23, but also cannot remember to ever have seen this behaviour. Given no-one else has reported this bug since, I am assuming now the cause has been fixed somehow somewhere. Thus closing now, please reopen if anyone still can see this in some recent versions of Konversation and/or Plasma. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 374690] Already running Konversation app invoked as handler for irc:// links does not enter channel from link
https://bugs.kde.org/show_bug.cgi?id=374690 Friedrich W. H. Kossebau changed: What|Removed |Added CC||s...@gmx.de --- Comment #2 from Friedrich W. H. Kossebau --- *** Bug 351484 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 351484] Url parameter does not work when a konversation instance is already running
https://bugs.kde.org/show_bug.cgi?id=351484 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Friedrich W. H. Kossebau --- Seems this report was missed out when I once created bug 374690, which meanwhile also is fixed. Sorry for that, and closing thus now as duplicate. *** This bug has been marked as a duplicate of bug 374690 *** -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 293112] konversation: Wrong French translation for "%2 sets the channel limit to %1 nicks."
https://bugs.kde.org/show_bug.cgi?id=293112 Bug 293112 depends on bug 336256, which changed state. Bug 336256 Summary: bad plural forms in channel mode message https://bugs.kde.org/show_bug.cgi?id=336256 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 336256] bad plural forms in channel mode message
https://bugs.kde.org/show_bug.cgi?id=336256 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Latest Commit||https://commits.kde.org/kon ||versation/ce98bddae39f084fe ||00d846a8bfd2342339aecfb Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||1.8.21121 --- Comment #4 from Friedrich W. H. Kossebau --- Accidentally came across that misbehaviour recently and directly fixed it, not knowing about this bug report. A shame the fix was so simple and even already described in the bug report itself (toInt()), shows the eternal lack of resources... so just looking at the positive side, bug can be declared fixed. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 444458] Tab bar should follow the KDE Human Interface Guidelines
https://bugs.kde.org/show_bug.cgi?id=58 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/7d4e931 ||09a239e84be31c8cbbf0bfd92db ||ab6774 Resolution|--- |FIXED Version Fixed In||0.26.7 --- Comment #3 from Friedrich W. H. Kossebau --- Git commit 7d4e93109a239e84be31c8cbbf0bfd92dbab6774 by Friedrich W. H. Kossebau. Committed on 25/11/2021 at 17:52. Pushed by kossebau into branch '0.26'. Create empty documents on LMB double-clicks in empty areas FIXED-IN: 0.26.7 M +1-0libs/kasten/gui/shell/multiviewareas.hpp M +2-0libs/kasten/gui/shell/multiviewareas_p.cpp M +30 -0libs/kasten/gui/shell/tabbar.cpp M +5-0libs/kasten/gui/shell/tabbar.hpp M +1-0libs/kasten/gui/shell/tabbedviews.hpp M +9-0libs/kasten/gui/shell/tabbedviews_p.cpp M +1-0libs/kasten/gui/shell/tabbedviews_p.hpp M +13 -0libs/kasten/gui/shell/tabwidget.cpp M +2-0libs/kasten/gui/shell/tabwidget.hpp M +7-0program/mainwindow.cpp M +1-0program/mainwindow.hpp https://invent.kde.org/utilities/okteta/commit/7d4e93109a239e84be31c8cbbf0bfd92dbab6774 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 444405] Okteta crashes after using the Strings tool and switching files
https://bugs.kde.org/show_bug.cgi?id=05 Friedrich W. H. Kossebau changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/6073903 ||15750815b0009b95ecd65699e2a ||1d110a Version Fixed In||0.26.7 Resolution|--- |FIXED --- Comment #4 from Friedrich W. H. Kossebau --- Git commit 607390315750815b0009b95ecd65699e2a1d110a by Friedrich W. H. Kossebau. Committed on 25/11/2021 at 17:52. Pushed by kossebau into branch '0.26'. String extraction tool: fix crash with marked strings in closed view FIXED-IN: 0.26.7 M +6-1kasten/controllers/view/stringsextract/stringsextracttool.cpp https://invent.kde.org/utilities/okteta/commit/607390315750815b0009b95ecd65699e2a1d110a -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 444458] Tab bar should follow the KDE Human Interface Guidelines
https://bugs.kde.org/show_bug.cgi?id=58 --- Comment #2 from Friedrich W. H. Kossebau --- Git commit 382981fad053a6998c73a9af581bd42f549ba5bd by Friedrich W. H. Kossebau. Committed on 25/11/2021 at 17:52. Pushed by kossebau into branch '0.26'. Add a context menu for the view area (incl. tabs) M +7-0libs/kasten/controllers/CMakeLists.txt A +134 -0 libs/kasten/controllers/shellwindow/viewareacontextmenu/viewareacontextmenucontroller.cpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +64 -0 libs/kasten/controllers/shellwindow/viewareacontextmenu/viewareacontextmenucontroller.hpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +30 -0 libs/kasten/controllers/shellwindow/viewareacontextmenu/viewareacontextmenucontrollerfactory.cpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +39 -0 libs/kasten/controllers/shellwindow/viewareacontextmenu/viewareacontextmenucontrollerfactory.hpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] M +1-0libs/kasten/gui/shell/multiviewareas.hpp M +16 -0libs/kasten/gui/shell/multiviewareas_p.cpp M +1-0libs/kasten/gui/shell/multiviewareas_p.hpp M +1-0libs/kasten/gui/shell/tabbedviews.hpp M +20 -0libs/kasten/gui/shell/tabbedviews_p.cpp M +1-0libs/kasten/gui/shell/tabbedviews_p.hpp M +2-0program/mainwindow.cpp M +10 -1program/oktetaui.rc https://invent.kde.org/utilities/okteta/commit/382981fad053a6998c73a9af581bd42f549ba5bd -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 444458] Tab bar should follow the KDE Human Interface Guidelines
https://bugs.kde.org/show_bug.cgi?id=58 --- Comment #1 from Friedrich W. H. Kossebau --- Git commit e5660829b5d9c85373139b48b68bc8ffcd7c3c00 by Friedrich W. H. Kossebau. Committed on 25/11/2021 at 17:52. Pushed by kossebau into branch '0.26'. Enable reordering of view tabs inside a single tab area M +1-0libs/kasten/gui/shell/tabbedviews_p.cpp https://invent.kde.org/utilities/okteta/commit/e5660829b5d9c85373139b48b68bc8ffcd7c3c00 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 430561] Konversation Does Not Appear on Top when Called from Plasma System Tray
https://bugs.kde.org/show_bug.cgi?id=430561 Friedrich W. H. Kossebau changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||1.8.21121 Latest Commit||https://invent.kde.org/netw ||ork/konversation/commit/82c ||f2e1fb59daf71c0d577f5a296b8 ||b2fb2b24a1 Resolution|--- |FIXED --- Comment #6 from Friedrich W. H. Kossebau --- Git commit 82cf2e1fb59daf71c0d577f5a296b8b2fb2b24a1 by Friedrich W. H. Kossebau. Committed on 22/12/2021 at 20:26. Pushed by kossebau into branch 'release/21.12'. On activation by KDBusService set proper startupId/activation token FIXED-IN: 1.8.21121 M +10 -0CMakeLists.txt M +1-0config-konversation.h.cmake M +4-0src/CMakeLists.txt M +17 -1src/application.cpp https://invent.kde.org/network/konversation/commit/82cf2e1fb59daf71c0d577f5a296b8b2fb2b24a1 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 446673] Channel Settings, Modes tab "User Limit" QSpinBox uses default max=99, messing up any higher setting by /cmode +l NNN
https://bugs.kde.org/show_bug.cgi?id=446673 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/konversation/commit/074 ||f80e2dcefdc6cd0b68714021481 ||ee35b7df30 Resolution|--- |FIXED Version Fixed In||1.8.21121 Status|ASSIGNED|RESOLVED --- Comment #2 from Friedrich W. H. Kossebau --- Git commit 074f80e2dcefdc6cd0b68714021481ee35b7df30 by Friedrich W. H. Kossebau. Committed on 18/12/2021 at 23:27. Pushed by kossebau into branch 'release/21.12'. Channel Settings UI: bump max value of "User limit" to 9 Max value was the default 99, which would result in... a) any higher value read from the channel mode being reset to 99 b) not allow users to set higher values if wanted. As applying the channel settings from the dialog always picks all the values of the dialog, also those not edited, in case of a) this also would mean changing the user limit in the channel to 99 then. RFCs are not known to define a max user limit, so this is server defined. While there is no path explored to query any max user limit capabilities, and servers implementations seems to just map too high numbers to random possible ones, there is no well defined max value to be used for the dialog. Using 9 as arbitrary value should serve for now all expected use-cases. To be raised later if there is respective feedback. FIXED-IN: 1.8.21121 M +3-0src/viewer/channeloptionsui.ui https://invent.kde.org/network/konversation/commit/074f80e2dcefdc6cd0b68714021481ee35b7df30 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 387596] Crash when toggling between new UI and old UI
https://bugs.kde.org/show_bug.cgi?id=387596 Friedrich W. H. Kossebau changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||kosse...@kde.org --- Comment #5 from Friedrich W. H. Kossebau --- The QtQuick UI branch would be considered dead by now, not having seen work in years and with normal development branches having walked further. See also https://mail.kde.org/pipermail/konversation-devel/2020-September/007078.html So closing now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447204] Task manager offers to launch new instance of kcmshell and systemsettings
https://bugs.kde.org/show_bug.cgi?id=447204 Friedrich W. H. Kossebau changed: What|Removed |Added CC||justin.zo...@gmail.com --- Comment #3 from Friedrich W. H. Kossebau --- *** Bug 429428 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 429428] Start New Instance
https://bugs.kde.org/show_bug.cgi?id=429428 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||kosse...@kde.org --- Comment #3 from Friedrich W. H. Kossebau --- Konversation is designed as a single instance application. Supporting multiple windows would need some big overhaul, nothing to be expected to be done from someone currently, given the maintenance state. The expectations given by the "Start new instance" are not Konversation's fault though, that is an issue with the task manager, So closing as duplicate of the related bug (which currently is seeing work gladly :) ). *** This bug has been marked as a duplicate of bug 447204 *** -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 435641] Incorrect french translation for right click on link, "enregistrer la lien sous..."
https://bugs.kde.org/show_bug.cgi?id=435641 Friedrich W. H. Kossebau changed: What|Removed |Added Component|general |fr Version|1.7.6 |unspecified CC||kosse...@kde.org Status|REPORTED|CONFIRMED Product|konversation|i18n Assignee|konversation-de...@kde.org |kde-francoph...@kde.org Ever confirmed|0 |1 --- Comment #1 from Friedrich W. H. Kossebau --- Still seeing "la lien" in latest catalog file, so passing on to translation team -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 442779] Wayland: When opening context menu while the Konversation window isn't focused, the context menu will have a window decoration
https://bugs.kde.org/show_bug.cgi?id=442779 Friedrich W. H. Kossebau changed: What|Removed |Added Version Fixed In||1.8.21120 Latest Commit||https://invent.kde.org/netw ||ork/konversation/-/commit/5 ||1e6ab4b193f4a1bc7ffce2a73b8 ||76d2f1232a7d Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||kosse...@kde.org --- Comment #2 from Friedrich W. H. Kossebau --- MR got merged, and by a quick test things seems to be fixed, so closing. Thanks for the fix. (closing manually, as bugs.kde.org integration needs the commit message to have a line "BUG: xyz" to auto-close the related bug.) -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 445986] Konversation got suddendly stuck
https://bugs.kde.org/show_bug.cgi?id=445986 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED CC||kosse...@kde.org Resolution|--- |UPSTREAM --- Comment #1 from Friedrich W. H. Kossebau --- By the backtrace, this seems an issue over at Qt side (or rather fontconfig), at least when used from gdb. Konversation just calls QInputDialog::getText() and things get stuck inside that call, so there is little we can do to fix that. This needs to be reported upstream, as Konversation would not be the only one affected by this. I would start with reporting to Qt, perhaps QFontconfigDatabase::setupFontEngine() does something wrong here. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 439892] Apparently random segmentation fault
https://bugs.kde.org/show_bug.cgi?id=439892 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||kosse...@kde.org --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. By backtrace should have the same cause as the fixed bug 437595, so closing as duplicate. Please reopen if still seeing with versions >= 1.8.21080. *** This bug has been marked as a duplicate of bug 437595 *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 437595] konversation crash when editing defaut identities
https://bugs.kde.org/show_bug.cgi?id=437595 Friedrich W. H. Kossebau changed: What|Removed |Added CC||b...@goodger.nl --- Comment #6 from Friedrich W. H. Kossebau --- *** Bug 439892 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 414727] Konversation crashes without any user input
https://bugs.kde.org/show_bug.cgi?id=414727 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED CC||kosse...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Friedrich W. H. Kossebau --- Thanks for the report. While the backtrace sadly lacks the needed info for the chain of calls ending up in the crashing operator== call, the present calls and the crash description hint this is the same cause as for the fixed bug 437595, so closing as duplicate. Please reopen if still seeing with versions >= 1.8.21080. *** This bug has been marked as a duplicate of bug 437595 *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 437595] konversation crash when editing defaut identities
https://bugs.kde.org/show_bug.cgi?id=437595 Friedrich W. H. Kossebau changed: What|Removed |Added CC||gtr...@gmail.com --- Comment #5 from Friedrich W. H. Kossebau --- *** Bug 414727 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 439509] Konversation crash on autostart with Plasma.
https://bugs.kde.org/show_bug.cgi?id=439509 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. By backtrace should have the same cause as the fixed bug 437595, so closing as duplicate. Please reopen if still seeing with versions >1.8.21080. *** This bug has been marked as a duplicate of bug 437595 *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 437595] konversation crash when editing defaut identities
https://bugs.kde.org/show_bug.cgi?id=437595 Friedrich W. H. Kossebau changed: What|Removed |Added CC||k...@kott.no-ip.biz --- Comment #4 from Friedrich W. H. Kossebau --- *** Bug 439509 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 437595] konversation crash when editing defaut identities
https://bugs.kde.org/show_bug.cgi?id=437595 Friedrich W. H. Kossebau changed: What|Removed |Added CC||k...@carewolf.com --- Comment #3 from Friedrich W. H. Kossebau --- *** Bug 440936 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 440936] Konversation crashes on network reconfiguration and laptop sleep
https://bugs.kde.org/show_bug.cgi?id=440936 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED CC||kosse...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. By backtrace should have the same cause as the fixed bug 437595, so closing as duplicate. Please reopen if still seeing with versions >1.8.21080. *** This bug has been marked as a duplicate of bug 437595 *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 437595] konversation crash when editing defaut identities
https://bugs.kde.org/show_bug.cgi?id=437595 Friedrich W. H. Kossebau changed: What|Removed |Added Version Fixed In||1.8.21080 CC||kosse...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 442109] 21.04.3: Tab completion broken
https://bugs.kde.org/show_bug.cgi?id=442109 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org Version Fixed In||1.8.21121 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 405714] trivial appearance bug
https://bugs.kde.org/show_bug.cgi?id=405714 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||eventviews/commit/fc416e6b1 ||6ed6ad165bf66de7bbccc216e69 ||d2f1 Version Fixed In||5.19.0 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from Friedrich W. H. Kossebau --- Git commit fc416e6b16ed6ad165bf66de7bbccc216e69d2f1 by Friedrich W. H. Kossebau. Committed on 29/11/2021 at 06:10. Pushed by kossebau into branch 'release/21.12'. Agenda view: fix misalignement of allday view & day headers \wo scrollbar FIXED-IN: 5.19.0 M +35 -9src/agenda/agendaview.cpp M +1-0src/agenda/agendaview.h https://invent.kde.org/pim/eventviews/commit/fc416e6b16ed6ad165bf66de7bbccc216e69d2f1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 405714] trivial appearance bug
https://bugs.kde.org/show_bug.cgi?id=405714 --- Comment #8 from Friedrich W. H. Kossebau --- Even simpler to reproduce: zooming in & out using Ctrl + scrollwheel :) The linked MR fixes things for me, please have a look if you can. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 405714] trivial appearance bug
https://bugs.kde.org/show_bug.cgi?id=405714 Friedrich W. H. Kossebau changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #5 from Friedrich W. H. Kossebau --- Just tested with latest development version (by resizing the window too a very large height, via moving the window by Alt+LMB partially out of screen and the enlarging by the bottom window border, multiple times). As I touched the code recently and still remember the scrollbar width considering code, will try this WE a patch. No promises though. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 405714] trivial appearance bug
https://bugs.kde.org/show_bug.cgi?id=405714 --- Comment #4 from Friedrich W. H. Kossebau --- (In reply to Nils from comment #1) > Created attachment 143946 [details] > Screenshot of the observed behaviour Hi Nils, what version of KOrganizer have you been using for that screenshot? (In reply to Allen Winter from comment #2) > Friedrich, this may be related to your recent changes in eventviews maybe? My changes should not have changed any properties of those two Agenda widget instances, the relative layout structure around them is as before . The scrollbar appearing under certain condition would have another cause I would think. Even as the original bug report is from before that. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 30331] implement moonphases in korganizer
https://bugs.kde.org/show_bug.cgi?id=30331 Friedrich W. H. Kossebau changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||kdepim-addons/commit/e19f81 ||97b0e7111a1f401114790cf7549 ||c8e0f64 Version Fixed In||21.12 --- Comment #9 from Friedrich W. H. Kossebau --- Git commit e19f8197b0e7111a1f401114790cf7549c8e0f64 by Friedrich W. H. Kossebau. Committed on 02/11/2021 at 09:15. Pushed by kossebau into branch 'master'. Reenable lunarphases korganizer plugin, use icon instead of text Also remove Lunarphases::createWeekElements(), old code would add an icon for the whole week if on start of the week there is a lunar event, which is not really something wanted. sc-status-moon-phase-full.svg is a copy of Breeze's weather-clear-night.svg of KF 5.84, with the other icons derived from it. FIXED-IN: 21.12 M +1-2korganizer/plugins/CMakeLists.txt M +11 -0korganizer/plugins/lunarphases/CMakeLists.txt M +41 -17 korganizer/plugins/lunarphases/lunarphases.cpp M +17 -1korganizer/plugins/lunarphases/lunarphases.h A +24 -0 korganizer/plugins/lunarphases/pics/sc-status-moon-phase-first-quarter.svg A +23 -0 korganizer/plugins/lunarphases/pics/sc-status-moon-phase-full.svg A +24 -0 korganizer/plugins/lunarphases/pics/sc-status-moon-phase-last-quarter.svg A +24 -0korganizer/plugins/lunarphases/pics/sc-status-moon-phase-new.svg https://invent.kde.org/pim/kdepim-addons/commit/e19f8197b0e7111a1f401114790cf7549c8e0f64 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 444405] Okteta crashes after using the Strings tool and switching files
https://bugs.kde.org/show_bug.cgi?id=05 --- Comment #3 from Friedrich W. H. Kossebau --- Thanks for the screen capture. Meanwhile found the flaw in the code, and also managed to force myself such crashes. So fix is already sketched and should land soonish. Given all the new reports I should see to do a release in the next weeks afterwards then, at least before end of year. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 444405] Okteta crashes after using the Strings tool and switching files
https://bugs.kde.org/show_bug.cgi?id=05 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. That the strings tool keeps the extracted strings around is on purpose, as there was interest to have them them available independent of whether the document is still loaded. There is explicit code to handle the document having been closed, but seems there is a flaw. Could not yet reproduce the crash, but the backtrace you provided matches what you describe, so serves as starting point to analyze the code. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 444453] The last character encoding combobox entries are unreachable by scrolling
https://bugs.kde.org/show_bug.cgi?id=53 Friedrich W. H. Kossebau changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Friedrich W. H. Kossebau --- Hi, thanks for the report. I can confirm the duplicated entry. Seems Qt broke here when switching to using ICU as backend, and request for TIS-620 and IBM874 are now both getting the same codec back. Meh. And seems there is quite some confusing naming for confusingly many variants of encodings for Latin/Thai. And Qt's code to connect to libicu is rather oversimplifying things, just caring for MIME and IANA naming now. Guess I have to escape into a custom codec then. Will think about the next days. I can also reproduce the error. That seems a bug in Qt, which also happens when adding a different data and icon to each entry, while using the same string. Ideally someone should file that bug with them. But once the charset duplication is fixed, should not bother us here. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 30331] implement moonphases in korganizer
https://bugs.kde.org/show_bug.cgi?id=30331 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org --- Comment #8 from Friedrich W. H. Kossebau --- While 3 years ago with https://invent.kde.org/pim/kdepim-addons/-/commit/a678c6bafc232b8e131f69607bf6152635776766 a first lunar phase plugin finally had made it into a repo, it was disabled from build though quickly again by https://invent.kde.org/pim/kdepim-addons/-/commit/638772af958e05b74687f709244eb1760233003b (commit considered it "too ugly"). Building up on that there now is though a new variant up for review which uses icons instead of text, which might be less ugly: https://invent.kde.org/pim/kdepim-addons/-/merge_requests/12 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 369486] "picture of the day" and "event of the day in history" are not displayed
https://bugs.kde.org/show_bug.cgi?id=369486 Friedrich W. H. Kossebau changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kdepim-addons/commit/120749 ||962e37f8713b32bfe9f5d8fa69a ||f19e9a8 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from Friedrich W. H. Kossebau --- Git commit 120749962e37f8713b32bfe9f5d8fa69af19e9a8 by Friedrich W. H. Kossebau. Committed on 19/10/2021 at 15:10. Pushed by kossebau into branch 'master'. Update KOrganizer POTD plugin for current Wikipedia API M +1-0korganizer/plugins/picoftheday/CMakeLists.txt A +385 -0korganizer/plugins/picoftheday/element.cpp [License: GPL(v2.0+)] A +95 -0korganizer/plugins/picoftheday/element.h [License: GPL(v2.0+)] M +23 -280 korganizer/plugins/picoftheday/picoftheday.cpp M +5-53 korganizer/plugins/picoftheday/picoftheday.h https://invent.kde.org/pim/kdepim-addons/commit/120749962e37f8713b32bfe9f5d8fa69af19e9a8 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 443983] khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 Friedrich W. H. Kossebau changed: What|Removed |Added Version Fixed In||21.08.3 CC||kosse...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 443983] khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 Friedrich W. H. Kossebau changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/kio-extras/commit/80986 ||3617a3fb76ce43f11dec541d4b9 ||4f63925a --- Comment #7 from Friedrich W. H. Kossebau --- Git commit 809863617a3fb76ce43f11dec541d4b94f63925a by Friedrich W. H. Kossebau. Committed on 19/10/2021 at 00:24. Pushed by kossebau into branch 'release/21.08'. man kio: fix crash due to bad memory pointer on REQ_ps handling 7d11a0932af2379cd46d338c49f758bc509acec7 accidentally moved the memory pointer increase out of the '+'-handling branch, which would either result in bad number being read or the pointer getting behind the end and resulting in garbage memory processing, potentially ending in a crash. Also changing to using dedicated own variable "sign" instead of reusing function-global variable "j" with meaningless name. global Fixed-in: 21.08.3 M +9-8man/man2html.cpp https://invent.kde.org/network/kio-extras/commit/809863617a3fb76ce43f11dec541d4b94f63925a -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 369486] "picture of the day" and "event of the day in history" are not displayed
https://bugs.kde.org/show_bug.cgi?id=369486 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org --- Comment #7 from Friedrich W. H. Kossebau --- Candidate MR to restore the "Picture of the day" plugin up at https://invent.kde.org/pim/kdepim-addons/-/merge_requests/17 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442496] Crash in QStackedLayout::widget when closing Okteta
https://bugs.kde.org/show_bug.cgi?id=442496 Friedrich W. H. Kossebau changed: What|Removed |Added Product|okteta |konsole Version|0.26.4 |21.08.0 Component|general |kpart Assignee|kosse...@kde.org|konsole-de...@kde.org --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Cannot reproduce here with with current Okteta & Konsole as of openSUSE TW packages (Konsole 21.08.1, Okteta 0.26.6) though. And seems a bug rather in Konsole by the backtrace, at least I think Okteta code is not interfering with anything related to where the crash happens, cmp. also https://invent.kde.org/utilities/okteta/-/blob/0.26/libs/kasten/controllers/document/terminal/terminalview.cpp Sidenote: you might want to poke the Fedora maintainer of the Okteta package to update to more receent 0.26.6 (released 2021-03-29) over what seems current with Fedora (0.26.4 from 2020-07-28). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390002] Message viewer: attached .doc file is shown as encrypted
https://bugs.kde.org/show_bug.cgi?id=390002 --- Comment #8 from Friedrich W. H. Kossebau --- Thanks for the quick reply and research, Ingo. Okay, so we need to fix/improve things on our side. Only on my schedule for next week#'s WE to continue here, so anyone is invited to have a look & go themselves until ;) -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 441855] Needs Actual dark theme
https://bugs.kde.org/show_bug.cgi?id=441855 --- Comment #4 from Friedrich W. H. Kossebau --- (In reply to hexile461 from comment #3) > The only reason why the screenshot is named deepin is because i'm using > Deepin Screentshot. it has nothing to do with the issue. So much for bad guessing :) So what is your environment then? The environment usually is used by Qt internals to decide which Qt platform adaption plugin (https://doc.qt.io/qt-5/qpa.html) is used. And that one also brings the theme adaption, which includes system palette mapping to the Qt one (https://doc.qt.io/qt-5/qpalette.html). Or it could be the widget theme which does a poor job on picking from the palette. In any case, nothing which is in control of Okteta, which completely relies on system color themes and Qt defaults. And something which would affect any other Qt-based application which does the same (and usually done for consistency). So this needs to be solved by those maintaining integration of Qt-based apps, even more as Qt went some extra miles to make integration smooth. Of course fails if the adaption plugin itself is badly done/configured. So please file this bug with Manjaro for their Qt apps integration for the environment you are using there. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390002] Message viewer: attached .doc file is shown as encrypted
https://bugs.kde.org/show_bug.cgi?id=390002 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kloec...@kde.org, ||kosse...@kde.org --- Comment #5 from Friedrich W. H. Kossebau --- Bug is still present in master branches of today, for the same reason as mentioned in comment 3. Pulling Ingo as a representative(? if not, please forward) of GPGMe into the discussion, to ask whether this should be also considered a bug in GPGMe that a msword or odt data blob is detected to be of type GpgME::Data::PGPOther? Works properly to report GpgME::Data::Unknown e.g. for PDF data blobs for me. On our side should registering EncryptedBodyPartFormatter as handler for "application/octet-stream" indeed be reconsidered and probably replaced with some special handling for known cases where the content type is not properly set to "text/pgp"? -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 441855] Needs Actual dark theme
https://bugs.kde.org/show_bug.cgi?id=441855 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |UPSTREAM --- Comment #2 from Friedrich W. H. Kossebau --- Thanks for the report. Just, Okteta uses the system color palette and tries to make use of the color semantics as close as possible. So far that worked out. See e.g. the screenshot when using Okteta with the Breeze Dark color scheme. It seems that the platform integration on your system injects colors while badly matching semantics at least to those known from Qt & KDE color palette ones. That will be hard to come by and surely also affects some other Qt-based applications? The name of your screenshot includes the name "Deepin", so you might want to contact them to improve their Qt platform integration plugin poissibly, which also might involve the color palette mapping. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 441855] Needs Actual dark theme
https://bugs.kde.org/show_bug.cgi?id=441855 --- Comment #1 from Friedrich W. H. Kossebau --- Created attachment 141227 --> https://bugs.kde.org/attachment.cgi?id=141227&action=edit Okteta with Breeze Dark -- You are receiving this mail because: You are watching all bug changes.
