date:20220104

[krita] [Bug 405643] Feature request: circle in a square assistant tool

2022-01-04 Thread Hector

https://bugs.kde.org/show_bug.cgi?id=405643

--- Comment #7 from Hector  ---
(In reply to Srirupa Datta from comment #6)
> anyone available to mentor this project?
I am not a mentor, but i can be your tester for this. If you need

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 447599] Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer below a visible layer

2022-01-04 Thread Dmitry Kazakov

https://bugs.kde.org/show_bug.cgi?id=447599

Dmitry Kazakov  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 447951] Renaming to itself locks Kate

2022-01-04 Thread Waqar Ahmed

https://bugs.kde.org/show_bug.cgi?id=447951

Waqar Ahmed  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/util
   ||ities/kate/commit/e50c8655c
   ||dd1894de5567508cbd654d4c4f2
   ||7a70

--- Comment #1 from Waqar Ahmed  ---
Git commit e50c8655cdd1894de5567508cbd654d4c4f27a70 by Waqar Ahmed.
Committed on 05/01/2022 at 07:40.
Pushed by waqar into branch 'master'.

Ignore rename if newName == oldName

M  +1-1kate/katefileactions.cpp

https://invent.kde.org/utilities/kate/commit/e50c8655cdd1894de5567508cbd654d4c4f27a70

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 447959] New: System hangs with blinking underscore at shutdown if turned off via confirmation prompt from Wayland session

2022-01-04 Thread bugzilla_noreply

https://bugs.kde.org/show_bug.cgi?id=447959

Bug ID: 447959
Summary: System hangs with blinking underscore at shutdown if
turned off via confirmation prompt from Wayland
session
Product: plasmashell
Version: 5.23.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: andrea.i...@gmail.com
Target Milestone: 1.0

SUMMARY
As per title.

STEPS TO REPRODUCE
1. Wayland session on 5.23.4
2. make sure you get the plasma logout/shutdown prompt when clicking the
shutdown entry in the K menu or pressing power button
3. shutdown from that prompt

OBSERVED RESULT
System hangs - takes a few minutes to fully shutdown.
During this time, after the user session is closed, only a blinking white
underscore is visible on screen.
Pressing arrow up brings to a usable tty.
If left untouched for a few minutes, eventually OEM logo (+ distro logo in my
case) shows up for a few seconds, before the system eventually shuts down.

EXPECTED RESULT
System should shut down quickly.
100% of the time I shutdown without going through the confirmation prompt,
shutdown happens as fast as expected (a few seconds).
Haven't tested on Xorg, but recently got the same problem on fedora KDE (which
uses Wayland by default), and worked around this issue by skipping the
logout/shutdown prompt.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220102
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.12-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz
Memory: 7,5 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics

ADDITIONAL INFORMATION
journalctl logs here:
https://www.reddit.com/r/openSUSE/comments/rvoz7o/blinking_cursor_at_shutdown_how_to_troubleshoot/

Thanks

--
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 447958] New: Discover hangs in "About" Dialog

2022-01-04 Thread Georg Grabler

https://bugs.kde.org/show_bug.cgi?id=447958

Bug ID: 447958
   Summary: Discover hangs in "About" Dialog
   Product: Discover
   Version: 5.23.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: ggrab...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
Discover seems to be endlessly looping when clicking the "About" dialog.

STEPS TO REPRODUCE
1. Open Discover
2. Click the "About" dialog

OBSERVED RESULT
Hangs spamming this two messages in the console:
Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
file:///usr/lib/qt/qml/org/kde/kirigami.2/AboutItem.qml:135:5: QML FormLayout:
Binding loop detected for property "implicitHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/AboutItem.qml:135:5: QML FormLayout:
Binding loop detected for property "implicitHeight"
Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
file:///usr/lib/qt/qml/org/kde/kirigami.2/AboutItem.qml:135:5: QML FormLayout:
Binding loop detected for property "implicitHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/AboutItem.qml:135:5: QML FormLayout:
Binding loop detected for property "implicitHeight"
Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
file:///usr/lib/qt/qml/org/kde/kirigami.2/AboutItem.qml:135:5: QML FormLayout:
Binding loop detected for property "implicitHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/AboutItem.qml:135:5: QML FormLayout:
Binding loop detected for property "implicitHeight"


