https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #2 from Shmerl ---
(In reply to Martin Flöser from comment #1)
>
> Obvious problem: this requires (expensive) hardware.
>
Do you mean monitors or GPUs? VRR is supported by low end GPUs as well. As for
monitors, you can find 192
https://bugs.kde.org/show_bug.cgi?id=405912
Bug ID: 405912
Summary: Add support for adaptive sync (FreeSync) in KWin for
Wayland and X sessions
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #58 from Shmerl ---
Well, if it requires changing some taken approaches, that's redesign already.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #56 from Shmerl ---
(In reply to Martin Flöser from comment #55)
> See comment #42
Does it require KWin redesign in some way, or the fix is just not trivial?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #54 from Shmerl ---
(In reply to Vlad Zagorodniy from comment #47)
>
> I picked wrong verb. There is no currently any fix.
Is it clear what needs fixing though or how to fix it, or so far it's not even
known?
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=403752
--- Comment #3 from Shmerl ---
lsof also shows, that kmail holds these files in $HOME/.pki/nssdb open while
running: cert9.db key4.db
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403752
--- Comment #2 from Shmerl ---
I'll try to narrow it down to some dependency, but it's certainly being created
when Kmail starts.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403752
Bug ID: 403752
Summary: Support XDG base directory specification when using
libnss
Product: kmail2
Version: 5.9.1
Platform: Debian testing
OS: Linux
St
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #49 from Shmerl ---
(In reply to Rainer Finke from comment #48)
> Thanks for your answer! Ok, this explains than why I got a flickering when
> kmail is open as a non maximized window and I open kate as well as a non
> maximized wi
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #45 from Shmerl ---
Good find, anyway! Hopefully this will be fixed soon.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #43 from Shmerl ---
(In reply to Vlad Zagorodniy from comment #42)
> https://phabricator.kde.org/source/kwin/browse/master/plugins/scenes/opengl/
> scene_opengl.cpp$1121-1144 won't be able to clip them when
> m_hardwareClip
https://bugs.kde.org/show_bug.cgi?id=180770
--- Comment #28 from Shmerl ---
Is this somehow useful to Konsole?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347323
--- Comment #10 from Shmerl ---
Thanks for the pointer! Looks like Debian testing has been stuck with 18.04.0
for quite some time already.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402206
--- Comment #4 from Shmerl ---
Opened Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1516290
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=390804
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #2 from Shmerl ---
I
https://bugs.kde.org/show_bug.cgi?id=347323
--- Comment #8 from Shmerl ---
Which konsole version will this be available in?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402206
--- Comment #3 from Shmerl ---
I can file a Mozilla bug if you think that's something on the Firefox side.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402206
--- Comment #1 from Shmerl ---
To clarify the above. Without GTK_USE_PORTAL=1, Firefox remembers "default
browser" setting by creating a NoDisplay .desktop file. Even with that file
present, it's still asking when GTK_USE_PORTAL=1 is se
https://bugs.kde.org/show_bug.cgi?id=402206
Shmerl changed:
What|Removed |Added
Platform|Other |Debian testing
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402206
Bug ID: 402206
Summary: Firefox keeps asking for being set as default browser
when GTK_USE_PORTAL=1 is set
Product: xdg-desktop-portal-kde
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #23 from Shmerl ---
It is still a KWin bug though, since the session shoulnd't be crashing when
there are no outputs found (which is the case here for a split moment caused by
amdgpu bug above).
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #12 from Shmerl ---
To give an update. This actually looks specific to Wine+dxvk (Vulkan) case and
it doens't happen in Wine+wined3d (OpenGL).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #22 from Shmerl ---
It's fixed now for amdgpu in Linux kernel master and the fix should be
available in 4.20 release.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #10 from Shmerl ---
Sorry for confusion, I opened it for the wrong project (Wayland). It should
have been for Xorg, so here is the correct one:
https://gitlab.freedesktop.org/xorg/xserver/issues/20
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #9 from Shmerl ---
XWayland developers also suggest for the compositors to:
> Basically, the compositor must not reparent a "borderless fullscreen" X11
> window to a larger X11 window (e.g. for drop shadows).
--
You ar
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #8 from Shmerl ---
Opened new XWayland bug:
https://gitlab.freedesktop.org/wayland/wayland/issues/67
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #7 from Shmerl ---
OK, I'll follow up with XWayland developers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #5 from Shmerl ---
May be then calculation of the (potential) framerate should be done differently
somehow? I.e. physical framerate is always capped by the monitor refrerh rate
either way. When various HUDs report framerate in X it'
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #4 from Shmerl ---
(In reply to Martin Flöser from comment #3)
> KWin is synced to the frame rate of the screen. On the other hand KWin does
> not limit the frame rate of windows. They can render as many frames as they
> want.
https://bugs.kde.org/show_bug.cgi?id=401797
--- Comment #2 from Shmerl ---
(In reply to David Edmundson from comment #1)
> What's the purpose of having a refresh rate higher than your monitor?
Testing performance of graphics drivers for instance.
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=401797
Bug ID: 401797
Summary: KWin/Wayland capping framerate to 60 fps in XWayland
in borderless fullscreen (Wine)
Product: kwin
Version: 5.14.3
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #37 from Shmerl ---
Just tested it with Plasma 5.14.3 since it's now available in Debian. The issue
is a bit less severe, but still plagues Kmail.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387454
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #41 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=328409
--- Comment #3 from Shmerl ---
I don't really have access to that hardware anymore, so I can't retest it.
Since then, Plasma Active became Plasma Mobile, so this bug isn't really
relevant anyway.
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=353796
--- Comment #3 from Shmerl ---
This bug doesn't happen anymore.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #33 from Shmerl ---
(In reply to Patrick Silva from comment #29)
> in plasma 5.14 beta (Arch) I can reproduce the same flickering in window
> decoration kcm. Click "get new decoration" button, drag the window... enjoy
&g
https://bugs.kde.org/show_bug.cgi?id=399861
Bug ID: 399861
Summary: Keyboard layout indicator doesn't change in
notification area (system tray) in Wayland session
Product: kxkb
Version: unspecified
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=387313
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #32 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #20 from Shmerl ---
It looks like it's related to
https://bugs.freedesktop.org/show_bug.cgi?id=107978
My monitor (Dell U2413) has a setting for toggling DisplayPort 1.2. When I
disable it, Wayland Plasma session isn't crashing a
https://bugs.kde.org/show_bug.cgi?id=352385
--- Comment #8 from Shmerl ---
When I switched from HDD to SSD, this stopped happening. So it's some race
condition which is exposed by slower I/O. KDE developers should test it on
HDDs.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #18 from Shmerl ---
It can be a downstream issue with Debian specifically (since according to Mesa
developers, it doesn't happen on Arch). So I also opened a Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909636
--
Yo
https://bugs.kde.org/show_bug.cgi?id=398890
Bug ID: 398890
Summary: Add monitor brightness to system settings
Product: systemsettings
Version: 5.13.5
Platform: Debian testing
OS: Linux
Status: REPORTED
Sev
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #16 from Shmerl ---
Corresponding wayland-client bug:
https://gitlab.freedesktop.org/wayland/wayland/issues/56
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #15 from Shmerl ---
I managed to make it produce a core. It's from kwin_wayland. After installing
needed debug symbol packages, here is a backtrace:
Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-se
https://bugs.kde.org/show_bug.cgi?id=396066
Shmerl changed:
What|Removed |Added
Summary|Wayland session is coring |Wayland session is coring
|right
https://bugs.kde.org/show_bug.cgi?id=396109
--- Comment #2 from Shmerl ---
Using focus makes it more natural. It's unnatural to use left and right to move
up and down.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #14 from Shmerl ---
Corresponding amdgpu/dri bug:
https://bugs.freedesktop.org/show_bug.cgi?id=107213
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #13 from Shmerl ---
It could be a bug in amdgpu driver. I'd appreciate any other suggestion how to
debug it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=390733
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #7 from Shmerl ---
I
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #12 from Shmerl ---
So what exactly can be segfaulting using QThread and
libwayland-client.so.0.3.0?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #10 from Shmerl ---
I also copied startplasmacompositor and edited kwin launch there to use:
gdb -ex run --args /usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/lib/x86_64-linux-gnu/libexec/startplasma
It hung the
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #9 from Shmerl ---
Is there some way to force core generation? I'm not sure why it's not created,
ulimit is set to unlimited.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #8 from Shmerl ---
startplasmacompositor: Starting up...
dbus-update-activation-environment: warning: error sending to systemd:
org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1
exited with status 1
No backend
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #6 from Shmerl ---
I tried to start Plasma session manually from tty, and got this:
startplasmacompositor: Starting up...
dbus-update-activation-environment: warning: error sending to systemd:
org.freedesktop.DBus.Error.InvalidArgs
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #5 from Shmerl ---
It functions OK for X11 session at least. And that Wayland client core did
appear in dmesg before.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396109
Bug ID: 396109
Summary: Allow using up and down arrows for navigating both
message list and message body
Product: kmail2
Version: 5.7.3
Platform: Debian testing
OS
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #3 from Shmerl ---
I wrote a script what intercepts kwin_wayland launch and attaches gdb to it.
But when I do continue in it, it simply exists rather that segfaults.
Where can I find KWin logs?
That's what I see in: $HOME/.local/
https://bugs.kde.org/show_bug.cgi?id=396066
--- Comment #2 from Shmerl ---
(In reply to Martin Flöser from comment #1)
> Please try to get a backtrace from KWin.
What is a good way to attach debugger to it before it crashes?
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=396066
Bug ID: 396066
Summary: Wayland session is coring right after login
[radeonsi/DisplayPort]
Product: kwin
Version: 5.13.1
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=383379
--- Comment #33 from Shmerl ---
(In reply to Nate Graham from comment #32)
> - Libinput-on-x11 mouse KCM is done and will be released in Plasma 5.13
And Wayland one too?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344180
Shmerl changed:
What|Removed |Added
CC|shm...@mykolab.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=390761
--- Comment #3 from Shmerl ---
(In reply to Roman Gilg from comment #2)
> What is Libinput's virtual middle-click button?
>
> On Wayland the Touchpad KCM has an Emulate middle button checkbox. And I
> just tested, that it works. Do y
https://bugs.kde.org/show_bug.cgi?id=390761
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #1 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=383379
--- Comment #26 from Shmerl ---
(In reply to Nate Graham from comment #25)
> yes, they have to be, because xinput isn't supported on Wayland. See Bug
> 390761.
Just for the reference, I'm talking about the mouse, not touchpad here, b
https://bugs.kde.org/show_bug.cgi?id=389962
--- Comment #7 from Shmerl ---
And I suppose since lock screen has no network access, in order to enable
something like picture of the day, there should be an explicit KDE service /
scheduled job "picture of the day" that user can enable
https://bugs.kde.org/show_bug.cgi?id=383379
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #24 from Shmerl ---
I
https://bugs.kde.org/show_bug.cgi?id=389962
Shmerl changed:
What|Removed |Added
Attachment #110794|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=389962
--- Comment #5 from Shmerl ---
Created attachment 110794
--> https://bugs.kde.org/attachment.cgi?id=110794&action=edit
Workaround script, for astronomy picture of the day
I made myself a workaround script. It downloads an image and save
https://bugs.kde.org/show_bug.cgi?id=389962
--- Comment #4 from Shmerl ---
(In reply to Martin Flöser from comment #1)
> Picture of the Day is not really supported. The lock screen disallows
> Internet access, thus the picture of the Day cannot be downloaded. If you
> also use Picture o
https://bugs.kde.org/show_bug.cgi?id=390685
--- Comment #1 from Shmerl ---
What happens is that old picture (from the last time it worked) doesn't change.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=390685
Bug ID: 390685
Summary: Astronomy picture of the day stopped working
Product: kscreenlocker
Version: 5.10.2
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=322060
Shmerl changed:
What|Removed |Added
CC|shm...@mykolab.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=384478
--- Comment #9 from Shmerl ---
Or you are saying that with calendar integration plasmashell can't complete
loading its UI before akonadiserver and mysqld finish starting?
Then I suppose it also requires some approach redesign, that UI should a
https://bugs.kde.org/show_bug.cgi?id=384478
--- Comment #8 from Shmerl ---
(In reply to Christoph Feck from comment #7)
> You are probably using the Plasma calender with KDEPIM integration. That
> needs akonadi, which in turn needs mysql. I suggest to disable the Plasma
> KDEPIM in
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #50 from Shmerl ---
(In reply to Christoph Feck from comment #49)
> If slideshow is the cause, and you are using Qt 5.9.1, then it probably is a
> duplicate of bug 381000.
Yep, I figured that's the reason. Using static images w
https://bugs.kde.org/show_bug.cgi?id=384478
--- Comment #6 from Shmerl ---
(In reply to David Edmundson from comment #4)
> It does have more priority. It's in autostart phase 0. The rest comes after,
> so done.
I hope you understood what I'm trying to say. I want to see deskto
https://bugs.kde.org/show_bug.cgi?id=384478
--- Comment #5 from Shmerl ---
(In reply to David Edmundson from comment #4)
> It does have more priority. It's in autostart phase 0. The rest comes after,
> so done.
Well the problem is still here. Current login time is atrocious on HDD,
https://bugs.kde.org/show_bug.cgi?id=384478
Shmerl changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=384478
Shmerl changed:
What|Removed |Added
Summary|Extremely slow login into |Refactor login logic to
|KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=384478
Shmerl changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #3 from Shmerl ---
(In reply to
https://bugs.kde.org/show_bug.cgi?id=384478
--- Comment #1 from Shmerl ---
For the reference, after logging out, and logging back in, it's almost instant,
which again suggests that it's I/O related issue, because on second login a lot
is already in filesystem cache.
I even t
https://bugs.kde.org/show_bug.cgi?id=384478
Bug ID: 384478
Summary: Extremely slow login into KDE Plasma because of
intense I/O
Product: plasmashell
Version: 5.10.5
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=363723
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #21 from Shmerl ---
I
https://bugs.kde.org/show_bug.cgi?id=384269
--- Comment #19 from Shmerl ---
Heh, this worked. I set System Settings > Desktop Behavior > Screen Edges left
edge to something, and then unset it back. That fixed the scrolling!
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=384269
--- Comment #18 from Shmerl ---
(In reply to gst402 from comment #16)
> how can I disable the touch edge?
> all of my "Active Screen Corners and Edges" are set to "No Action"
I second that. I found that in System Settings
https://bugs.kde.org/show_bug.cgi?id=384453
Bug ID: 384453
Summary: Mouse actions are not working on the left most edge in
maximized Firefox in KDE on Linux
Product: plasmashell
Version: 5.10.5
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #45 from Shmerl ---
And just for the reference, it only happens when screen locker is using image
slideshow. With static image CPU usage is minimal.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=316348
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #44 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=345378
Shmerl changed:
What|Removed |Added
CC|shm...@mykolab.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=373856
Bug ID: 373856
Summary: KInfoCenter doesn't report core profile version for
OpenGL
Product: kinfocenter
Version: 5.8.2
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=363917
--- Comment #2 from Shmerl ---
Does anyone plan to work on this bug? I might be interested in helping, if
someone could give me some pointers where to start.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369174
Bug ID: 369174
Summary: Add image preview option for "Save As" dialog
Product: Spectacle
Version: unspecified
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363917
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=352385
--- Comment #6 from Shmerl ---
My env:
OS: Debian testing (x86_64).
plasma-desktop: 5.6.4.
baloo-kf5: 5.22.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352385
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #5 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=347602
--- Comment #59 from Shmerl ---
@Adam Felson: This sounds like distro problem, not KDE problem. You are using a
periodic release distro, where new Plasma comes in only very rarely. You can
switch to a rolling distro to get it in a timely fashion. Given
https://bugs.kde.org/show_bug.cgi?id=181290
Shmerl changed:
What|Removed |Added
CC||shm...@mykolab.com
--- Comment #147 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=303627
--- Comment #9 from Shmerl ---
It still happens in KDE Plasma 5.4.3 (Debian testing), but now it's way
smaller:
Processing triggers for shared-mime-info (1.5-2) ...
Unknown media type in type 'all/all'
Unknown media type in type
https://bugs.kde.org/show_bug.cgi?id=344145
--- Comment #8 from Shmerl ---
Just happened to me again - ksmserver eating 100% on shutdown and dialog not
coming up...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344145
--- Comment #5 from Shmerl ---
Actually not, recently it didn't happen anymore.
--
You are receiving this mail because:
You are watching all bug changes.
201 - 300 of 300 matches
Mail list logo
