[Skanlite] [Bug 480425] Skanlite runs the scan again after saving a scanned image
https://bugs.kde.org/show_bug.cgi?id=480425 --- Comment #5 from Kåre Särs --- Thanks for the update. The area detection maybe just could not find the two areas... If you cannot reproduce the unexpected behavior, maybe we can leave this as WORKSFORME? /Kåre -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 484231] Search & Replace plugin: Results are inserted in active tab
https://bugs.kde.org/show_bug.cgi?id=484231 Kåre Särs changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- Working on it now. It is a bit risky change, need to be careful -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 485320] Wishlist: remember scanning resolution between invocation
https://bugs.kde.org/show_bug.cgi?id=485320 Kåre Särs changed: What|Removed |Added CC||a.stipp...@gmx.net Component|general |general Version|23.08.5 |24.02.1 Ever confirmed|0 |1 Product|Skanlite|libksane Status|REPORTED|CONFIRMED --- Comment #1 from Kåre Särs --- Thanks for the report! This is most probably an issue with the order of the scanner options. When we save the options, we write them back in that same order that we get them. if the resolution is set before the scan source or mode, the resolution is probably reset when the scan-source or mode is set There would be a need to make it possible to apply the saved options in the right order I wonder if some crashes with some backends might be because of this order too... -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 484246] Skanlite randomly detects scanner dimensions as 16557 mm wide upon initialization.
https://bugs.kde.org/show_bug.cgi?id=484246 Kåre Särs changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Kåre Särs --- Thanks for the report. This looks like a backend issue, possibly caused by trying to restore settings from the previous session... Can you try to run Skanlite with debug logging enabled for the epson2 backend? The command to run in a terminal would be something like: SANE_DEBUG_EPSON2=16 skanlite And maybe play with the number a bit to see what gives a reasonable output, the values go from 1 to 128 and 128 returns all possible debug output... Then attach the output here, Thanks in advance, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 192302] Use Ocropus & Tesseract for OCR (goal: 'paperless office')
https://bugs.kde.org/show_bug.cgi?id=192302 Kåre Särs changed: What|Removed |Added Resolution|--- |NOT A BUG Status|CONFIRMED |RESOLVED --- Comment #7 from Kåre Särs --- Yep, I think we can point to Skanpage for the OCR parts -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483180] Build plugin: Working directory variables are not replaced when executing "Run command"
https://bugs.kde.org/show_bug.cgi?id=483180 Kåre Särs changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- Thanks for the report! You seem to have looked at the code already. Do you want to scratch your itch and create a merge request? If not, I'll add it to my todo -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 482210] Juk 24.02 crashes on start with ASSERT failure in QList::operator[]: "index out of range"
https://bugs.kde.org/show_bug.cgi?id=482210 Kåre Särs changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- Hi, I got hit by the same thing It seems that Playlist::calculateColumnWeights() somehow gets a mismatch in the number of columns. m_weightDirty contains column index 11, but m_columnWeights only has 11 columns And a possibly related bug I have after adding an index check, is that column content after "Album" is shifted one step to the right. "Track" is empty -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 481719] When opening the "Find in files" with some text in the search field, it will not close by pressing ESC
https://bugs.kde.org/show_bug.cgi?id=481719 --- Comment #6 from Kåre Särs --- If you have multiple matches visible at the same time and no selected word in the current document, it is quite obvious what happens when you press Esc the first time, but I can agree that if there is only the selected word that matches, it is quite hard to notice as the selection or the common word-highlight covers the match highlight. Unfortunately, I don't have any idea on how to accommodate both scenarios I think the separate de-selection and clearing of highlights are quite important features. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 481719] When opening the "Find in files" with some text in the search field, it will not close by pressing ESC
https://bugs.kde.org/show_bug.cgi?id=481719 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #4 from Kåre Särs --- The original reason for not closing is that the first Esc removes the search result highlights (in case they are distracting) -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 480816] Skanlite crashed while receiving data from the HP officejet pro 8720 after scanning job completed
https://bugs.kde.org/show_bug.cgi?id=480816 Kåre Särs changed: What|Removed |Added Product|Skanlite|libksane Component|general |general --- Comment #1 from Kåre Särs --- Thanks for the report! This actually looks like a bug in the library KSaneCore -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 480425] Skanlite runs the scan again after saving a scanned image
https://bugs.kde.org/show_bug.cgi?id=480425 Kåre Särs changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Kåre Särs --- Hi, Thanks for the report, I think the reason might be that you have not disabled the automatic area detection and it has probably detected two areas and then go on to scan the next area. Might that be the issue? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 479461] When saving a text file kate always appends a new line at the end
https://bugs.kde.org/show_bug.cgi?id=479461 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #3 from Kåre Särs --- A file that does not end with a \n looks like it is truncated. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Kåre Särs changed: What|Removed |Added Resolution|REMIND |FIXED Status|VERIFIED|RESOLVED Version Fixed In||24.02.0 CC||kare.s...@iki.fi --- Comment #6 from Kåre Särs --- Hi, This has been improved in master and will be released with 24.02.0 in February. If you need the improvement _now_, you have to compile your self or use some bleeding development edge distribution that packages beta versions of KDE software. Instructions for building it your self: https://kate-editor.org/build-it/ Br, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433619] Images which are referenced using relative routes are not seen
https://bugs.kde.org/show_bug.cgi?id=433619 Kåre Särs changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #9 from Kåre Särs --- What about the "Emportrado" (Embedding) tab? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475109] The color picker plugin doesn't work properly.
https://bugs.kde.org/show_bug.cgi?id=475109 Kåre Särs changed: What|Removed |Added Ever confirmed|0 |1 CC||kare.s...@iki.fi Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- --- Comment #2 from Kåre Särs --- Hmm... I wonder if this got closed by mistake It is not about the preview plugin (but it does have the word in it) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 478212] saving to remote symlink replaces link with file
https://bugs.kde.org/show_bug.cgi?id=478212 Kåre Särs changed: What|Removed |Added Version|23.08.3 |5.112.0 Product|kate|frameworks-kio CC||kare.s...@iki.fi, ||kdelibs-b...@kde.org Component|application |general Assignee|kwrite-bugs-n...@kde.org|kio-bugs-n...@kde.org --- Comment #1 from Kåre Särs --- Unfortunately, fixing this is not going to be trivial The way it works is that the file is downloaded, edited and then uploaded on save... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478206] kate hangs while editing remote files
https://bugs.kde.org/show_bug.cgi?id=478206 Kåre Särs changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Kåre Särs --- I can see that you have the debug symbols for KTextEditor, but the line: #5 0x7f8a981892de in KateProjectPlugin::projectForDir(QDir, bool) () from /usr/lib64/qt5/plugins/ktexteditor/kateprojectplugin.so does indicate that the ones for Kate and it's plugins might be missing something... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478206] kate hangs while editing remote files
https://bugs.kde.org/show_bug.cgi?id=478206 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Kåre Särs --- Thanks for the report. Can you install the debug symbols also for Kate? Smells a bit like the project plugin is trying to figure out a possible project in the remote folder -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 476278] Discover fails to install libraries libvte-2.9 and libokularcore10:amd64 on intel Acer laptop with new kernel 6.2.0-35
https://bugs.kde.org/show_bug.cgi?id=476278 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Kåre Särs --- I wonder if this bug is filed for the wrong component? libksane is a image and document scanning library -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475725] 搜索中文错误
https://bugs.kde.org/show_bug.cgi?id=475725 Kåre Särs changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO CC||kare.s...@iki.fi --- Comment #4 from Kåre Särs --- I have a bit hard time reproducing the issue... Is it so that you have Windows locale set to use GB2312 ? Did I understand it correctly that the file uses one encoding in the editor and then when you search, the encoding is different in the search results? -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 472393] Scanner fails to open
https://bugs.kde.org/show_bug.cgi?id=472393 --- Comment #3 from Kåre Särs --- Ooops I have managed to miss this one... What backend are you using? sane-airscan? or is there also some USB backend? if it is sane-airscan you could start Skanlite with sane debugging enabled I'm not 100% sure about this backend's debugging, but it is usually something like "SANE_DEBUG_=[0-255] skanlite" This page probably has more data on debugging: https://manpages.debian.org/testing/sane-airscan/sane-airscan.5.en.html -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 474316] Will not remember selected scan resolution between restarts of the software. Defaults to 4,800 DPI.
https://bugs.kde.org/show_bug.cgi?id=474316 --- Comment #3 from Kåre Särs --- Does it have an option that says "Scan Source" ? If yes, can you change that to something else, change the resolution and then change the "Scan Source" back to "Flatbed" (or similar) and see if the resolution changes? -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 474316] Will not remember selected scan resolution between restarts of the software. Defaults to 4,800 DPI.
https://bugs.kde.org/show_bug.cgi?id=474316 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Kåre Särs --- Thanks for the report! I suspect that it has to do with the order in which the parameters are restored. If we first set the resolution and then the scan source, it might be that setting the scan source also sets a default resolution Can you test doing it manually? setting an other scan source, set resolution and then set the scan source a gain. Does this change the resolution too? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473266] Regex doesn't seem to respect flag state
https://bugs.kde.org/show_bug.cgi?id=473266 --- Comment #3 from Kåre Särs --- Sorry not the string "\n" but the new-line character '\n' is used to join lines in multi-line searches :) -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 473183] Crash on FastFoto scan
https://bugs.kde.org/show_bug.cgi?id=473183 Kåre Särs changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Kåre Särs --- Thanks for the report! >From the crash-dump (nice with all the debug symbols, thanks!) it looks like the crash is deep in the scanner backend. Can you reproduce the problem with XSane or is it specific to Skanlite/Skanpage. Anyhow, I'm afraid this is a bug in the backend and a bit out of Skanlite/libksane/KSaneCore's hands. Looks like the utsushi backend is maintained at https://gitlab.com/utsushi/utsushi Can you make a bug report there? Thanks, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473266] Regex doesn't seem to respect flag state
https://bugs.kde.org/show_bug.cgi?id=473266 Kåre Särs changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||kare.s...@iki.fi --- Comment #2 from Kåre Särs --- Thanks for the report! I think the problem might be that Kate treats every line as a separate string. Only if the regular expression includes "\n", the search will search in a copy of all lines joined into one string with "\n". It could be interesting to test if this could be fixed by also treating the (?s) flags as a trigger to join the lines. This would have to be checked/fixed both in the KTextEditor search and the Kate multi-file search plugin (this does go into the more advanced regular expressions :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472608] Search in files: Enter key should replace only current item
https://bugs.kde.org/show_bug.cgi?id=472608 Kåre Särs changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472608] Search in files: Enter key should replace only current item
https://bugs.kde.org/show_bug.cgi?id=472608 Kåre Särs changed: What|Removed |Added Ever confirmed|0 |1 CC||kare.s...@iki.fi Status|REPORTED|CONFIRMED --- Comment #1 from Kåre Särs --- Hi, Thanks for the report! It is unfortunate that the searches behaves differently. Problem 1: In the search & replace plugin, a search might be very expensive. That is why a full search is only triggered by enter (the current file is searched after a certain amount of waiting). The plugin also does not move the cursor when the the search is done, so moving on the second enter, feels a bit strange (it did jump to the first match at some point, but that was removed at some point) Problem 2A: In my experience, the replace all matches is the more common task for the cross-files replace, so making "replace-next" the more prominent one is probably not a good idea. Adding a (configurable) shortcut for Replace-Next is probably a good idea. Problem 2B: Undoing the last multi-file replace is definitely something we need! Should be added as a new separate wish-item. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472299] Key repeat failure for Backspace key in Search/Replace panel
https://bugs.kde.org/show_bug.cgi?id=472299 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Kåre Särs --- I can confirm that this issue is present on Wayland (not X11). Running KDE Neon + master Kate -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433619] Images which are referenced using relative routes are not seen
https://bugs.kde.org/show_bug.cgi?id=433619 Kåre Särs changed: What|Removed |Added Resolution|--- |UPSTREAM CC||kare.s...@iki.fi Status|REOPENED|RESOLVED --- Comment #5 from Kåre Särs --- Hi, The Okular part does not seem to like the relative path or something. Please install markdownpart (sudo apt install markdownpart) and either remove the Okular markdown backend or move it down the list in file associations in System Settings. The markdown part works nicer with Kate as it has much less keyboard shortcuts that might conflict. If you want to continue using the Okular kpart, you need to file this bug to Okular. I hope this helps -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468452] Feature Request: Enable Multiple String Search in Search and Replace Plug-in
https://bugs.kde.org/show_bug.cgi?id=468452 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #3 from Kåre Särs --- Hi, I was going to say that this is a prime example for regular-expressions, but when trying to construct such, I notice a problem. ^ is beginning of line and $ is end of line and there is currently no way to specify a regular expression that specifies start of document and end of document. So in short is it a bit hard to get a regular expression the excludes a word from the whole document. I was first thinking that \^ and \$ could be used for that, but that is needed for actual ^ and $. Ideas are well come. An ugly workaround would be to add an option to treat the whole document as one long string, in which case ^ would be start of document and $ end of document... -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 466659] Application crash at the stage of choosing a scanner or scanning
https://bugs.kde.org/show_bug.cgi?id=466659 Kåre Särs changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #4 from Kåre Särs --- Thanks for the update. I can see from the logs that it is a Pantum printer/scanner. It seems that it is not supported by sane (http://www.sane-project.org/sane-mfgs.html), but Pantum has a proprietary sane-backend. Unfortunately I cannot help much here :( I don't know much else than that you would report the issue to Pantum. Maybe they have a scanning application also that does not trigger that bug... For me the download for Linux was a .deb package made for Ubuntu, maybe the package for Arch, is just a repackaged binary that might not be 100% compatible...? Then it could work on Ubuntu... -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 466659] Application crash at the stage of choosing a scanner or scanning
https://bugs.kde.org/show_bug.cgi?id=466659 Kåre Särs changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Kåre Särs --- Thank you for the report. With a quick look at the crash-log, it looks like the crash is in the sane-backend (driver). Do you get the same crash with XSane? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463993] Save button grayed out when adding ctags directories
https://bugs.kde.org/show_bug.cgi?id=463993 Kåre Särs changed: What|Removed |Added Version Fixed In||22.12.2 Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/kate/commit/474ff73bc |ities/kate/commit/526d04db8 |4ee05134ab1730cdb1cef6cf5ec |2d4b65c61b4b0f607c4b2ffa8a0 |8e3e|2f3d --- Comment #3 from Kåre Särs --- Git commit 526d04db82d4b65c61b4b0f607c4b2ffa8a02f3d by Kåre Särs. Committed on 08/01/2023 at 20:15. Pushed by sars into branch 'release/22.12'. Fix settings saving regression in CTags plugin. FIXED-IN: 22.12.2 M +3-0addons/kate-ctags/kate_ctags_plugin.cpp https://invent.kde.org/utilities/kate/commit/526d04db82d4b65c61b4b0f607c4b2ffa8a02f3d -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463993] Save button grayed out when adding ctags directories
https://bugs.kde.org/show_bug.cgi?id=463993 Kåre Särs changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/474ff73bc ||4ee05134ab1730cdb1cef6cf5ec ||8e3e --- Comment #2 from Kåre Särs --- Git commit 474ff73bc4ee05134ab1730cdb1cef6cf5ec8e3e by Kåre Särs. Committed on 08/01/2023 at 20:13. Pushed by sars into branch 'master'. Fix settings saving regression in CTags plugin. M +3-0addons/kate-ctags/kate_ctags_plugin.cpp https://invent.kde.org/utilities/kate/commit/474ff73bc4ee05134ab1730cdb1cef6cf5ec8e3e -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463993] Save button grayed out when adding ctags directories
https://bugs.kde.org/show_bug.cgi?id=463993 Kåre Särs changed: What|Removed |Added Ever confirmed|0 |1 CC||kare.s...@iki.fi Status|REPORTED|CONFIRMED --- Comment #1 from Kåre Särs --- Thanks for the report. I can reproduce the issue. As a workaround you can check uncheck an option on another settings page to enable the save button... This needs fixing... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463767] search & replace unicode char is very slow
https://bugs.kde.org/show_bug.cgi?id=463767 --- Comment #4 from Kåre Särs --- There is the "Replace checked" button that replaces all the checked items. After a search all matches are checked until you un-check them -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463767] search & replace unicode char is very slow
https://bugs.kde.org/show_bug.cgi?id=463767 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #2 from Kåre Särs --- I can also reproduce the issue. As a workaround, for now at least, you can use the Search & Replace plugin. With the plugin, the search is done in less than a second. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462933] Left-Clicking on kwrite minimap jumps to location instead of advancing one page
https://bugs.kde.org/show_bug.cgi?id=462933 Kåre Särs changed: What|Removed |Added Status|REPORTED|RESOLVED CC||kare.s...@iki.fi Resolution|--- |NOT A BUG --- Comment #1 from Kåre Särs --- Thanks for the report. This behavior is by design. We have explicitly made it behave like this when you have the minimap enabled. With a normal scrollbar you do not see what is below or above, so you do not know exactly where you want to go. With the minimap you have indications and can jump quite accurately to the wanted position. (middle-click seems to be a very advanced-user action) Page up/down gives the same scrolling as left click on a normal scroll-bar. BR, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 462408] Skanlite cashes when trying to cancel scan
https://bugs.kde.org/show_bug.cgi?id=462408 --- Comment #9 from Kåre Särs --- Thanks for the fix! I just back-ported it to 22.12.1 BR, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 462408] Skanlite cashes when trying to cancel scan
https://bugs.kde.org/show_bug.cgi?id=462408 Kåre Särs changed: What|Removed |Added Version Fixed In||22.12.1 Latest Commit||https://invent.kde.org/grap ||hics/skanlite/commit/0aab98 ||f92ce1f05cd7f9e3d39bb170f6c ||3e5e3cd Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #8 from Kåre Särs --- Git commit 0aab98f92ce1f05cd7f9e3d39bb170f6c3e5e3cd by Kåre Särs, on behalf of Alexander Wilms. Committed on 11/12/2022 at 08:09. Pushed by sars into branch 'release/22.12'. Use lambdas for disabling and enabling 'Reselect Device' button FIXED-IN: 22.12.1 M +6-13 src/skanlite.cpp M +0-2src/skanlite.h https://invent.kde.org/graphics/skanlite/commit/0aab98f92ce1f05cd7f9e3d39bb170f6c3e5e3cd -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 462408] Skanlite cashes when trying to cancel scan
https://bugs.kde.org/show_bug.cgi?id=462408 Kåre Särs changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Kåre Särs --- Thanks for the report! Nice to get a report once in a while that actually is a clear bug in Skanlite/libksane and not just a buggy backend :) Since you already have the code and are working on it. Are you interested in debugging and fixing? BR, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462220] Kate's search & replace interprets captured text in regex mode
https://bugs.kde.org/show_bug.cgi?id=462220 --- Comment #6 from Kåre Särs --- Yes, "¤Search¤" is a reserved string, but it has been like that for over 9 years and I have not seen a bug report about it yet ;) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 457246] Problem with Editor background Text Area and translucent color!
https://bugs.kde.org/show_bug.cgi?id=457246 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #4 from Kåre Särs --- Then dave.next...@gmail.com please provide a non-breaking patch to make transparency work for the background of the rendered lines. The code for rendering lines is complicated and has not been designed with transparency in mind. And it seems that this is not an itch or big issue for the current volunteers developing Kate or KTextEditor. Thanks, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462220] Kate's search & replace interprets captured text in regex mode
https://bugs.kde.org/show_bug.cgi?id=462220 Kåre Särs changed: What|Removed |Added Version Fixed In||22.12 Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/kate/commit/8bd136ad5 |ities/kate/commit/554df48b3 |c1c05a92ce91286765b20538a9a |d35ce0c9e552016627106f860da |bad9|fc5f --- Comment #4 from Kåre Särs --- Git commit 554df48b3d35ce0c9e552016627106f860dafc5f by Kåre Särs. Committed on 27/11/2022 at 10:55. Pushed by sars into branch 'release/22.12'. S: Do not do "\t" -> '\t' and similar for regex captures FIXED-IN: 22.12 M +10 -6addons/search/MatchModel.cpp https://invent.kde.org/utilities/kate/commit/554df48b3d35ce0c9e552016627106f860dafc5f -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462220] Kate's search & replace interprets captured text in regex mode
https://bugs.kde.org/show_bug.cgi?id=462220 Kåre Särs changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/8bd136ad5 ||c1c05a92ce91286765b20538a9a ||bad9 Resolution|--- |FIXED --- Comment #3 from Kåre Särs --- Git commit 8bd136ad5c1c05a92ce91286765b20538a9abad9 by Kåre Särs. Committed on 27/11/2022 at 10:53. Pushed by sars into branch 'master'. S: Do not do "\t" -> '\t' and similar for regex captures M +10 -6addons/search/MatchModel.cpp https://invent.kde.org/utilities/kate/commit/8bd136ad5c1c05a92ce91286765b20538a9abad9 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462220] Kate's search & replace interprets captured text in regex mode
https://bugs.kde.org/show_bug.cgi?id=462220 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Kåre Särs --- Thanks for the report! It took me a little while to understand the problem, but I can confirm this issue In char string terms: In stead of replacing "\\t" with "\\t", as it should, it replaces it with '\t' -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 462206] Flatpak package
https://bugs.kde.org/show_bug.cgi?id=462206 --- Comment #1 from Kåre Särs --- There is at least intentions to try to create a snap package by Ubuntu, but the big problem is that some scanners have backends provided by the producers and are not opensource. If the application is sand-boxed and only can access the bundled libraries, you cannot access scanners that have proprietary or third-party backends. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 458072] Ctrl+. broken as a keybind
https://bugs.kde.org/show_bug.cgi?id=458072 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #11 from Kåre Särs --- Do you have ibus installed? I did a distribution upgrade and suddenly I had ibus installed... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458961] Sidebar with persistent display
https://bugs.kde.org/show_bug.cgi?id=458961 Kåre Särs changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||kare.s...@iki.fi --- Comment #7 from Kåre Särs --- Hi, There is a setting to specify the size of the icon or even go back to having vertical text: Settings -> Configure Kate.. -> Behavior -> Sidebars -> Icon size & Show text for... If you do not want the plugins at all , I guess KWrite is the right tool for you. But if you do want some plugins, you can save the session and then open that session. The unnamed session enables these plugins... Hmm I just saved a session with the name "Default" and that actually stores the plugin settings. Hope this helps, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 460355] Skanlite always scans “first“ auto-detected area after scan preview
https://bugs.kde.org/show_bug.cgi?id=460355 Kåre Särs changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |LATER --- Comment #3 from Kåre Särs --- This was an unfortunate design decision at the time, to make it default on You can disable the automatic selection in the Skanlite settings. You can also clear all selections with the clear-selections button. For the Qt6 version I think we will make automatic selection not be turned on by default. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 460607] Laptop camera detected as a scanner.
https://bugs.kde.org/show_bug.cgi?id=460607 Kåre Särs changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Kåre Särs --- To prevent the camera from showing up, disable the v4l backend in /etc/sane.d/dll.conf (comment it out with a # in front) I don't know why it is enabled by default, but that is just how it is... Hope this helps. Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 254186] skanlite's “Reload devices list” does not work
https://bugs.kde.org/show_bug.cgi?id=254186 --- Comment #5 from Kåre Särs --- The problem is still the same as in comment 1. The problems have not been fixed in backends :( So after more than 10 years, maybe it would be time to actually do a workaround..., but the only current workaround makes it impossible to open multiple devices from one process. on the other hand I do not know about any application that would open more than one device at a time... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 459696] New: qml-module-qt3d packaging broken
https://bugs.kde.org/show_bug.cgi?id=459696 Bug ID: 459696 Summary: qml-module-qt3d packaging broken Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: kare.s...@iki.fi CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- It seems there is something wrong with the packaging of Qt3D. When I try to run any Qt3D examples I get: "Cannot mix incompatible Qt library (5.15.5) with this library (5.15.6)" When I run the application with qml-module-qt3d not installed I just get QML warnings about missing QML modules. I tried to locally build the debian packages for qt3d-opensource-src-5.15.5+p22.04+tunstable+git20220909.0022, but that failed to build out of the box. I then cloned the qt3d git repo and built the head of the 5.15 branch and installed it to /usr (not on a production machine). After the install Qt3D applications started working again. Same problem is also present in the p20.04 version Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 458048] org.kde.skanlite//master doesn't find network scanner
https://bugs.kde.org/show_bug.cgi?id=458048 Kåre Särs changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Kåre Särs --- Thanks for the report. The reason is most probably that you do not have the device specific sane driver/backend installed. check if there are brother-specific packages for sane or then go to brothers support pages and download their driver there. Then it might be easier to get to work with native packages as the sand-boxed flatpacks might not see system installed extra backends I hope this helps to get your issue resolved. Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 457526] First time crash in Skanlite
https://bugs.kde.org/show_bug.cgi?id=457526 --- Comment #3 from Kåre Särs --- Thanks for the update! :) Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 457526] First time crash in Skanlite
https://bugs.kde.org/show_bug.cgi?id=457526 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Kåre Särs --- Thanks for the report! Can you install the debug symbol packages for libsane hopefully this command should do it: sudo apt-get install libsane-dbg then try to reproduce the crash and attach the crashlog Thanks, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456808] Crash when changing scan source or color option
https://bugs.kde.org/show_bug.cgi?id=456808 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|ASSIGNED|NEEDSINFO --- Comment #8 from Kåre Särs --- Hi, I checked this a bit and it does look like a back-end/driver issue in the epson2 back-end, but It would help to get a bit more info. What scanner do you have? Does it have automatic document feeder? Does the problem go away if you click on the "Revert scanner options to default values" in the configure dialog? Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456808] Crash when changing scan source or color option
https://bugs.kde.org/show_bug.cgi?id=456808 Kåre Särs changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |ASSIGNED --- Comment #7 from Kåre Särs --- Thanks for the back-trace! Now there are file and line numbers that can help in finding the issue. This is quite probably a back-end/driver issue, but I'll have a look what we can do. /Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456808] Crash when changing scan source or color option
https://bugs.kde.org/show_bug.cgi?id=456808 --- Comment #4 from Kåre Särs --- Thanks, Unfortunately that package you installed was not the debug symbols. I think the package name should end in "debuginfo" Maybe sane-backends-debuginfo or libsane-debuginfo (or something similar). It would be good to also get the debuginfo pacakage also for libksane. Thanks, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456808] Crash when changing scan source or color option
https://bugs.kde.org/show_bug.cgi?id=456808 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Kåre Särs --- Thanks for the report! Can you install the debug symbol package for libsane/sane-backends and for libksane and then reproduce the crash? BR, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 454409] Skanlite crashes when it attempts to access my scanner.
https://bugs.kde.org/show_bug.cgi?id=454409 --- Comment #5 from Kåre Särs --- (In reply to BEEDELL ROKE JULIAN LOCKHART from comment #3) > (In reply to Kåre Särs from comment #2): > > Can you install the debug symbols for sabe-backends? > > As "http://reddit.com/comments/vdquh2/comment/icm40wf; directs? I'm a bit uncertain as I do not use Fedora... but does look like it could work :) Thanks, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456092] Scan area size unit should not be translated to inch since we do not have the conversion
https://bugs.kde.org/show_bug.cgi?id=456092 Kåre Särs changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Summary|unit shoud be millimeters |Scan area size unit should |or changeable |not be translated to inch ||since we do not have the ||conversion Status|NEEDSINFO |CONFIRMED --- Comment #3 from Kåre Särs --- Hmm... I guess there might be a translation error, because we do not have mm to inch conversion anywhere... -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456092] unit shoud be millimeters or changeable
https://bugs.kde.org/show_bug.cgi?id=456092 Kåre Särs changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Kåre Särs --- Thanks for the report. When using the test backend I can only see imperial units in the scan resolution (DPI) but that unit is basically everywhere... For me the scan-area size is in mm... What locale do you have? could it be a translation error? What scanner/backend do you have could it be something from the backend? -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 454409] Skanlite crashes when it attempts to access my scanner.
https://bugs.kde.org/show_bug.cgi?id=454409 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Kåre Särs --- Thanks for the report. Can you install the debug symbols for sabe-backends? Thanks, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 454531] Skanlite crashed when I chose "color" to be "scan mode".
https://bugs.kde.org/show_bug.cgi?id=454531 --- Comment #3 from Kåre Särs --- Thanks for the report! Sorry for not answering earlier. I somehow have missed this report. :( It looks like it is crashing in the epson2 backend, but we need the debug symbols to be able to see exactly, where in there, it crashes. Can you install the debug package for the sane-backends (maybe sane-backends-libs-debuginfo? guessing as I do not have Fedora installed) Thanks, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 453162] Skanlite crash when scanning one or several selections
https://bugs.kde.org/show_bug.cgi?id=453162 Kåre Särs changed: What|Removed |Added Resolution|NOT A BUG |UPSTREAM --- Comment #4 from Kåre Särs --- Thanks for checking this! Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 453403] Please, use name schema like spectacle
https://bugs.kde.org/show_bug.cgi?id=453403 Kåre Särs changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Kåre Särs --- Hi, Thanks for the wish! I do agree. It would be nice! Patches are very welcome! ;) Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 453162] Skanlite crash when scanning one or several selections
https://bugs.kde.org/show_bug.cgi?id=453162 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Kåre Särs --- Thanks for the report. This looks very much like a bug in the sane escl backend from the backtrace. Do you get the same crash with xsane? Br, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451978] Kate Build plugin does not recognize pylint command output
https://bugs.kde.org/show_bug.cgi?id=451978 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Kåre Särs --- Thanks for the report. I think the reason is that pylint outputs everything to stdout in stead of putting errors and warnings to stderr like gcc and clang. We have added a workaround for similar issues when using Ninja for building... -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 451082] libksane should not expose "source" for the Brother DS-640
https://bugs.kde.org/show_bug.cgi?id=451082 Kåre Särs changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Kåre Särs --- I think this is a bug in the backend, if it is not an "Automatic Document Feeder" it should not advertise itself as one. My preferred solution would be to have the brother backend "fixed". Maybe it should state only "Document feeder"? Then again this is not a thing that is governed by the sane-standard and only heuristics in libksane... :( Adding an option like you said is not impossible either, but a bit ugly workaround for something that could be "fixed" in the backend... Then again there might be code shared between multiple brother scanners and that would add extra burden there... You seem to have coding skills ;) maybe you want to help? 1) My first choice would be to ask brother to fix it. Seems to be proprietary :( 2) Add a public API to libksane and use that in Skanlite. 3) A bit risky variant would be to "blacklist" ADF for that model Are you willing to do it? -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 450204] Refuses to scan the whole of an A4 page
https://bugs.kde.org/show_bug.cgi?id=450204 --- Comment #5 from Kåre Särs --- Hmm... if you have multiple selections all of those should be scanned with one press of the scan button... You can "save" the manual selection by clicking the '+' in the middle of the selection and the same way you can convert a "red/saved" selection to manual by clicking the '-' sign in the middle -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 450204] Refuses to scan the whole of an A4 page
https://bugs.kde.org/show_bug.cgi?id=450204 Kåre Särs changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from Kåre Särs --- Hi, Unfortunately 10+ years ago I added automatic photo/region selection that is on by default. This is unfortunate as it is not very good for text documents. The automatic selection can be disabled in the settings of Skanlite. You can also click the clear-selections button below the preview to remove the automatic selections. The option comes from libksane and I think when we move to Qt6, we should change the default to off. Hope this helps, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451238] Project/Build-Plugin + .kateproject is buggy
https://bugs.kde.org/show_bug.cgi?id=451238 --- Comment #7 from Kåre Särs --- Yeah, I think I was too quick to draw conclusions. I saw the code path for old project files (< 4.12). in those times we only had build, clean, quick targets I do not use the handwritten project file nor the CMake generated so I am oblivious to any bugs there... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451238] Project/Build-Plugin + .kateproject is buggy
https://bugs.kde.org/show_bug.cgi?id=451238 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #5 from Kåre Särs --- This is install target not showing up is a problem in the build plugin... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450414] 'Search and Replace' & 'Find' discrepancies (search and replace has no X button and doesn't automatically paste highlighted text)
https://bugs.kde.org/show_bug.cgi?id=450414 --- Comment #17 from Kåre Särs --- It was meant to read @jimbo, Sorry for the typo :( -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450414] 'Search and Replace' & 'Find' discrepancies (search and replace has no X button and doesn't automatically paste highlighted text)
https://bugs.kde.org/show_bug.cgi?id=450414 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #16 from Kåre Särs --- @jumbo 1) Please use the "Edit -> Search in Files" action in stead. The "View -> Tool Views... -> Show ..." actions are there just to open close the tool views with no extra functionality. 2) Pressing ESC will remove the highlighting (if you have search matches), otherwise it will close the tool-view (Note: different than collapsing) -> Two ESC presses will always close the search tool-view. @Waqar 3) Wonder if we should investigate disabling the collapsing of the tool-views altogether... It only brings confusion when people collapse it and then can't find their tool-views... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449545] Replace in "Search and Replace" does not work when the search regex contains lookahead or lookbehind part
https://bugs.kde.org/show_bug.cgi?id=449545 Kåre Särs changed: What|Removed |Added Version Fixed In||22.04 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449545] Replace in "Search and Replace" does not work when the search regex contains lookahead or lookbehind part
https://bugs.kde.org/show_bug.cgi?id=449545 Kåre Särs changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/cb759994b ||eb24b119492e588147be1916390 ||d017 --- Comment #3 from Kåre Särs --- Git commit cb759994beb24b119492e588147be1916390d017 by Kåre Särs. Committed on 09/02/2022 at 20:14. Pushed by sars into branch 'master'. S: Fix Look-ahead & behind highlighting & replace Strip the look-ahead and look-behind from the regular-expression that checks if a string has been modified after search and returns the possible captures. We strip the look-ahead/behind because we only match against the previously found range. M +27 -1addons/search/MatchModel.cpp M +6-0addons/search/MatchModel.h A +48 -0addons/search/autotest/input/LookaheadLookbehindTestFile.txt A +22 -0addons/search/autotest/input/MultilineStartEndOfLineMatch.txt M +2-9addons/search/plugin_search.cpp https://invent.kde.org/utilities/kate/commit/cb759994beb24b119492e588147be1916390d017 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449545] Replace in "Search and Replace" does not work when the search regex contains lookahead or lookbehind part
https://bugs.kde.org/show_bug.cgi?id=449545 Kåre Särs changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- I can confirm this bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449434] whole word
https://bugs.kde.org/show_bug.cgi?id=449434 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Severity|critical|wishlist Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Kåre Särs --- Hi, The search plugin only supports plain-text and regular-expression modes. I can see from the screenshot that the match-case and regular-expression tool-buttons have very dark icons and are barely visible :( With regular-expressions you get the "whole word" search with adding "\b" before and after the word like: "\bFooBar\b". As you can se, it is really easy to get the whole word with just a little regular-expressions, so I think there is not a big reason to add yet another button or option for that... (When you enable regular-expressions, you also get a context menu in the search field with common regular-expressions) I hope this helps, Kåre -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 444605] Default focus is put on button "Close": hitting ENTER closes the program
https://bugs.kde.org/show_bug.cgi?id=444605 --- Comment #11 from Kåre Särs --- This bug is really strange! Me and Alexander, cannot reproduce... I have tested both on Wayland and X11 Are there any Archlinux specific patches? The button removal is mainly to get it more in line with Spectacle's UI. Alt-F4 and Ctrl-Q quits the application and you have the normal close button on the Window, so you might not really need the separate close-button. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448786] Feature request: add a toggle in settings to close kwrite when the open document is closed
https://bugs.kde.org/show_bug.cgi?id=448786 Kåre Särs changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #2 from Kåre Särs --- Sorry missed that it was mainly for KWrite..., there it does not work. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448786] Feature request: add a toggle in settings to close kwrite when the open document is closed
https://bugs.kde.org/show_bug.cgi?id=448786 Kåre Särs changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- This has been added some time ago :) Settings -> Configure Kate... -> Session -> Application Shutdown Behavior -> Close Kate entirely when the last file is closed -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 414362] Old file changed dialog had some advantages over the current KMessageWidget-based UI
https://bugs.kde.org/show_bug.cgi?id=414362 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #11 from Kåre Särs --- Trying to be a bit constructive ;) Point 1) about not noticing the changed files before navigating to the effected files, is something that we could have a look at. I find myself doing "Reload All" a bit too often to make sure I have up to date content in the loaded files. Searching in Project / Folder will give you old data until you reload... That said I do not want to go back to the previous dialog. Maybe we could make sure that we get a KMessageWidget immediately in the active view(s) that could contain a "Reload All" button or something similar? -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 444605] Default focus is put on button "Close": hitting ENTER closes the program
https://bugs.kde.org/show_bug.cgi?id=444605 --- Comment #6 from Kåre Särs --- That is strange, I'm using the KDE Gear 21.12.0, KF5 5.89.0 and Qt 5.15.3 version on KDE Neon and I can't even get the focus to the close button (Esc closes the window so not a problem). -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 446612] Feature Request - Save as PDF
https://bugs.kde.org/show_bug.cgi?id=446612 Kåre Särs changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Kåre Särs --- I'm happy to say that the next Skanlite release will have single page PDF support, but most of all, there is now a dedicated multi-page document scanning application called Skanpage: https://apps.kde.org/skanpage/ https://invent.kde.org/utilities/skanpage check it out :) *** This bug has been marked as a duplicate of bug 299517 *** -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 299517] Skanlite should support scan to pdf.
https://bugs.kde.org/show_bug.cgi?id=299517 Kåre Särs changed: What|Removed |Added CC||kde-b...@spaetzle.info --- Comment #47 from Kåre Särs --- *** Bug 446612 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443977] URGENT REGRESSION: unusable with non-english keyboard: adds space before every accented character
https://bugs.kde.org/show_bug.cgi?id=443977 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #13 from Kåre Särs --- Hello php4...@gmail.com The problem here is that we do not know what the problem is or, if it is a Kate bug, when it has been introduced... how far back should be go? Can this be reproduced on Kubuntu 20.10 does it reproduce on early Kubuntu 21.04?... -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 445139] Skanpage coredump
https://bugs.kde.org/show_bug.cgi?id=445139 --- Comment #6 from Kåre Särs --- Thanks for the trace... Strange that Skanlite works, but Skanpage crashes The backtrace shows that the actual crash is in the net backend in sane... The reason why it crashes is still a bit unclear... Could you install also the debug symbols for libsane (libsane-dbg) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445103] Allow build plugin to show terminal application output
https://bugs.kde.org/show_bug.cgi?id=445103 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- Hi, Thanks for the report. Unfortunately this would require a bit more work. The build plugin just reads the stdout and stderr of the application an does not do proper tty handling. As a workaround if you do not need the console output, you could run the application in konsole: konsole -e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 444883] Autocomplete / suggestion is very slow and insert random result once I hit ENTER
https://bugs.kde.org/show_bug.cgi?id=444883 --- Comment #11 from Kåre Särs --- @waqar Now that I want to reproduce it I have a hard time doing so... The last time I remember it happening I have a vague memory that the LSP plugin was re-highlighting at the same time as I was typing and selecting the completions... At least I can reproduce a quirk that if I type the beginning of a completion word, press arrow down to select it, and continue typing that same word, it will clear the selection (LSP + document backends)... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 444883] Autocomplete / suggestion is very slow and insert random result once I hit ENTER
https://bugs.kde.org/show_bug.cgi?id=444883 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #9 from Kåre Särs --- I have also noticed the problem (or related) in Kate. I have chosen to not auto-select the first suggestion and quite often, when I have pressed arrow down to select a completion, the selection is reset to nothing... Just as if a model-reset had been done -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 429260] Very slow UI
https://bugs.kde.org/show_bug.cgi?id=429260 Kåre Särs changed: What|Removed |Added Version Fixed In||KDE Gear 21.08.3 & KDE Gear ||21.12 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 429260] Very slow UI
https://bugs.kde.org/show_bug.cgi?id=429260 Kåre Särs changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/libksane/commit/04cf02 |hics/libksane/commit/2bdbe9 |49370b42ac7f9146a67b6545e68 |99808a225f1cfa10f10a4fcf09e |cb2e723 |45444e4 --- Comment #12 from Kåre Särs --- Git commit 2bdbe999808a225f1cfa10f10a4fcf09e45444e4 by Kåre Särs. Committed on 18/10/2021 at 15:17. Pushed by sars into branch 'release/21.08'. Naughty-list pixma network backend option polling The Pixma network backend behaves badly. polling a value will result in 1 second sleeps for every poll. The problem has been reported, but no easy/quick fix was available and the bug has been there for multiple years. Since this destroys the usability of the backend totally, we simply put the backend on the naughty list and disable the option polling. M +20 -9src/ksanecore_p.cpp M +1-0src/ksanecore_p.h https://invent.kde.org/graphics/libksane/commit/2bdbe999808a225f1cfa10f10a4fcf09e45444e4 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 429260] Very slow UI
https://bugs.kde.org/show_bug.cgi?id=429260 Kåre Särs changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/libksane/commit/04cf02 ||49370b42ac7f9146a67b6545e68 ||cb2e723 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Kåre Särs --- Git commit 04cf0249370b42ac7f9146a67b6545e68cb2e723 by Kåre Särs. Committed on 18/10/2021 at 14:29. Pushed by sars into branch 'master'. Naughty-list pixma network backend option polling The Pixma network backend behaves badly. polling a value will result in 1 second sleeps for every poll. The problem has been reported, but no easy/quick fix was available and the bug has been there for multiple years. Since this destroys the usability of the backend totally, we simply put the backend on the naughty list and disable the option polling. M +20 -9src/ksanecore_p.cpp M +1-0src/ksanecore_p.h https://invent.kde.org/graphics/libksane/commit/04cf0249370b42ac7f9146a67b6545e68cb2e723 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 429260] Very slow UI
https://bugs.kde.org/show_bug.cgi?id=429260 --- Comment #9 from Kåre Särs --- Note: We are _not_ disabling the backend, just the one feature of polling of the read-only options (like detecting a button being pressed on the scanner). Since Simple-scan does not seem to support that feature, it does not get bitten by it's problems either. Once this feature is disabled the scanning should be fine again. So basically we disable just that one feature that does not work. The new (sad) thing here is that this is the first time that we check what backend is in use, in stead of being generic. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405488] Wrong behaviour while previewing
https://bugs.kde.org/show_bug.cgi?id=405488 Kåre Särs changed: What|Removed |Added CC||gerhard.rie...@gmail.com --- Comment #8 from Kåre Särs --- *** Bug 417147 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 417147] Not possible to add a blank when markdown preview pane is open
https://bugs.kde.org/show_bug.cgi?id=417147 Kåre Särs changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Kåre Särs --- *** This bug has been marked as a duplicate of bug 405488 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443709] Not possible to enter numbers 1-6 while markdown preview is open
https://bugs.kde.org/show_bug.cgi?id=443709 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Kåre Särs --- This is a bit of a known issue the preview widget steals the key-presses... Try installing the markdownpart and ensure that it is preferred over the okular-kpart in file assosiations. *** This bug has been marked as a duplicate of bug 405488 *** -- You are receiving this mail because: You are watching all bug changes.