EXPECTED RESULT
Actually, not hanging :-).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 5.15.12-arch
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.89.0 (within that, kirigami2 5.89.0)
Qt Version: 5.15.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 447851] Finishing transform sometimes fails when user forget to approve (press Enter)

2022-01-04 Thread Dmitry Kazakov

https://bugs.kde.org/show_bug.cgi?id=447851

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #2 from Dmitry Kazakov  ---
Hi, hcorwin!

The backtrace shows that Krita actually crashed in the Move Tool. Could you
clarify a few questions?

1) Did you use Move Tool right after the transformation? Or you used the Move
Tool for the transformation itself?
2) What are your settings in Settings->Performance->Instant Preview? Do you use
"in-stack preview" for the transform tool? And do you have forced Instant
Preview enabled for both Move and Transform tool?

PS:
By now I couldn't reproduce this issue, and answers to questions above might
give some clues

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 447101] Plasma Crashes Sometimes When Closing Applications

2022-01-04 Thread Noah

https://bugs.kde.org/show_bug.cgi?id=447101

Noah  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Noah  ---
Since I haven't been able to reproduce the crash, and I can't provide more
information because of that, I'm marking this bug as 'resolved'. But if it
happens to me again (which I think it could, just don't know when) I'm going to
reopen this bug providing more information.

I try to make my bug reports useful, so if there's something I can do
differently in my bug reports to aid in that, please let me know.

With this particular bug, I just don't know how to add debug symbols to a
backtrace after it's already been generated (or if that's possible).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 446075] several crashes

2022-01-04 Thread John Clark

https://bugs.kde.org/show_bug.cgi?id=446075

John Clark  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 CC||john.cl...@cantab.net
 Status|CONFIRMED   |REPORTED

--- Comment #3 from John Clark  ---
Hi, a quick scan of your logs shows that you have a LOT going on on this
machine. Ultimately it's an X Server crash which I would guess is resource
exhaustion. You have many thousand (234145!!) instances of this:

 2021-12-30 13:31:15: Initialising aMule 2.3.2 compiled with wxGTK2 v3.0.4 and
Boost 1.67
 2021-12-30 13:31:15: Checking if there is an instance already running...
!2021-12-30 13:31:15: There is an instance of aMule already running
 2021-12-30 13:31:15: (lock file: /home/duns/.aMule/muleLock)
 2021-12-30 13:31:15: Raising current running instance.

eventually followed by a crash:

klauncher: Exiting on signal 15
klauncher: Exiting on signal 1
XIO:  fatal IO error 4 (Interrupted system call) on X server ":0"
  after 2072 requests (2072 known processed) with 0 events remaining.
XIO:  fatal IO error 0 (Success) on X server ":0"
  after 234145 requests (234122 known processed) with 0 events remaining.
Exception in thread XInterface-thread:
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
  File "/usr/lib/python3/dist-packages/autokey/interface.py", line 1206, in run
self.recordDisplay.record_enable_context(self.ctx, self.__processEvent)
  File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 239, in
enable_context
EnableContext(
  File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 220, in
__init__
rq.ReplyRequest.__init__(self, *args, **keys)
  File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1369, in
__init__
self.reply()
  File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1381, in
reply
self._display.send_and_recv(request = self._serial)
  File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 610, in
send_and_recv
raise self.socket_error
Xlib.error.ConnectionClosedError: Display connection closed by server

after that everything goes wrong, as you might expect. May I suggest stopping
aMule and seeing if that helps?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446757] Appimage update does not work, underlying mechanism is either not present or not executable.

2022-01-04 Thread Dmitry Kazakov

https://bugs.kde.org/show_bug.cgi?id=446757

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #12 from Dmitry Kazakov  ---
For the releases we need to update the release manual for that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 447949] lsp-client: gopls results in constant errors when typing

2022-01-04 Thread Waqar Ahmed

https://bugs.kde.org/show_bug.cgi?id=447949

Waqar Ahmed  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||waqar@gmail.com

--- Comment #1 from Waqar Ahmed  ---
Hi Adam,

Firstly, maybe you are interested in updating the default config for gopls so
that users don't have to manually override it? if so, you can find the repo
here: http://invent.kde.org/utilities/kate/. The lsp config code is under
addons/lsp directory

For your issue, perhaps you can paste the full output of the OutputView here?
We made some improvements recently to the LSP, and seeing that you are on arch
linux, it will probably be very easy to test them out for you and see if the
issue is still there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 422140] Annoying and obtrusive notifications KDE connect

2022-01-04 Thread Alex

https://bugs.kde.org/show_bug.cgi?id=422140

Alex  changed:

   What|Removed |Added

 CC||alex...@protonmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 421451] Kate raises hspell error when launched from command line

2022-01-04 Thread Waqar Ahmed

https://bugs.kde.org/show_bug.cgi?id=421451

Waqar Ahmed  changed:

   What|Removed |Added

 Status|REOPENED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #9 from Waqar Ahmed  ---
> I do not have hspell installed. 

> Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.

The above lines says that you do have it installed but don't have the
dictionaries. Please either uninstall it completely or install the dictionaries
and check if its still giving warnings.

https://packages.ubuntu.com/hirsute/amd64/hspell/filelist shows the list of
files installed on your system if hspell is installed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[rkward] [Bug 447957] New: Sendcode integration on sublime text

2022-01-04 Thread Ryan

https://bugs.kde.org/show_bug.cgi?id=447957

Bug ID: 447957
   Summary: Sendcode integration on sublime text
   Product: rkward
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: R Console
  Assignee: rkward-de...@kde.org
  Reporter: jryan.dani...@gmail.com
  Target Milestone: ---

SUMMARY
I am trying to find a replacement for Rstudio as I am now on sway (wayland) on
Ubuntu 22.04 and Rstudio does not support wayland.
RKWard seems to work well so far but I cannot send R code from sublime text to
RKWard.
Is there something I can do to get this up and running?


STEPS TO REPRODUCE
1.  I installed rkward from the apt repo.
2. I have added the following to my 'sendcode' settings in sublime text, in the
hope that it would that simple:
"R": { "bracketed_paste_mode": false, "prog": "rkward", }, "rmd" : { "prog":
"rkward", "bracketed_paste_mode": false },

OBSERVED RESULT
I get an error message "rkward is not supported for current syntax'.

EXPECTED RESULT
The code from sublime text is magically transported to the RKWard R console and
the code runs. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Linux 5.15.0-14-generic #14-Ubuntu SMP Tue Dec 14 10:08:09 UTC 2021 x86_64
GNU/Linux

Sublime text build 4126

RKWard v0.7.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 447956] Wayland: inverted DBUS-notifications appear in app title bar

2022-01-04 Thread Michael Hamilton

https://bugs.kde.org/show_bug.cgi?id=447956

--- Comment #1 from Michael Hamilton  ---
I should note that in the screenshot I attached, the notification that
corrupted the title bar has already timed out and dismissed itself, so it is
not visible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 447956] New: Wayland: inverted DBUS-notifications appear in app title bar

2022-01-04 Thread Michael Hamilton

https://bugs.kde.org/show_bug.cgi?id=447956

Bug ID: 447956
   Summary: Wayland: inverted DBUS-notifications appear in app
title bar
   Product: kwin
   Version: 5.23.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mich...@actrix.gen.nz
  Target Milestone: ---

Created attachment 145122
  --> https://bugs.kde.org/attachment.cgi?id=145122=edit
Screenshot of a corrupted title bar.

SUMMARY
When using Wayland with Nvidia 470.86-46, sometimes inverted parts of DBUS
desktop-notifications appear in title-bars of unrelated applications.

I'm not sure if it has anything to do with the bug, but the DBUS-notifications
have a 30 second timeout. They are being raised by jouno, a systemd-Journal
viewer which features Freedesktop/DBUS Notifications forwarding  (
https://github.com/digitaltrails/jouno ).

STEPS TO REPRODUCE
1.  Raise a lot of notifications.
2.  Sometimes a notification corrupts an unrelated application's title bar, but
I cannot predict when.

OBSERVED RESULT
Part of an notification will appear as inverted text in the title bar of an
unrelated application.

EXPECTED RESULT
The notification should not be able to corrupt the title bar of an unrelated
application.  Presumably this is also security issue given Wayland is supposed
to isolate each app's windows.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed 20211124
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Nvidia 470.86-46

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 446413] zero blur in option but still has blur

2022-01-04 Thread Bug Janitor Service

