https://bugs.kde.org/show_bug.cgi?id=398326
--- Comment #6 from David Hurka ---
For me, NotoSans-Regular and NotoSans-Bold are used.
When I change /usr/share/fonts/truetype/noto/NotoSans-Regular.ttf to
Ubuntu-Regular, it looks equally wrong. When I change it to Tahoma-Regular, it
looks correct
https://bugs.kde.org/show_bug.cgi?id=398326
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=398326
--- Comment #4 from David Hurka ---
Well, I’ve just installed Tahoma and now it’s displayed fine.
My Okular action “About Backends” doesn’t work, but in aptitude I have
libpoppler 0.41.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=400189
--- Comment #1 from David Hurka ---
I only tried the PDF way. I can’t reproduce that on my system.
The properties window can not be resized down until it’s too small for all text
lines. When I force it to be smaller (titlebar -> rightclick -> s
https://bugs.kde.org/show_bug.cgi?id=400890
--- Comment #1 from David Hurka ---
Reproduced with:
Okular Version: 5.1.2
Operating System: KDE neon 5.13
KDE Plasma Version: 5.14.0
Qt Version: 5.11.1
KDE Frameworks Version: 5.50.0
Happens only with continuous mode on; but with different zooms
https://bugs.kde.org/show_bug.cgi?id=398606
--- Comment #4 from David Hurka ---
I think, powerful tools which are not well known from other PDF readers would
benefit.
For example: Trim to selection
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=342003
--- Comment #6 from David Hurka ---
Small hint if difficult to reproduce:
The trimmed margins must be large enough. If this is not the case in your PDF,
try to use "trim to selection" instead of "trim margins"
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=399467
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=141289
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=141289
--- Comment #11 from David Hurka ---
How about using dock panels for Thumbnails, Bookmarks, etc.? The dock panel
stack would have a tab bar at the bottom, and if no dock panel is shown, they
can be activated using toolbar buttons.
This way it would
https://bugs.kde.org/show_bug.cgi?id=399488
Bug ID: 399488
Summary: Move page bar to main toolbar by default
Product: okular
Version: unspecified
Platform: unspecified
OS: unspecified
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=398929
--- Comment #1 from David Hurka ---
Don't worry, other people are as clumsy as you.
I can't reproduce this behavior with Okular 1.5.1. But it sounds familar to me.
Which mouse button and which mode (browse, zoom, selection) do you use? Does
your
https://bugs.kde.org/show_bug.cgi?id=401098
--- Comment #1 from David Hurka ---
Reproduced on my machine. Apparently, Okular doesn't like itself...
Okular Version: 1.5.2
Operating System: KDE neon 5.13
KDE Plasma Version: 5.14.0
Qt Version: 5.11.1
KDE Frameworks Version: 5.50.0
--
You
https://bugs.kde.org/show_bug.cgi?id=403445
Bug ID: 403445
Summary: Explain purpose of filter text boxes in side panels
Product: okular
Version: 1.6.1
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=403486
--- Comment #5 from David Hurka ---
I see the problem, but an option to show/hide it at opening new documents would
not do it for me.
When I open an email attachment, I usually do not need the side bars. But when
I open a microcontroller datasheet, I
https://bugs.kde.org/show_bug.cgi?id=403486
--- Comment #9 from David Hurka ---
Maybe I understood you wrong, so I will try to clarify.
I thought you are talking about showing/hiding the Thumbnails/Contents Panel
when opening a new document, provided the Navigation Bar is already shown
https://bugs.kde.org/show_bug.cgi?id=402110
Bug ID: 402110
Summary: Table Selection should not pollute clipboard history
Product: okular
Version: unspecified
Platform: Other
OS: unspecified
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=169516
--- Comment #52 from David Hurka ---
I would like it if the zoom is not remembered per document, because I usually
read datasheets, zoom into one small detail, and close the datasheet. The next
time I open it, I always have to zoom out.
Dolphin has
https://bugs.kde.org/show_bug.cgi?id=401944
--- Comment #1 from David Hurka ---
I'm sure this is not an okular bug, because it also happens with pdftotext.
pdftotext related to poppler, so it might be a poppler bug.
$ pdftotext /tmp/OkularBug.pdf
$ cat /tmp/OkularBug.txt
Listing 1: Skript um
https://bugs.kde.org/show_bug.cgi?id=401329
--- Comment #1 from David Hurka ---
This layout is the same as in most other KDE applications, and I think it's
fine.
I personally can't imagine whether another order is easier to understand. A
simple test might be invoking okular with "o
https://bugs.kde.org/show_bug.cgi?id=398731
--- Comment #4 from David Hurka ---
(In reply to RJVB from comment #3)
> The offending commit: cc8b2208
That's what I was searching for for a long time, before I opened this report.
(I did grep -r "Search Wrapped", but without success.)
https://bugs.kde.org/show_bug.cgi?id=401269
--- Comment #1 from David Hurka ---
There was KGestures once (or still is?), which used libstroke.
gschem still uses libstroke. It claims, that it can detect when you are trying
to draw an 'E' as gesture, but even struggles at detecting a 'D'. I had
https://bugs.kde.org/show_bug.cgi?id=401268
--- Comment #1 from David Hurka ---
With my okular, the width is correct while drawing. It's just not antialiased,
and it flashes once when the line is finished.
Okular Version: 1.5.2
Operating System: KDE neon 5.13
KDE Plasma Version: 5.14.0
Qt
https://bugs.kde.org/show_bug.cgi?id=398731
--- Comment #9 from David Hurka ---
Under normal use: very rarely.
It was very convenient for these database summary files, to compare the first
and the last entry of the same thing. I didn't install updates on that machine,
to keep the corner
https://bugs.kde.org/show_bug.cgi?id=398731
--- Comment #7 from David Hurka ---
With this patch the messages still queue, when you jump forward and back fast
enough.
However, in my opinion the messages may do anything, unless they are in the
middle of the screen...
(In reply to RJVB from
https://bugs.kde.org/show_bug.cgi?id=401329
--- Comment #5 from David Hurka ---
(In reply to Nate Graham from comment #2)
> Not all KDE apps use this layout; Konsole for example has Previous before
> Next.
Not really, the buttons change when you deselect "Search Backwards".
K
https://bugs.kde.org/show_bug.cgi?id=401509
Bug ID: 401509
Summary: Autocompletion doesn't complete incomplete
uppercase-snake-style words
Product: kate
Version: unspecified
Platform: unspecified
OS: All
https://bugs.kde.org/show_bug.cgi?id=401509
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=401441
--- Comment #1 from David Hurka ---
When I try to suspend, my computer reboots instead... When I lock and unlock
the screen, Okular behaves as expected.
As you use the word "slide" and mention the popping-up menu: Do you mean
"Pr
https://bugs.kde.org/show_bug.cgi?id=398605
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=398731
Bug ID: 398731
Summary: Search wrapped info message at wrong position
Product: kate
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=398731
David Hurka changed:
What|Removed |Added
Platform|Other |Neon Packages
Version|unspecified
https://bugs.kde.org/show_bug.cgi?id=398731
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=403486
--- Comment #8 from David Hurka ---
Created attachment 117615
--> https://bugs.kde.org/attachment.cgi?id=117615=edit
Words used by David
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406313
Bug ID: 406313
Summary: Neon installer crashed while partitioning:
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=404803
--- Comment #5 from David Hurka ---
This dates back to... long ago?
There are basically these commits (and probably others) which introduced this
message (KMessageWidget *Okular::Part::m_migrationMessage):
commit
https://bugs.kde.org/show_bug.cgi?id=405542
--- Comment #3 from David Hurka ---
(In reply to Oliver Sander from comment #2)
> Anyone for replacing double clicks by single clicks here?
In general, me. But currently, every stroke becomes a new annotation.
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=405435
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=405435
Bug ID: 405435
Summary: In Open Recent menu, underscores in filenames become
accelerators
Product: kate
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=405280
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=405280
Bug ID: 405280
Summary: Wish: Dropping text on the line number border should
insert at the beginning of that line.
Product: kate
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=403997
--- Comment #2 from David Hurka ---
(In reply to Ahmad Samir from comment #1)
> it could well be that it's not case sensitivity that's causing the
> issue, but rather it's sorting by opening order.
No, it’s case sensitivity. The shortcuts na
https://bugs.kde.org/show_bug.cgi?id=403997
Bug ID: 403997
Summary: Documents panel sorts case insensitive and Projects
panel sorts case sensitive, so Previous/Next Document
navigates different than expected
Product: kate
https://bugs.kde.org/show_bug.cgi?id=403997
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=293402
--- Comment #7 from David Hurka ---
Just discovered these rich-text buttons, and wanted to suggest exactly this:
(In reply to Travis Evans from comment #2)
> making them match the configured text foreground color
> (which the user would presumab
https://bugs.kde.org/show_bug.cgi?id=293402
--- Comment #6 from David Hurka ---
Created attachment 118017
--> https://bugs.kde.org/attachment.cgi?id=118017=edit
Invisible buttons in sticky note
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403902
--- Comment #4 from David Hurka ---
I am now ready to confirm that the .spx file causes the crash. Meanwhile I got
other .spx files, and since I did the following command, baloo does not crash
anymore.
balooctl config add excludeFilters *.spx
--
You
https://bugs.kde.org/show_bug.cgi?id=403943
--- Comment #4 from David Hurka ---
(In reply to Albert Astals Cid from comment #3)
> Adobe Reader [...]
Ah, that is why PDFs are deployed with such excessive whitespace in the TOC.
Then Okular should probably not silently remove the whitesp
https://bugs.kde.org/show_bug.cgi?id=403943
--- Comment #2 from David Hurka ---
I see that this makes it easier to read a document (sometimes).
It makes sense to preserve the true contents of a document (e. g. to test some
LaTeX output), but it would be nice to have this as option, similar
https://bugs.kde.org/show_bug.cgi?id=403975
Bug ID: 403975
Summary: Background color for text selection in the document
should be configurabe, instead of relying on system
color scheme
Product: okular
Version:
https://bugs.kde.org/show_bug.cgi?id=403976
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=403976
Bug ID: 403976
Summary: Message viewer: Lines starting with | (pipe symbol)
incorrectly shown as quoted lines
Product: kmail2
Version: unspecified
Platform: Neon Packages
https://bugs.kde.org/show_bug.cgi?id=403902
--- Comment #10 from David Hurka ---
I have created sum[i=1; 4](26^i) = 475254 files with the same content as the
problematic .spx file. The file indexer crashes only at .spx (although *.spx is
in the excludeFilter)
.
$ balooctl index Test
https://bugs.kde.org/show_bug.cgi?id=403755
--- Comment #1 from David Hurka ---
Wow... Confirmed with:
Okular 1.6.1
KDE Neon 5.14 (Ubuntu 18.04)
KDE Frameworks 5.54
Qt 5.11.2
Poppler 0.62
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403782
--- Comment #5 from David Hurka ---
avlas' use case is (similar to)
1. clicking a PDF link in a web browser -> opens in Okular
2. wanting to keep the PDF file
3. clicking Save As (because Save obiously doesn't work)
Then avlas wants Save As to sugg
https://bugs.kde.org/show_bug.cgi?id=403782
--- Comment #6 from David Hurka ---
I thought a bit about this.
(In reply to David Hurka from comment #5)
> Better would be
> [_] If document URL is non-writable [...]
This could be confusing, if URLs randomly appear to be non-writable.
Also,
https://bugs.kde.org/show_bug.cgi?id=403902
Bug ID: 403902
Summary: Since I named an XML file .spx, Baloo crashes at every
login
Product: frameworks-baloo
Version: 5.54.0
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=403902
David Hurka changed:
What|Removed |Added
CC||david.hu...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=403943
Bug ID: 403943
Summary: Entries in table of contents should be normalized
(whitespace stripped)
Product: okular
Version: 1.6.1
Platform: unspecified
OS:
https://bugs.kde.org/show_bug.cgi?id=384267
--- Comment #14 from David Hurka ---
(In reply to Albert Astals Cid from comment #1)
> No, that solution doesn't work, because people that use dark themes (where
> selection is usually a white-ish color) would not see the selection when
> rea
https://bugs.kde.org/show_bug.cgi?id=407988
--- Comment #1 from David Hurka ---
Already tried this?
https://bugs.kde.org/show_bug.cgi?id=407731#c5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #5 from David Hurka ---
Just discovered a class FileKeeper, which should do this.
Added in commit 6531398b919e58def8c6ba4711d20ea517147189, eleven years ago.
Just grep for #ifdef OKULAR_KEEP_FILE_OPEN
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=407884
David Hurka changed:
What|Removed |Added
Summary|Previous/Next Bookmark |Previous/Next Bookmark
|don’t
https://bugs.kde.org/show_bug.cgi?id=407884
--- Comment #2 from David Hurka ---
So it’s intended that they don’t do what the menu says, but do what the menu
would say if invoked another way?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407731
--- Comment #13 from David Hurka ---
The firefox nssdb is used to verify that the digital signatures are
"cryptografically valid", whatever *exactly* that means, I guess?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408222
--- Comment #3 from David Hurka ---
Created attachment 120507
--> https://bugs.kde.org/attachment.cgi?id=120507=edit
Page 188 in Okular
A friend just told me that this is readable.
However, how does it look different in Evince? It uses the s
https://bugs.kde.org/show_bug.cgi?id=408222
--- Comment #10 from David Hurka ---
Created attachment 120580
--> https://bugs.kde.org/attachment.cgi?id=120580=edit
Pixels
Using Albert’s screenshot, one could say that Evince and Okular draw slightly
different. Indeed, where the arrow poi
https://bugs.kde.org/show_bug.cgi?id=408273
--- Comment #1 from David Hurka ---
See also the discussion about these new scaling options. (Pointing to one
comment explaining the issue.)
https://phabricator.kde.org/D7962#339567
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=408316
Bug ID: 408316
Summary: In Window Decorations -> Buttons, it’s hard to
rearrange buttons
Product: kwin
Version: 5.15.5
Platform: Neon Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=407438
--- Comment #2 from David Hurka ---
(In reply to Lukas Jelinek from comment #0)
> EXPECTED RESULT
> All text are rendered as with text hinting disabled.
May I ask how the hinting works for the rendered texts?
I enabled hinting in my Okular, an
https://bugs.kde.org/show_bug.cgi?id=334297
--- Comment #4 from David Hurka ---
(In reply to David Hurka from comment #3)
> Seems like Okular passes the wrong RegularAreaRect to the highlighter tool,
> a RegularAreaRect that somehow got the page rotation applied.
Experimented
https://bugs.kde.org/show_bug.cgi?id=332117
--- Comment #8 from David Hurka ---
Is this fixed with the new “Typewriter” annotation tool now?
These are Typewriter annotations:
(In reply to avlas from comment #0)
> - transparent background (but not necessarily text as well, as opacity d
https://bugs.kde.org/show_bug.cgi?id=408272
--- Comment #8 from David Hurka ---
(In reply to Nate Graham from comment #4)
> - Make the scaling combobox more visible and prominent so it's easier to
> notice and change
Additionally to that, could there be a graphic next to the combobox to e
https://bugs.kde.org/show_bug.cgi?id=408544
--- Comment #2 from David Hurka ---
Thought about that, but all 4 bugs seem to be mostly the same to me. PageView
doesn’t care about what should get Escape, but cancels “what it likes to
cancel”.
Should I really open 4 different bug reports?
--
You
https://bugs.kde.org/show_bug.cgi?id=407869
--- Comment #4 from David Hurka ---
I have just looked at PageView event handling. It implements several scrolling
commands trough the event system, and not trough action shortcuts. That is why
you can still type all the letters, although PageView uses
https://bugs.kde.org/show_bug.cgi?id=368598
David Hurka changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=342003
David Hurka changed:
What|Removed |Added
CC||poltro...@gmail.com
--- Comment #10 from David
https://bugs.kde.org/show_bug.cgi?id=342003
David Hurka changed:
What|Removed |Added
CC||zakhar.nasi...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=407583
--- Comment #1 from David Hurka ---
Is this duplicate of 402017? It does not mention editing, but KDirWatch
probably doesn’t care about it. And usually, editing means deleting the file
and writing a slightly different file with the same path.
--
You
https://bugs.kde.org/show_bug.cgi?id=391352
David Hurka changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=334297
David Hurka changed:
What|Removed |Added
CC||luca.tagliaco...@fqa.ub.edu
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=407865
David Hurka changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=186531
--- Comment #24 from David Hurka ---
Works fine with Okular 1.7.2.
Even after both changing color mode and restarting Okular.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=342003
--- Comment #12 from David Hurka ---
Also reproducible with Trim to Selection, supporting the investigation of
jimbo1qaz.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408495
Bug ID: 408495
Summary: Trim to Selection does not work when the view is
rotated
Product: okular
Version: 1.7.2
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=384700
--- Comment #8 from David Hurka ---
(In reply to kadlecf from comment #2)
> I can confirm a similar behavior in okular 1.2.3 in OpenSUSE Tumbleweed.
> This concerns various shortcuts as "Selection tool", "Fit Width",
> &quo
https://bugs.kde.org/show_bug.cgi?id=408496
Bug ID: 408496
Summary: Magnifier tool makes the document scroll infinitely.
Product: okular
Version: 1.7.2
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=330643
--- Comment #1 from David Hurka ---
Confirmed with Okular 1.7.2.
It’s simple: Every tab is a Part, and when changing the view mode in a Part, it
is written to the configuration file. (Only the viewport position is stored
per-document.)
Trim margins
https://bugs.kde.org/show_bug.cgi?id=408918
--- Comment #1 from David Hurka ---
You reported a fact, and it doesn’t seem noteworthy to me so far.
If you think this is a bug, or that something should be changed, you will need
to provide the EXPECTED RESULTS section. Otherwise someone
https://bugs.kde.org/show_bug.cgi?id=408918
--- Comment #3 from David Hurka ---
I still don’t understand what exactly should be different.
But could you describe a situation in which scaling scrolling is helpful, and
what is making problems while the user tries to complete a task?
E. g
https://bugs.kde.org/show_bug.cgi?id=408918
--- Comment #5 from David Hurka ---
So you want the scroll speed multiplied by the zoom factor?
I don’t think that’s possible, because it would make scrolling virtually
uncontrollable at high zoom levels. I also don’t see a reason why scrolling
should
https://bugs.kde.org/show_bug.cgi?id=409082
Bug ID: 409082
Summary: Icon request: View layout icons for Okular: Single
Page, Facing Pages, Facing Pages (First Page
Centered), Overview
Product: Breeze
Version:
https://bugs.kde.org/show_bug.cgi?id=155563
--- Comment #7 from David Hurka ---
(In reply to Henrik Fehlauer from comment #3)
> There are two ways we could improve usability regarding text selection:
> - Make the "Text Selection Tool" the default choice for the button in the
&
https://bugs.kde.org/show_bug.cgi?id=408222
--- Comment #21 from David Hurka ---
(In reply to Tobias Deiminger from comment #20)
> But that impression is subjective, can we try to
> quantize a bit what "better" means? E.g., we could measure "densitiy of
> black" in
https://bugs.kde.org/show_bug.cgi?id=185636
--- Comment #9 from David Hurka ---
Created attachment 120708
--> https://bugs.kde.org/attachment.cgi?id=120708=edit
Print options for page set
This seems to be fixed now.
KDE Frameworks 5.58
Qt 5.12.0
Okular 1.7.1
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=398108
David Hurka changed:
What|Removed |Added
Summary|Annoying switch from Browse |Annotation toolbar works
https://bugs.kde.org/show_bug.cgi?id=408511
--- Comment #1 from David Hurka ---
Hi,
I thought this is a duplicate of some other bug, but don’t find it now.
I already thought about this, see https://phabricator.kde.org/D21195
Maybe continuing work soon.
A night mode would probably be Invert
https://bugs.kde.org/show_bug.cgi?id=408544
Bug ID: 408544
Summary: Pressing Escape does not cancel operations correctly.
Product: okular
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=407217
--- Comment #6 from David Hurka ---
(Maybe it’s better to just dump everything besides the left Change Colors
button.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407217
--- Comment #5 from David Hurka ---
Created attachment 119987
--> https://bugs.kde.org/attachment.cgi?id=119987=edit
Screenshot of new Change Colors menu
I have secretly created an interesting patch which introduces a new Change
Colors menu.
W
1 - 100 of 851 matches
Mail list logo
