date:20211221

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

--- Comment #6 from Maik Qualmann  ---
Please send a test video, if not public, to my email address. The best thing to
do is to film a watch to see if digiKam is detecting the correct time.

Maik

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

[kdenlive] [Bug 447342] Cannot export a frame

2021-12-21 Thread Sam Thibaut

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

--- Comment #1 from Sam Thibaut  ---
Fixed by setting up the OpenGl backend to Opengl ( was DirectX(ANGLE) )

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

[digikam] [Bug 415949] Can't write sidecar file if image file is a symlink to readonly directory [patch]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||7.5.0
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/digikam/commit/32ea05d
   ||81842a311dd11c6d983e895fc19
   ||d1da48

--- Comment #7 from Maik Qualmann  ---
Git commit 32ea05d81842a311dd11c6d983e895fc19d1da48 by Maik Qualmann.
Committed on 22/12/2021 at 07:18.
Pushed by mqualmann into branch 'master'.

write sidecar to the symlink if destination dir write protect
FIXED-IN: 7.5.0

M  +1-1NEWS
M  +23   -14   core/libs/metadataengine/engine/metaengine_fileio.cpp

https://invent.kde.org/graphics/digikam/commit/32ea05d81842a311dd11c6d983e895fc19d1da48

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

[okteta] [Bug 447373] New: Okteta (Snap) cannot open file on removable media

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

Bug ID: 447373
   Summary: Okteta (Snap) cannot open file on removable media
   Product: okteta
   Version: 0.26.6
  Platform: Snap
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kosse...@kde.org
  Reporter: 334wgc...@mozmail.com
  Target Milestone: ---

SUMMARY
Okteta (Snap) cannot open file on removable media (flash drive for example).
Try to resolve it by "snap connect okteta:removable-media" but failed with
```
error: snap "okteta" has no plug named "removable-media"
```

STEPS TO REPRODUCE
1. Install with "snap install okteta" 
2. Plug in a flash drive (mounted at /media//)
3. Using Files, browse the flash drive, right click on any file, choose Open
With, choose Okteta

OBSERVED RESULT
Okteta show error "Permission denied"

EXPECTED RESULT
Okteta open file successfully.

SOFTWARE/OS VERSIONS
Ubuntu 20.04.3 LTS
snap 2.53.4
okteta 0.26.6

ADDITIONAL INFORMATION
Found https://bugs.kde.org/show_bug.cgi?id=405713 that seem to be resolved, but
the problem still remain.

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

[digikam] [Bug 447354] Red eye tool creates empty image

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||7.5.0
 Resolution|--- |FIXED

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

[digikam] [Bug 432369] Wrong time for mp4 in _almost_ all places, metadata differs from filesystem/other apps. DB issues?

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||pmgy...@gmail.com

--- Comment #10 from Maik Qualmann  ---
*** Bug 447371 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 447371] Date of videos seems incorrect

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #5 from Maik Qualmann  ---


*** This bug has been marked as a duplicate of bug 432369 ***

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

[digikam] [Bug 447371] Date of videos seems incorrect

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #4 from Maik Qualmann  ---
The video date has a long history at digiKam. Yes, when we detect an Android
video, we use the time zone. You should then have the correct local time. We
have received test videos from users with logs of what time a video was
recorded and what digiKam detects. As a result, it was shown that the time zone
must be observed on an Android device.

Maik

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

[konversation] [Bug 447372] New: The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them....

2021-12-21 Thread John Riley

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

Bug ID: 447372
   Summary: The listed users and repositories cannot be searched
either because the resources do not exist or you do
not have permission to view them
   Product: konversation
   Version: unspecified
  Platform: Homebrew (macOS)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: rileyi...@gmail.com
  Target Milestone: ---

Created attachment 144778
  --> https://bugs.kde.org/attachment.cgi?id=144778=edit
The entire copy and paste from the Mac Terminal.

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
***


STEPS TO REPRODUCE
1.   brew install kde-mac/kde/konversation
2. 
3. 

OBSERVED RESULT

[8/124] cd /tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src &&
/usr/local/Cellar/cmake/3.22.1/bin/cmake -E cmake_autogen
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src/CMakeFiles/KF5XmlGui_autogen.dir/AutogenInfo.json
Release && /usr/local/Cellar/cmake/3.22.1/bin/cmake -E touch
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src/KF5XmlGui_autogen/timestamp
&& /usr/local/Cellar/cmake/3.22.1/bin/cmake -E cmake_transform_depfile Ninja
gccdepfile /tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/src
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src/KF5XmlGui_autogen/deps
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/CMakeFiles/d/68716d242549687c6c47d988432c4be78542d92ac9037136b18426c52902e1a8.d
ninja: build stopped: subcommand failed.

If reporting this issue please do so to (not Homebrew/brew or Homebrew/core):
  kde-mac/kde