https://bugs.kde.org/show_bug.cgi?id=446413

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 447103] Only the canvas function is executed together with the full screen, which is not good. krita5.0 began to appear

2022-01-04 Thread Bug Janitor Service

https://bugs.kde.org/show_bug.cgi?id=447103

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 445370] Lecture des .raw

2022-01-04 Thread Bug Janitor Service

https://bugs.kde.org/show_bug.cgi?id=445370

--- Comment #3 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations

2022-01-04 Thread Robert Webb

https://bugs.kde.org/show_bug.cgi?id=447955

--- Comment #3 from Robert Webb  ---
Tried it a third time, slightly differently.

Opened Gwenview.
This time, instead of clicking in the Places sidebar, I clicked
'recentlyused:/locations/' under the Recent Folders tab.
Gwenview crashed immediately.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6  0x7f3ab0fc9a2e in QVector >::count
(this=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:241
#7  QVariantAnimationPrivate::recalculateCurrentInterval (this=0x7ffe0004,
force=false) at animation/qvariantanimation.cpp:228
#8  0x7f3ab2291f15 in QModelIndex::parent (this=0x5610f643c300) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443
#9  QListView::scrollTo (this=0x5610f650a4c0, index=...,
hint=QAbstractItemView::EnsureVisible) at itemviews/qlistview.cpp:571
#10 0x7f3ab2253300 in QAbstractItemView::currentChanged
(this=0x5610f650a4c0, current=..., previous=...) at
itemviews/qabstractitemview.cpp:3677
#11 0x7f3ab11fb3c8 in doActivate (sender=0x5610f6424680,
signal_index=4, argv=0x7ffe11319c30) at kernel/qobject.cpp:3898
#12 0x7f3ab11f485f in QMetaObject::activate
(sender=sender@entry=0x5610f6424680, m=m@entry=0x7f3ab14990a0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe11319c30)
at kernel/qobject.cpp:3946
#13 0x7f3ab116f6d3 in QItemSelectionModel::currentChanged
(this=this@entry=0x5610f6424680, _t1=..., _t2=...) at
.moc/moc_qitemselectionmodel.cpp:482
#14 0x7f3ab11730b9 in QItemSelectionModel::setCurrentIndex
(this=0x5610f6424680, index=..., command=...) at
itemmodels/qitemselectionmodel.cpp:1416
#15 0x7f3ab224cedf in QAbstractItemView::setCurrentIndex (this=, index=...) at itemviews/qabstractitemview.cpp:1080
#16 0x5610f42e6d0f in Gwenview::MainWindow::slotDirListerCompleted
(this=0x5610f64418c0) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/app/mainwindow.cpp:1399
#17 Gwenview::MainWindow::qt_static_metacall (_o=0x5610f64418c0, _c=, _id=, _a=) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/build/app/gwenview_autogen/EWIEGA46WW/moc_mainwindow.cpp:245
#18 0x7f3ab11fb3c8 in doActivate (sender=0x5610f643c070,
signal_index=4, argv=0x7ffe11319e90) at kernel/qobject.cpp:3898
#19 0x7f3ab11f485f in QMetaObject::activate
(sender=sender@entry=0x5610f643c070, m=m@entry=0x7f3ab2a2ff60
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#20 0x7f3ab29b9cb3 in KCoreDirLister::completed
(this=this@entry=0x5610f643c070) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/build/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:479
#21 0x7f3ab29c203b in KCoreDirListerCache::slotResult (this=0x7f3ab2a333c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
j=) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/kcoredirlister.cpp:1327
#22 0x7f3ab11fb393 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1131a080,
r=0x7f3ab2a333c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
this=0x5610f6da72d0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0x5610f6da59a0, signal_index=6,
argv=0x7ffe1131a080) at kernel/qobject.cpp:3886
#24 0x7f3ab11f485f in QMetaObject::activate
(sender=sender@entry=0x5610f6da59a0, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe1131a080)
at kernel/qobject.cpp:3946
#25 0x7f3ab15e8ffc in KJob::result (this=this@entry=0x5610f6da59a0,
_t1=, _t1@entry=0x5610f6da59a0, _t2=...) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#26 0x7f3ab15ed39b in KJob::finishJob (this=0x5610f6da59a0,
emitResult=) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/src/lib/jobs/kjob.cpp:98
#27 0x7f3ab11fb393 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1131a150,
r=0x5610f6da59a0, this=0x5610f6c65ec0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#28 doActivate (sender=0x5610f6c6db90, signal_index=7,
argv=0x7ffe1131a150) at kernel/qobject.cpp:3886
#29 0x7f3ab296b39d in KIO::SlaveInterface::dispatch (this=0x5610f6c6db90,
_cmd=104, rawdata=...) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/slaveinterface.cpp:149
#30 0x7f3ab2963989 in KIO::SlaveInterface::dispatch (this=0x5610f6c6db90)
at /usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/slaveinterface.cpp:78
#31 0x7f3ab296d14a in KIO::Slave::gotInput (this=0x5610f6c6db90) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/slave.cpp:336
#32 0x7f3ab11fb393 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1131a390,
r=0x5610f6c6db90, this=0x5610f6dbbf70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#33 doActivate (sender=0x5610f6c04000,

