https://bugs.kde.org/show_bug.cgi?id=482985
--- Comment #3 from Thomas Lübking ---
export LESS_TERMCAP_mb=$'\e[1;34m' # begin bold
export LESS_TERMCAP_md=$'\e[1;34m' # begin blink
export LESS_TERMCAP_so=$'\e[01;44;37m' # begin reverse video
export LESS_TERM
https://bugs.kde.org/show_bug.cgi?id=455632
--- Comment #11 from Thomas Lübking ---
That's trojita, same problem (likely) - network gone.
Alternatively outlook.office365 simply kicked you.
However, I'm out.
@Jan, if you've editing rights on the tracker, I'd appreciate i
https://bugs.kde.org/show_bug.cgi?id=455632
--- Comment #8 from Thomas Lübking ---
"Jans" software…
There's no doubt about where that dialog comes from. Just that it's not gonna
be the cause for the effect of an unstable network connection.
And there's a reasonable chan
https://bugs.kde.org/show_bug.cgi?id=455632
--- Comment #6 from Thomas Lübking ---
Don't full-quote the discussion, you're also exposing your email and private
address and phone number…
You might want to edit your posts accordingly.
On topic, this is likely backwards: Your con
https://bugs.kde.org/show_bug.cgi?id=447326
--- Comment #5 from Thomas Lübking ---
The problem is in gpg, but tests/Cryptography/keygen.sh has indeed
LD_PRELOAD=./libfake-dev-random.so ${GPG} --batch --quiet --gen-key
${SRCDIR}/tests/Cryptography/batch-keygen
which will likely trigger that
https://bugs.kde.org/show_bug.cgi?id=447326
--- Comment #3 from Thomas Lübking ---
https://dev.gnupg.org/T5444 but afaiu that's the SuSE build system and nothing
related to the built source (trojitá)?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=300349
--- Comment #2 from Thomas Lübking ---
Not a bug bug code deficiency that lead to clumsy client code as illustrated by
the patch in the (now 404) review link (was a fix by Martin to the desktop cube
effect)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=359467
--- Comment #6 from Thomas Lübking ---
No idea whether that's still reelvant, this "bug" discusses working around a
threading issue in Qt's X11 code that existed in 2016
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352234
--- Comment #2 from Thomas Lübking ---
No idea, the code layout changed and manage.cpp seems gone/moved.
Just grep the code of "&& false" if you want to know whether such stanza still
exists.
Since it completely deactivates the att
https://bugs.kde.org/show_bug.cgi?id=349190
--- Comment #2 from Thomas Lübking ---
Same situation as https://bugs.kde.org/show_bug.cgi?id=349191 - but on the
window manager side, not the desktop side.
It's a fringe bug, but spec violation.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=349191
--- Comment #3 from Thomas Lübking ---
Same problem, don't use KDE since years and this isn't a behavioral bug
description.
You can try whether it's still a problem by (i think - the original bug was on
a multiscreen layout and idk whet
https://bugs.kde.org/show_bug.cgi?id=344257
--- Comment #4 from Thomas Lübking ---
I stopped using KDE ~5 years ago and also haven't really looked at the kwin
code ever since then (this wasn't a user bug, I was heavily involved in kwin
development)
I would suggest to check whether
https://bugs.kde.org/show_bug.cgi?id=406034
--- Comment #2 from Thomas Lübking ---
https://bugs.kde.org/show_bug.cgi?id=344606
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399863
--- Comment #5 from Thomas Lübking ---
Smells like you'd have to trigger multiple sorts within one event cycle,
possibly due to some scheduled model sanitation at cycle starts/ends?
=> Try to limit the sorting to once per event cycle (eg. w/ a
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #10 from Thomas Lübking ---
The config is probably misleading, but I'm pretty sure gmail won't do STARTTLS
on 465 (you can wireshark what's going on)
I assume the issue at hand to be Qt w/o 1.3 support running into an
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #8 from Thomas Lübking ---
465 *is* SSL, you'll not use STARTTLS on it (no idea about the trojitá config
GUI suggesting something different?)
So this is a TLS version conflict (and 1.3 mess), can one see your distros
downstream patch
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #5 from Thomas Lübking ---
Looks like TLS/1.3 but Qt 5.12 should not even support that…
Do you use smtp on port 465 or port 587?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #149 from Thomas Lübking ---
Or maybe just read https://bugs.kde.org/show_bug.cgi?id=322060#c141 about the
nature of the "bug" and the state of the resolution ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391667
--- Comment #4 from Thomas Lübking ---
Jan.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391350
--- Comment #2 from Thomas Lübking ---
Thomas didn't use KDE for over 3 years...
Anyway, the actual bug is correctly identified and not at all related to kwin
(and only to a minor extent to kglobalaccel):
"Alt+Shift should only be triggerd
https://bugs.kde.org/show_bug.cgi?id=390452
--- Comment #5 from Thomas Lübking ---
The way the code looks, injecting
to the top of any html mail should do.
Otherwise the behavior seems intended. You can configure the default behavior,
but the webpage has the last word on this.
---
ceterum
https://bugs.kde.org/show_bug.cgi?id=390362
--- Comment #4 from Thomas Lübking ---
> I reported for the body text.
notify-send "bold summary" "bold body"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #141 from Thomas Lübking ---
As pointed out in the original report, this has *never* been about vsync
functionality per se.
The other yield methods (at that time, I dropped KDE for other reasons) caused
ridiculous CPU load (when
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #136 from Thomas Lübking ---
The full composition pipeline indirects rendering in the driver. It's implicit
when eg. xrandr scaling the output or so.
As for the "not what you said" comment, I focused on the "old wallpa
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #132 from Thomas Lübking ---
> and the time on the systray says "20:00", but the time now is 21:00
That's not what you said :-P
https://bugs.kde.org/show_bug.cgi?id=353983
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #128 from Thomas Lübking ---
> Plasma freezes for a moment and then all advanced graphics appear frozen.
Sounds just as if steam blocks/disables the compositor?
> My wallpaper even reverts back to some previous datetime's im
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #124 from Thomas Lübking ---
Impossible. nvidia and nouveau are incompatible on the kernel layer and act on
the same HW. It's no way near the optimus condition.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #122 from Thomas Lübking ---
Comment #120 sounds more like a client related issue anyway - resizing
(QtQuick) GL contexts is PITA - at least on nvidia but OPenGL wasn't drafted
for this behavior anyway.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=322060
--- Comment #119 from Thomas Lübking ---
Given that thanks to QtQuick OpenGL is now everywhere, shipping a global
environment snippet might be a good idea.
Otherwise see the initial posts on problems to setup libgl from kwin this way.
I'd ha
https://bugs.kde.org/show_bug.cgi?id=386351
Thomas Lübking changed:
What|Removed |Added
Resolution|DUPLICATE |DOWNSTREAM
--- Comment #4 from Thomas Lübking
https://bugs.kde.org/show_bug.cgi?id=386353
--- Comment #1 from Thomas Lübking ---
Try chaning src/Gui/Util.cpp to
const QString Css::warningBorder = QString::fromLatin1("border: 2px solid red;
background-color: #E7C575; color: black; padding: 5px; margin: 5px; text-align:
center;")
https://bugs.kde.org/show_bug.cgi?id=384761
--- Comment #1 from Thomas Lübking ---
Not reproducible here (you're aware that your Qt version is slightly dated?)
"Try to set other filter"
How in particular?
The backtrace sugests the removal of another (the last?) index, ie. do yo
https://bugs.kde.org/show_bug.cgi?id=378684
Thomas Lübking changed:
What|Removed |Added
CC||m...@riseup.net
--- Comment #5 from Thomas
https://bugs.kde.org/show_bug.cgi?id=383478
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=382160
--- Comment #2 from Thomas Lübking ---
Putting a ton of lineedits there makes the thing look terribly crowded (and
it's rather meant to be looked at)
How would you feel about altering the look of only the focused label? Like
passing it a
https://bugs.kde.org/show_bug.cgi?id=381799
--- Comment #3 from Thomas Lübking ---
"xwininfo | grep Depth" will likely reveal that it's not a 32bit drawable?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381461
--- Comment #12 from Thomas Lübking ---
Doesn't really knock out fluxbox, but once you pass focus to the "wrong"
dialog, they apparently start a race on the window focus and you cannot pass it
at will.
The reason seems to be clien
https://bugs.kde.org/show_bug.cgi?id=381461
--- Comment #3 from Thomas Lübking ---
"locks up the window manager hard"
This needs a better explanation on what actually happened.
It *might* be a stale mouse grab, caused by some accidental click-drag,
unreleased because trojita went un
https://bugs.kde.org/show_bug.cgi?id=379566
--- Comment #1 from Thomas Lübking ---
The background is that the original abook¹ has no actual XDG support (you can
pass a config and data file on start, but it only looks up ~/.abook by default)
Otherwise one would of course have used QSettings
https://bugs.kde.org/show_bug.cgi?id=371862
Thomas Lübking changed:
What|Removed |Added
CC||thomas.luebk...@gmail.com
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=378951
Thomas Lübking changed:
What|Removed |Added
CC||thomas.luebk...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=378951
--- Comment #4 from Thomas Lübking ---
This sounds as if the touch device (driver) fakes a pointer and this fails when
the touch device is passively grabbed?
xinput
lspci
lsusb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377382
--- Comment #14 from Thomas Lübking ---
ping?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377382
--- Comment #13 from Thomas Lübking ---
"another e-mail provider" will *certainly* not have lead to that very result,
you need to identify the "another e-mail provider" and share the error response
in order to get anywhere here.
-
https://bugs.kde.org/show_bug.cgi?id=377382
--- Comment #10 from Thomas Lübking ---
Evolution has OAUTH2 support - it's not exaclty proprietary (that wouldn't make
sense) but it's certainly far from unobjected, see
https://en.wikipedia.org/wiki/OAuth#Controversy
Leaving the comp
https://bugs.kde.org/show_bug.cgi?id=377382
--- Comment #7 from Thomas Lübking ---
Ok, again:
If you want trojitá (or mutt or ...) to work with gmail, go to the url that the
dialog links and follow the instructions. Trojiá will be able to log in
afterwards.
This requires either a setting
https://bugs.kde.org/show_bug.cgi?id=377382
--- Comment #5 from Thomas Lübking ---
Afaiu google uses OAUTH2 also to hand out different passwords per service, ie.
the authentication provided to you MUA won't let you access you playstore
account. (Yes, one could simply have different password
https://bugs.kde.org/show_bug.cgi?id=377382
--- Comment #2 from Thomas Lübking ---
Go to that URL and follow the instructions; gmail only permits OAUTH2 by
default, other credential systems are considered "insecure" and you need to
explicitly allow this.
Notice that "insecure&quo
https://bugs.kde.org/show_bug.cgi?id=360457
--- Comment #11 from Thomas Lübking ---
The page says that the clent shall wire down a "mini-me" representation to the
taskbar, could be a downscaled window or some specific information (like
pressing dates from a calendar application) or a
https://bugs.kde.org/show_bug.cgi?id=375143
--- Comment #6 from Thomas Lübking ---
> 23:40:28.743 >>> y20 IDLE␍␊
> 23:40:28.920 <<< + IDLE accepted, awaiting DONE command.␍␊
> 23:40:46.408 >>> DONE␍␊
> 23:40:46.409 >>> y21 UID STORE 4556 +FLAGS (\
https://bugs.kde.org/show_bug.cgi?id=375151
--- Comment #5 from Thomas Lübking ---
The 150 seconds looked too compelling :)
Please attach two or three more logs of connection breaks.
Then add "IDLE" to the extension blacklist and also elaborate on mentioned
possible network ins
https://bugs.kde.org/show_bug.cgi?id=375151
--- Comment #1 from Thomas Lübking ---
try lower the imap idle timeout to (apparently) "2" in the imap page of the
settings dialog.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374822
--- Comment #1 from Thomas Lübking ---
you're aware that it's an online query and will cause quite some traffic? (let
alone there's no realtime guarantee)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374798
--- Comment #2 from Thomas Lübking ---
"Freestyle", ie. allow to add custom menu items based on a filter, maybe.
On POSIX systems one would likely use wget or curl - trojita is no download
manager (nor does it provide one)
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=372168
--- Comment #19 from Thomas Lübking ---
The only™ reasonable way is to move the reply/delete/... buttons into the
messageview (window)
Otherwise, when more than one mail is opened, there's no strong indication
about mail the buttons will work on
https://bugs.kde.org/show_bug.cgi?id=372135
--- Comment #8 from Thomas Lübking ---
Personally, I'm out for the OPs manners.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372135
--- Comment #6 from Thomas Lübking ---
You're missing the point: the palsmashell theme should be able to override the
icon. The icon is not hardcoded since QSystemtrayIcon should really be using
SNI, by what only the icon name is transferred and
https://bugs.kde.org/show_bug.cgi?id=372135
--- Comment #4 from Thomas Lübking ---
QSystemTray icon should use SNI on plasma anyway (through QPA), but I'm not
sure in how far you can override the try icon with the theme (which would be
the one and only reasonable approach for it makes zero
https://bugs.kde.org/show_bug.cgi?id=369131
--- Comment #10 from Thomas Lübking ---
If it's not partial, the window would be shrunk (for no reason)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369131
--- Comment #8 from Thomas Lübking ---
> 1366x768+1920+432
^
I suppose this to be the troublemaker.
The window asks to be bigger than your screen (no hackish attempt to be
maximized) and your screen geometry
https://bugs.kde.org/show_bug.cgi?id=369131
Thomas Lübking changed:
What|Removed |Added
CC||thomas.luebk...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=369832
Thomas Lübking changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369130
--- Comment #1 from Thomas Lübking ---
One (or both) of the monitors will go to deep sleep or the kscreen daemon
detaches them, the workspace shrinks, kwin keeps them in sight but when the
screen gets re-added doesn't see requirement to reposition
https://bugs.kde.org/show_bug.cgi?id=369131
--- Comment #1 from Thomas Lübking ---
Please specify "the application" for KDE applications should restore geometry
"per screen" anyway and the client may reconfigure itself to that position
after mapping (ie. there're severa
https://bugs.kde.org/show_bug.cgi?id=368685
--- Comment #2 from Thomas Lübking ---
xdotool, and the forum says "slide conky off screen"
in that case, you just want to bind a kwin script that does this (and skip
shell and xdotool)
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=368003
--- Comment #1 from Thomas Lübking ---
> should match the outgoing message exactly, bite-wise
+100
> detect that we cannot submit our message in this way, remove the previously
> stored copy, upload a new one with no CTE: 8bit et al
Sound
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
CC||thomas.luebk...@gmail.com
--- Comment #67
https://bugs.kde.org/show_bug.cgi?id=367685
--- Comment #1 from Thomas Lübking ---
This belongs to either plasma-desktop (kickoff) or krunner. Maybe kglobalaccel
if some default binding is provided but certainly not kwin ;-)
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=367534
--- Comment #7 from Thomas Lübking ---
This is not a kwin bug, but please attach the output of glxinfo (to provide a
hint on why compositing may fail)
There's most likely a window (the dialog?) with uninitialized content which
also doesn't
https://bugs.kde.org/show_bug.cgi?id=367554
--- Comment #7 from Thomas Lübking ---
No. The role was originally handled lowercased in kwin. This was implicitly
changed by no more keeping the value internally but relying on the
kwindowsystem value. As a result, the rule now matches case
https://bugs.kde.org/show_bug.cgi?id=366742
--- Comment #8 from Thomas Lübking ---
Some static backtrace won't get you anywhere reg. CPU load - this would only
work if kwin would be trapped in an infinite loop.
Suspend the compositor (SHIFT+Alt+F12), run qbittorrent and watch remainin
https://bugs.kde.org/show_bug.cgi?id=367534
--- Comment #5 from Thomas Lübking ---
> Can you please post the output of:
> qdbus org.kde.KWin /KWin supportInformation
It doesn't actually look like the compositor is running at all (hard to say on
the particular setup, but the round
https://bugs.kde.org/show_bug.cgi?id=367554
Thomas Lübking changed:
What|Removed |Added
Summary|Special Window Settings |Special Window Settings are
https://bugs.kde.org/show_bug.cgi?id=367554
--- Comment #3 from Thomas Lübking ---
Smells related to bug #343709 - "mainwindow" is probably really "MainWindow" or
similar.
Please attach the ouput of "xprop" on a window you want to control this way.
--
You are re
https://bugs.kde.org/show_bug.cgi?id=348227
Thomas Lübking changed:
What|Removed |Added
CC|thomas.luebk...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=365918
--- Comment #14 from Thomas Lübking ---
Is rebooting required or does switching the compositor backend or restarting
kwin clear the stage as well?
You could disable the two effects but that would only provide negative
knowledge, of course (ie. if it
https://bugs.kde.org/show_bug.cgi?id=366794
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=358369
--- Comment #27 from Thomas Lübking ---
*** Bug 366794 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365918
--- Comment #12 from Thomas Lübking ---
The flicker is due to the re-used buffer, the question is why one of them is
invalid but for the newly exposed area and this seems to be related to window
decorations.
Let's start with the obvious: p
https://bugs.kde.org/show_bug.cgi?id=366742
--- Comment #2 from Thomas Lübking ---
> Xorg and kwin_x11
Smells like something (qbittorrent? plasmashell?) will cause massive repaints.
Suspend the compositor (SHIFT+Alt+F12) and check the remaining load on Xorg
plus whatever process else boils
https://bugs.kde.org/show_bug.cgi?id=366651
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=342326
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=365299
Thomas Lübking changed:
What|Removed |Added
Severity|major |normal
--- Comment #4 from Thomas Lübking
https://bugs.kde.org/show_bug.cgi?id=286146
--- Comment #62 from Thomas Lübking ---
Firefox in particular is unrelated to this bug since it doesn't use kxmlgui or
any KDE class.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366498
--- Comment #4 from Thomas Lübking ---
Can you please provide more log data, ideally all, but at least starting w/ the
matching SELECT call (ie ">>> y17" in *this* case, could be a differet tag in
another try)
The reply looks incompl
https://bugs.kde.org/show_bug.cgi?id=364633
--- Comment #13 from Thomas Lübking ---
Thanks for your efforts and sorry for the delay.
The only apparent pattern* is that they all seem to be quick tiled (at least it
looks like) so this really does seem to be the trigger.
As for myself, I'm
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||rosan...@lajt.hu
--- Comment #24 from Thomas
https://bugs.kde.org/show_bug.cgi?id=366126
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=351763
--- Comment #14 from Thomas Lübking ---
> I don't know if I am experiencing the same problem.
Please attach a backtrace*, otherwise one will never figure ;-)
* developer information tab in the crash dialog, the console output is
irrelev
https://bugs.kde.org/show_bug.cgi?id=366097
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||const.nekras...@gmail.com
--- Comment #23
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||kde.jr...@grifent.com
--- Comment #22 from
https://bugs.kde.org/show_bug.cgi?id=366096
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=366091
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=362531
Thomas Lübking changed:
What|Removed |Added
CC||Panagiotis.Kavalagios@eurod
https://bugs.kde.org/show_bug.cgi?id=366081
--- Comment #6 from Thomas Lübking ---
https://bugs.kde.org/show_bug.cgi?id=342716#c18
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||sami.lie...@iki.fi
--- Comment #21 from
https://bugs.kde.org/show_bug.cgi?id=366012
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=347495
Thomas Lübking changed:
What|Removed |Added
CC||guoyunhebr...@gmail.com
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=365964
Thomas Lübking changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|BACKTRACE
1 - 100 of 1508 matches
Mail list logo