/usr/local/Homebrew/Library/Homebrew/utils/github/api.rb:304:in `raise_error':
Validation Failed: [{"message"=>"The listed users and repositories cannot be
searched either because the resources do not exist or you do not have
permission to view them.", "resource"=>"Search", "field"=>"q",
"code"=>"invalid"}] (GitHub::API::ValidationFailedError)
from /usr/local/Homebrew/Library/Homebrew/utils/github/api.rb:234:in
`open_rest'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:166:in
`search'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:34:in
`search_issues'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:67:in
`issues_for_formula'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:491:in
`fetch_issues'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:487:in `issues'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:541:in `dump'
from /usr/local/Homebrew/Library/Homebrew/brew.rb:155:in `rescue in
'
from /usr/local/Homebrew/Library/Homebrew/brew.rb:143:in `'
/usr/local/Homebrew/Library/Homebrew/formula.rb:2307:in `block in system':
Failed executing: cmake --build build (BuildError)
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2243:in `open'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2243:in `system'
from
/usr/local/Homebrew/Library/Taps/kde-mac/homebrew-kde/Formula/kf5-kxmlgui.rb:25:in
`install'
from /usr/local/Homebrew/Library/Homebrew/build.rb:172:in `block (3
levels) in install'
from /usr/local/Homebrew/Library/Homebrew/utils.rb:588:in `with_env'
from /usr/local/Homebrew/Library/Homebrew/build.rb:134:in `block (2
levels) in install'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:1297:in `block in
brew'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2473:in `block (2
levels) in stage'
from /usr/local/Homebrew/Library/Homebrew/utils.rb:588:in `with_env'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2472:in `block in
stage'
from /usr/local/Homebrew/Library/Homebrew/resource.rb:126:in `block (2
levels) in unpack'
from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:115:in
`chdir'
from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:115:in
`chdir'
from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:102:in
`stage'
from /usr/local/Homebrew/Library/Homebrew/resource.rb:122:in `block in
unpack'
from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `block in
run'
from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `chdir'
from /usr/local/Homebrew/Library/Homebre

[digikam] [Bug 447371] Date of videos seems incorrect

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

--- Comment #3 from caulier.gil...@gmail.com ---
Arf, sorry, i just seen that you use Windows, not Linux... Forget my previous
comment (:=)))

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

[digikam] [Bug 447371] Date of videos seems incorrect

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

--- Comment #2 from caulier.gil...@gmail.com ---
Video dates are take by digiKam using ffmpeg. You ca double check from CLI
using "ffmpeg -i video_file"
By comparison, look also the result with ExifTool from CLI.

Gilles Caulier

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

[digikam] [Bug 447370] GPS Processing Method tag is incorrectly read as Caption tag

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
There is no relation between GPS Processing Method tags and Caption contents.
digiKam never use GPS tags to populate caption entry in database.

This is certainly a side effect of Exiv2 library which cannot interpret the
comment from Exif and do not push the data in RAW but a tag content format as
ASCII.

I remember a similar old bug coming from Exiv2. Which version did you use
exactly ? Look in Help/Components Info dialog for details.

Gilles Caulier

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

[digikam] [Bug 447371] Date of videos seems incorrect

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

--- Comment #1 from pmgy...@gmail.com ---
I would like to add that the dates of videos during EDT (datelight saving time
: -4) is exactly 4 hours ahead.
And the ones now (EST: -5) are exactly 5 hours ahead.
So it must be caused by timezone interpretation issue.

(Sorry if this is not digikam's issue. Since I have no other means to check
EXIF data, I can only trust Google Photo App or DigiKam. And Google photo app
is showing the right time to me.)

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

[digikam] [Bug 447371] Date of videos seems incorrect

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|Metadata-Exif   |Metadata-Video
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 447371] New: Date of videos seems incorrect

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

Bug ID: 447371
   Summary: Date of videos seems incorrect
   Product: digikam
   Version: 7.4.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Exif
  Assignee: digikam-bugs-n...@kde.org
  Reporter: pmgy...@gmail.com
  Target Milestone: ---

Dates in metadata (e.g. EXIF date and time values) in images seems *correct*.
However, dates of videos (EXIF "Date and Time" variances, ExifTool
"MediaCreateDate" etc.) seems to be incorrect.
More specifically, it looks like the date values of videos are bumped up by my
timezone.
e.g. I am on EST (-5). If a video is taken at 01:20, the values appear in
digikam becomes 06:20.

The photos/videos are taken on an Android phone.
Checking the date information in Google Photo, and the dates looks correct to
me.

STEPS TO REPRODUCE
1. Browse a video
2. Look at the date values in Metadata

OBSERVED RESULT
Most Date/Times are "time zone hours" ahead, i.e. the time in photo seems to be
treated as UTC if it is not coincident.
The only correct dates I see are "File*Date" under "ExifTool"

EXPECTED RESULT
Date/Time should be correct.

SOFTWARE/OS VERSIONS
Windows: 10

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

[digikam] [Bug 447370] New: GPS Processing Method tag is incorrectly read as Caption tag

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

Bug ID: 447370
   Summary: GPS Processing Method tag is incorrectly read as
Caption tag
   Product: digikam
   Version: 7.1.0
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Exif
  Assignee: digikam-bugs-n...@kde.org
  Reporter: hieutv2...@gmail.com
  Target Milestone: ---

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

For some reason, digiKam reads GPS Processing Method tag as Caption of the
photo. Please see the attached screenshot. After manually clearing the caption
some time, that "ASCII" text just reappears out of nowhere.

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

[konsole] [Bug 446830] Konsole crashes when splitting a window

2021-12-21 Thread Bernie Innocenti

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

--- Comment #2 from Bernie Innocenti  ---
#4  0x77d2a7ef in Konsole::ViewManager::splitView (this=0x55827c20,
orientation=Qt::Horizontal)
at /home/bernie/kde/src/konsole/src/ViewManager.cpp:603
603 Q_ASSERT(currentSessionId >= 0);
(gdb) list
598
599 void ViewManager::splitView(Qt::Orientation orientation)
600 {
601 int currentSessionId = currentSession();
602 // At least one display/session exists if we are splitting
603 Q_ASSERT(currentSessionId >= 0);
604
605 Session *activeSession =
SessionManager::instance()->idToSession(currentSessionId);
606 Q_ASSERT(activeSession);
607
(gdb) p currentSessionId
$1 = -1

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

[konsole] [Bug 446830] Konsole crashes when splitting a window

2021-12-21 Thread Bernie Innocenti

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

Bernie Innocenti  changed:

   What|Removed |Added

 CC||ber...@codewiz.org
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Bernie Innocenti  ---
I was able to reproduce this with konsole built from git master:

(gdb) r
Starting program: /home/bernie/kde/usr/bin/konsole 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffefefc640 (LWP 226434)]
QIBusPlatformInputContext: invalid portal bus.
QSocketNotifier: Can only be used with threads started with QThread
[New Thread 0x7fffe17d1640 (LWP 226436)]
[New Thread 0x7fffe0fd0640 (LWP 226437)]
[New Thread 0x7fffdbfff640 (LWP 226438)]
[New Thread 0x7fffdb7fe640 (LWP 226439)]
[New Thread 0x7fffdaffd640 (LWP 226440)]
[New Thread 0x7fffda7fc640 (LWP 226441)]
[New Thread 0x7fffd9ffb640 (LWP 226442)]
[New Thread 0x7fffd97fa640 (LWP 226443)]
[New Thread 0x7fffd8ff9640 (LWP 226444)]
[Detaching after fork from child process 226445]
[New Thread 0x7fffabc95640 (LWP 226467)]
[Detaching after fork from child process 226468]
[Detaching after fork from child process 226470]
[Detaching after fork from child process 226472]
[Detaching after fork from child process 226474]
[Detaching after fork from child process 226476]
[Detaching after fork from child process 226478]
QIBusPlatformInputContext: invalid portal bus.
QSocketNotifier: Can only be used with threads started with QThread
[Detaching after fork from child process 226492]
[Detaching after fork from child process 226494]
[Detaching after fork from child process 226496]
[Detaching after fork from child process 226499]
[Detaching after fork from child process 226501]
[Detaching after fork from child process 226544]
[Detaching after fork from child process 226545]
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x55c37360) which does not match the
current topmost grabbing popup,
QtWaylandClient::QWaylandXdgSurface(0x56289160) According to the xdg-shell
protocol, this is not allowed. The wayland QPA plugin is currently handling it
by setting the parent to the topmost grabbing popup. Note, however, that this
may cause positioning errors and popups closing unxpectedly because xdg-shell
mandate that child popups close before parents
ASSERT: "currentSessionId >= 0" in file
/home/bernie/kde/src/konsole/src/ViewManager.cpp, line 603

Thread 1 "konsole" received signal SIGABRT, Aborted.
0x74bd9d22 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x74bd9d22 in raise () from /usr/lib/libc.so.6
#1  0x74bc3862 in abort () from /usr/lib/libc.so.6
#2  0x7516e910 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
#3  0x7516dcf5 in qt_assert(char const*, char const*, int) () from
/usr/lib/libQt5Core.so.5
#4  0x77d2a7ef in Konsole::ViewManager::splitView (this=0x55827c20,
orientation=Qt::Horizontal)
at /home/bernie/kde/src/konsole/src/ViewManager.cpp:603
#5  0x77d2a77b in Konsole::ViewManager::splitLeftRight
(this=0x55827c20) at /home/bernie/kde/src/konsole/src/ViewManager.cpp:591
#6  0x77d38176 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void (Konsole::ViewManager::*)()>::call(void
(Konsole::ViewManager::*)(), Konsole::ViewManager*, void**) (
f=(void (Konsole::ViewManager::*)(Konsole::ViewManager * const))
0x77d2a75e , o=0x55827c20, 
arg=0x7fffc8b0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152
#7  0x77d375c0 in QtPrivate::FunctionPointer::call, void>(void
(Konsole::ViewManager::*)(), Konsole::ViewManager*, void**) (f=(void
(Konsole::ViewManager::*)(Konsole::ViewManager * const)) 0x77d2a75e
, 
o=0x55827c20, arg=0x7fffc8b0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:185
#8  0x77d3617d in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x55831810, r=0x55827c20, a=0x7fffc8b0, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:418
#9  0x753ce7cb in ?? () from /usr/lib/libQt5Core.so.5
#10 0x760a4203 in QAction::triggered(bool) () from
/usr/lib/libQt5Widgets.so.5
#11 0x760a6f18 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/libQt5Widgets.so.5
#12 0x76234103 in ?? () from /usr/lib/libQt5Widgets.so.5
#13 0x7623be39 in ?? () from /usr/lib/libQt5Widgets.so.5
#14 0x760ee0be in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#15 0x760aad62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#16 0x760b2ac9 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#17

[konsole] [Bug 442371] Split-View windows can vanish

2021-12-21 Thread Bernie Innocenti

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

Bernie Innocenti  changed:

   What|Removed |Added

 CC||ber...@codewiz.org

--- Comment #2 from Bernie Innocenti  ---
Reproduced on konsole built from git master.

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

[okular] [Bug 445883] Okular crashes when trying to save a documents on a CIFS-backed mount

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 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.

[Koko] [Bug 447369] New: Image previews not updating after editing image

2021-12-21 Thread Phos

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

Bug ID: 447369
   Summary: Image previews not updating after editing image
   Product: Koko
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: unassigned-b...@kde.org
  Reporter: phosph0phyll...@yandex.com
CC: n...@kde.org
  Target Milestone: ---

SUMMARY
After editing an image in koko (ex cropping), the previews are not updated


STEPS TO REPRODUCE
1. Crop image
2. Save image
3. Notice that the preview on the bottom is not updated

OBSERVED RESULT
Image previews are not updated

EXPECTED RESULT
Image previews should be updated

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.10-zen1-1-zen (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Installed from AUR using koko-git v21.12.r3.gc447d10-1

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

[kinfocenter] [Bug 445861] Distro icon missing from kinfocenter after upgrading

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 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.

[Plasma Vault] [Bug 446552] The context menu actions don't refresh the dolphin folder

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

--- Comment #5 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.

[systemsettings] [Bug 446613] Feature request for changing the application specific theme in plasma.

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

--- Comment #2 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.

[kmymoney] [Bug 445721] AqBanking crash while Setting up American Express Account

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #11 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.

[frameworks-kwallet] [Bug 446538] Kwalletd does not start, Icon theme "gnome" not found.

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

--- Comment #2 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.

[systemsettings] [Bug 444993] Incorrect ColorScheme set in kdeglobals after applying Breeze Dark Global Theme

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

--- Comment #9 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.

[systemsettings] [Bug 447058] Unable to add Login Script, or run scripts after Login

2021-12-21 Thread Winston Nolan

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

--- Comment #10 from Winston Nolan  ---
Just dropping the fix here

I created a script with the contents

```
#!/usr/bin/env bash
# https://unix.stackexchange.com/a/361612/386718
dbus-monitor --session "type='signal',interface='org.freedesktop.ScreenSaver'"
|
  while read x; do