[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations

2022-01-04 Thread Robert Webb

https://bugs.kde.org/show_bug.cgi?id=447955

--- Comment #2 from Robert Webb  ---
Tried it again.  Same result.

Gwenview opened, by DrKonqi after the last crash.
Showing the Recent Folders tab.
I clicked on Recent Locations in the Places sidebar.
Crash.  (DrKonqi did not open this time.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations

2022-01-04 Thread Robert Webb

https://bugs.kde.org/show_bug.cgi?id=447955

Robert Webb  changed:

   What|Removed |Added

 CC||ro.web...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations

2022-01-04 Thread Robert Webb

https://bugs.kde.org/show_bug.cgi?id=447955

--- Comment #1 from Robert Webb  ---
Correction:
I clicked on Recent Locations in the Places sidebar.

Additional info:
The main "sub-window" was showing the Recent Folders tab
upon opening Gwenview.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations

2022-01-04 Thread Robert Webb

https://bugs.kde.org/show_bug.cgi?id=447955

Robert Webb  changed:

   What|Removed |Added

Summary|Gwenview crashed after  |Gwenview crashed after
   |clicking Recently Used  |clicking Places
   |Locations   |sidebar/Recent Locations

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 447862] Could not open a PDF file in Krita 5.0.0 in macOS

2022-01-04 Thread vanyossi

https://bugs.kde.org/show_bug.cgi?id=447862

vanyossi  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/2814f3f7a |hics/krita/commit/602e55754
   |555b8359230e157c306dbd53576 |200d02dcd463b0d666a7bebaf4e
   |dddc|c76b
 Resolution|--- |FIXED

--- Comment #8 from vanyossi  ---
Git commit 602e55754200d02dcd463b0d666a7bebaf4ec76b by Ivan Yossi, on behalf of
L. E. Segovia.
Committed on 05/01/2022 at 02:30.
Pushed by ivany into branch 'master'.

Fix patch for fontconfig triggering autoreconf

Both .am and compiled files need to be updated. Let's also make sure
their modification times don't change, either.

M  +40   -11   3rdparty/ext_fontconfig/0001-Fix-FC_DEFAULT_FONTS-on-macOS.patch

https://invent.kde.org/graphics/krita/commit/602e55754200d02dcd463b0d666a7bebaf4ec76b

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 387455] Column view in Dolphin

2022-01-04 Thread Prajna Sariputra

https://bugs.kde.org/show_bug.cgi?id=387455

Prajna Sariputra  changed:

   What|Removed |Added

 CC||putr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 447955] New: Gwenview crashed after clicking Recently Used Locations

2022-01-04 Thread Robert Webb

https://bugs.kde.org/show_bug.cgi?id=447955

Bug ID: 447955
   Summary: Gwenview crashed after clicking Recently Used
Locations
   Product: gwenview
   Version: 21.12.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: ro.web...@gmail.com
  Target Milestone: ---

Application: gwenview (21.12.0)

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.23.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Opened Gwenview.
Clicked 'Recently Used Locations'.
A moment later, after showing [an empty list?], Gwenview crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6  0x7fafc15d3a2e in QVector >::count
(this=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:241
#7  QVariantAnimationPrivate::recalculateCurrentInterval (this=0x7ffc0004,
force=false) at animation/qvariantanimation.cpp:228
#8  0x7fafc289bf15 in QModelIndex::parent (this=0x55e667c8f9b0) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443
#9  QListView::scrollTo (this=0x55e6674336c0, index=...,
hint=QAbstractItemView::EnsureVisible) at itemviews/qlistview.cpp:571
#10 0x7fafc285d300 in QAbstractItemView::currentChanged
(this=0x55e6674336c0, current=..., previous=...) at
itemviews/qabstractitemview.cpp:3677
#11 0x7fafc18053c8 in doActivate (sender=0x55e66734c890,
signal_index=4, argv=0x7ffc86154530) at kernel/qobject.cpp:3898
#12 0x7fafc17fe85f in QMetaObject::activate
(sender=sender@entry=0x55e66734c890, m=m@entry=0x7fafc1aa30a0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc86154530)
at kernel/qobject.cpp:3946
#13 0x7fafc17796d3 in QItemSelectionModel::currentChanged
(this=this@entry=0x55e66734c890, _t1=..., _t2=...) at
.moc/moc_qitemselectionmodel.cpp:482
#14 0x7fafc177d0b9 in QItemSelectionModel::setCurrentIndex
(this=0x55e66734c890, index=..., command=...) at
itemmodels/qitemselectionmodel.cpp:1416
#15 0x7fafc2856edf in QAbstractItemView::setCurrentIndex (this=, index=...) at itemviews/qabstractitemview.cpp:1080
#16 0x55e666fb4d0f in Gwenview::MainWindow::slotDirListerCompleted
(this=0x55e667360540) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/app/mainwindow.cpp:1399
#17 Gwenview::MainWindow::qt_static_metacall (_o=0x55e667360540, _c=, _id=, _a=) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/build/app/gwenview_autogen/EWIEGA46WW/moc_mainwindow.cpp:245
#18 0x7fafc18053c8 in doActivate (sender=0x55e667371b20,
signal_index=4, argv=0x7ffc86154790) at kernel/qobject.cpp:3898
#19 0x7fafc17fe85f in QMetaObject::activate
(sender=sender@entry=0x55e667371b20, m=m@entry=0x7fafc3039f60
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#20 0x7fafc2fc3cb3 in KCoreDirLister::completed
(this=this@entry=0x55e667371b20) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/build/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:479
#21 0x7fafc2fcc03b in KCoreDirListerCache::slotResult (this=0x7fafc303d3c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
j=) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/kcoredirlister.cpp:1327
#22 0x7fafc1805393 in QtPrivate::QSlotObjectBase::call (a=0x7ffc86154980,
r=0x7fafc303d3c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
this=0x55e667c1fb30) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0x55e667c20690, signal_index=6,
argv=0x7ffc86154980) at kernel/qobject.cpp:3886
#24 0x7fafc17fe85f in QMetaObject::activate
(sender=sender@entry=0x55e667c20690, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc86154980)
at kernel/qobject.cpp:3946
#25 0x7fafc1bf2ffc in KJob::result (this=this@entry=0x55e667c20690,
_t1=, _t1@entry=0x55e667c20690, _t2=...) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#26 0x7fafc1bf739b in KJob::finishJob (this=0x55e667c20690,
emitResult=) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/src/lib/jobs/kjob.cpp:98
#27 0x7fafc1805393 in QtPrivate::QSlotObjectBase::call (a=0x7ffc86154a50,
r=0x55e667c20690, this=0x55e667b49490) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#28 doActivate (sender=0x55e667b44a60, signal_index=7,
argv=0x7ffc86154a50) at

[ark] [Bug 447954] New: ARK takes ages to start

2022-01-04 Thread bugzilla_noreply

https://bugs.kde.org/show_bug.cgi?id=447954

Bug ID: 447954
   Summary: ARK takes ages to start
   Product: ark
   Version: 21.12.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: damien.v.teyss...@outlook.com
CC: aa...@kde.org, rthoms...@gmail.com
  Target Milestone: ---

SUMMARY
ARK takes ages to start


STEPS TO REPRODUCE
1. Launch Ark (with or without a file to open)

OBSERVED RESULT
The Ark window takes 30+ seconds after start to appear

EXPECTED RESULT
Get the window immediately after starting the app

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.14.21-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 447556] Some wayland native games in KDE 5.23.4 crash instantly on startup

2022-01-04 Thread bugzilla_noreply

https://bugs.kde.org/show_bug.cgi?id=447556

