https://bugs.kde.org/show_bug.cgi?id=375861
Bug ID: 375861
Summary: Korganizer crashed after message "ksmserver could not
be started"
Product: korgac
Version: 5.4.1
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=315488
--- Comment #39 from Kai Krakow <k...@kaishome.de> ---
So maybe this should be reopened? Although some of the discussion points into
the wrong direction by saying that explicitly ungrouping applications is the
same - but that is not true.
https://bugs.kde.org/show_bug.cgi?id=315488
--- Comment #44 from Kai Krakow <k...@kaishome.de> ---
Okay, works... Gentoo backported some patches to 5.8.3 which didn't compile, I
reverted back to the previous patch level with this patch included and now it
works.
What I am missing is c
https://bugs.kde.org/show_bug.cgi?id=315488
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
CC||k...@kaishome.de
--- C
https://bugs.kde.org/show_bug.cgi?id=348812
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
CC|k...@kaishome.de |
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=377588
--- Comment #4 from Kai Krakow <k...@kaishome.de> ---
Well, it's sort of a multi monitor system. Indeed, it has two monitors always
attached.
The first one is my standard PC monitor for working with the system (via DVI).
The second one is
https://bugs.kde.org/show_bug.cgi?id=377588
--- Comment #2 from Kai Krakow <k...@kaishome.de> ---
Created attachment 104624
--> https://bugs.kde.org/attachment.cgi?id=104624=edit
affected config file
Sure, here it is...
I didn't try to reproduce it reliably but it seems that t
https://bugs.kde.org/show_bug.cgi?id=377588
Bug ID: 377588
Summary: plasma panels not shown after reboot
Product: plasmashell
Version: 5.9.3
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=361521
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
CC||k...@kaishome.de
--- C
https://bugs.kde.org/show_bug.cgi?id=379420
Bug ID: 379420
Summary: showPhoto crashed after resize
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=390260
Bug ID: 390260
Summary: akonadi-ews-resource segfault
Product: Akonadi
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=343931
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=332227
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UNMAINTAINED
https://bugs.kde.org/show_bug.cgi?id=324808
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=390260
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
Platform|Other |Gentoo Packages
-
https://bugs.kde.org/show_bug.cgi?id=368870
Kai Krakow <k...@kaishome.de> changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=390261
--- Comment #1 from Kai Krakow <k...@kaishome.de> ---
Related dmesg entry:
[ 6342.923363] kdeconnectd[31138]: segfault at 10 ip 7ff6dc9f1b67 sp
7fff939cef00 error 4 in kdeconnect_notifications.so[7ff6dc9eb000+1b000]
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=390261
Bug ID: 390261
Summary: kdeconnectd notifications crash once in a while
Product: kdeconnect
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=390260
--- Comment #1 from Kai Krakow <k...@kaishome.de> ---
The crash seems to be in KF5:
[ 166.432091] akonadi_ews_res[3018]: segfault at 8 ip 7f4f39a9489b sp
7fff069ee290 error 4 in libKF5ConfigCore.so.5.42.0[7f4f39a51000+61000]
$ equery
https://bugs.kde.org/show_bug.cgi?id=375951
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=390261
--- Comment #3 from Kai Krakow <k...@kaishome.de> ---
(In reply to Nicolas Fella from comment #2)
> Two questions:
> Which version of KIO are you running?
$ equery l kde-frameworks/kio
* Searching for kio in kde-frameworks ...
[I
https://bugs.kde.org/show_bug.cgi?id=375951
--- Comment #14 from Kai Krakow ---
I'd like to see that various window contents could be moved to the title bar.
E.g. a video player could put player controls there (pause, play, restart,
volume) as buttons. Applications like video players should have
https://bugs.kde.org/show_bug.cgi?id=287582
Kai Krakow changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=343651
Kai Krakow changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=390260
--- Comment #3 from Kai Krakow ---
I removed Akonadi completely because it started to accumulate gigabytes of RAM
over time since one of the last updates (the processes growing to 9 GB of RAM
usage). And there's even not a sane mail client to actually
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #3 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #5 from Kai Krakow ---
@Martin
Yes, you're right. Let's keep this nice and tidy. Let's see how a solution
works out. I'll then look into maybe opening new issues or looking into the
source code to suggest a patch.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=412005
Bug ID: 412005
Summary: Konsole crashes when trying to paste (long texts) from
clipboard
Product: konsole
Version: 19.08.1
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #8 from Kai Krakow ---
Created attachment 122919
--> https://bugs.kde.org/attachment.cgi?id=122919=edit
Experimental: Reduce mmap by one magnitude
This patch reduces the memory map size for LMDB by one order of magnitude (16
inst
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #9 from Kai Krakow ---
Here's more evidence of why LMDB may be a particularly bad choice for the
workload applied by baloo: It is btree organized, and writing and maintaining
btrees will result in a lot of random I/O. At some point in time
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #7 from Kai Krakow ---
Created attachment 122918
--> https://bugs.kde.org/attachment.cgi?id=122918=edit
Reduce stack pressure
This patch reduces pressure on the used stack size by looping instead of
recursively calling itself w
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #18 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #16)
> I bet I can just compile baloo via kdesrc. Does it have many dependencies on
> KF libraries? I do not like to break my system at this point in time and it
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #12 from Kai Krakow ---
Created attachment 122927
--> https://bugs.kde.org/attachment.cgi?id=122927=edit
Don't fsync the file-system
Let's not stress the system with fsync() after each DB transaction. This
database can be easily rebu
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #17 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #15)
> Kai, thank you very much for your work on this! About an alternative to
> LMDB… I am not sure at the moment. Will think about it.
Currently with my p
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #13 from Kai Krakow ---
I've added some patches to my experimental patchset after crunching through
some of the documentation and articles available. The system responsiveness has
improved a lot. Can anyone confirm that these patches help
https://bugs.kde.org/show_bug.cgi?id=356357
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #14 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #11 from Kai Krakow ---
Created attachment 122926
--> https://bugs.kde.org/attachment.cgi?id=122926=edit
Disable read-ahead of mmap access
We should not read-ahead when accessing the database because it may introduce
thrashing during
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #10 from Kai Krakow ---
Created attachment 122925
--> https://bugs.kde.org/attachment.cgi?id=122925=edit
Prepare simpler coding of environment flags
This simply prepares the following patches and introduces no functional change.
--
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #14 from Kai Krakow ---
Meanwhile, my patched indexer started content indexing phase. I also added back
all the expensive directories I excluded previously. It's currently indexing
with a mixed R/W workload of up to 200 MB/s (most time 50
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #19 from Kai Krakow ---
After testing this a few days, with my patches it works flawlessly: No
performance impact, krunner finds result immediately without thrashing the HDD,
etc. That is, until you reboot: While with the patches it has
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=356357
Kai Krakow changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #21 from Kai Krakow ---
@Martin
I think your bug report is already really about this issue: Re-indexing all
files over and over again and consuming a lot of memory and IO that way.
The performance aspects of this are already covered
https://bugs.kde.org/show_bug.cgi?id=400704
Kai Krakow changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #23 from Kai Krakow ---
I'll have a look at that soon. First I'd like to get the "Reduce stack
pressure" patch upstreamed (also as a learning curve because this is my first
KDE contribution). I've uploaded it to Phabricator a
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #25 from Kai Krakow ---
Yes, that's my plan. But I'd like to refine them a bit first. Especially
turning fsync() off seems to involve a big controversy discussion about whether
this should be done or not. So I will research the side effects
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
Attachment #122918|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #33 from Kai Krakow ---
Also, LMDB is totally the wrong tool when using 32-bit systems because your
index cannot grow beyond a certain size before crashing baloo.
I'm not sure if 32-bit systems are still a thing
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #36 from Kai Krakow ---
Oh, nice... Sometimes it helps to talk about a few things.
I could think of the following solution:
Add another UUID->CounterID mapping table to the database, that is easy to
achieve. Everytime we encounter a
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #32 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #30)
> I believe this bug is at
> least about two or three independent issues, but as you told, let's have it
> about the re-indexing files thing. I bet ge
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #31 from Kai Krakow ---
As far as I understand from researching the discussions in phabricator, this
problem won't be easy to fix as it is baked into the design decision that
defined the database scheme.
Based on the fact that the DocId
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #38 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #35)
> I like the idea to use one DB per filesystem. This way you can save the
> complete filesystem UUID and/or other identifying information *once* and use
> th
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
Attachment #122925|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #29 from Kai Krakow ---
During the re-index job after reboot, baloo shows very strange behavior when
evaluating the indexSize:
$ balooctl indexSize
File Size: 6,83 GiB
Used: 25,48 MiB
PostingDB: 1.018,96 MiB 3998.360
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #28 from Kai Krakow ---
(In reply to Kai Krakow from comment #19)
> After testing this a few days, with my patches it works flawlessly: No
> performance impact, krunner finds result immediately without thrashing the
>
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #40 from Kai Krakow ---
Further research confirms: btrfs has unstable device ids because it exposes
subvolumes as virtual block devices without their own device node in /dev.
Thus, device id numbers are allocated dynamically at runtime from
https://bugs.kde.org/show_bug.cgi?id=415286
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #10 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=420030
Bug ID: 420030
Summary: Konsole crashed after creating a new profile
Product: konsole
Version: 19.12.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=421131
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #9 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=375951
--- Comment #38 from Kai Krakow ---
(In reply to Adam from comment #34)
> I would love to see LIM. Having the two bars is a waste of space imo.
>
> I tried with the menu button before, but then you don't see which menus are
&g
https://bugs.kde.org/show_bug.cgi?id=364947
Kai Krakow changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UNMAINTAINED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=377588
--- Comment #6 from Kai Krakow ---
I can still reproduce it on a real 2-monitor system at work: After an update to
Plasma 5.20, one panel was gone, the other moved over to the second monitor.
When I switch between Wayland session and X11 session, I
https://bugs.kde.org/show_bug.cgi?id=422282
--- Comment #19 from Kai Krakow ---
Following up on my original report https://bugs.kde.org/show_bug.cgi?id=428770:
When the problem occurs, I usually see every folder entry duplicated. I only
observed that in folder tree mode when expanding the tree
https://bugs.kde.org/show_bug.cgi?id=428770
Bug ID: 428770
Summary: Dolphin crashed when browsing cifs mounts
Product: dolphin
Version: 20.08.2
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #11 from Kai Krakow ---
BTW: It's not only the mouse cursor lagging, key presses are also simply not
detected. And this even happens with a low average CPU load if you just have
some processes stuck in IO for a few ms: I was thinking I'm
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #14 from Kai Krakow ---
I'd say that "loss of input events" should be actionable... (reported in
comment #11) I don't care if mouse lags behind a little bit or jumps during CPU
spikes, this also happens using X11. But it also l
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #22 from Kai Krakow ---
(In reply to tagwerk19 from comment #20)
> (In reply to Kai Krakow from comment #18)
> > ... I suggest to
> > read that entirely to understand the problem ...
> I've done my best :-) Than
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #19 from Kai Krakow ---
BTW: Such a UUID-to-deviceId mapping table would allow baloo to properly
support most yet unsupported filesystems, probably also zfs. With such an idea
implemented, the only requirement left to a supported filesystem
https://bugs.kde.org/show_bug.cgi?id=402154
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #18 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=435444
Bug ID: 435444
Summary: bluetooth is constantly scanning for services /
devices
Product: Bluedevil
Version: 5.21.3
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=435444
--- Comment #1 from Kai Krakow ---
Killing kdeconnectd seems to stop this behavior.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435444
Kai Krakow changed:
What|Removed |Added
Version|5.21.3 |5.21.4
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=435444
--- Comment #3 from Kai Krakow ---
Are there instruction on how to properly create a dbus monitor log?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=441077
Bug ID: 441077
Summary: Plasmashell panels may freeze, usually unrelated but
unresponsive NFS/SMB mounts are involved
Product: plasmashell
Version: 5.21.5
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #1 from Kai Krakow ---
Created attachment 140791
--> https://bugs.kde.org/attachment.cgi?id=140791=edit
thread apply all bt full
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #7 from Kai Krakow ---
(In reply to Nate Graham from comment #5)
> That's what kio-fuse was meant to solve. Do you have it installed?
Ah ok, didn't know how it worked - and it was eventually kicked from the system
previously by s
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #9 from Kai Krakow ---
I'm not sure how that could even work.
(a) it runs from a different session context, it's running from systemd system
service while kio-fuse is a user session dbus service
(b) this would imply that I could use `ls
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #10 from Kai Krakow ---
OTOH, I could try migrating to a borg client/server model instead of opening
the repository via filesystem directly. This also decouples some security
concerns as the borg service limits access patterns to those
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #4 from Kai Krakow ---
(In reply to Nate Graham from comment #2)
> In general, this is why KIO exists: to provide asynchronous, non-blocking
> access to flaky network resources. When you bypass KIO and mount them
> directly, you'r
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #5 from Kai Krakow ---
It worked for a few days in a row. But yesterday evening and today morning,
this happened again and the behavior is quite random:
This time, only the top panel moved to the wrong screen while the bottom panel
stood
https://bugs.kde.org/show_bug.cgi?id=453554
Kai Krakow changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=453554
Kai Krakow changed:
What|Removed |Added
Version Fixed In|5.25|
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #9 from Kai Krakow ---
Created attachment 150180
--> https://bugs.kde.org/attachment.cgi?id=150180=edit
configuration completely doesn't match the output
Here's an example of messed up content:
As you can see, the panels over
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #6 from Kai Krakow ---
Okay, so I'm now on Plasma 5.25 and this original issue seems fixed.
But now, when I turn the monitor back on, the background image of that monitor
is gone and completely black. I also cannot right click
https://bugs.kde.org/show_bug.cgi?id=356727
--- Comment #76 from Kai Krakow ---
(In reply to Nate Graham from comment #75)
> As a result it would
> probably be best if people who are still affected could file new bug
> reports, and I will try my best to triage them accordingly. Thanks!
https://bugs.kde.org/show_bug.cgi?id=453554
Bug ID: 453554
Summary: turning one monitor off kills the panel configuration
of the second monitor
Product: plasmashell
Version: 5.24.5
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #3 from Kai Krakow ---
(In reply to Marco Martin from comment #1)
> are all outputs connected to the internal videocard or there are external DP
> dongles involved?
No dongles but there is one DP-to-HDMI cable. Not sure if that
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #4 from Kai Krakow ---
Also, Plasma version is probably not the only thing that changed. The nvidia
driver was also updated at least once, and Xorg components were also updated at
least once. But I cannot really pin-point that to one
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #33 from Kai Krakow ---
(In reply to Iyán Méndez Veiga from comment #32)
> Plasma 5.25.90 has a new issue and it's really unstable and difficult to
> replicate. Every morning when I connect the laptop to the docking station I
> hav
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #27 from Kai Krakow ---
We probably need a system which stores a containment layout per number of
monitors connecting. If an additional monitor gets connected, clone the next
"lower count" layout. Then, sort the prima
https://bugs.kde.org/show_bug.cgi?id=412005
Kai Krakow changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #409 from Kai Krakow ---
(In reply to Nate Graham from comment #408)
> This bug report is only about Plasma panels moving, not windows. That's a
> different issue.
Except it may be not... I'm seeing a similar behavior: Usually, w
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #37 from Kai Krakow ---
(In reply to Nate Graham from comment #35)
> Unfortunately this is exactly right. [...]
> The current system needs to be thrown away and replaced with
> something better-engineered from the sta
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #77 from Kai Krakow ---
For me it seems to be fixed or at least works as expected after I disabled the
kscreen service in the system settings. With each plasma updates, the behavior
seems to change in random and unpredictable ways
https://bugs.kde.org/show_bug.cgi?id=141267
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #22 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=450301
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #12 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=469279
Bug ID: 469279
Summary: Running akonadi servers easily doubles or triples VRAM
usage
Classification: Frameworks and Libraries
Product: Akonadi
Version: 5.23.0
Platform:
https://bugs.kde.org/show_bug.cgi?id=469279
--- Comment #1 from Kai Krakow ---
BTW: Running "kcmshell5 qtquicksettings" and forcing software rendering for
plasma completely eliminates the issue (with Xorg staying really low on VRAM)
but then plasma loudly complains about non-optimal
https://bugs.kde.org/show_bug.cgi?id=469281
Bug ID: 469281
Summary: windows with background blur (e.g., konsole) flicker
and leave mouse trails
Classification: Plasma
Product: kwin
Version: 5.27.4
Platform: Gentoo
1 - 100 of 128 matches
Mail list logo