case "$x" in 
  *"boolean true"*) /usr/bin/sleep 1;;
  *"boolean false"*) /usr/bin/sleep 1 && /usr/bin/latte-dock --replace &;;  
esac
  done
```

I added this script to be executed at startup

This script will listen to events for lock and unlock and restart latte dock on
an unlock event

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

[kate] [Bug 447368] New: Move Spell Check Suggestions to top of top level menu

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

Bug ID: 447368
   Summary: Move Spell Check Suggestions to top of top level menu
   Product: kate
   Version: 21.12.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: pqwoerituytruei...@gmail.com
  Target Milestone: ---

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

SUMMARY
In every piece of software I have used with spellcheck support corrections are
at the top of the top level menu, there should at the very least be a option to
do this in kate, normally when someone right clicks a word detected as a
spelling error they want to see the corrections

In geany this sub menu appears at the top of the list, this never bugged me
cause i never thought about it cause it was at the top, but this bugs me to no
end

no body could tell me where any suck option is, so i assume there is none
https://www.reddit.com/r/kde/comments/rjbd6r/move_kate_spell_check_suggestions/

STEPS TO REPRODUCE
1. right click a typo
2. wonder where my corrections are cause why would they be 1/2 way down the
menu and fail to comprehended the use case for why they would be there

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.16.0-051600rc6-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: Radeon RX 580 Series

ADDITIONAL INFORMATION

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

[krita] [Bug 447367] New: The pop-up interface is abnormal

2021-12-21 Thread thetwo

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

Bug ID: 447367
   Summary: The pop-up interface is abnormal
   Product: krita
   Version: 5.0.0-beta5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: thetwo...@foxmail.com
  Target Milestone: ---

Created attachment 144775
  --> https://bugs.kde.org/attachment.cgi?id=144775=edit
Flashing problem gif cannot be recorded

SUMMARY

When krita produced pop-up interfaces (brush interface, pop-up window to close
the document, etc.), I found that the outer edge projection flickered very
seriously.
The most serious impact is the pop-up interface. Right-click has a certain
probability to directly lock the brush parameters.
I asked a friend who used the 5.1 beta, and he said that this problem still
exists

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

[systemsettings] [Bug 447366] New: Screen locking should be referenced (linked or inserted) under power management

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

Bug ID: 447366
   Summary: Screen locking should be referenced (linked or
inserted) under power management
   Product: systemsettings
   Version: 5.23.4
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_powerdevil
  Assignee: plasma-b...@kde.org
  Reporter: pqwoerituytruei...@gmail.com
CC: k...@privat.broulik.de
  Target Milestone: ---

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

SUMMARY
I think most people associate screen power saving with screen locking and it
may not occurs to some that these are actually separate things (see screenshot
of both sections)

Options I can think of (not all are good):
* Merge these 2 sections
* each can link to the other via a looking for Screen Locking/Power
management/screensaver button
* insert each into the other (this seems redundant)
* show both screen locking and power management when searching for either

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.16.0-051600rc6-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: Radeon RX 580 Series

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

[Discover] [Bug 419504] Auto restart after installing updates

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

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/discover/-/merge_requests/221

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

[frameworks-kirigami] [Bug 447365] New: Side menu buttons disappear and stay invisible after switching globalToolBar.style from None to any other value and back to None

2021-12-21 Thread Javier O . Cordero Pérez

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

Bug ID: 447365
   Summary: Side menu buttons disappear and stay invisible after
switching globalToolBar.style from None to any other
value and back to None
   Product: frameworks-kirigami
   Version: 5.86.0
  Platform: Compiled Sources
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: javiercorderope...@gmail.com
  Target Milestone: Not decided

SUMMARY
Side menu buttons, used to access global and context menus, disappear and stay
invisible after switching globalToolBar.style from None to any other valid
value and back to None.

STEPS TO REPRODUCE
1. Assign `pageStack.globalToolBar.style` to a condition where
`Kirigami.ApplicationHeaderStyle.None` is the initial value. 
> property bool toggleMeValue: false
> pageStack.globalToolBar.style: toggleMeValue ? 
> Kirigami.ApplicationHeaderStyle.Titles : Kirigami.ApplicationHeaderStyle.None
2. Provide a way to change the previous condition, so that any other style is
used.
> MouseArea {
> anchors.fill: parent
> onClicked: toggleMeValue = !toggleMeValue
> }
3. Run the program. Toggle from None to alternate style, see menu buttons
disappear as intended.
4. Toggle from alternate style back to None, buttons will be re-instantiated
but they will not be visible.

OBSERVED RESULT
Kirigami menu buttons disappear and return as intended, but will remain
invisible upon returning.

EXPECTED RESULT
Kirigami menu buttons should be visible upon being re-instantiated.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Craft with MSVC compiler
macOS: macOS Monterey Craft with Clang x86 compiler
Linux/KDE Plasma: KDE Neon Craft with both GCC and Clang compilers
Android: Android 12, with GCC compiler
KDE Plasma Version: 5.23.4 (testing branches, host Linux system)
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2 and 5.15.3

ADDITIONAL INFORMATION
When using Qt's Material theme, a shadow is visible where the buttons are
placed, but the buttons themselves remain invisible. Under Plasma Mobile there
are no shadows surrounding the buttons, therefore when the buttons return,
there is no way to tell they've been re-instantiated.

https://github.com/Cuperino/QPrompt/releases/tag/v1.0.0-beta-006
You can see this bug in action in the latest beta of my project, QPrompt
v1.0.0-beta-006. If I've done something wrong in my use of
pageStack.globalToolBar.style, please let me know.

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

[systemsettings] [Bug 447364] New: Unable to set current time manually

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

Bug ID: 447364
   Summary: Unable to set current time manually
   Product: systemsettings
   Version: 5.23.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_clock
  Assignee: p...@taniwha.com
  Reporter: ian.eric@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 144773
  --> https://bugs.kde.org/attachment.cgi?id=144773=edit
Unable to set current time manually

SUMMARY
Error when disabling "Set date and time automatically" 

Error: Unable to set current time


STEPS TO REPRODUCE
1. Open system settings > regional settings > Date & time.  
2. Untick "Set date and time automatically".
3. click apply. 

OBSERVED RESULT
Error: Unable to set current time

EXPECTED RESULT
manual date and time will take effect.

SOFTWARE/OS VERSIONS 
Linux: 5.15.10-arch1-1 (64-bit)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor

2021-12-21 Thread BeatLink

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

--- Comment #14 from BeatLink  ---
Additionally, there could be an option to allow the user to choose between
manipulating the gamma levels and the backlight levels. Both should be rather
easy to implement since KCM should have access to these options already from
its brightness applet and display modules

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

[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland

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

--- Comment #13 from Andrey  ---
(In reply to Conrad from comment #12)
> Figured out the problem. It was caused by ~/.config/kcminputrc and more
> precisely by these lines:
> 
> [Keyboard]
> KeyRepeat=repeat
> NumLock=0
> RepeatDelay=600
> RepeatRate=25
> 
> It must have been created by some older version of kde/plasma.

Hmm, what exactly the key causing this? We probably need to sort it out in
upgrade scripts, then..

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

[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor

2021-12-21 Thread BeatLink

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

BeatLink  changed:

   What|Removed |Added

 CC||beatlink+kdebugs@simplelogi
   ||n.co

--- Comment #13 from BeatLink  ---
I am 100% for this feature request.

Many studies have shown that not only the screen color temperature can affect
sleep, but the screen brightness as well. In fact, some studies, such as this
one: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6751071/ found that screen
brightness had a greater effect on sleep than even the color temperature

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on Intel RAID/NTFS volume scan

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

Ihor  changed:

   What|Removed |Added

Summary|KDE Partition Manager   |KDE Partition Manager
   |delays for several minutes  |delays for several minutes
   |on USB flash scan   |on Intel RAID/NTFS volume
   ||scan

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on USB flash scan

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

--- Comment #7 from Ihor  ---
(In reply to Andrius Štikonas from comment #5)
> ntfsinfo --mft --force deviceNode
> 
> Can you check if this command works fast? We can then switch to it too.

It works almost instantly:

-
time sudo ntfsinfo --mft --force /dev/md124p1
Volume Information 
Name of device: /dev/md124p1
Device state: 11
Volume Name: Media
Volume State: 91
Volume Flags: 0x
Volume Version: 3.1
Sector Size: 512
Cluster Size: 4096
Index Block Size: 4096
Volume Size in Clusters: 443812216
MFT Information 
MFT Record Size: 1024
MFT Zone Multiplier: 0
MFT Data Position: 24
MFT Zone Start: 441274685
MFT Zone End: 443008326
MFT Zone Position: 441274685
Current Position in First Data Zone: 443008326
Current Position in Second Data Zone: 0
Allocated clusters 493056 (0,1%)
LCN of Data Attribute for FILE_MFT: 441274685
FILE_MFTMirr Size: 4
LCN of Data Attribute for File_MFTMirr: 88294
Size of Attribute Definition Table: 2560
Number of Attached Extent Inodes: 0
FILE_Bitmap Information 
FILE_Bitmap MFT Record Number: 6
State of FILE_Bitmap Inode: 80
Length of Attribute List: 0
Number of Attached Extent Inodes: 0
FILE_Bitmap Data Attribute Information
Decompressed Runlist: not done yet
Base Inode: 6
Attribute Types: not done yet
Attribute Name Length: 0
Attribute State: 3
Attribute Allocated Size: 55480320
Attribute Data Size: 55476528
Attribute Initialized Size: 55476528
Attribute Compressed Size: 0
Compression Block Size: 0
Compression Block Size Bits: 0
Compression Block Clusters: 0
Free Clusters: 283662933 (63,9%)
sudo ntfsinfo --mft --force /dev/md124p1  0,06s user 0,04s system 14% cpu 0,713
total
-(In
reply to Andrius Štikonas from comment #6)

> Also partition size might be wrong because nobody worked on RAID support for
> partitionmanager. So something might be going wrong there.

Intel RAID (half-software) could be harder to implement than real hardware RAID
(hardware controller shows it to system as single volume).

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

[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start

2021-12-21 Thread Eugene

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

--- Comment #39 from Eugene  ---
Anyone can test it now fron attachment. Now how can we pull it in main
codebase? I don't understand all thouse programming rules.

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

[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start

2021-12-21 Thread Eugene

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

--- Comment #38 from Eugene  ---
Created attachment 144772
  --> https://bugs.kde.org/attachment.cgi?id=144772=edit
yakuake compiled with patch

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

[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start

2021-12-21 Thread Eugene

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

--- Comment #37 from Eugene  ---
(In reply to trmdi from comment #35)
> Can anyone who heavily uses Yakuake test the patch in the comment 32?

Recently I tried to compile yakuake with that additional string in patch and it
weems it works well.

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

[okular] [Bug 447363] Kile crashes in Okular::Page::formFields() when rapidly switching between tabs using the keyboard shortcut

2021-12-21 Thread Nate Graham

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

Nate Graham  changed:

   What|Removed |Added

  Component|general |general
Version|2.9.93  |unspecified
   Assignee|michel.lud...@kdemail.net   |okular-de...@kde.org
Product|kile|okular

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

[kile] [Bug 447363] New: Kile crashes in Okular::Page::formFields() when rapidly switching between tabs using the keyboard shortcut

2021-12-21 Thread Nate Graham

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

Bug ID: 447363
   Summary: Kile crashes in Okular::Page::formFields() when
rapidly switching between tabs using the keyboard
shortcut
   Product: kile
   Version: 2.9.93
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: n...@kde.org
  Target Milestone: ---

Application: kile (2.9.93)
 (Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.15.7-200.fc35.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 35 (KDE Plasma)
DrKonqi: 5.23.80 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:

Rapidly switching between open tabs using the keyboard shortcut (Alt+arrows by
default)

The crash can be reproduced every time.

-- Backtrace:
Application: Kile (kile), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5  QLinkedList::QLinkedList (l=, this=0x7ffd5bd86768,
this@entry=0x7f2ebf13a59e ) at
/usr/include/qt5/QtCore/qlinkedlist.h:99
#6  Okular::Page::formFields (this=0x0) at
/home/nate/kde/src/okular/core/page.cpp:514
#7  0x7f2ea89a8f29 in SignatureGuiUtils::getSignatureFormFields
(doc=, allPages=allPages@entry=true, pageNum=pageNum@entry=-1)
at /home/nate/kde/src/okular/part/signatureguiutils.cpp:23
#8  0x7f2ea89aca83 in SignaturePanel::notifySetup (setupFlags=, this=0x8c24920) at /home/nate/kde/src/okular/part/signaturepanel.cpp:114
#9  SignaturePanel::notifySetup (this=0x8c24920, setupFlags=) at
/home/nate/kde/src/okular/part/signaturepanel.cpp:108
#10 0x7f2ea87bd10a in Okular::Document::closeDocument (this=0x8a31a00) at
/home/nate/kde/src/okular/core/document.cpp:2558
#11 Okular::Document::closeDocument (this=0x8a31a00) at
/home/nate/kde/src/okular/core/document.cpp:2486
#12 0x7f2ea88f0384 in Okular::Part::closeUrl (this=0x8a11590,
promptToSave=) at /home/nate/kde/src/okular/part/part.cpp:1894
#13 0x7f2ec0ff3907 in KileTool::LivePreviewManager::clearLivePreview
(this=0xa394130) at /home/nate/kde/src/kile/src/livepreview.cpp:362
#14 0x7f2ec0ffa5f0 in KileTool::LivePreviewManager::handleTextViewActivated
(this=0xa394130, view=0xa727240, clearPreview=,
forceCompilation=) at
/home/nate/kde/src/kile/src/livepreview.cpp:1087
#15 0x7f2ebe663430 in doActivate (sender=0x8a21540, signal_index=6,
argv=0x7ffd5bd86a30) at kernel/qobject.cpp:3898
#16 0x7f2ebe65e367 in QMetaObject::activate (sender=,
m=m@entry=0x7f2ec11856a0 ,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd5bd86a30)
at kernel/qobject.cpp:3946
#17 0x7f2ec0e3f3d2 in KileView::Manager::textViewActivated (this=, _t1=) at
/home/nate/kde/build/kile/src/kdeinit_kile_autogen/EWIEGA46WW/moc_kileviewmanager.cpp:740
#18 0x7f2ebe6633e9 in QtPrivate::QSlotObjectBase::call (a=0x7ffd5bd86b40,
r=, this=0xa175730) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#19 doActivate (sender=0xa172460, signal_index=7, argv=0x7ffd5bd86b40)
at kernel/qobject.cpp:3886
#20 0x7f2ebe65e367 in QMetaObject::activate (sender=,
m=m@entry=0x7f2ebf63c4e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd5bd86b40)
at kernel/qobject.cpp:3946
#21 0x7f2ebf2c2092 in QTabBar::currentChanged (this=,
_t1=) at .moc/moc_qtabbar.cpp:338
#22 0x7f2ebe6633e9 in QtPrivate::QSlotObjectBase::call (a=0x7ffd5bd86c60,
r=, this=0xa3bc3c0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0xa3bc740, signal_index=4, argv=0x7ffd5bd86c60)
at kernel/qobject.cpp:3886
#24 0x7f2ebe65e367 in QMetaObject::activate (sender=sender@entry=0xa3bc740,
m=m@entry=0x7f2ebf62b260 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd5bd86c60)
at kernel/qobject.cpp:3946
#25 0x7f2ebf0fd916 in QAction::triggered (this=this@entry=0xa3bc740,
_t1=) at .moc/moc_qaction.cpp:376
#26 0x7f2ebf10062c in QAction::activate (this=0xa3bc740, event=) at kernel/qaction.cpp:1161
#27 0x7f2ebf101217 in QAction::event (e=, this=) at kernel/qaction.cpp:1086
#28 QAction::event (this=, e=) at
kernel/qaction.cpp:1075
#29 0x7f2ebf104443 in QApplicationPrivate::notify_helper (this=, receiver=0xa3bc740, e=0x7ffd5bd86e10) at kernel/qapplication.cpp:3632
#30 0x7f2ebe62f7d8 in QCoreApplication::notifyInternal2
(receiver=0xa3bc740, event=0x7ffd5bd86e10) at kernel/qcoreapplication.cpp:1064
#31 0x7f2ebeaacf32 in QShortcutMap::dispatchEvent (this=,
e=) at kernel/qshortcutmap.cpp:675
#32 0x7f2ebeaad5a3 in QShortcutMap::tryShortcut (this=this@entry=0x1bc6118,
e=e@entry=0x7ffd5bd86ed0) at kernel/qshortcutmap.cpp:343
#33 0x7f2ebea640a7 in

[konversation] [Bug 446673] Channel Settings, Modes tab "User Limit" QSpinBox uses default max=99, messing up any higher setting by /cmode +l NNN

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/netw
   ||ork/konversation/commit/074
   ||f80e2dcefdc6cd0b68714021481
   ||ee35b7df30
 Resolution|--- |FIXED
   Version Fixed In||1.8.21121
 Status|ASSIGNED|RESOLVED

--- Comment #2 from Friedrich W. H. Kossebau  ---
Git commit 074f80e2dcefdc6cd0b68714021481ee35b7df30 by Friedrich W. H.
Kossebau.
Committed on 18/12/2021 at 23:27.
Pushed by kossebau into branch 'release/21.12'.

Channel Settings UI: bump max value of "User limit" to 9

Max value was the default 99, which would result in...
a) any higher value read from the channel mode being reset to 99
b) not allow users to set higher values if wanted.

As applying the channel settings from the dialog always picks all the
values of the dialog, also those not edited, in case of a) this also
would mean changing the user limit in the channel to 99 then.

RFCs are not known to define a max user limit, so this is server defined.
While there is no path explored to query any max user limit capabilities,
and servers implementations seems to just map too high numbers to random
possible ones, there is no well defined max value to be used for the
dialog.

Using 9 as arbitrary value should serve for now all expected use-cases.
To be raised later if there is respective feedback.

FIXED-IN: 1.8.21121

M  +3-0src/viewer/channeloptionsui.ui

https://invent.kde.org/network/konversation/commit/074f80e2dcefdc6cd0b68714021481ee35b7df30

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

[plasmashell] [Bug 442970] Opening a large zip file with kickoff hangs plasmashell and floods systemd journal

2021-12-21 Thread Fushan Wen

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

Fushan Wen  changed:

   What|Removed |Added

 CC||qydwhotm...@gmail.com

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

[systemsettings] [Bug 447362] Feature Request: Auto dark/light theme

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

--- Comment #1 from romula...@protonmail.com ---
*With Night Color Control changing making it darker/lighter depending on the
time.

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

[systemsettings] [Bug 447362] Feature Request: Auto dark/light theme

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

romula...@protonmail.com changed:

   What|Removed |Added

Summary|Auto dark/light theme   |Feature Request: Auto
   ||dark/light theme

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

[systemsettings] [Bug 447362] New: Auto dark/light theme

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

Bug ID: 447362
   Summary: Auto dark/light theme
   Product: systemsettings
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_desktoptheme
  Assignee: plasma-b...@kde.org
  Reporter: romula...@protonmail.com
  Target Milestone: ---

With night color control turning it night/day.

Thoughts?

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

[kwin] [Bug 422841] OSD causes window focus to briefly change

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

--- Comment #9 from natalie_clar...@yahoo.de ---
The OSD pops up in the right place for me though.

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

[kwin] [Bug 422841] OSD causes window focus to briefly change

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

natalie_clar...@yahoo.de changed:

   What|Removed |Added

 CC||natalie_clar...@yahoo.de

--- Comment #8 from natalie_clar...@yahoo.de ---
It's not just Wayland, I'm having the same issue on X11. Plasma 5.23.4 with
Framework 5.88.0 on Arch, and didn't have the problem before 5.23 iirc.

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on USB flash scan

2021-12-21 Thread Andrius Štikonas

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

--- Comment #6 from Andrius Štikonas  ---
Also partition size might be wrong because nobody worked on RAID support for
partitionmanager. So something might be going wrong there.

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on USB flash scan

2021-12-21 Thread Andrius Štikonas

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

--- Comment #5 from Andrius Štikonas  ---
(In reply to Ihor from comment #2)
> gparted detects it correctly
> 
Looks like these days gparted uses ntfsinfo command to read used sectors (I
think ntfsinfo command is somewhat newer and wasn't available when ntfs support
was added). Gparted seems to run

ntfsinfo --mft --force deviceNode

Can you check if this command works fast? We can then switch to it too.

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on USB flash scan

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

--- Comment #4 from Ihor  ---
Created attachment 144771
  --> https://bugs.kde.org/attachment.cgi?id=144771=edit
gparted has no problem detecting partition size correctly

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on USB flash scan

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

--- Comment #3 from Ihor  ---
Created attachment 144770
  --> https://bugs.kde.org/attachment.cgi?id=144770=edit
partitionmanager incorrectly detects partition size, which is lower than used
size

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on USB flash scan

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

--- Comment #2 from sytn...@gmail.com ---
(In reply to Andrius Štikonas from comment #1)
> Try running partitoinmanager with
> 
> KPMCORE_DEBUG=y partitionmanager
> 
> It will print list of commands that it is executing. Unfortunately without
> timestamps but you should still be able to visually see if one command takes
> a long time. (I suspect it might be udevadm)

Thanks, I got timestamps with this command
KPMCORE_DEBUG=y partitionmanager 1>&1 2>&1 | gnomon --high=10  

That wasn't SMI flash drive responsible, but ntfsresize command that runs every
time so long:
 121.7743s   "Command: ntfsresize --info --force --no-progress-bar
/dev/md124p1"

md124p is ICH10R "half-software" RAID0 MBR volume based on two WD RE3 drives
md124p1 is NTFS partition of 1.65 TB which was resized some time ago by EaseUS
in Windows. 
chkdsk doesn't find errors prior running partitionmanager 
partitionmanager incorrectly detects its total size (total size is lower than
used size)
gparted detects it correctly

PS: manjaro was successfully installed via manjaro-architect

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

[dolphin] [Bug 447321] When dolphin opens, all 4 panels are open, and the whole window is small (quarter of screen); also for windows opened by restore of saved session; new in v 21.12.

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

--- Comment #4 from radi...@gmail.com ---
Of the 14 dolphin windows that I left open last night, before saving the
session,
10 were restored occupying the whole screen (in normal mode, not fullscreen)
although I had left most of them at about 90% of screenwidth.
The other 4 are full width but half height.
All 14 have all 4 panels open.

It seems that the mechanism  for saving and restoring
window size and postion  is now rather random.

I had 1 window of PCmanFM-Qt open last night,
and it was restored with the right size and position today,
but the tabs within it were completely lost, so that's no use to me.

I use Dolphin because Thunar and PCmanFM crashed regularly,
and I use Plasma because I can save multiple Dolphin windows as a session.

The file manager has always been at the core of how I use a PC,
since Windows in 1995, through Xubuntu 2009-2017, then Manjaro KDE until now.

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

[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start

2021-12-21 Thread Robby Engelmann

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

--- Comment #36 from Robby Engelmann  ---
I am using Yakuake, but do not know, how to test it...

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

[plasmashell] [Bug 445481] Notification shows mount point while Dolphin copies data to usb removable device for the first time after login

2021-12-21 Thread Kai Uwe Broulik

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

--- Comment #2 from Kai Uwe Broulik  ---
I suppose the KFilePlacesModel, which is created when a job is created, updated
asynchronously after the job text has already been queried and since there is
only a single file, the text does not update.

Listening to KFilePlacesModel signals and updating the text live has been on my
agenda for a while but was blocked on the model not emitting signals properly,
which was fixed recently iirc.

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

[plasmashell] [Bug 446431] Automatic do not disturb reason can be confusing

2021-12-21 Thread Kai Uwe Broulik

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

--- Comment #3 from Kai Uwe Broulik  ---
xdg-desktop-portal doesn't know the app (or rather, it doesn't trust it to
claim who it is) when it is not sandboxed. This is a limitation (design choice)
on their end.

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

[frameworks-kio] [Bug 445764] Option to display full path of moved file source / destination in the notification's applet

2021-12-21 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

  Component|Notifications   |general
 CC||kdelibs-b...@kde.org
   Target Milestone|1.0 |---
   Assignee|k...@privat.broulik.de   |kio-bugs-n...@kde.org
Product|plasmashell |frameworks-kio
Version|5.23.3  |5.89.0

--- Comment #3 from Kai Uwe Broulik  ---
The maximum line count is 5, actually, which should be plenty.

The truncation you're seeing here happens in KIO. This was mostly done to avoid
sending multi-megabytes of data: URLs around.

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

[Discover] [Bug 447361] New: on Fedora 35, plasma-discover reports that an update is available to update my system from 34 to 32.

2021-12-21 Thread Waitman Gobble

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

Bug ID: 447361
   Summary: on Fedora 35, plasma-discover reports that an update
is available to update my system from 34 to 32.
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: wait...@waitman.net
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 144769
  --> https://bugs.kde.org/attachment.cgi?id=144769=edit
it'sa screenshot

STEPS TO REPRODUCE
1. boot system, updates available icon shown in tray.
2. 
3. 

OBSERVED RESULT
plasma-discover reports an update is available that appears to indicate the
install will "upgrade" Fedora 34 to Fedora 32. The system is running Fedora 35.
dnf shows that system is up-to-date.


EXPECTED RESULT
no updates available.

SOFTWARE/OS VERSIONS
Windows: 
macOS:
Linux/KDE Plasma: Fedora 35
(available in About System)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland

2021-12-21 Thread Conrad

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

--- Comment #12 from Conrad  ---
Figured out the problem. It was caused by ~/.config/kcminputrc and more
precisely by these lines:

[Keyboard]
KeyRepeat=repeat
NumLock=0
RepeatDelay=600
RepeatRate=25

It must have been created by some older version of kde/plasma.

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

[dolphin] [Bug 447321] When dolphin opens, all 4 panels are open, and the whole window is small (quarter of screen); also for windows opened by restore of saved session; new in v 21.12.

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

radi...@gmail.com changed:

   What|Removed |Added

  Component|panels: terminal|general

--- Comment #3 from radi...@gmail.com ---
Changed component to 'general' as it's not about a panel.

copy/paste from 'about system':
Operating System: Manjaro Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.10.84-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E5-2665 0 @ 2.40GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVE7

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

[dolphin] [Bug 447321] When dolphin opens, all 4 panels are open, and the whole window is small (quarter of screen); also for windows opened by restore of saved session; new in v 21.12.

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

radi...@gmail.com changed:

   What|Removed |Added

 CC||radi...@gmail.com

--- Comment #2 from radi...@gmail.com ---
Created attachment 144768
  --> https://bugs.kde.org/attachment.cgi?id=144768=edit
2 of dolphinrc, one from before the error, one after.

Both copies of dolphinrc were taken soon after login,
before any dolphin window was adjusted.
The main difference I see is that 
the old version has 'State' under [MainWindow],
but the new version does not.

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

[okular] [Bug 447325] Special # character in the filename affects the readability of the content

2021-12-21 Thread David Hurka

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

--- Comment #1 from David Hurka  ---
I think this is related to specifying the page after a # sign, like
'some_document.pdf#15'.

That feature is available for all platforms, but I can not reproduce this issue
with KDE Neon user edition. I do not have Windows.

Two questions which might help others to reproduce this:

The properties dialog seems to show that Okular actually managed to “open” the
desktop, and got this 0 byte image then. Can you describe this image a bit
more? Is it some special kind of file?

How did you launch Okular? Double-click the desktop icon of the document you
want to open?

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

[kget] [Bug 444591] KGet crashes when attempting to download anything

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

--- Comment #22 from george.stefana...@gmail.com ---
Created attachment 144767
  --> https://bugs.kde.org/attachment.cgi?id=144767=edit
New crash information added by DrKonqi

kget (21.12.0) using Qt 5.15.3

- What I was doing when the application crashed:
Just trying to download an ISO file.  I had just copied the link, paste it to
New Download, in Kget.  Kget insert the link and tried to download the file,
and then crashed.  I have tried it 4 times with the same result.

-- Backtrace (Reduced):
#4  0x7f79c6a5bcc4 in KMountPoint::mountType() const () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#5  0x7f79c721a759 in DataSourceFactory::start (this=0x7f79b8007b70) at
./core/datasourcefactory.cpp:277
#6  0x7f79c721ad78 in DataSourceFactory::slotFoundFileSize
(this=0x7f79b8007b70, source=, fileSize=,
segmentRange=...) at ./core/datasourcefactory.cpp:151
#7  0x7f79c51abdce in QtPrivate::QSlotObjectBase::call (a=0x7ffe909458f0,
r=0x7f79b8007b70, this=0x55c82a62b2b0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate (sender=0x55c82a6699e0, signal_index=3,
argv=0x7ffe909458f0) at kernel/qobject.cpp:3886

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

[kget] [Bug 444591] KGet crashes when attempting to download anything

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

george.stefana...@gmail.com changed:

   What|Removed |Added

 CC||george.stefana...@gmail.com

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

[kmplot] [Bug 447339] typing a Circonflex ^ Doesn't respond

2021-12-21 Thread Henk Mertens

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

--- Comment #2 from Henk Mertens  ---
Hello Christoph,
Just standard shift+6
In other applications it works as normal. Tested in Libreoffice, Geogebra,
browser Typebox..
Greetings,
Henk

Outlook voor Android downloaden

From: Christoph Feck 
Sent: Tuesday, December 21, 2021 10:55:28 PM
To: henkmert...@hotmail.com 
Subject: [kmplot] [Bug 447339] typing a Circonflex ^ Doesn't respond

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

--- Comment #1 from Christoph Feck  ---
Are you using a "dead key" variant of the keymap? Please also test other
applications.

--
You are receiving this mail because:
You reported the bug.

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

[kmplot] [Bug 447339] typing a Circonflex ^ Doesn't respond

2021-12-21 Thread Christoph Feck

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

--- Comment #1 from Christoph Feck  ---
Are you using a "dead key" variant of the keymap? Please also test other
applications.

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

[kdeplasma-addons] [Bug 447345] when i right click any quicklaunch applet the cursor change to the drag state and i have to press Esc for do anything

2021-12-21 Thread Codezela

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

Codezela  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages

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

[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland

2021-12-21 Thread Conrad

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

--- Comment #11 from Conrad  ---
Thanks for your help so far! I tested with a newly created user just now and
the problem does not occur there. Any idea where I could start looking to
narrow down the cause?

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

[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)

2021-12-21 Thread phrxmd

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

--- Comment #10 from phrxmd  ---
Addendum: 2560x1440 (the resolution the external screen is stuck at) is also
the physical resolution of the internal screen of my laptop, I'm not sure if
that matters.

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

[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)

2021-12-21 Thread phrxmd

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

phrxmd  changed:

   What|Removed |Added

 Attachment #144765|application/octet-stream|text/plain
  mime type||

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

[kwin] [Bug 447305] feature-request: add support of wlr-randr for wayland sessions

2021-12-21 Thread Lars Bischoff

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

Lars Bischoff  changed:

   What|Removed |Added

Version|unspecified |5.23.4
   Platform|unspecified |Ubuntu Packages

--- Comment #2 from Lars Bischoff  ---
Ah, thanks! I was searching for a native kde command-line tool to manage
screens  when I wrote my little screen switching script years ago, but couldn't
find any.

Now, if it only would work when using wayland...
First problem I encountered was that the output names are not the same as when
using X11.
On X11 I have: "DisplayPort-0" and "HDMI-A-0"
On wayland I just have outputs "1" and "2".
So it's not possible to use exactly the same commands on both X11 and wayland.
And then the  first time I used that to switch the output from one output to
the other, my whole system froze... had to hard reset...
Guess I better let wayland mature for another 5 years before trying again, huh?
;)

Anyway: Even if kscreen-doctor would work properly, having a DE (or
wayland-compositor) independent command-line tool for managing display outputs
(similar to xrandr), is IMHO still preferable. So would be great if something
like wlr-randr is considered at some point.

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

[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)

2021-12-21 Thread phrxmd

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

--- Comment #9 from phrxmd  ---
Created attachment 144765
  --> https://bugs.kde.org/attachment.cgi?id=144765=edit
drm_info output when the screen is stuck at 2560x1440

It's happened again, now my external screen is stuck at 2560x1440. 
I can set it to a larger resolution, but the physical resolution of the screen
does not change - there seems to be a larger screen buffer of which I see only
the bottom left corner. 

What I did was to unplug an USB device (a Brother QL-700 label printer, if it
matters) from one of the USB ports on my laptop. At that moment the screen went
black. In order to bring it back up again, I deactivated it in System Settings
(resulting in a Plasmashell crash). When I reactivated it, it came up at
2560x1440 and has been stuck at the resolution since.

Attached is the drm_info output for the case when it's stuck at 2560x1440.

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

[digikam] [Bug 431797] Face recognition <1% despite extensive training data of up to 300 occasions of faces

2021-12-21 Thread Thomas Beckler

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

--- Comment #6 from Thomas Beckler  ---
Thank you for the update. This is great news that there has been some
development.

I confirm that the YOLOv3 face detection/recognition is excellent. This thread
is about the use case of manually drawn rectangles or rectangles drawn by other
programs. 

https://bugs.kde.org/show_bug.cgi?id=415782#c22 states:
We will try to improve this as part of the GSoC 2021. With a current digikam,
it is important to rebuild the training database

The rebuild of the training database doesn't help on my collection.  Can you
confirm that the integration of the GSoC-2021 is going to include improvement
in respect to the face rectangles drawn by others than digikam?

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

[kmail2] [Bug 447360] New: KMail crashes on startup when it can't authenticate account

2021-12-21 Thread Loren Burkholder

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

Bug ID: 447360
   Summary: KMail crashes on startup when it can't authenticate
account
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: computersemiexp...@outlook.com
  Target Milestone: ---

Application: kmail (5.19.0 (21.12.0))

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

-- Information about the crash:
- What I was doing when the application crashed:
KMail was not loading emails from any of my accounts, so I tried restarting it.
When I restart KMail, it crashes and then starts up again. This is very
possibly related to the fact that my employer's email server seems to be down
so that KMail can't authenticate that account.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x7f6407463a75 in QScopedPointer >::operator-> (this=0x8) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#7  qGetPtrHelper > > (ptr=...) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1143
#8  QAction::d_func (this=this@entry=0x0) at kernel/qaction.h:63
#9  QAction::setText (this=this@entry=0x0, text=...) at kernel/qaction.cpp:714
#10 0x7f640f89495a in KMMainWidget::updateFolderMenu (this=0x7f63b4120ab0)
at /usr/src/debug/kmail-21.12.0-1.1.x86_64/src/kmmainwidget.cpp:4038
#11 0x7f640f88b6cc in KMMainWidget::setupActions (this=0x7f63b4120ab0) at
/usr/src/debug/kmail-21.12.0-1.1.x86_64/src/kmmainwidget.cpp:3400
#12 0x7f640f8752ea in KMMainWidget::KMMainWidget (this=,
parent=, aGUIClient=, actionCollection=, config=..., this=, parent=,
aGUIClient=, actionCollection=, config=...) at
/usr/src/debug/kmail-21.12.0-1.1.x86_64/src/kmmainwidget.cpp:248
#13 0x7f640f83c25b in KMMainWin::KMMainWin (this=,
this=) at
/usr/src/debug/kmail-21.12.0-1.1.x86_64/src/kmmainwin.cpp:49
#14 0x7f640f84ddf7 in KMKernel::openReader (this=,
onlyCheck=, startInTray=) at
/usr/src/debug/kmail-21.12.0-1.1.x86_64/src/kmkernel.cpp:565
#15 0x7f640f8530ef in KMKernel::action (this=0x7ffeac7d72c0,
mailto=, check=, startInTray=,
to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=...,
customHeaders=..., replyTo=..., inReplyTo=..., identity=...) at
/usr/src/debug/kmail-21.12.0-1.1.x86_64/src/kmkernel.cpp:1276
#16 0x7f640f84c8d3 in KMKernel::handleCommandLine (this=,
noArgsOpensReader=noArgsOpensReader@entry=true, args=..., workingDir=...) at
/usr/src/debug/kmail-21.12.0-1.1.x86_64/src/kmkernel.cpp:476
#17 0x55b741cc5882 in KMailApplication::activate (this=,
args=..., workingDir=...) at
/usr/src/debug/kmail-21.12.0-1.1.x86_64/src/main.cpp:100
#18 0x7f640f986213 in
KontactInterface::PimUniqueApplication::qt_static_metacall (_c=,
_id=, _a=0x7ffeac7d67a0, _o=0x7ffeac7d72a0) at
/usr/src/debug/kontactinterface-21.12.0-1.1.x86_64/build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:87
#19 KontactInterface::PimUniqueApplication::qt_static_metacall
(_o=_o@entry=0x7ffeac7d72a0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=1, _a=_a@entry=0x7ffeac7d67a0) at
/usr/src/debug/kontactinterface-21.12.0-1.1.x86_64/build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:79
#20 0x7f640f9862f3 in KontactInterface::PimUniqueApplication::qt_metacall
(this=0x7ffeac7d72a0, _c=QMetaObject::InvokeMetaMethod, _id=1,
_a=0x7ffeac7d67a0) at
/usr/src/debug/kontactinterface-21.12.0-1.1.x86_64/build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:124
#21 0x7f6405f2769b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190
#22 0x7f6405f2b08c in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7f63c8003c00, object=0x7ffeac7d72a0, flags=81, msg=...) at
qdbusintegrator.cpp:904
#23 0x7f6405f2b91d in QDBusConnectionPrivate::activateCall (msg=...,
flags=, object=, this=0x7f63c8003c00) at
qdbusintegrator.cpp:853
#24 QDBusConnectionPrivate::activateObject (this=0x7f63c8003c00, node=...,
msg=..., pathStartPos=) at qdbusintegrator.cpp:1521
#25 0x7f6405f2de38 in QDBusActivateObjectEvent::placeMetaCall
(this=0x55b743aa7e40) at qdbusintegrator.cpp:1617
#26 0x7f64068e4fee in QObject::event (this=0x7ffeac7d72a0,
e=0x55b743aa7e40) at kernel/qobject.cpp:1314
#27 0x7f6407467a7f in QApplicationPrivate::notify_helper (this=, receiver=0x7ffeac7d72a0, e=0x55b743aa7e40) at

[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland

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

--- Comment #10 from Andrey  ---
You can test in VM, but if it works for Sway then it's probably something
different..
Still we need a way to reproduce it, so yes, please test on VM. You can use
Neon iso.

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

[systemsettings] [Bug 447256] layout switching shortcut not working after system login

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

--- Comment #17 from Andrey  ---
At least Neon would be fine.

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

[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland

2021-12-21 Thread Conrad

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

--- Comment #9 from Conrad  ---
No, sway is its own wayland compositor. "etc." sounded like that was what you
were asking for. Any way to test this without having to install the whole gnome
suite on my system?

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

[dolphin] [Bug 447219] Doplhin do not copy files through MNT Android

2021-12-21 Thread Michal Janousek

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

--- Comment #1 from Michal Janousek  ---
Copy wors but when exist same folder Dollphin show error. It should show if I
want to merge the folder, and keep or overwrite the files in it.

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

[systemsettings] [Bug 447256] layout switching shortcut not working after system login

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

--- Comment #16 from moshe_shelo...@outlook.com ---
(In reply to Andrey from comment #15)
> I've ran out of ideas, if nobody can confirm I'm afraid we still need to
> test on VM, sorry.

I may try asking some friends to try running vm. Which os is needed to be in
vm? same as mine - vanilla arch, or any arch-based will do?
or any distro at all would work as well?

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

[kwin] [Bug 439332] Ghost windows and popups

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

alk...@protonmail.com changed:

   What|Removed |Added

 CC||alk...@protonmail.com

--- Comment #20 from alk...@protonmail.com ---
Interesting enough, I personally don't experience this issue anymore.

I had "translucent windows" effects disabled because of this issue, however I
have re-enabled it since the latest "Manjaro Stable" update (2021-12-16) and
did not experience this issue yet. 

Before it was pretty easy to trigger with Firefox, but for now it seems to
work.

My guess it could be solved by either of those: 
- KDE Plasma update 5.23.4
- NVIDIA 495xx Driver update (that wouldn't explain why AMD Users had the same
issue)
- x.org update (21.1.2)
- KDE Gear update 21.12

Other people which experienced this issue might want to re-test it they can
reproduce this on similar versions like me. 

Operating System: Manjaro Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.10.84-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

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

[dolphin] [Bug 447356] On DE's other then Plasma, Dolphin background may not respect QT theming via qt5ct

2021-12-21 Thread Kauê Sena

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

Kauê Sena  changed:

   What|Removed |Added

 CC||kaue.sena...@gmail.com

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

[kid3] [Bug 447323] Import from Discogs not fetching 'Catalog Number' tag

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

vvk...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from vvk...@gmail.com ---
(In reply to Urs Fleisch from comment #1)
> I am sorry to hear that the new release has not met your expectations. Could
> you please elaborate a bit more detailed what is expected and what is
> received, if possible with a link to the Discogs URL of one or more albums.
> 
> Unfortunately, the "standard" Discogs import is rather shaky because it
> depends on the HTML output coming from the Discogs server, and this output
> is changing a lot. I stopped counting how many commits with description "Fix
> Discogs import" I had to make in the past.
> 
> Have you tried the JSON API import? It is stable and uses the official
> Discogs API. You just have to get register at Discogs.com, get an API token,
> enter it in Kid3's Discogs import dialog and click "Save Settings" (this is
> described in the handbook). Maybe this will bring you the catalog numbers
> you are expecting.

Yes, it worked with the token! Thank you very much, Urs!

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

[Elisa] [Bug 430233] Please consider ReplayGain tags

2021-12-21 Thread Tobias Leupold

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

--- Comment #4 from Tobias Leupold  ---
Is there any work going on about this? Is there possibly something I could do
to help?

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

[systemsettings] [Bug 447256] layout switching shortcut not working after system login

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

Andrey  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #15 from Andrey  ---
I've ran out of ideas, if nobody can confirm I'm afraid we still need to test
on VM, sorry.

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

[konversation] [Bug 387596] Crash when toggling between new UI and old UI

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UNMAINTAINED
 CC||kosse...@kde.org

--- Comment #5 from Friedrich W. H. Kossebau  ---
The QtQuick UI branch would be considered dead by now, not having seen work in
years and with normal development branches having walked further. See also
https://mail.kde.org/pipermail/konversation-devel/2020-September/007078.html

So closing now.

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

[frameworks-kholidays] [Bug 435210] Pakistani Holidays Missing from Calendar

2021-12-21 Thread Allen Winter

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

--- Comment #3 from Allen Winter  ---
We do have Pakistan holidays in English since a couple months.

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

[lattedock] [Bug 433661] Enabling scrolling makes plasmoid "too short"

2021-12-21 Thread Riccardo Robecchi

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

Riccardo Robecchi  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #8 from Riccardo Robecchi  ---
(In reply to Michail Vourlakos from comment #6)
> (In reply to Riccardo Robecchi from comment #5)
> > Created attachment 144596 [details]
> > Latte layout
> > 
> > Here is the requested file.
> 
> I can not reproduce.
> Please try upcoming 0.10.5 and see if it is still valid for you.
> If it is, I will need also exact steps to reproduce, your sent layout
> provides two bottom docks, I enabled scrolling but with none of them I
> observed any issue.

Version 10.6 does fix the issue, thank you!

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

[plasmashell] [Bug 447359] Displays are overlapping when using fractional scaling and re-login with XOrg

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

--- Comment #1 from lrdarkne...@yahoo.de ---
Created attachment 144764
  --> https://bugs.kde.org/attachment.cgi?id=144764=edit
Screenshot showing the display settings

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

[lattedock] [Bug 442524] Widgets/menus are placed incorrectly and windows cannot move beyond some invisible bounds after connecting a second screen

2021-12-21 Thread Riccardo Robecchi

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

Riccardo Robecchi  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Riccardo Robecchi  ---
(In reply to Michail Vourlakos from comment #4)
> is it fixed with 0.10.5?

I was only able to test it today with version 10.6. It does indeed fix the
issue, thanks!

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

[systemsettings] [Bug 447256] layout switching shortcut not working after system login

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

--- Comment #14 from moshe_shelo...@outlook.com ---
(In reply to Andrey from comment #13)
> Try to reproduce with new user and on VM

Newly created user still has the bug

I'm unable to run VM, unfortunately, so I can't check it there.

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

[plasmashell] [Bug 447359] New: Displays are overlapping when using fractional scaling and re-login with XOrg

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

Bug ID: 447359
Summary: Displays are overlapping when using fractional scaling
and re-login with XOrg
Product: plasmashell
Version: 5.23.4
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Multi-screen support
Assignee: aleix...@kde.org
Reporter: lrdarkne...@yahoo.de
CC: plasma-b...@kde.org
Target Milestone: 1.0

Created attachment 144763
--> https://bugs.kde.org/attachment.cgi?id=144763=edit
Screenshot showing the overlapping of the displays

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
***
I have a big 4k display and a smaller FHD display on the right side.
Trying out Plasmas Wayland capabilities, i've set the scaling of the 4k display
to 125% while the smaller on the right side remains at 100%.
When i now logout from the Wayland session and re-login using X11, both
displays are "overlapping" somehow and i can't manage to separate them from
each other.
The settings show that the display should be separated but in fact they aren't.
I guess that has something to do with the fractional scaling settings from the
Wayland session that confuse Xorg.

STEPS TO REPRODUCE
1. Login using the Wayland session
2. Set the scaling of the 4k display to 125%, leave the other display at 100%.
3. Re-login with XOrg

OBSERVED RESULT
Both displays overlap as shown in the screenshot that I attached.

EXPECTED RESULT
This shouldn't happen.

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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 447204] Task manager offers to launch new instance of kcmshell and systemsettings

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 CC||justin.zo...@gmail.com

--- Comment #3 from Friedrich W. H. Kossebau  ---
*** Bug 429428 has been marked as a duplicate of this bug. ***

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

[konversation] [Bug 429428] Start New Instance

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||kosse...@kde.org

--- Comment #3 from Friedrich W. H. Kossebau  ---
Konversation is designed as a single instance application. Supporting multiple
windows would need some big overhaul, nothing to be expected to be done from
someone currently, given the maintenance state.

The expectations given by the "Start new instance" are not Konversation's fault
though, that is an issue with the task manager, So closing as duplicate of the
related bug (which currently is seeing work gladly :) ).

*** This bug has been marked as a duplicate of bug 447204 ***

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

[frameworks-kxmlgui] [Bug 447358] New: App crash when displaying tooltip on tray icon

2021-12-21 Thread Juraj

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

Bug ID: 447358
   Summary: App crash when displaying tooltip on tray icon
   Product: frameworks-kxmlgui
   Version: 5.89.0
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: jurajora...@mailo.com
  Target Milestone: ---

SUMMARY
The application crashes when the tooltip should be displayed over the old
styled tray icon (tint2 panel).
I tested it on Kmail and in the past on some other kde program.
Possibly related to https://bugs.kde.org/show_bug.cgi?id=442352


STEPS TO REPRODUCE
1. Start kmail with tray icon enabled
2. Do with mouse over the tray icon
3. Wait for tooltip to show

OBSERVED RESULT
Crash

EXPECTED RESULT
Display tooltip.

SOFTWARE/OS VERSIONS
KDE version are latest from git at the moment of posting. (could not quickly
build kinfocenter.)
Qt Version: 5.15.2+kde+r263-6

ADDITIONAL INFORMATION
I tracked this issue to the kxmlgui through the bacjtrace, there is aposibility
that it is bug in Qt.

BACKTRACE
#0  0x7fffed714a55 in QWidget::toolTip() const () at
/usr/lib/libQt5Widgets.so.5
#1  0x7fffeed61cd1 in KToolTipHelperPrivate::handleToolTipEvent(QWidget*,
QHelpEvent*) (this=0x55cde4a0, watchedWidget=0x7fff740364f0,
helpEvent=0x7fffd900)
at /home/juraj/kde/src/kxmlgui/src/ktooltiphelper.cpp:216
#2  0x7fffeed610b9 in KToolTipHelperPrivate::eventFilter(QObject*, QEvent*)
(this=0x55cde4a0, watched=0x7fff740364f0, event=0x7fffd900)
at /home/juraj/kde/src/kxmlgui/src/ktooltiphelper.cpp:72
#3  0x7fffeed61033 in KToolTipHelper::eventFilter(QObject*, QEvent*)
(this=0x55cde420, watched=0x7fff740364f0, event=0x7fffd900)
at /home/juraj/kde/src/kxmlgui/src/ktooltiphelper.cpp:61
#4  0x7fffec9c5dde in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#5  0x7fffed6e6032 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#6  0x7fffec9c61ba in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#7  0x7fffedaab5dc in  () at /usr/lib/libQt5Widgets.so.5
#8  0x7fffed6e5ff6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#9  0x7fffed6eed33 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#10 0x7fffec9c61ba in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#11 0x7fffed6ebc6c in QApplication::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#12 0x7fffed6e5ff6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#13 0x7fffec9c61ba in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#14 0x7fffeca1edbd in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#15 0x7fffeca1f6fa in  () at /usr/lib/libQt5Core.so.5
#16 0x7fffe74980ec in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#17 0x7fffe74ed889 in  () at /usr/lib/libglib-2.0.so.0
#18 0x7fffe7495735 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#19 0x7fffeca1fada in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#20 0x7fffec9c4a6b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#21 0x7fffec9cd258 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#22 0x9975 in main(int, char**) (argc=1, argv=0x7fffdf88) at
/home/juraj/kde/src/kmail/src/main.cpp:175

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

[frameworks-kholidays] [Bug 447201] Missing Polish holidays.

2021-12-21 Thread Allen Winter

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #1 from Allen Winter  ---
I'm forwarding this to the author of the Poland Holidays file.

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

[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland