https://bugs.kde.org/show_bug.cgi?id=455326
--- Comment #9 from Steve Vialle ---
(In reply to David Edmundson from comment #6)
> Is this still reproducible against newer Plasma (5.27)
Apologies for the late update, I am unable to reproduce this with 5.27.6.
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #27 from Steve ---
I managed to find an installation image (.iso) from February 6th (2023). This
version of Slackware64 has the following KDE5 versions:
Core Desktop binaries: 5.26.5
Frameworks: 5.102.0
Applications: 22.12.2
I recently
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #25 from Steve ---
I can definitively state that in 5.27.5 this is only an issue with Plasma X11.
Wayland and Full Wayland on my Slackware64 distro (Current tree) do not exhibit
this behavior (bug) with Plasma shell - i.e. losing it's
https://bugs.kde.org/show_bug.cgi?id=470444
Steve Vialle changed:
What|Removed |Added
CC||stev...@orcon.net.nz
--- Comment #1 from Steve
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #19 from Steve ---
That would be great detective work LabHamster! I would venture that would be
much appreciated by the Plasma team. That would help them immensely in
tracking down what changed in Plasma. I can say definitively
https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #16 from Steve ---
FWIW I am including my display configuration. My docking station has 1 display
port and 1 HDMI port. It is the display port that goes to my 4-way HDMI switch
(via a display-port to HDMI adapter) and ultimately monitor #3
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #5 from Steve ---
(In reply to Steve from comment #4)
> I disagree this is a duplicate of bug 467074. The behavior might be similar
> but it is triggered here by a completely different mechanism. That is a
> (temporary)
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #4 from Steve ---
I disagree this is a duplicate of bug 467074. The behavior might be similar but
it is triggered here by a completely different mechanism. That is a
(temporary) hardware disconnection of the secondary monitor - unlike
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #2 from Steve ---
There is more detail in a discussion on LQ here:
https://www.linuxquestions.org/questions/showthread.php?p=6432534=1#post6432534
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470184
--- Comment #1 from Steve ---
There is a discussion with more detail on LQ here:
https://www.linuxquestions.org/questions/showthread.php?p=6432534=1#post6432534
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470184
Bug ID: 470184
Summary: Dual-monitor PC will not refresh secondary desktop
after switching HDMI port in X11
Classification: Plasma
Product: Active Window Control
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=470108
Bug ID: 470108
Summary: Touchscreen zoom not working as expected
Classification: Applications
Product: okular
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=469927
Bug ID: 469927
Summary: Please provide a way to rotate individual pages
clockwise or counterclockwise
Classification: Applications
Product: okular
Version: 22.12.3
Platform:
https://bugs.kde.org/show_bug.cgi?id=463527
Steve Therrien changed:
What|Removed |Added
CC||kdeb...@stevetherrien.ca
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=469772
Steve Cossette changed:
What|Removed |Added
Platform|Other |Fedora RPMs
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469772
Bug ID: 469772
Summary: Keyboard shortcut "CTRL+S" works roughly 50% of the
time
Classification: Applications
Product: Spectacle
Version: 23.04.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=398458
--- Comment #7 from Steve Franks ---
(In reply to caulier.gilles from comment #6)
> @Steve,
>
> digiKam 8.0.0 is out. This entry still valid with this release ?
>
> Best regards
>
> Gilles Caulier
I haven't seen this error i
https://bugs.kde.org/show_bug.cgi?id=438203
--- Comment #8 from Steve Franks ---
(In reply to caulier.gilles from comment #7)
> @steve
>
> digiKam 8.0.0 is out. This entry still valid with this release ?
>
> Best regards
>
> Gilles Caulier
Another bug fixed.
R
https://bugs.kde.org/show_bug.cgi?id=435902
--- Comment #13 from Steve Franks ---
(In reply to caulier.gilles from comment #12)
> @Steve
>
> digiKam 8.0.0 is out. This entry still valid with this release ?
>
> Best regards
>
> Gilles Caulier
It is fine now, you may close
https://bugs.kde.org/show_bug.cgi?id=468507
--- Comment #9 from Steve Cossette ---
(In reply to Steve Cossette from comment #8)
> Just a headsup, the brand new 1.0.1 version still behaves exactly the same
For some reason, this crash doesn't occur on my second machine, so honestly I
don't k
https://bugs.kde.org/show_bug.cgi?id=468507
--- Comment #8 from Steve Cossette ---
Just a headsup, the brand new 1.0.1 version still behaves exactly the same
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468507
Steve Cossette changed:
What|Removed |Added
CC||farch...@gmail.com
--- Comment #7 from Steve
https://bugs.kde.org/show_bug.cgi?id=452441
--- Comment #15 from Steve Franks ---
I will try to repeat the situation and let you know ,
Steve
On Wed, 19 Apr 2023 at 06:58, wrote:
> https://bugs.kde.org/show_bug.cgi?id=452441
>
> --- Comment #14 from caulier.gil...@gmail.com ---
&
https://bugs.kde.org/show_bug.cgi?id=468115
--- Comment #12 from Steve Franks ---
That's what I meant, sorry I've been busy and haven't looked at it for a
while.
I cloned that with SSH, but was denied access when I tried to upload it.
I'll try again and let you know exactly what happens.
Steve
https://bugs.kde.org/show_bug.cgi?id=468115
--- Comment #10 from Steve Franks ---
Ok, I will download that. I realised that Beta 1 is the version that ‘lost’
exiftool.
BTW I said that I would like to help with the manual. I checked it out from
GitHub and made some minor changes, but GitHub
https://bugs.kde.org/show_bug.cgi?id=468115
--- Comment #8 from Steve Franks ---
Thank you, I’ll download beta1.
Regards
Steve
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468115
--- Comment #5 from Steve Franks ---
Yes. There’s still a question, why did Digikam ignore Exiftool? The
location was correct.
Regards
Steve
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468115
--- Comment #3 from Steve Franks ---
(In reply to Maik Qualmann from comment #1)
> No problem reading the tags here with the digiKam-8.0.0 from git/master.
> Since Exiv2 reports an error in the Olympus IFD Makernote header, make sure
>
https://bugs.kde.org/show_bug.cgi?id=468115
Steve Franks changed:
What|Removed |Added
CC||steve...@gmail.com
--- Comment #2 from Steve
https://bugs.kde.org/show_bug.cgi?id=453208
Steve Allewell changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
Status: REPORTED
Severity: normal
Priority: NOR
Component: Maintenance-Metadata
Assignee: digikam-bugs-n...@kde.org
Reporter: steve...@gmail.com
Target Milestone: ---
Created attachment 157814
--> https://bugs.kde.org/attachment.cgi
https://bugs.kde.org/show_bug.cgi?id=467941
--- Comment #2 from Steve Cossette ---
So, I've checked and it seems discover doesn'T really do update notification
completion, so if anything, I can create a separate suggestion ticket about
this.
Though I think there should still be a "Downlo
https://bugs.kde.org/show_bug.cgi?id=467941
--- Comment #1 from Steve Cossette ---
Created attachment 157707
--> https://bugs.kde.org/attachment.cgi?id=157707=edit
Update Progress
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=467941
Steve Cossette changed:
What|Removed |Added
Summary|[Fedora Distupgrade using |[Fedora Distupgrade using
https://bugs.kde.org/show_bug.cgi?id=467941
Bug ID: 467941
Summary: [Fedora Distupgrade using Discover] Minor UI issue
Classification: Applications
Product: Discover
Version: 5.27.3
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=316734
Steve Vialle changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=467341
Steve Cossette changed:
What|Removed |Added
CC||farch...@gmail.com
--- Comment #1 from Steve
https://bugs.kde.org/show_bug.cgi?id=445652
Steve Steiner changed:
What|Removed |Added
CC||sstein...@gmail.com
--- Comment #10 from Steve
https://bugs.kde.org/show_bug.cgi?id=422088
Steve changed:
What|Removed |Added
Ever confirmed|1 |0
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=422088
Steve changed:
What|Removed |Added
Platform|Archlinux |Flatpak
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=422088
Steve changed:
What|Removed |Added
CC||sbra...@gmail.com
--- Comment #14 from Steve ---
Same
https://bugs.kde.org/show_bug.cgi?id=466366
Bug ID: 466366
Summary: "Communication not allowed" on
/usr/share/dbus-1/system.d/org.kde.kded.inotify.conf
Classification: Plasma
Product: kde-inotify-survey
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=466322
Bug ID: 466322
Summary: Translations are not wired in the build file
Classification: Plasma
Product: kde-inotify-survey
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=442901
--- Comment #46 from Steve Vialle ---
(In reply to Luca Bacci from comment #45)
> We fixed the issue of unscaled XWayland apps for KDE
> 5.27.1, but unfortunately I had to cut out the part which properly reads
> Xft.DPI due to the
https://bugs.kde.org/show_bug.cgi?id=442901
--- Comment #44 from Steve Vialle ---
Additional quick tests:
Setting Xft.dpi to 82 in /etc/X11/Xresources -> plasma/QT/GTK all 96DPI.
Setting "DPI" "82x82" in /etc/X11/xorg.conf.d/foo.conf -> plasma runs at 96DPI.
Sett
https://bugs.kde.org/show_bug.cgi?id=442901
Steve Vialle changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=466207
--- Comment #1 from Steve Cossette ---
Clarification: This happens everytime the app is started.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466207
Bug ID: 466207
Summary: Crash right after start/login
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=442901
Steve Vialle changed:
What|Removed |Added
CC||stev...@orcon.net.nz
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=465675
--- Comment #2 from Steve Riches ---
OK I just opened compare.doc with Kwrite and can see tons of control
characters - not exactly binary - but I hear you. You must get a lot of
reports like mine. I would suggest modifying that terse message I
https://bugs.kde.org/show_bug.cgi?id=465675
Bug ID: 465675
Summary: kompare version 22.12.2
Classification: Applications
Product: kompare
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=464851
Bug ID: 464851
Summary: Ejecting vs unmounting ISO image confusing
Classification: Applications
Product: dolphin
Version: 22.12.1
Platform: Neon
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=462542
--- Comment #16 from Steve Franks ---
Created attachment 154431
--> https://bugs.kde.org/attachment.cgi?id=154431=edit
dbgview log Windows 10 digikam 7.10.0
This is the debug view log captured whilst generating HTML Gallery 20110720
Varne.
Wind
https://bugs.kde.org/show_bug.cgi?id=462542
Steve Franks changed:
What|Removed |Added
Attachment #154302|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=462542
--- Comment #14 from Steve Franks ---
I downloaded 7.10.0 debug for Windows and have attached the DebugView
output.
The reason that there were no images for the galleries created
for albums in my earlier po0sts, is that the tool doesn't include
sub
https://bugs.kde.org/show_bug.cgi?id=462542
--- Comment #12 from Steve Franks ---
I couldn’t get either to work, as I expected, but the appimage did produce
output for both the selected album and tag.
Is it possible to capture all of the debugging output including that from
the Create HTML
https://bugs.kde.org/show_bug.cgi?id=462542
--- Comment #10 from Steve Franks ---
I agree that a gallery is created which shows all photos with the selected
tag. Isn’t the output supposed to be just images in the selected album(s)
that have that tag?
If you run the gallery creation tool again
https://bugs.kde.org/show_bug.cgi?id=462542
--- Comment #9 from Steve Franks ---
I discovered this running 7.8.0 under Windows 10, it is the same in 7.9.0
and I attached dbgView output to a previous email.
My Linux PC is misbehaving, it frequently refuses to start, but if I can
make it work I
https://bugs.kde.org/show_bug.cgi?id=462542
--- Comment #7 from Steve Franks ---
digikam-7.9.0-20221202T144203-x86-64-debug.appimage running under MX Linux
is similar. One or more albums must be selected before filtering by tags
(Album 2012 which contains 2012-01-January to 2012-12-December. Tag
https://bugs.kde.org/show_bug.cgi?id=453937
--- Comment #19 from steve ---
(In reply to Nate Graham from comment #18)
> This should be fixed in Plasma 5.27 (aka current git master) as of various
> ports and fixes.
Looking forward to February 2023 then. Recently it seems like it is creatin
https://bugs.kde.org/show_bug.cgi?id=462542
--- Comment #6 from Steve Franks ---
I found the problem whilst using 7.8.0 on my Windows 10 PC. I downloaded
and installed 7.9.0 and the problem persists.
I’m not sure what a virtual album is. Each album on my system relates to a
top-level folder
https://bugs.kde.org/show_bug.cgi?id=377399
--- Comment #4 from Steve ---
I can't reproduce this with the current release. I needed help a long time ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462542
Steve Franks changed:
What|Removed |Added
CC||steve...@gmail.com
--
You are receiving
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: digikam-bugs-n...@kde.org
Reporter: steve...@gmail.com
Target Milestone: ---
Created attachment 154223
--> https://bugs.kde.org/attachment.cgi?id=154223=edit
dbgview
https://bugs.kde.org/show_bug.cgi?id=384546
--- Comment #5 from Steve Soule ---
You're right, of course. I don't know what I was thinking. I'm sorry for
wasting your time.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384546
Steve Soule changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=377982
--- Comment #2 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377979
--- Comment #3 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377590
--- Comment #2 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=378172
--- Comment #3 from Steve ---
No, I can't reproduce it. I needed help many years ago.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=461251
--- Comment #1 from Steve Zakulec ---
Think I figured out what was going on- libpoppler-glib8 was getting blocked by
a small number of packages I had on my system from 20.04 (possibly Wine-related
packages).
Once I tried installing libpoppler-glib8
the upgrade
process.
Here's the output from trying to install the package using apt:
sudo apt install skanlite
[sudo] password for steve:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2
https://bugs.kde.org/show_bug.cgi?id=460941
--- Comment #3 from Steve Franks ---
I did this on an old i7 Desktop, which only has 8gb RAM. digikam doesn't
appear to run out of memory, so I don't know why it failed.
The second run died at about 57%, so I changed the environment variable
https://bugs.kde.org/show_bug.cgi?id=460274
Steve Allen changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=460941
--- Comment #2 from Steve Franks ---
I tried several times.
In the end I removed the album from the collection and restarted
digikam and added the folder again. That prompted a complete rescan,
which is now running.
I will do as you
Status: REPORTED
Severity: normal
Priority: NOR
Component: Albums-Engine
Assignee: digikam-bugs-n...@kde.org
Reporter: steve...@gmail.com
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace
https://bugs.kde.org/show_bug.cgi?id=460274
--- Comment #9 from Steve Allen ---
That's really helpful, thanks.
Moving the config worked a treat. Seems its regenerated and windows are
appearing as normal.
Will miss Bismuth tiling, hopefully the depends issue with the 20.04 base
will get sorted
https://bugs.kde.org/show_bug.cgi?id=460274
--- Comment #7 from Steve Allen ---
If I create a new user, login with that user (to see if its my user setting
causing issues) cycles the ssdm loginscreen
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460274
--- Comment #6 from Steve Allen ---
Actually output is `--no entries--`
Is there a way to backup and clear my Kwin settings (e.g decoration etc) back
to default?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460274
--- Comment #5 from Steve Allen ---
I will struggle to cut/pates logs. I only have my phone and the laptop (which I
can only use the tty on) with me
I won't be able to ssh in from my desktop until friday.
Is there anything I should be looking
https://bugs.kde.org/show_bug.cgi?id=460274
--- Comment #3 from Steve Allen ---
Not a script, but I did use kwin-bismuth, but uninstalled that to rule it out.
I wonder if the windows are trying to tile / kwin is trying to use bismuth
decoration even though bismuth is not installed anymore
https://bugs.kde.org/show_bug.cgi?id=460274
--- Comment #1 from Steve Allen ---
I should note that it doesn't matter whether loginnis with x11 or wayland
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460274
Steve Allen changed:
What|Removed |Added
CC||stephenalle...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=460274
Bug ID: 460274
Summary: Windows don't display properly since Neon Plasma 5.26
Update
Classification: Plasma
Product: kwin
Version: unspecified
Platform: Neon
https://bugs.kde.org/show_bug.cgi?id=459868
--- Comment #1 from Steve Allewell ---
Thank you for reporting these issues and suggestions, sometimes a quick
question to the mailing list may have answered a number of these points.
The Tools>Draw function will produce full cross stitches for li
https://bugs.kde.org/show_bug.cgi?id=441539
--- Comment #8 from Steve Franks ---
That is what I do most days. Occasionally digikam doesn’t say that it cannot
find my Photo folder.
N.B. This wasn’t a replacement drive. I used to have my photos on a USB Hard
Disk, then decided to copy everything
https://bugs.kde.org/show_bug.cgi?id=441539
Steve Franks changed:
What|Removed |Added
CC||steve...@gmail.com
--- Comment #6 from Steve
https://bugs.kde.org/show_bug.cgi?id=404583
--- Comment #2 from Steve Soule ---
It's tedious to try to reproduce this crash, since it only occurs at the end of
a game. I just tried it once, and kpat didn't crash. How many times do you
want me to try to reproduce it?
My current specs
https://bugs.kde.org/show_bug.cgi?id=440663
--- Comment #90 from Steve Vialle ---
(In reply to Andrey from comment #87)
> I just fixed it so it started to work for the context menu created archives
> at all (yes, it was there for them either).
As far as I can see the problem began with
https://bugs.kde.org/show_bug.cgi?id=440663
--- Comment #86 from Steve Vialle ---
> Checking "open new folders in tabs" does indeed prevent the spawning of new
dolphin windows on extraction.
s/extraction/compression/g
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440663
--- Comment #85 from Steve Vialle ---
(In reply to Andrey from comment #83)
> What about extraction? Does it respect "open destination folder after
> extraction" in ark?
Checked or unchecked, nothing is opened after extraction from the
https://bugs.kde.org/show_bug.cgi?id=440663
--- Comment #81 from Steve Vialle ---
(In reply to Andrey from comment #80)
> Are you creating archive in Ark or in Dolphin's context menu?
Dolphin context menu, "Compress here". Any archive type.
> Does it depend on any options
https://bugs.kde.org/show_bug.cgi?id=440663
--- Comment #78 from Steve Vialle ---
Confirmed, again. Revert of the revert of the revert patch added back into my
portage tree. Again.
Can we not just kill this misfeature with fire, please? And not keep trying to
put it back in, pretty please?
I
https://bugs.kde.org/show_bug.cgi?id=459175
Bug ID: 459175
Summary: Okular annotations should be moveable and editable
Product: okular
Version: 21.12.3
Platform: Ubuntu
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=458752
--- Comment #4 from Steve Franks ---
Thanks, I will rename the XMP files to .xmp.
Steve
On Mon, 5 Sep 2022 at 17:37, Maik Qualmann wrote:
> https://bugs.kde.org/show_bug.cgi?id=458752
>
> --- Comment #3 from Maik Qualmann ---
> Ok, no
: REPORTED
Severity: normal
Priority: NOR
Component: Metadata-Exif
Assignee: digikam-bugs-n...@kde.org
Reporter: steve...@gmail.com
Target Milestone: ---
Created attachment 151846
--> https://bugs.kde.org/attachment.cgi?id=151846=edit
xmp contain
https://bugs.kde.org/show_bug.cgi?id=458605
Bug ID: 458605
Summary: 100% CPU usage and infinite loop while opening HTML
file.
Product: ark
Version: 22.08.0
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=453890
Steve Vialle changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC
https://bugs.kde.org/show_bug.cgi?id=423372
Steve Wills changed:
What|Removed |Added
CC||swi...@freebsd.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #31 from steve ---
Hi everyone
This is fixed by turning off stellarsolver partitioning. The latter is now
default as of kstars 3.6.0
**does this count as RESOLVED?
--
You are receiving this mail because:
You are watching all bug changes.
201 - 300 of 806 matches
Mail list logo
