[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #4 from Manuel Geißer --- Created attachment 143624 --> https://bugs.kde.org/attachment.cgi?id=143624&action=edit Update log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #3 from Manuel Geißer --- By the way, the purple description background is really strange. That's only on X, not on Wayland, though. Is this on purpose, or should I file a separate issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #2 from Manuel Geißer --- Same problem on X - I have made you a screencast. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #1 from Manuel Geißer --- Created attachment 143622 --> https://bugs.kde.org/attachment.cgi?id=143622&action=edit Screencast -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Manuel Geißer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] New: Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Bug ID: 445587 Summary: Response to mouse clicks broken Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY Since today's kde/qt updates, the Overview effect does not respond to mouse clicks anymore. (This used to work correctly prior to the update.) STEPS TO REPRODUCE 1. Trigger the Overview effect (e. g. using active corner or shortcut) 2. (Left-)click on the area of a window OBSERVED RESULT Nothing happens. EXPECTED RESULT The effect should be closed and the clicked window should be shown. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Might be Wayland-only. I haven't used X since a longer time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 --- Comment #23 from Manuel Geißer --- > Present Windows effect is what is causing the issue here. Disabled it and I > can > see the background once again. Wow, good catch! Disabling Present Windows indeed solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #95 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Well, actually that turns out to be wrong. It got released today (that is, in KDE Neon). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #93 from Manuel Geißer --- > What do you mean? Nate said the effect is being shipped with Plasma 5.23 > though > it "may" (which I guess is now "will") not replace it until later. Is this > wrong? The problem we're talking about is that it will take even longer for this usability issue to be fixed, due to Plasma 5.23 getting additional months of polishing and QA. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #91 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Yeah, if developers had acknowledged what an annoyance this dimming is, they could just have commented out the problematic line and release an updated package nine years ago, or they could have merged PR 885 five months ago... It appears that fixing usability issues is just regarded as an unimportant side-effect of the Present Windows replacement; primarily it's just the move to a different underlying technology. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 --- Comment #4 from Manuel Geißer --- I think this is perhaps rather an issue with Qt(-Wayland) than with Kate -- A question: Is it possible to deactivate completition, or dismiss the completition history as a workaround? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #27 from Manuel Geißer --- Sure. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #25 from Manuel Geißer --- Created attachment 142205 --> https://bugs.kde.org/attachment.cgi?id=142205&action=edit (unrelated) okular-mupdf-backend build error -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #24 from Manuel Geißer --- So I installed the dependencies and tried to build okular-mupdf-backend (from git master), but it fails with some "Variable not declared in this scope" error. Also there have been no commits to the repository since a year. Is this backend still functional? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #23 from Manuel Geißer --- I guess you are referring to https://invent.kde.org/sandsmark/okular-mupdf-backend ? The thing is, there are multiple unofficial Okular MuPDF generators around... Moreover, why is this not officially part of Okular and not packaged in Debian, Ubuntu, and KDE Neon? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #21 from Manuel Geißer --- `grep -r mupdf` on the Okular source tree doesn't find anything, either -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #20 from Manuel Geißer --- > There is also a muPDF backend for Okular. Did you try that? Is this at all still current? I checked out okular from https://invent.kde.org/graphics/okular.git and built with CMake, but couldn't find any hints on a MuPDF backend. `ls generators/` only shows ``` chm CMakeLists.txt comicbook djvu dvi epub fax fictionbook kimgio markdown mobipocket plucker poppler spectre tiff txt xps ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #21 from Manuel Geißer --- Switching the compositing method does not affect the bug in any way. I already tried that long ago... I rather thought in the direction of a damaged configuration file issue. I've already had that a few times. If it were random rendering glitches, I would also suspect the graphics driver, but the issue with transparent instead of black background is so systematic that this seems kind of unlikely to me. However, I will file a bug with the graphics developer when I have time. I also thought of reinstalling the system at some point and see whether that fixes some of my impossible-to-reproduce issues. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #19 from Manuel Geißer --- Not sure whether the driver really is the cause. Yes, it may be possible, but I think you shouldn't rule out a cause in Plasma or Qt without further investigation. I'd rather not consider this issue resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 442900] New: [Feature request] Optional reStructuredText syntax highlighting for inline Python documentation
https://bugs.kde.org/show_bug.cgi?id=442900 Bug ID: 442900 Summary: [Feature request] Optional reStructuredText syntax highlighting for inline Python documentation Product: frameworks-syntax-highlighting Version: 5.86.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- SUMMARY Many Python projects use inline code documentation with sphinx-autodoc, since this is a lot less maintenance work than separate code documentation. This way, it is much easier to keep code and docs consistent, especially as method parameter headers are generated automatically. STEPS TO REPRODUCE 1. Open a Python file with inline Sphinx reStructuredText documentation in Kate OBSERVED RESULT The Python code is syntax-highlighted. The inline rst markup is not highlighted, however. EXPECTED RESULT It would be nice to have optional rst syntax highlighting for inline code documentation indicated with `""" documentation text here """`. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-36-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7.2 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Perhaps this idea is a bit far-fetched and/or hard to implement, so this is really just a suggestion. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #19 from Manuel Geißer --- > There is also a muPDF backend for Okular. Did you try that? The Ubuntu Focal mupdf package currently fails to open the file (https://bugs.launchpad.net/ubuntu/+source/mupdf/+bug/1943366). This likely is fixed in newer versions of mupdf or affects the MuPDF GUI only, though. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #18 from Manuel Geißer --- > I think it might be better if the Okular developers would report to Poppler, > since I never used the Poppler library interface myself and thus don't have > the > required background. I now filed an issue at Poppler nevertheless, as nobody else seems to have felt any responsibility to do so. The report essentially just references this thread, as it should contain all relevant information. https://gitlab.freedesktop.org/poppler/poppler/-/issues/1139 @OkularDevelopers: Please verify/confirm whether changing pageSize() and pageSizeF() would really be sufficient to fix the UserUnit issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #17 from Manuel Geißer --- > I think you should report at PDFium, pdf.js, Poppler, and pikepdf. I think it might be better if the Okular developers would report to Poppler, since I never used the Poppler library interface myself and thus don't have the required background. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #16 from Manuel Geißer --- > I think you should report at PDFium, pdf.js, Poppler, and pikepdf. Be careful - there are considerable differences between these libraries. I don't really know about pdf.js and PDFium, but pikepdf is quite low-level and does not provide a function to obtain page size on its own - this needs to be done downstream using CropBox/MediaBox, UserUnit, and Rotate. > There is also a muPDF backend for Okular. Did you try that? `mutool info > userunit_10.pdf` reports `[ 0 0 17856 17856 ]`. Yes, I am aware that MuPDF directly takes /UserUnit into account. I noticed this during the tests for my lib (which also has a (Py)MuPDF rendering backend). How do I obtain the MuPDF backend for Okular, though? Is it possible that KDE Neon does not provide it? (I already have the okular-extra-backends package installed...) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #15 from Manuel Geißer --- >From the referenced code we can see that Okular uses the Poppler::Page::pageSizeF() function to obtain the page size: https://poppler.freedesktop.org/api/qt5/classPoppler_1_1Page.html#a598c287971839a113552176fc387ab30 This function is based on CropBox and returns points. What about the following solution: - the pageSize() and pageSizeF() functions should be changed to take /UserUnit into account, as the docs suggest the returned value is always given in 1/72in units - Additionally there should be some way to obtain the /UserUnit value with poppler. I couldn't find any such option in the documentation, though I only skimmed it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #13 from Manuel Geißer --- Another possibly relevant code passage: https://github.com/KDE/okular/blob/3a513f34b8bbba87bd96718dc96089e079578d55/generators/poppler/generator_pdf.cpp#L1303 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #12 from Manuel Geißer --- I've searched a bit in the code, and at least the rendering proportions issue is Okular's fault I think: https://github.com/KDE/okular/blob/3a513f34b8bbba87bd96718dc96089e079578d55/generators/poppler/generator_pdf.cpp#L721 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #11 from Manuel Geißer --- Pdfinfo from poppler-utils does not show regular units like centimetres or inches, but it keeps the PDF points. Pdfinfo is a low-level tool that does not perform unit conversion on its own. However, it does not display the UserUnit value, so you could say it's somewhat wrong in the sense that it withholds information. So to judge who is at fault, it would be relevant to know how Okular obtains the displayed page size. Does it inspect CropBox/MediaBox and convert to units itself, or does it retrieve finished unit values from Poppler? In the first case, the source of the bug would be in Okular, in the second case it would be in Poppler. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #9 from Manuel Geißer --- Sorry. I just thought you'd be the maintainer of Okular, and wondered why you are not in the CC list, but apparently this has its reason. Sorry, really. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #7 from Manuel Geißer --- Created attachment 141456 --> https://bugs.kde.org/attachment.cgi?id=141456&action=edit adobe_reader ... only Adobe Reader gets the proportions right -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #6 from Manuel Geißer --- List of other affected PDF software: * Chromium integrated PDF viewer (uses PDFium) * Firefox integrated PDF viewer (uses pdf.js) * Inkscape PDF importer (uses Poppler) * Scribus PDF importer * PDFStitcher (uses pikepdf) * PDF Arranger (uses pikepdf) * even the proprietary Master PDF Editor 4 and 5 Probably more ... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added Summary|Okular does not take|Okular does not take |/UserUnit into account |/UserUnit into account |(page size incorrect) |(page size incorrect for ||certain files) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #5 from Manuel Geißer ---
Created attachment 141455
--> https://bugs.kde.org/attachment.cgi?id=141455&action=edit
Proportions pdf
For you to confirm the UserUnit is set on the first page of the document in the
screenshot, but not on the other pages.
```python3
>>> from tests_pdfnodegraph.pathtools import TestOutput
>>> pdf = pikepdf.open(join(TestOutput,'out_14.pdf'))
>>> page = pdf.pages[0]
>>> page.UserUnit
Decimal('10.0')
>>> page_2 = pdf.pages[1]
>>> page_2.UserUnit
Traceback (most recent call last):
File "", line 1, in
File "/home/manuel/.local/lib/python3.8/site-packages/pikepdf/_methods.py",
line 1143, in __getattr__
return getattr(self.obj, name)
AttributeError: /UserUnit
>>>
```
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #4 from Manuel Geißer --- > the space reserved for rendering the actual page or better formulated: the proportions of different pages to each other -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #3 from Manuel Geißer --- To clarify, I think it is not only the displayed size number that is incorrect, but also the space reserved for rendering the actual page: The screenshot I just added illustrates it better: The first page is from the userunit_10 file. The other 2 pages are ANSI A and A4 size, which is very roughly 200mm width - put one of the smaller pages three times next to each other, and it approximately matches the width of the larger page, although in fact it should be a lot larger - roughly thirty times the width of the smaller page! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #2 from Manuel Geißer --- Created attachment 141454 --> https://bugs.kde.org/attachment.cgi?id=141454&action=edit userunit_screenshot -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #1 from Manuel Geißer ---
Python shell code to reproduce (replace TestFiles.userunit_10 with the path
string where you saved the file, and skip the first import which depends on
custom test infrastructure of the lib I am developing):
```python3
Python 3.8.10 (default, Jun 2 2021, 10:49:15)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from tests_pdfnodegraph.testfiles import TestFiles
>>> import pikepdf
>>> pdf = pikepdf.Pdf.open(TestFiles.userunit_10)
>>> page = pdf.pages[0]
>>> page.MediaBox
pikepdf.Array([ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'),
Decimal('1785.6') ])
>>> page.UserUnit
Decimal('10.0')
>>> 1785.6 * 1/72 * 25.4
629.91998
>>> 1785.6*10 * 1/72 * 25.4
6299.2
```
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 --- Comment #1 from Manuel Geißer --- Ping. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added CC||aa...@kde.org, ||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] New: Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
Bug ID: 442280
Summary: Okular does not take /UserUnit into account (page size
incorrect)
Product: okular
Version: 21.08.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: PDF backend
Assignee: okular-de...@kde.org
Reporter: geisse...@gmail.com
Target Milestone: ---
Created attachment 141453
--> https://bugs.kde.org/attachment.cgi?id=141453&action=edit
userunit_10.pdf
SUMMARY
[PDF background]
In the PDF format, coordinates are given in PDF points, where by default 1
point is equivalent to 1/72 of an inch (1in -> 2.54cm). However, PDFs can
define custom units on a per-page basis, using the /UserUnit key.
/UserUnit is a float or decimal that scales the default conversion fraction of
1/72, so for a /UserUnit of 10, 1pt would mean 10/72in.
[What Okular does]
It seems that Okular (like many other open-source PDF software) does not take
/UserUnit into account for the displayed page size.
The attached test document `userunit_10.pdf` defines a /UserUnit of 10.
The document's /MediaBox looks like this:
```python3
[ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'), Decimal('1785.6')
```
Now the default conversion with 1pt -> 1/72in returns 630x630mm, which is what
Okular displays. However, this is incorrect. In reality, the size is 6300mm, 10
times larger!
(In particular, /UserUnit is used by Adobe Illustrator and possibly other PDF
software to circumvent the maximum number of 14400pt imposed by Adobe Reader
and some other PDF renderers.)
STEPS TO REPRODUCE
1. Open the attached file in Okular
2. Go to File -> Properties
3. See the displayed page size
4. Inspect the document with the pikepdf python library, or and other PDF
library of your choice
5. Print the /MediaBox and /UserUnit of page 0
OBSERVED RESULT
Displayed page size is too small by factor 10.
EXPECTED RESULT
Displayed page size should always reflect the real page size and take /UserUnit
into account.
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-34-generic (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 --- Comment #2 from Manuel Geißer --- It is "regression from earlier on wayland". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Manuel Geißer changed: What|Removed |Added CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Manuel Geißer changed: What|Removed |Added Keywords||regression, wayland CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] New: [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Bug ID: 442226 Summary: [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions Product: kate Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- Created attachment 141422 --> https://bugs.kde.org/attachment.cgi?id=141422&action=edit Pop-up window SUMMARY When typing in a string into either of the "Search" or "Replace" fields, there are sometimes strange floating windows instead of a dropdown menu for completition propositions. These windows are rather annoying, because they steal focus from the text input field. Then I usually press ESC with the intention to get rid of the pop-up, but instead it closes the search/replace plugin... I think this issue affects Wayland only. STEPS TO REPRODUCE 1. Open Kate 2. Open the "Search and Replace" plugin 3. Type in a string into the "Search" or "Replace" field 4. Keep editing the text until the bug occurs. OBSERVED RESULT Sometimes a separate, centered pop-up window appears instead of a dropdown menu. EXPECTED RESULT There should never be pop-ups for this. It should always be a dropdown menu. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-34-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 --- Comment #4 from Manuel Geißer --- Thanks for the help! I'm rather new to KDevelop and haven't unraveled its full capabilities yet. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 --- Comment #2 from Manuel Geißer --- Aha, thank you! I only searched the settings and the plugin, but overlooked the project configuration. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027 --- Comment #3 from Manuel Geißer --- Thanks for the response. Unfortunately I can't contribute to KDevelop myself, as I only know Python an no C++. I'm currently learning PySide2 but my Qt skills are still very limited. I also don't have the time to get my feet wet on a new software project at the moment... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] New: [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Bug ID: 442029 Summary: [Feature request] Add file exclude options for quick open Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: QuickOpen Assignee: kdevelop-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY Quick open is a useful feature. However, I am missing an option to exclude certain directories or file extensions. For example, my repository contains Sphinx documentation, and quick open also shows all documentation build artifacts. This can be quite problematic: If I have a file named `api.rst`, building the docs would also generate an artifact named `api.rst.txt`. Now it could happen that you accidentally open and edit the `.txt` file which has the same content as the `.rst` equivalent, but it will be overwritten with the next build cycle and all changes are lost. So it would be quite helpful to be able to exclude the build directory from quick open, not only to prevent inadvertently opening the wrong file, but also to get a cleaner overview. My quick open panel is often spammed with compiled objects. STEPS TO REPRODUCE 1. Clone a repository that contains Sphinx documentation 2. Import it into KDevelop 3. Build the documentation (`make html`) 4. Trigger quick open OBSERVED RESULT All documentation build artifacts will show up. EXPECTED RESULT Only relevant project files should be displayed. Therefore, an option in the settings would be required to exclude certain file types or directories. (Alternatively, though more complex, it could also be possible to read the .gitignore file and not show objects that aren't part of the revision control, but as KDevelop also supports versioning systems other than git this might not be a straightforward solution.) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Since KDevelop is a large application, the option I am requesting might already exist at some hidden place. If so, please point me at it and forgive the false issue :) -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027 --- Comment #1 from Manuel Geißer --- outside f-string*s -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] New: Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027
Bug ID: 442027
Summary: Variables inside f-strings are not highlighted and not
recognised for renaming
Product: kdev-python
Version: 5.6.2
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: geisse...@gmail.com
Target Milestone: ---
SUMMARY
In Python 3.6 f-strings got introduced. They're a simple and well-readable way
to include variables in messages. If a string is preceded with an f character,
variables can be stated inside curly brackets and will automatically get
formatted as a string.
Example:
```python3
x0 = 5
y0 = 20
multiplied = x0 * y0
message = f"Position: ({x0}, {y0}); multiplied {multiplied}"
```
There are lots of nice guides concerning f-string, e. g.
https://www.geeksforgeeks.org/formatted-string-literals-f-strings-python/
Variables inside the f-string curly brackets are apparently not recognised by
KDevelop. There is no syntax highlighting for these variables and they are also
not considered for renaming operations. Renaming either of `x0` or `y0` in the
above example would ignore the occurrence inside the f-string.
This is a likely cause for UnboundLocalErrors: The user renames the variable,
clicks on KDevelop's auto-rename feature and thinks all variables are replaced,
but suddenly the code crashes at f-string formatting becaues the old variable
name is still there.
STEPS TO REPRODUCE
1. Paste any f-string code into KDevelop, for instance the above example. Save
the file for highligthing and semantic analysis to get active.
2. Rename a variable, e. g. `x0` to `xpos`
3. Use the auto-rename feature
OBSERVED RESULT
- Variables inside f-strings are not highlighted
- While all occurrences of a variable outside f-string are replaced properly,
the occurrences inside f-string curly brackets are ignored.
EXPECTED RESULT
- Variables should always be highlighted, also inside f-strings
- Renaming operations should also replace occurrences of the variable in
f-strings
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-27-generic (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
/
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 442012] [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=442012 --- Comment #2 from Manuel Geißer --- At first I was a bit puzzled by this issue because stopping syntax highlighting first gave me the impression that there was a fault in my code. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 442012] [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=442012 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #1 from Manuel Geißer --- Created attachment 141295 --> https://bugs.kde.org/attachment.cgi?id=141295&action=edit Without `*,` syntax -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 442012] New: [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=442012 Bug ID: 442012 Summary: [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting Product: frameworks-syntax-highlighting Version: 5.85.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- Created attachment 141294 --> https://bugs.kde.org/attachment.cgi?id=141294&action=edit With *, syntax SUMMARY Since Python 3, one can enforce the use of keyword arguments in method definitions. This ensures that downstream code is proof against possible future changes to the order of positional arguments. All arguments from a `*,` onwards need to be preceeded with explicit keywords (cf. https://www.vegardstikbakke.com/python-keyword-only/). However, this syntax seems to partly break KDevelop's Python syntax highlighting, with default arguments following the `*,` not being recognised/highlighted anymore. Example: ```python3 import os class Backend: AUTO = None def run( info, tempdir, *, backend = Backend.AUTO, n_processes = os.cpu_count()+1, n_chunks = 1, scaling = 1, cache_name = 'cache', verbose = True, ): pass ``` STEPS TO REPRODUCE 1. Paste a Python code using the keyword-only enforcing `*,` into KDevelop, for instance the above example. 2. Save it as $SOME_FILENAME.py for syntax highlighting to get active. 3. Remove the `*,` and see how syntax highlighting changes OBSERVED RESULT Default arguments after `*,` are not highlighted. Without `*,` they are. EXPECTED RESULT Default arguments should always be highlighted correctly, regardless of whether there is a `*,` or not. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Maybe this is rather a problem with KDevelop than with the syntax highlighting framework. If you think so, feel free to move the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #27 from Manuel Geißer --- One thing I've learned now: Before judging a software project, look at how developers act in its bug tracker. Then you will find out whether they are friendly or unfriendly, competent or incompetent people. Man muß den Bären in seiner Höhle gesehen haben, bevor man ein Urteil über ihn abgeben kann. And yes, you are officially allowed to mark this as spam if you really want to display yourself in the way you do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 Manuel Geißer changed: What|Removed |Added CC|geisse...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #28 from Manuel Geißer --- > I'd be quite interested in the scorcher Martin Keary alias Tantacrul would > give > you if he ever tested Present Windows or Overview... Ah, I really can't wait for that scorcher... I need to contact Martin and ask him whether he wants to do it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #26 from Manuel Geißer --- I don't imply bad faith (you seem to do though?). This was merely something I noticed. And you just confirmed that what I consider usability issues is indeed all intentional. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #24 from Manuel Geißer --- Created attachment 141270 --> https://bugs.kde.org/attachment.cgi?id=141270&action=edit Just in case anyone wants to enframe this conversation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 Manuel Geißer changed: What|Removed |Added CC|geisse...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #23 from Manuel Geißer --- Okay, hiding my comments as spam - really? Anyway, I think I have expressed my POV clearly and said everything that I consider relevant. This conversations is now a waste of time. If you ever happen to change your mind, feel free to notify me directly via e-mail. I'm demonstratively leaving this conversation now. As a last remark, I'd be quite interested in the scorcher Martin Keary alias Tantacrul would give you if he ever tested Present Windows or Overview... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #21 from Manuel Geißer --- Clarification to self about the Present Windows issues: No one of ever wanted to fix them, it was all intentional. Surely devs as capable as Nate, Vlad or David could have commented out the dimming and all the other annoyances in less than a minute. The intent behind Overview never was to fix usability issues, it's just the shift to a different underlying technology. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #20 from Manuel Geißer --- > everyone thinks they're right Some give meaningful reasons, others don't. > I am trying to help you be effective here. I care about correct and comprehensible decisions, not necessarily about being effective. And there is no need to mock. Your comment is a bit of a bad joke, honestly. > than writing clearly ineffective walls of argumentative text. In other words, you don't care about logical reasons, you probably don't even bother to read them. > or even submitting a merge request to implement it. If it were Python I might help, but I do not know any C++ nor QML. I currently don't have the time and interest to learn these programming languages. Plasma is your project, not mine. I'm just an advisory capacity :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #18 from Manuel Geißer --- (In reply to Nate Graham from comment #14) > 2. Thew more we argue, the less likely it is that we will agree on anything > as we become more entrenched in our original positions. I generally prefer good opposition to bad compromises. And from looking at the code, it gets clear that this can't be called a compromise at all. Just as in Present Windows, the icons/labels will be (over-)large and centered (and, as a disimprovement, not even optional): ```qml width: PlasmaCore.Units.iconSizes.large horizontalAlignment: Text.AlignHCenter verticalAlignment: Text.AlignVCenter ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #17 from Manuel Geißer --- (In reply to Nate Graham from comment #14) > Two things are clear: > > 1. People use this effect in different ways based on what's most comfortable > for them; one size does not fit all. > 2. The more we argue, the less likely it is that we will agree on anything > as we become more entrenched in our original positions. This is much more about logic and UI usability considerations than about taste. I'd like to repeat that no other operating system or desktop environment overlays centered icons / captions. From a usability perspective they're rubbish, and any trained UI expert will most probably tell you so. I have already outlined clear reasons in support of this position in my previous comments, none of which have been responded to with substantive counter-arguments (likely because there are no such). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #16 from Manuel Geißer --- Oh, so to my bad luck this mis-feature got addded. And it seems it's not even optional. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #13 from Manuel Geißer --- too difficult *to identify pardon -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #12 from Manuel Geißer --- Well, obviously I disagree very much. > Without relatively big icons, the whole overview effect will become useless > for me. *With* icons it becomes useless. The purpose of an overview effect is to quickly recognise open applications by their content, by what they look like. Icons don't tell you anything about what the window is for, what work you want to do in there. Icons don't help at all to get an overview, to see what is going on in different windows. > my first search is for the icon, the second one is for the miniature If the icon/text overlay is over-large / centered, it gets too difficult identify and memorise the content, which is the primary purpose of Overview. Icons-based app management is already available with the task bar. Icons are used just about everywhere and I tend to find them disgusting because they usually have very little logical connection to what the app actually does. > So if the new overview effect lacked of those, IT WOULD BE A MAJOR REGRESSION > and you would get flowed with bug reports, at least from persons who use > overview effect. To be clear, removing these annoying overlays would be an IMPROVEMENT and a nice step towards clean, usable code without non-features. > If I see only miniatures and I can't filter out anything, it's like a > spinning carousel and I can't make heads of tails of what I see. It takes too > long to recognize anything, and the whole effect would be useless. Absolutely not. With the visual pattern the whole window makes up, it's very nice to identify, and you can see what is going on inside the window, compare windows, watch windows simultaneously, etc. In contrast, icons are way too generic. Overview is about *specific open windows*, not about the app in general. > So the icons are a must, even with multiple instances. No. Really no. They just make it harder to distinguish multiple instances and hide relevant content. They're nothing more than an annoyance. > Will the current options be upheld in the new version? I see no reasons why > wouldn't they be. Believe me, I see many, many good reasons. > Also, the current default icons+titles is a reasonable one IMO. I would rather think about whether it is worth the effort being implemented at all (especially with Overview being in such an early beta stage), but most clearly icons+titles shouln't be the default. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441673] Build qt5-image-formats-plugins with JP2 support
https://bugs.kde.org/show_bug.cgi?id=441673 --- Comment #13 from Manuel Geißer --- I just installed the two packages. Works perfectly in Gwenview and Dolphin now :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441673] Build qt5-image-formats-plugins with JP2 support
https://bugs.kde.org/show_bug.cgi?id=441673 --- Comment #12 from Manuel Geißer --- Whoah, that was quick. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441673] Build qt5-image-formats-plugins with JP2 support
https://bugs.kde.org/show_bug.cgi?id=441673 --- Comment #9 from Manuel Geißer --- What exactly are the concerns about JasPer? As of 2021, it is actively maintained by the original author Michael Adams. There have been 8 releases this year, and the previous week's git history is full of commits. And JasPer seems to be fairly popular, too. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441673] Build qt5-image-formats-plugins with JP2 support
https://bugs.kde.org/show_bug.cgi?id=441673 Manuel Geißer changed: What|Removed |Added Summary|Add support for JPEG2000|Build |JP2 images |qt5-image-formats-plugins ||with JP2 support -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441673] Add support for JPEG2000 JP2 images
https://bugs.kde.org/show_bug.cgi?id=441673 Manuel Geißer changed: What|Removed |Added Component|general |Packages User Edition Version|21.08.0 |unspecified Product|gwenview|neon Platform|Other |Neon Packages CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Assignee|gwenview-bugs-n...@kde.org |neon-b...@kde.org --- Comment #8 from Manuel Geißer --- Thanks for these very helpful hints. Indeed, KDE Neon seem to have built qt5-image-formats-plugins without JP2 support. libqjp2.so is not present in the plugins directory. The image-related JasPer is not in Ubuntu/Neon, instead only [this jasper package](https://packages.ubuntu.com/focal/jasper), which had confused me first. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #451 from Manuel Geißer --- > LXDE works well, the communication with the developers is excellent, but the > performance is not optimal Probably off-topic, anyway: The performance of LXDE is brilliant, it's the desktop environment that even runs smoothly on our old Raspberry Pi 2B (one of those small ARM devices). One could say that LXDE is a bit spartan, but that's probably necessary to acheive such a high level of responsiveness, and in my opinion it provides all relevant features. - Maybe you rather meant XFCE? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 --- Comment #14 from Manuel Geißer --- To be frank, there is absolutely no need for bossing me around. I am doing a lot of bug reporting and I know how to deal with it. All relevant information has reached you, probably even faster than a new report would have been. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 --- Comment #13 from Manuel Geißer --- Comment 11: -1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 Manuel Geißer changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441673] Add support for JPEG2000 JP2 images
https://bugs.kde.org/show_bug.cgi?id=441673 --- Comment #5 from Manuel Geißer --- The Krita issue just got fixed (see https://invent.kde.org/graphics/krita/-/commit/542dcd306e236ec776a81e389d0a601387739e48) Maybe the cause is similar for Gwenview and Dolphin? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 --- Comment #10 from Manuel Geißer --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 --- Comment #8 from Manuel Geißer --- > but maybe there is something in particular with the file The file is valid and loads correctly with any other JP2-supporting program, so this is unlikely. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 --- Comment #7 from Manuel Geißer --- > jpeg2000 support is in krita since 4.3.0 using the library openJPEG. I do have libopenjp2-7 installed. Does this hint at a packaging issue? (The Krita build is from Neon User edition.) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 183903] cannot display JPEG2000 images (image/jp2)
https://bugs.kde.org/show_bug.cgi?id=183903 --- Comment #4 from Manuel Geißer --- Ok -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441673] Add support for JPEG2000 JP2 images
https://bugs.kde.org/show_bug.cgi?id=441673 --- Comment #4 from Manuel Geißer --- > It works for me though on Arch Linux If it works on Arch, then maybe we should move the issue to Neon User issues? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439480] Google accounts can't be added
https://bugs.kde.org/show_bug.cgi?id=439480 --- Comment #3 from Manuel Geißer --- > Can't help here, I don't use KMail myself. Okay, thanks anyway :) Is KMail unmaintained? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 Manuel Geißer changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #6 from Manuel Geißer --- Please do not randomly mark bugs as fixed when they aren't. I see no need whatsoever to open a new report. Bug 441673 contains all relevant information. I don't have eternal amounts of time and this is just a formality. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441673] Add support for JPEG2000 JP2 images
https://bugs.kde.org/show_bug.cgi?id=441673 Manuel Geißer changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Manuel Geißer --- qt5-imageformats and libopenjp2-7 are both installed jasper has nothing to do with JP2 images, it's a package for configuring ext2/3. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 --- Comment #4 from Manuel Geißer --- Created attachment 141116 --> https://bugs.kde.org/attachment.cgi?id=141116&action=edit Opening JP2 fails -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 208578] Add support for jp2 / Jpeg 2000
https://bugs.kde.org/show_bug.cgi?id=208578 Manuel Geißer changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #3 from Manuel Geißer --- I quickly reopened this bug on the fly when actually filing an issue at Gwenview (Bug 441673). Information on platform, affected files etc. can all be found in this report (I forgot to link it, sorry). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 Manuel Geißer changed: What|Removed |Added CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] New: Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 Bug ID: 441676 Summary: Resizing the left panel is jerky Product: okular Version: 21.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY In case you haven't noticed yet, resizing the left panel of Okular (which contains preview images, annotations, bookmarks, the outline, and layers) is super laggy since quite some time, I believe at least since two stable releases. STEPS TO REPRODUCE 1. Open Okular, ideally with a PDF file. 2. Expand the left panel (F7), in case it is currently hidden 3. Try to resize the panel. OBSERVED RESULT Resizing the panel is jerky. EXPECTED RESULT The panel should resize smoothly, like any other panel does. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7.2 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION I'm surprised that apparently no one has noticed the issue yet? It's super obvious. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441675] Right part of File Assosications page is cropped off on smaller monitors
https://bugs.kde.org/show_bug.cgi?id=441675 --- Comment #3 from Manuel Geißer --- Another workaround is to call `kcmshell5 filetypes` directly, rather than using it in the system settings wrapper. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441675] Right part of File Assosications page is cropped off on smaller monitors
https://bugs.kde.org/show_bug.cgi?id=441675 --- Comment #2 from Manuel Geißer --- Created attachment 141110 --> https://bugs.kde.org/attachment.cgi?id=141110&action=edit Buttons visible (manually extended window size) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441675] Right part of File Assosications page is cropped off on smaller monitors
https://bugs.kde.org/show_bug.cgi?id=441675 --- Comment #1 from Manuel Geißer --- Created attachment 141109 --> https://bugs.kde.org/attachment.cgi?id=141109&action=edit Buttons not visible (fullscreen) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441675] Right part of File Assosications page is cropped off on smaller monitors
https://bugs.kde.org/show_bug.cgi?id=441675 Manuel Geißer changed: What|Removed |Added Version|unspecified |5.22.4 CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