nekone...@protonmail.ch changed:

   What|Removed |Added

 OS|Other   |Linux
   Keywords||usability, wayland
   Platform|Other   |Flatpak

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 447556] Some wayland native games in KDE 5.23.4 crash instantly on startup

2022-01-04 Thread bugzilla_noreply

https://bugs.kde.org/show_bug.cgi?id=447556

nekone...@protonmail.ch changed:

   What|Removed |Added

 CC||nekone...@protonmail.ch

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 446434] Adding an event to a calendar does not add anything

2022-01-04 Thread Claudio Cambra

https://bugs.kde.org/show_bug.cgi?id=446434

Claudio Cambra  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Claudio Cambra  ---
This is caused by having a local Akonadi instance running, when the
kdesrc-build Kalendar has been built against the most up-to-date Akonadi
version acquired through kdesrc-build.

You can stop your system's Akonadi instance with akonadictl stop. Running
kalendar with kdesrc-build will now work as intended.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 447953] New: Only the most recent selection appears on the sample titlebar, making it such that you can't see what you've got unless / until you hit apply.

2022-01-04 Thread Joe Carey

https://bugs.kde.org/show_bug.cgi?id=447953

Bug ID: 447953
   Summary: Only the most recent selection appears on the sample
titlebar, making it such that you can't see what
you've got unless / until you hit apply.
   Product: kde
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: joeca...@gmail.com
  Target Milestone: ---

Created attachment 145121
  --> https://bugs.kde.org/attachment.cgi?id=145121=edit
screenshot indicating areas of concern

SUMMARY
***
System Settings > Appearance> Window Decorations > Titlebar Buttons.
When trying to change the settings here and add or change the order of the
titlebar buttons, your pending selections do not properly appear.  Only the
most recent selection appears on the sample titlebar, making it such that you
can't see what you've got unless / until you hit apply.
***


STEPS TO REPRODUCE
1. Open System Settings > Appearance> Window Decorations > Titlebar Buttons.
2. Drag some buttons to the sample titlebar as if you were going to make a
change / add a new button


OBSERVED RESULT

If you share with me in experiencing this bug only  your most recent selection
will have appeared.

EXPECTED RESULT

It should show all your pending selection, ie. the changes that will take
effect upon clicking "Apply".


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 447945] Ability to continually show green markings indicating changes

2022-01-04 Thread Thiago Sueto

https://bugs.kde.org/show_bug.cgi?id=447945

Thiago Sueto  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from Thiago Sueto  ---
Indeed, and depending on git is probably a no-go for me. Now that I think of
it, perhaps it's possible to implement a better solution for the proofreading
problem with a plugin or adjusting my workflow. I'll see what I can do about it
later. Thank you for your time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 447952] Plasmashell eating up memory when screen locked

2022-01-04 Thread Andy

https://bugs.kde.org/show_bug.cgi?id=447952

--- Comment #1 from Andy  ---
Created attachment 145120
  --> https://bugs.kde.org/attachment.cgi?id=145120=edit
Valgrind output

Executed with: valgrind --leak-check=full --show-reachable=yes
--track-origins=yes --trace-children=yes --log-file=plasmashell.log plasmashell

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 447952] New: Plasmashell eating up memory when screen locked

2022-01-04 Thread Andy

https://bugs.kde.org/show_bug.cgi?id=447952

Bug ID: 447952
Summary: Plasmashell eating up memory when screen locked
Product: plasmashell
Version: 5.23.4
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: andreas.we...@silicoid.de
CC: plasma-b...@kde.org
Target Milestone: 1.0

Created attachment 145119
--> https://bugs.kde.org/attachment.cgi?id=145119=edit
Output of journalctl with grep for kernel and plasmashell

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

Whenever I lock my screen plamsashell starts to use more and more memory until
it gets killed by the kernel.
This doesn't happen if I switch the rendering backend from automatic to
software.

I did run valgrind to see if it logs anything, but unfortunately it didn't.

STEPS TO REPRODUCE
1. Set rendering backend to automatic (default)
2. Lock screen
3. Wait

OBSERVED RESULT
Eventually plasma will use up too much memory and the kernel will kill it.

EXPECTED RESULT
Plasma not using up memory

SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Kernel 5.15.12-1 Manjaro
NVidia driver version: 495.44

--
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 444136] Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen

2022-01-04 Thread Ryan Ronnander

https://bugs.kde.org/show_bug.cgi?id=444136

Ryan Ronnander  changed:

   What|Removed |Added

 CC||rronnan...@gmail.com

--- Comment #1 from Ryan Ronnander  ---
I've noticed similar behavior when moving to a triple monitor configuration
with one center horizontal monitor flanked by two vertical monitors a few weeks
ago. I believe it may also be related to using "Ctrl + D"  to exit Konsole.
When you close Konsole in this manner the "remember window position"
functionality does not appear to save on exit. 

I was able to reproduce this just now. Closing Konsole through kwin's titlebar
saves Konsole's position and size upon exit allowing Konsole to open as
expected during the next launch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 437970] ESPAÑOL cuando entro a krita todo anda bien el problema es que cuando dibujo en la tableta el lienzo se ve borroso. solo si estoy sin zoom, porque si agrando la imagen se ve bien

2022-01-04 Thread vanyossi

https://bugs.kde.org/show_bug.cgi?id=437970

vanyossi  changed:

   What|Removed |Added

 CC||ghe...@gmail.com
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #2 from vanyossi  ---
Please fill bug reports in english. And try to reply to further communications
in english.

What Krita version is this happening?, did you have your display properties
setup correctly? (check
https://docs.krita.org/en/reference_manual/preferences/display_settings.html?highlight=preferences%20display)
. Please attach information from "Ayuda -> mostrar información de sistema en
los informes de fallos".

Without any further information im afraid we cannot help you.

-- 
You are receiving this mail because:
You are watching all bug changes.

[libkdegames] [Bug 447863] flatpak build fails when using libkdegames

2022-01-04 Thread Albert Astals Cid

https://bugs.kde.org/show_bug.cgi?id=447863

--- Comment #7 from Albert Astals Cid  ---
personally i prefer building from tarballs, but i guess that would work

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 447951] New: Renaming to itself locks Kate

2022-01-04 Thread MisterE

https://bugs.kde.org/show_bug.cgi?id=447951

Bug ID: 447951
   Summary: Renaming to itself locks Kate
   Product: kate
   Version: 21.12.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: ed...@kleinmentink.com
  Target Milestone: ---

Created attachment 145118
  --> https://bugs.kde.org/attachment.cgi?id=145118=edit
Example

SUMMARY
Renaming to itself locks Kate

STEPS TO REPRODUCE
1. Open file
2. Select the tab -> right mouse -> rename
3. Leave the name as is and apply

OBSERVED RESULT
It locks (2 popups)


EXPECTED RESULT
It should not be possible to rename to itself

SOFTWARE/OS VERSIONS
Suse Tumbleweed

ADDITIONAL INFORMATION
See the movie

-- 
You are receiving this mail because:
You are watching all bug changes.

[libkdegames] [Bug 447863] flatpak build fails when using libkdegames

2022-01-04 Thread D Alexander

https://bugs.kde.org/show_bug.cgi?id=447863

--- Comment #6 from D Alexander  ---
Hmm Well I copied that from another flatpak project so ... my bad.. So this is
the sort of thing I should do , correct? 


```
"modules": [
{
"config-opts": [ "-DENABLE_TESTING=OFF" ],
"name": "libkdegames",
"buildsystem": "cmake-ninja",
"sources": [ { "type": "git", "url":
"https://anongit.kde.org/libkdegames.git;, "branch": "release/21.12" } ],
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 447950] New: Wayland and mouse cursor on XWayland windows

2022-01-04 Thread Alexandre Pereira

https://bugs.kde.org/show_bug.cgi?id=447950

Bug ID: 447950
   Summary: Wayland and mouse cursor on XWayland windows
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: pereira.a...@gmail.com
  Target Milestone: ---

Hi,

Since last week, using the wayland session with xwayland apps, the mouse cursor
icon does not work like normal. It was working perfectly fine a just before.

What happens: 

The mouse cursor in xwayland windows is always the same, even if I hover
something specific that used to change into another cursor (like for example
resizing).
It is also always "stuck", in that when a specific mouse cursor at entering the
window is set, it will be that mouse cursor until I leave the window. for
example, if the icon is at resize icon, it will always be that icon when I am
hovering the window.

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

1 2 3 >

1 - 100 of 291 matches

Mail list logo