[plasmashell] [Bug 473552] Undoing the removal of a Widget inside a panel leaves an additional "ghost" copy

2023-08-19 Thread youkai
https://bugs.kde.org/show_bug.cgi?id=473552

youkai  changed:

   What|Removed |Added

   Keywords||qt6

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

[plasmashell] [Bug 473552] New: Undoing the removal of a Widget inside a panel leaves an additional "ghost" copy

2023-08-19 Thread youkai
https://bugs.kde.org/show_bug.cgi?id=473552

Bug ID: 473552
   Summary: Undoing the removal of a Widget inside a panel leaves
an additional "ghost" copy
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: k...@youkai.dev
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 161064
  --> https://bugs.kde.org/attachment.cgi?id=161064=edit
Video recording of reproducing the bug

SUMMARY
When removing a widget inside a panel and undoing said removal by clicking undo
in the removal-notification the original widget reappears plus an additional
"ghost" copy (no icon/content/etc... visible).

STEPS TO REPRODUCE
1. Take any panel and add a widget onto that panel, e.g. the Analog Clock
2. Right-click on the panel and enter edit mode
3. Hover your mouse above the previously added widget and remove it
4. Undo the removal via the removal-notification

OBSERVED RESULT
The panel now has the restored widget and an additional "ghost" copy

EXPECTED RESULT
No ghosts should appear

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 38
(available in About System)
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Graphics Platform: Wayland

ADDITIONAL INFORMATION

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

[KClock] [Bug 473549] Components Overlap Each Other in Big Components or Small Window Sizes

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473549

hanyo...@protonmail.com changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/util
   ||ities/kclock/-/commit/d980d
   ||8f715df05ae163fa3856272d8c0
   ||280f96e7

--- Comment #4 from hanyo...@protonmail.com ---
Git commit d980d8f715df05ae163fa3856272d8c0280f96e7 by Han Young.
Committed on 20/08/2023 at 07:28.
Pushed by hanyoung into branch 'master'.

fix: timer command text overflow on list page

M  +1-1src/kclock/qml/timer/TimerListDelegate.qml

https://invent.kde.org/utilities/kclock/-/commit/d980d8f715df05ae163fa3856272d8c0280f96e7

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

[KClock] [Bug 473549] Components Overlap Each Other in Big Components or Small Window Sizes

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=473549

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/utilities/kclock/-/merge_requests/100

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

[KClock] [Bug 473549] Components Overlap Each Other in Big Components or Small Window Sizes

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473549

hanyo...@protonmail.com changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from hanyo...@protonmail.com ---
I think I'll give stopwatch clipping a pass because the window is tiny. Script
text one need to be clipped though.

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

[krunner] [Bug 473528] KRunner doesn't follow mouse cursor

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473528

djme...@outlook.com changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||djme...@outlook.com

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

[krita] [Bug 471046] Bug in the brush stroke after using Mirror Screen Vertically; Brush duplicated, on the other side of the screen.

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=471046

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- 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 472090] Crash When Pasting Copied Vector

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=472090

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 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 471355] Every time I attempt to load up the GMIC-Qt option under filter the app freezes.

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=471355

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.

[plasmashell] [Bug 446833] Unable to select text when renaming files on desktop

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=446833

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

[NeoChat] [Bug 471268] If a Room's description in the Room Information drawer is too long, the Options and Members sections of the drawer are inaccessible

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=471268

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

[Heaptrack] [Bug 408547] ERROR: failed to lock heaptrack output file

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=408547

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.

[plasmashell] [Bug 472984] Memory leaks

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=472984

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

[NeoChat] [Bug 469593] Website links are resolved inside code blocks

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=469593

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

[frameworks-kitemviews] [Bug 380800] High CPU usage with 'Desktop Effects' enabled

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=380800

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

[plasmashell] [Bug 427218] Task manager shows windows from all screen or nothing

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=427218

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

[print-manager] [Bug 421319] cannot add printer via GUI

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=421319

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

[dolphin] [Bug 473377] Dolphin crashes if you remove a tab after deleting a folder

2023-08-19 Thread Amol Godbole
https://bugs.kde.org/show_bug.cgi?id=473377

Amol Godbole  changed:

   What|Removed |Added

 CC||amolagodb...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[isoimagewriter] [Bug 473551] New: Percentage of write not showing correctly

2023-08-19 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=473551

Bug ID: 473551
   Summary: Percentage of write not showing correctly
Classification: Applications
   Product: isoimagewriter
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: j...@jriddell.org
  Reporter: justin.zo...@gmail.com
  Target Milestone: ---

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

See attached screenshot

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

[kate] [Bug 473550] New: Select word right and left includes space

2023-08-19 Thread Robbie
https://bugs.kde.org/show_bug.cgi?id=473550

Bug ID: 473550
   Summary: Select word right and left includes space
Classification: Applications
   Product: kate
   Version: 23.04.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: yqz38...@duck.com
  Target Milestone: ---

SUMMARY
***
Select word right (ctrl+shift+right) or left (ctrl+shift+left) includes spaces
in the selection
***


STEPS TO REPRODUCE
1. Type two strings separated by a space
2. Start at the beginning of the left-most string and press ctrl+shift+right
3. Clear selection and start at the end of the right-most string and press
ctrl+shift+left

OBSERVED RESULT
In both cases, the space between the strings is selected along with the strings

EXPECTED RESULT
Only the string up to the space would be selected, similar to what would be
selected if double clicking on the string

SOFTWARE/OS VERSIONS
Linux: 5.15.0-79-generic
(available in About System)
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

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

[systemsettings] [Bug 408563] Provide option for day/night color theme switching

2023-08-19 Thread King Kang Kong
https://bugs.kde.org/show_bug.cgi?id=408563

King Kang Kong  changed:

   What|Removed |Added

 CC||r2b2x3+kde...@gmail.com

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

[kontact] [Bug 473209] Feature: Display synchronization status

2023-08-19 Thread sourcemaker
https://bugs.kde.org/show_bug.cgi?id=473209

sourcemaker  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #3 from sourcemaker  ---
I have the same problem again with a fresh, clean Akonadi installation. 
My vCards are not fully transferred to Radicale!

Unfortunately I don't see any error message.

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

[KClock] [Bug 473549] Components Overlap Each Other in Big Components or Small Window Sizes

2023-08-19 Thread K. Cottonears
https://bugs.kde.org/show_bug.cgi?id=473549

K. Cottonears  changed:

   What|Removed |Added

 Attachment #161061|Here in the timer page, |Here in the timer page,
description|text is overflowing and |text is overflowing.
   |buttons are becoming|
   |inaccessible.   |

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

[KClock] [Bug 473549] Components Overlap Each Other in Big Components or Small Window Sizes

2023-08-19 Thread K. Cottonears
https://bugs.kde.org/show_bug.cgi?id=473549

--- Comment #1 from K. Cottonears  ---
Created attachment 161062
  --> https://bugs.kde.org/attachment.cgi?id=161062=edit
Seconds at the stopwatch page being cut off.

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

[KClock] [Bug 473549] New: Components Overlap Each Other in Big Components or Small Window Sizes

2023-08-19 Thread K. Cottonears
https://bugs.kde.org/show_bug.cgi?id=473549

Bug ID: 473549
   Summary: Components Overlap Each Other in Big Components or
Small Window Sizes
Classification: Applications
   Product: KClock
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: espi...@gmail.com
  Reporter: k_cottone...@pm.me
CC: hanyo...@protonmail.com
  Target Milestone: ---

Created attachment 161061
  --> https://bugs.kde.org/attachment.cgi?id=161061=edit
Here in the timer page, text is overflowing and buttons are becoming
inaccessible.

SUMMARY
If text is too long, or the window size is small, some elements within the page
may overlap, "bleed," or just generally extend in places that probably should
not be there or out of range.

STEPS TO REPRODUCE
1. Resize the window to be small, preferably to its minimum size limits.
2. Go to the pages for timezone, timers, and stopwatch.

OBSERVED RESULT
Some components and text end up overlapping each other.

EXPECTED RESULT
Have some kind of way to handle this when this occurs.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

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

[gwenview] [Bug 463902] let's reduce the zoom step

2023-08-19 Thread Misha Aizatulin
https://bugs.kde.org/show_bug.cgi?id=463902

--- Comment #10 from Misha Aizatulin  ---
Ping. I think needing to compile the most recent tree is an incredibly high bar
for a casual contributor like me who only wants to change one line. I'm happy
to submit a PR from whatever version I can compile on my (latest) OS, and
pretty promise it will rebase fine.

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

[kdenlive] [Bug 472627] Bug: Sequence's Audio Waveform is not generate.

2023-08-19 Thread OitoFA
https://bugs.kde.org/show_bug.cgi?id=472627

OitoFA  changed:

   What|Removed |Added

 CC||adorno.facu...@gmail.com

--- Comment #2 from OitoFA  ---
*** Bug 472634 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 472634] SEQUENCES - Audio Thumbnail are not showing in timeline when use a sequence into other sequence

2023-08-19 Thread OitoFA
https://bugs.kde.org/show_bug.cgi?id=472634

OitoFA  changed:

   What|Removed |Added

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

--- Comment #1 from OitoFA  ---


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

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

[plasma-pk-updates] [Bug 473548] New: plasma-pk-updates applet doesn't load under Fedora 37 KDE desktop

2023-08-19 Thread ND
https://bugs.kde.org/show_bug.cgi?id=473548

Bug ID: 473548
   Summary: plasma-pk-updates applet doesn't load under Fedora 37
KDE desktop
Classification: Plasma
   Product: plasma-pk-updates
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: general.and...@gmail.com
  Target Milestone: ---

In my Fedora 37 system, since a recent update with more than 350 packages the
PackageKit (“Software Updates”) applet in the system tray doesn’t load anymore.

STEPS TO REPRODUCE
1.  Start KDE session in Fedora 37
2. Click the Software Updates icon in the system tray and observe the error
message.

OBSERVED RESULT
Message of Software Updates (Get software updates) icon:
Sorry! There was an error loading Software Updates.

file:///usr/share/plasma/plasmoids/org.kde.plasma.pkupdates/contents/ui/main.qml:25:1:
plugin cannot be loaded for module “org.kde.plasma.PackageKit”: Cannot load
library /usr/lib64/qt5/qml/org/kde/plasma/PackageKit/libplasmapk_qmlplugins.so:
(/usr/lib64/qt5/qml/org/kde/plasma/PackageKit/libplasmapk_qmlplugins.so:
undefined symbol: _ZN5Solid3Job16staticMetaObjectE)


EXPECTED RESULT
- The loaded applet, updates info.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 37
KDE Plasma Version: 5.27.6
version: plasma-pk-updates-1:0.3.2-13.fc37.i686
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
- Updating via the command line does work.
- I asked on discuss.kde.org whether this is a bug or just my configuration,
but in lack of an answer there I am reporting it as a bug here.
https://discuss.kde.org/t/plasma-pk-updates-doesnt-load-in-f37/3801?u=andy

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

[Discover] [Bug 473547] New: Hashes give me error

2023-08-19 Thread Pat
https://bugs.kde.org/show_bug.cgi?id=473547

Bug ID: 473547
   Summary: Hashes give me error
Classification: Applications
   Product: Discover
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: patk...@proton.me
CC: aleix...@kde.org
  Target Milestone: ---

When i Open About discover window i get the error message I've pasted below 



E: http://ca.archive.ubuntu.com/ubuntu lunar-updates/main amd64 DEP-11 Metadata
is not (yet) available (Hash Sum mismatch
Hashes of expected file:
 - Filesize:333734 [weak]
 - SHA256:25b1f398ad7689676741525cd6d0c38dd98869096aacf7f15f011430ecd5b7dc
 - SHA1:21c916a0a5bb2d1aa89bba67f63be735fbefef44 [weak]
 - MD5Sum:97a2d0fca20a18b551f517cdf4b4729e [weak]
Hashes of received file:
 - SHA256:0d4e5a44e216ef11226c2a42d0856c53b252b5618a2582f04cf39a52f2cc3be5
 - SHA1:60828e4ea4a01e6917f41e1a474cb20439434ac2 [weak]
 - MD5Sum:8706d895752c4b97dfdd5ccfefee526b [weak]
 - Filesize:333734 [weak]
Last modification reported: Sat, 19 Aug 2023 17:34:22 +
Release file created at: Sat, 19 Aug 2023 20:52:02 +

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

[akregator] [Bug 473546] New: Akregator crash on laptop after waking from sleep and logging in

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473546

Bug ID: 473546
   Summary: Akregator crash on laptop after waking from sleep and
logging in
Classification: Applications
   Product: akregator
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: mowing.beams...@icloud.com
  Target Milestone: ---

Application: akregator (5.23.3 (23.04.3))

Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.11-200.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 38 (KDE Plasma)
DrKonqi: 5.27.6 [KCrashBackend]

-- Information about the crash:
the lid on my laptop was closed, had been for maybe 30 minutes, I opened it,
logged in and Akregator crashed

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault

[KCrash Handler]
#4  0x7fa8daf7d20c in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
#5  0x7fa8db68c769 in QVector::insert(int*, int, int const&) [clone
.isra.0] () from /lib64/libQt5Core.so.5
#6  0x7fa8db690763 in
QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&,
QVector const&, QModelIndex const&, Qt::Orientation, bool) () from
/lib64/libQt5Core.so.5
#7  0x7fa8db695247 in
QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5
#8  0x7fa8db6e8608 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#9  0x7fa8db662561 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5
#10 0x7fa8bc0e1e1f in
Akregator::SubscriptionListModel::subscriptionChanged(Akregator::TreeNode*) ()
from /usr/lib64/qt5/plugins/akregatorpart.so
#11 0x7fa8db6e8481 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#12 0x7fa8dd058364 in
Akregator::FeedList::signalNodeChanged(Akregator::TreeNode*) () from
/lib64/libakregatorprivate.so.5
#13 0x7fa8db6e8481 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#14 0x7fa8dd059264 in
Akregator::TreeNode::signalChanged(Akregator::TreeNode*) () from
/lib64/libakregatorprivate.so.5
#15 0x7fa8dd07d513 in
Akregator::Feed::appendArticles(QSharedPointer const&) ()
from /lib64/libakregatorprivate.so.5
#16 0x7fa8dd082bd0 in Akregator::Feed::fetchCompleted(Syndication::Loader*,
QSharedPointer, Syndication::ErrorCode) () from
/lib64/libakregatorprivate.so.5
#17 0x7fa8dd05e574 in Akregator::Feed::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libakregatorprivate.so.5
#18 0x7fa8db6e8608 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#19 0x7fa8dc19d900 in
Syndication::Loader::loadingComplete(Syndication::Loader*,
QSharedPointer, Syndication::ErrorCode) () from
/lib64/libKF5Syndication.so.5
#20 0x7fa8dc1dc06f in Syndication::Loader::slotRetrieverDone(QByteArray
const&, bool) () from /lib64/libKF5Syndication.so.5
#21 0x7fa8db6e8481 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#22 0x7fa8dc19d844 in Syndication::DataRetriever::dataRetrieved(QByteArray
const&, bool) () from /lib64/libKF5Syndication.so.5
#23 0x7fa8dd0890d1 in Akregator::FeedRetriever::getFinished(KJob*) () from
/lib64/libakregatorprivate.so.5
#24 0x7fa8db6e8481 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#25 0x7fa8dcd20fc6 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#26 0x7fa8dcd26bab in KJob::finishJob(bool) () from
/lib64/libKF5CoreAddons.so.5
#27 0x7fa8db6e8481 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#28 0x7fa8daa54688 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() from /lib64/libKF5KIOCore.so.5
#29 0x7fa8daa4f81b in KIO::SlaveInterface::dispatch() () from
/lib64/libKF5KIOCore.so.5
#30 0x7fa8daa52141 in KIO::Slave::gotInput() () from
/lib64/libKF5KIOCore.so.5
#31 0x7fa8db6e8481 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#32 0x7fa8db6ded2b in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#33 0x7fa8dc3aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#34 0x7fa8db6b41a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#35 0x7fa8db6b7655 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#36 0x7fa8db706c5f in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#37 0x7fa8d971348c in 

[krita] [Bug 473515] Crash when activating Multibrush tool

2023-08-19 Thread Freya Lupen
https://bugs.kde.org/show_bug.cgi?id=473515

Freya Lupen  changed:

   What|Removed |Added

   Keywords||regression
 CC||penguinflyer2...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Freya Lupen  ---
Confirming as a regression caused by commit cabfac1d
(https://invent.kde.org/graphics/krita/-/commit/cabfac1d4ad9a4c5f43b49f8ee4c9cf849abc959).

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

[Elisa] [Bug 473545] New: Some bugs and inadequacies (Linux version)

2023-08-19 Thread Clemens
https://bugs.kde.org/show_bug.cgi?id=473545

Bug ID: 473545
   Summary: Some bugs and inadequacies (Linux version)
Classification: Applications
   Product: Elisa
   Version: 20.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: radb...@gmail.com
  Target Milestone: ---

Preliminary:
I've been trying for a while to recreate all the programs/functions of my
previous "main computer" a Mac Mini, in Linux.
As far as managing and playing music is concerned, so far "Elisa" is the best
approximation to iTunes/Apple Music i could find.  Therefore many thanks to the
developers!

However, I have found some bugs/inadequacies:


1. in my music folder there are subfolders that I do NOT want to play with
Elisa (audio books). In this respect, it should also be possible not only to
add new paths, but also to remove / exclude paths.



2. if I "re-read" the music collection, then NOTHING is visible at first,
neither albums nor artists etc..
Only after quitting and restarting Elisa, the newly read in music collection is
available again.

3. if I click on "Genre" on the left, all matching artists are displayed in the
main window. 
This is not factually correct:  Artists cannot be clearly assigned to a genre,
but albums can.
So the albums matching the genre (with cover) should be displayed in the main
window.

I use "Elisa" under MX-Linux 21.3 on an Intel NUC12 (64 bit).

Best regards
 Clemens

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

[dolphin] [Bug 216433] dragging a folder in to the tab-bar should open a new tab

2023-08-19 Thread Amol Godbole
https://bugs.kde.org/show_bug.cgi?id=216433

Amol Godbole  changed:

   What|Removed |Added

 Status|CONFIRMED   |NEEDSINFO
 Resolution|--- |WORKSFORME

--- Comment #3 from Amol Godbole  ---
This is a very old bug report. The requested feature works as of Dolphin
23.04.3.

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

[plasmashell] [Bug 473544] New: Plasma crashed while using Firefox

2023-08-19 Thread James Eanes Jr.
https://bugs.kde.org/show_bug.cgi?id=473544

Bug ID: 473544
   Summary: Plasma crashed while using Firefox
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jwea...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-11-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I think I had just clicked a link in Firefox. The screen blinked. Then
displayed that Plasma crashed. Note I keep a lot of Tabs open. It's in the
hundreds. However I had just booted up cold about 10 - 15 minuits & had only
opened one though they were all avalable at the top of the screen.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

   PID: 1254 (plasmashell)
   UID: 1000 (jamie)
   GID: 1000 (jamie)
Signal: 6 (ABRT)
 Timestamp: Sat 2023-08-19 16:52:09 EDT (1min 14s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (jamie)
   Boot ID: 515c44574f2140ab8ceee5cb4dfad6b6
Machine ID: 27236a6718aa431db9a9e4eb26e57746
  Hostname: Poly
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.515c44574f2140ab8ceee5cb4dfad6b6.1254.169247832900.zst
(present)
  Size on Disk: 34.8M
   Message: Process 1254 (plasmashell) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64
Stack trace of thread 1254:
#0  0x7fa5066a9d3c n/a (libc.so.6 + 0x8ad3c)
#1  0x7fa50665af32 raise (libc.so.6 + 0x3bf32)
#2  0x7fa508bdeb46 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b46)
#3  0x7fa50665afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7fa5066a9d3c n/a (libc.so.6 + 0x8ad3c)
#5  0x7fa50665af32 raise (libc.so.6 + 0x3bf32)
#6  0x7fa50665afd0 n/a (libc.so.6 + 0x3bfd0)
#7  0x7fa5066a4da4 n/a (libc.so.6 + 0x85da4)
#8  0x7fa5066a7468 pthread_cond_wait (libc.so.6 + 0x88468)
#9  0x7fa5068d1a2b
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b)
#10 0x7fa50860ad80 n/a (libQt5Quick.so.5 + 0x20ad80)
#11 0x7fa506f493f5 _ZN7QWindow5eventEP6QEvent
(libQt5Gui.so.5 + 0x1493f5)
#12 0x7fa507762fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
#13 0x7fa506ab16f8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b16f8)
#14 0x7fa506f3e5cd
_ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE
(libQt5Gui.so.5 + 0x13e5cd)
#15 0x7fa506f11cac
_ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Gui.so.5 + 0x111cac)
#16 0x7fa5083664b0 n/a (libQt5WaylandClient.so.5 + 0xb14b0)
#17 0x7fa5053da7a9 g_main_context_dispatch
(libglib-2.0.so.0 + 0x547a9)
#18 0x7fa5053daa38 n/a (libglib-2.0.so.0 + 0x54a38)
#19 0x7fa5053daacc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#20 0x7fa506b09836
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x309836)
#21 0x7fa506ab017b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2b017b)
#22 0x7fa506ab82d6 _ZN16QCoreApplication4execEv
(libQt5Core.so.5 + 0x2b82d6)
#23 0x5628db72edc3 n/a (plasmashell + 0x26dc3)
#24 0x7fa5066461ca n/a (libc.so.6 + 0x271ca)
#25 0x7fa506646285 __libc_start_main (libc.so.6 + 0x27285)
#26 0x5628db72eee1 n/a (plasmashell + 0x26ee1)

Stack trace of thread 1280:
#0  0x7fa5067170bc read (libc.so.6 + 0xf80bc)
#1  0x7fa505429c9f n/a (libglib-2.0.so.0 + 0xa3c9f)
#2  0x7fa5053da4c5 

[kstars] [Bug 473543] QHY174GPS camera not displaying GPS in images

2023-08-19 Thread Mike M
https://bugs.kde.org/show_bug.cgi?id=473543

Mike M  changed:

   What|Removed |Added

Version|unspecified |3.6.6

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

[kstars] [Bug 473543] New: QHY174GPS camera not displaying GPS in images

2023-08-19 Thread Mike M
https://bugs.kde.org/show_bug.cgi?id=473543

Bug ID: 473543
   Summary: QHY174GPS camera not displaying GPS in images
Classification: Applications
   Product: kstars
   Version: unspecified
  Platform: Ubuntu
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: m...@bptrobotics.com
  Target Milestone: ---

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. Run KSTARS / INDI Control Panel
2. Turn on GPS Header in Camera control panel
3. Turn on Calibration LED in Camera control panel

OBSERVED RESULT
after several minutes all GPS Data fields (in Camera control panel) appear to
be properly populated.  There's a yellow indicator in the radio button next to
[GPS] "Locked"
No Time data or location data is displayed in images.

EXPECTED RESULT
GPS Time Stamp in imaged

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu Linux (x86_64) release 6.2.0-26 generic
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3 built against 5.15.3

ADDITIONAL INFORMATION
camera: QHY174GPS for recording asteroid occultations - GPS is built into the
camera to provide a timestamp in each image.

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

[kde] [Bug 473542] craft kate build fails with qcollectiongenerator not found

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=473542

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/643

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

[kwin] [Bug 237365] Usability: Not focused after opening from systray

2023-08-19 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=237365

Alexander Potashev  changed:

   What|Removed |Added

Product|frameworks-knotifications   |kwin
Version|5.86.0  |5.27.4
  Component|general |platform-x11-standalone
   Assignee|kdelibs-b...@kde.org|kwin-bugs-n...@kde.org

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

[kde] [Bug 473542] New: craft kate build fails with qcollectiongenerator not found

2023-08-19 Thread matthias sweertvaegher
https://bugs.kde.org/show_bug.cgi?id=473542

Bug ID: 473542
   Summary: craft kate build fails with qcollectiongenerator not
found
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: matthias.sweertvaeg...@gmail.com
  Target Milestone: ---

SUMMARY
***
I'm trying to build kate on apple silicon macos using craft. it builds for 15
mins but then fails trying to compile kuserfeedback.

STEPS TO REPRODUCE
1. craft kate

OBSERVED RESULT
build fails

EXPECTED RESULT
build succeeds

SOFTWARE/OS VERSIONS
macOS: 13.3.1 (a) 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
here is the build output (for last target):
*** Handling package: kde/unreleased/kuserfeedback, action: all ***
*** Action: fetch-binary for kde/unreleased/kuserfeedback ***
Could not find kde/unreleased/kuserfeedback=1.2.0 in
https://files.kde.org/craft/master/23.07/macos/clang/arm64/RelWithDebInfo
Could not find kde/unreleased/kuserfeedback=1.2.0 in
https://files.kde.org/craft/master/23.07/macos/clang/arm64/Release
*** kde/unreleased/kuserfeedback not found in cache ***
*** Action: fetch for kde/unreleased/kuserfeedback ***
curl https://download.kde.org/stable/kuserfeedback/kuserfeedback-1.2.0.tar.xz
Warning: --ssl is an insecure option, consider --ssl-reqd instead
#=#=-  #   #   
   
   
   #=O#- #   
#
100.0%
*** Action: unpack for kde/unreleased/kuserfeedback ***
executing command: /Users/matthias/CraftRoot/dev-utils/bin/7za x
/Users/matthias/CraftRoot/download/archives/kde/unreleased/kuserfeedback/kuserfeedback-1.2.0.tar.xz
-so -bsp2 | /usr/bin/tar --directory
/Users/matthias/CraftRoot/build/kde/unreleased/kuserfeedback/work -xf -
*** Action: compile for kde/unreleased/kuserfeedback ***
executing command: /Users/matthias/CraftRoot/dev-utils/bin/cmake -G Ninja
-DBUILD_TESTING=ON -DBUILD_SHARED_LIBS=ON -DENABLE_DOCS=OFF
-DCMAKE_INSTALL_PREFIX=/Users/matthias/CraftRoot
-DCMAKE_PREFIX_PATH=/Users/matthias/CraftRoot
-DCMAKE_REQUIRED_INCLUDES=/Users/matthias/CraftRoot/include
-DCMAKE_C_STANDARD_INCLUDE_DIRECTORIES=/Users/matthias/CraftRoot/include
-DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo
-DKDE_INSTALL_BUNDLEDIR=/Users/matthias/CraftRoot/Applications/KDE
-DAPPLE_SUPPRESS_X11_WARNING=ON -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -S
/Users/matthias/CraftRoot/build/kde/unreleased/kuserfeedback/work/kuserfeedback-1.2.0
-- The C compiler identification is AppleClang 14.0.0.1429
-- The CXX compiler identification is AppleClang 14.0.0.1429
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
- skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
- skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could not set up the appstream test. appstreamcli is missing.
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - not found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Could NOT find Qt5DocTools (missing: Qt5DocTools_DIR)
CMake Warning at /Users/matthias/CraftRoot/lib/cmake/Qt5/Qt5Config.cmake:39
(message):
  Failed to find Qt5 component "DocTools" config file at
  "/Users/matthias/CraftRoot/lib/cmake/Qt5DocTools/Qt5DocToolsConfig.cmake"
Call Stack (most recent call first):
  CMakeLists.txt:43 (find_package)


CMake Error at
/Users/matthias/CraftRoot/lib/cmake/Qt5Help/Qt5HelpConfig.cmake:14 (message):
  The imported target "Qt5::Help" references the file

 "/Users/matthias/CraftRoot/bin/qcollectiongenerator"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 

[kde] [Bug 473541] New: No touch input within the Overview Effect & Present Windows

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473541

Bug ID: 473541
   Summary: No touch input within the Overview Effect & Present
Windows
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: djme...@outlook.com
  Target Milestone: ---

SUMMARY
There is no touch input within the Overview Effect and Present Windows.


STEPS TO REPRODUCE
1. Open Overview Effect or Present Windows.
2. Attempt to use touchscreen.

OBSERVED RESULT
Touchscreen does not function.

EXPECTED RESULT
There should be a response when using the touchscreen (e.g., touching an open
window should bring it into focus).

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-26-generic (64-bit)
Graphics Platform: Wayland

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

[kwin] [Bug 473212] Dragging tabs from Wayland-using Firefox on to the Desktop doesn't work

2023-08-19 Thread DeKay
https://bugs.kde.org/show_bug.cgi?id=473212

--- Comment #7 from DeKay  ---
I have experimented some more with "MOZ_ENABLE_WAYLAND=1 firefox".  I had said
that dragging tabs to the desktop doesn't work and this is true if I do a slow
and deliberate drag from the tab to the Desktop.

BUT if I very quickly grab the tab and almost "flick" it onto the Desktop as
quick as I can, it works about roughly one time in three on average.  Sometimes
it might work every second time, other times I might need to try four or five
times.  Seems like some kind of race condition?

Firefox 116.0.2 and Plasma 5.27.7

Note that dragging a tab from one Firefox window to another Firefox window
always works.

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

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=469079

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #15 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/476

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

[frameworks-kcoreaddons] [Bug 473517] DrKonqi reports crashes for non-KDE software on bugs.kde.org

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=473517

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/368

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

[kde] [Bug 473540] New: Wi-Fi Connection issue

2023-08-19 Thread Adam
https://bugs.kde.org/show_bug.cgi?id=473540

Bug ID: 473540
   Summary: Wi-Fi Connection issue
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: a-boraw...@o2.pl
  Target Milestone: ---

There is a relatively frequent problem with the connection between the phone in
hotspot mode and the Tp-Link TN722N V3.20 wi-fi card.
An exclamation mark appears on the network icon and I have to disconnect and
reconnect, and then the internet works. It works without a problem on Windows
10, so it's probably not a problem with the Wi-Fi card.

KDE Plasma Ver: 5.27.7
Qt: 5.15.10
Kernel: 6.2.0-26

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

[kde] [Bug 473539] New: Double binding of a shortcut with varying results

2023-08-19 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=473539

Bug ID: 473539
   Summary: Double binding of a shortcut with varying results
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Archlinux
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

Hi there. 

Cut (usually on Ctrl+X) and Delete File (usually Shift+Del) has, for some
reason, the same shortcut. 
Cut has Shift + Del as alternative keybinding. 

If I try to delete a file (with Shift + Del) does it show up a message box,
that does tell me about the conflict. 

I am aware, that this is the case for at least two other people, who are also
on Arch. 
They do not experience the issue, and the system just prefers the delete
function to the cut function. 

OBSERVED RESULT

I have to delete the alternative shortcut binding of "Cut" in order to use the
"Delete" functionality. 
By default, I get an error about the ambiguity of the shortcut "Shift + Del" 


EXPECTED RESULT

Delete file when pressing Shift + Del

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

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

[kde] [Bug 473537] Double Keybinding - Establishing standards to prevent this

2023-08-19 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=473537

Matthias  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |MOVED

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

[rkward] [Bug 473254] Graphics version mismatch

2023-08-19 Thread Francisco Cribari
https://bugs.kde.org/show_bug.cgi?id=473254

--- Comment #2 from Francisco Cribari  ---
(In reply to m.eik michalke from comment #1)
> thanks for the report.
> 
> from the information you provided it looks like your installation of RKWard
> was built with R 4.2.2 and you later replaced this with R 4.3.1, which also
> upgraded the R graphics engine from version 15 (compile time) to 16
> (runtime). your build of RKWard can't fully handle that newer version, but
> needs to be recompiled in order to also support  R 4.3.

I do realize that the Arch package needs to be rebuilt. I marked it as
out-of-date. Nonetheless, the package maintainer told me to report the issue
here. (His reply: "Please stop flagging this package out of date. If you want
to report an issue, use the bug tracker.") That's why I filed this bug report.

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

[frameworks-kcoreaddons] [Bug 473517] DrKonqi reports crashes for non-KDE software on bugs.kde.org

2023-08-19 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=473517

--- Comment #2 from Nicolas Fella  ---
Creating a KAboutData itself is fine as long as we don't apply it globally (via
KAboutData::setApplicationData). That's what we do in
https://invent.kde.org/frameworks/kxmlgui/-/blob/master/src/kmainwindow.cpp#L275
though.

What's worse is that KAboutData::applicationData implicitly creates a
KAboutData if none exists, and we use that in several places. Maybe for KF6 we
should just not do that

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

[plasmashell] [Bug 473535] Plasmashell open thousands of pipes and crashing continuously

2023-08-19 Thread Reverier Xu
https://bugs.kde.org/show_bug.cgi?id=473535

--- Comment #4 from Reverier Xu  ---
This bug may related to window decorations.

When I check the "allow the window manager to control the windows" in winecfg,
the bug happens.

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

[dolphin] [Bug 472458] Confirmation for "Closing Windows with multiple Tabs" doesn't work

2023-08-19 Thread Amol Godbole
https://bugs.kde.org/show_bug.cgi?id=472458

Amol Godbole  changed:

   What|Removed |Added

 CC||amolagodb...@gmail.com

--- Comment #6 from Amol Godbole  ---
The confirmation message will not be displayed if the dolphin setting for
'remember opened tabs' has been selected. 
This is available in Settings->Configure Dolphin->Startup->Show on
startup->Folders, tabs, and window state from last time. 

Could you please confirm if you have not configured dolphin to remember tabs?

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

[plasmashell] [Bug 473538] New: Plasma crashes when trying to open Flatpak Thunderbird

2023-08-19 Thread Roguefort
https://bugs.kde.org/show_bug.cgi?id=473538

Bug ID: 473538
   Summary: Plasma crashes when trying to open Flatpak Thunderbird
Classification: Plasma
   Product: plasmashell
   Version: 5.27.7
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: roguefor...@protonmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.7)

Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.9-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.7 [CoredumpBackend]

-- Information about the crash:
I was on Brave browser trying to download info from a medical portal and I went
on my bottom panel, which is a auto hide floating one, to start the flatpak
version of Thunderbird.

The moment I clicked, both Plasma and Brave browser crashed.

Neither Thunderbird or Brave browser opened after plasma restarted.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

   PID: 1963 (plasmashell)
   UID: 1000 (roguefort)
   GID: 1000 (roguefort)
Signal: 11 (SEGV)
 Timestamp: Sat 2023-08-19 18:00:56 WEST (2min 20s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (roguefort)
   Boot ID: efeebe2eaa234ebe8668a54fd1f4836c
Machine ID: 8339ac74cebc4cd082053c8fbb506226
  Hostname: localhost.localdomain
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.efeebe2eaa234ebe8668a54fd1f4836c.1963.169246445600.zst
(present)
  Size on Disk: 55.3M
   Message: Process 1963 (plasmashell) of user 1000 dumped core.

Stack trace of thread 1978:
#0  0x7fc93e491e4c __pthread_kill_implementation (libc.so.6
+ 0x91e4c)
#1  0x7fc93e43f126 raise (libc.so.6 + 0x3f126)
#2  0x7fc941010d3a _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x7d3a)
#3  0x7fc93e43f1f0 __restore_rt (libc.so.6 + 0x3f1f0)
#4  0x7fc93e491e4c __pthread_kill_implementation (libc.so.6
+ 0x91e4c)
#5  0x7fc93e43f126 raise (libc.so.6 + 0x3f126)
#6  0x7fc93e43f1f0 __restore_rt (libc.so.6 + 0x3f1f0)
#7  0x7fc93ed04507 _ZN6QMutex4lockEv (libQt5Core.so.5 +
0x104507)
#8  0x7fc93ef46785 n/a (libQt5Core.so.5 + 0x346785)
#9  0x7fc93d8b6730 g_main_context_check (libglib-2.0.so.0 +
0x5d730)
#10 0x7fc93d8b6ce8 n/a (libglib-2.0.so.0 + 0x5dce8)
#11 0x7fc93d8b6e5c g_main_context_iteration
(libglib-2.0.so.0 + 0x5de5c)
#12 0x7fc93ef464be
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x3464be)
#13 0x7fc93eeebffb
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2ebffb)
#14 0x7fc93ed02dce _ZN7QThread4execEv (libQt5Core.so.5 +
0x102dce)
#15 0x7fc940124517 n/a (libQt5DBus.so.5 + 0x1a517)
#16 0x7fc93ed03ffd n/a (libQt5Core.so.5 + 0x103ffd)
#17 0x7fc93e48ffa4 start_thread (libc.so.6 + 0x8ffa4)
#18 0x7fc93e5187fc __clone3 (libc.so.6 + 0x1187fc)

Stack trace of thread 1985:
#0  0x7fc93e48c54e __futex_abstimed_wait_common (libc.so.6
+ 0x8c54e)
#1  0x7fc93e48f290 pthread_cond_wait@@GLIBC_2.3.2
(libc.so.6 + 0x8f290)
#2  0x7fc9320c7f2b n/a (r600_dri.so + 0xc7f2b)
#3  0x7fc93217 n/a (r600_dri.so + 0x17)
#4  0x7fc93e48ffa4 start_thread (libc.so.6 + 0x8ffa4)
#5  0x7fc93e5187fc __clone3 (libc.so.6 + 0x1187fc)

Stack trace of thread 2231:
#0  0x7fc93e515141 pselect (libc.so.6 + 0x115141)
#1  0x7fc93cbcbb37 n/a (libusbmuxd-2.0.so.6 + 0x4b37)
#2  0x7fc93cbcc7a3 n/a (libusbmuxd-2.0.so.6 + 0x57a3)
#3  0x7fc93e48ffa4 start_thread (libc.so.6 + 0x8ffa4)
#4  0x7fc93e5187fc __clone3 (libc.so.6 + 0x1187fc)

Stack trace of thread 2277:
#0  0x7fc93e50a0af __poll (libc.so.6 + 0x10a0af)
#1  0x7fc93d8b6d3e n/a (libglib-2.0.so.0 + 0x5dd3e)
#2  0x7fc93d8b6e5c g_main_context_iteration

[krita] [Bug 473527] Text-in-shape layout is different from Inkscape

2023-08-19 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=473527

--- Comment #5 from Alvin Wong  ---
It looks like maybe Inkscape is laying out the first line using the calculated
line-height, but Krita is using the actual bounding boxes (or maybe
ascent/descent).

No clue what's going on with the leading. It looks like the actual line height
stops scaling correctly once it's below a certain value.

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

[kde] [Bug 473537] New: Double Keybinding - Establishing standards to prevent this

2023-08-19 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=473537

Bug ID: 473537
   Summary: Double Keybinding - Establishing standards to prevent
this
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

Hi there. KDE seems to regularly ship releases with double and triple usages of
certain key combinations as shortcuts, who all even each other out, and KDE
then tells to to manually check. 

Sorry, why do we need to set the standard to instantly delete files in Dolphin
to Shift + Del, as we do since ever, and then also as an optional command to
Ctrl+X? Like, whats the point? I am pretty sure I already used Shift + Del to
delete stuff in Windows 98SE, and KDE luckily adopts that standard. 

Now, since the newest update, is Shift + Del set to "Cut" as well, and neither
works. 

STEPS TO REPRODUCE
1. Go into Dolphin
2. Mark some file that you like to delete
3. Hit Shift + Del

OBSERVED RESULT

KDE spawns a message, that tells me that the shortcut is set for multiple
commands, and it does not know which one you like. It does not say which
shortcut that is, it does also not offer to spawn the shortcut application for
you with the command pre-applied in the search bar, to handle this. 

EXPECTED RESULT

It just works. Shift + Del deletes the file 

Arch rolling

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3


ADDITIONAL INFORMATION

Sorry guys. Could we just setup some standard, that does not allow, that such a
setup ever ships? There needs to be some regulatory statement around this
issue, it just comes back time after time

Prevent people from shipping double keybindings, particularly if they **did not
test if it actually works** 
Thanks

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

[krita] [Bug 473536] New: Cannot open animated WEBP images in Krita

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473536

Bug ID: 473536
   Summary: Cannot open animated WEBP images in Krita
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: alerikaisatt...@protonmail.com
  Target Milestone: ---

SUMMARY
Opening animated WEBP images in Krita fails with "The file format contains
unsupported features"

STEPS TO REPRODUCE
1. Open an animated WEBP image in Krita

OBSERVED RESULT
Error message "The file format contains unsupported features" is displayed

EXPECTED RESULT
The file should open

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Observed with at least 2 different files

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

[plasmashell] [Bug 446627] Pager does not show correct size when PLASMA_USE_QT_SCALING=1 is set on X11

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=446627

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED

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

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

[plasma-pa] [Bug 473093] Multiple duplicate entries after interface re-connection

2023-08-19 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=473093

Nicolas Fella  changed:

   What|Removed |Added

 CC||maxbar...@tutanota.com

--- Comment #19 from Nicolas Fella  ---
*** Bug 473531 has been marked as a duplicate of this bug. ***

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

[kde] [Bug 473531] Audio widget does not change volume/duplicate audio devices

2023-08-19 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=473531

Nicolas Fella  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||nicolas.fe...@gmx.de

--- Comment #1 from Nicolas Fella  ---


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

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

[plasmashell] [Bug 446627] Pager does not show correct size when PLASMA_USE_QT_SCALING=1 is set on X11

2023-08-19 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=446627

Fushan Wen  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

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

[plasmashell] [Bug 356446] [Meta] Enable Qt scaling on X11

2023-08-19 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=356446
Bug 356446 depends on bug 446627, which changed state.

Bug 446627 Summary: Pager does not show correct size when 
PLASMA_USE_QT_SCALING=1 is set on X11
https://bugs.kde.org/show_bug.cgi?id=446627

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

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

[digikam] [Bug 473481] Digikam 8.1 crashes on startup

2023-08-19 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=473481

--- Comment #4 from Maik Qualmann  ---
Hmm, it crashes in the Breeze Widget Style we added in digiKam-8.1.0. However,
there seems to be access to a Breeze component installed on your system
"/lib/x86_64-linux-gnu/libbreezecommon5.so.5"

@Gilles, Drumsal uses the AppImage.

Maik

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

[plasmashell] [Bug 473535] Plasmashell open thousands of pipes and crashing continuously

2023-08-19 Thread Reverier Xu
https://bugs.kde.org/show_bug.cgi?id=473535

Reverier Xu  changed:

   What|Removed |Added

 CC||reverier...@outlook.com

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

[plasmashell] [Bug 473535] Plasmashell open thousands of pipes and crashing continuously

2023-08-19 Thread Reverier Xu
https://bugs.kde.org/show_bug.cgi?id=473535

--- Comment #3 from Reverier Xu  ---
I tried to list all the files in plasmashell's proc fd, and i got this:

$ ll /proc/(pidof plasmashell)/fd
[/proc/9741/fd/469: No such file or directory (os error 2)]
Permissions Size User Date ModifiedName
lr-x--64 reverier 2023-08-19 23:52 0 -> /dev/null
lrwx--@   64 reverier 2023-08-19 23:52 1 -> socket:[84562]
lrwx--@   64 reverier 2023-08-19 23:52 2 -> socket:[84562]
lrwx--@   64 reverier 2023-08-19 23:52 3 -> socket:[112714]
lrwx--64 reverier 2023-08-19 23:52 4 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 5 -> anon_inode:[eventfd]
lrwx--@   64 reverier 2023-08-19 23:52 6 -> socket:[115118]
lrwx--@   64 reverier 2023-08-19 23:52 7 -> socket:[115119]
lr-x--64 reverier 2023-08-19 23:52 8 -> anon_inode:inotify
lrwx--@   64 reverier 2023-08-19 23:52 9 -> socket:[104920]
lrwx--64 reverier 2023-08-19 23:52 10 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 11 -> anon_inode:[eventfd]
lr-x--64 reverier 2023-08-19 23:52 12 -> pipe:[104921]
l-wx--64 reverier 2023-08-19 23:52 13 -> pipe:[104921]
lr-x--64 reverier 2023-08-19 23:52 14 -> pipe:[97985]
l-wx--64 reverier 2023-08-19 23:52 15 -> pipe:[97985]
lr-x--64 reverier 2023-08-19 23:52 16 -> anon_inode:inotify
lrwx--64 reverier 2023-08-19 23:52 17 -> /dev/nvidiactl
lrwx--64 reverier 2023-08-19 23:52 18 -> /dev/nvidia0
lrwx--64 reverier 2023-08-19 23:52 19 -> /dev/nvidia0
lrwx--64 reverier 2023-08-19 23:52 20 -> /dev/dri/renderD128
lrwx--64 reverier 2023-08-19 23:52 21 -> /dev/dri/renderD128
lrwx--64 reverier 2023-08-19 23:52 22 -> /dev/dri/renderD128
lrwx--64 reverier 2023-08-19 23:52 23 -> /dev/dri/renderD128
lrwx--64 reverier 2023-08-19 23:52 24 -> anon_inode:[eventfd]
lrwx--@   64 reverier 2023-08-19 23:52 25 -> socket:[98515]
lr-x--64 reverier 2023-08-19 23:52 26 ->
/home/reverier/.cache/ksycoca5_zh_OJh4RQrrNygTONJgtS85EOOYpRc=
lr-x--64 reverier 2023-08-19 23:52 27 ->
/home/reverier/.local/share/mime/mime.cache
lr-x--64 reverier 2023-08-19 23:52 28 -> /usr/share/mime/mime.cache
lr-x--64 reverier 2023-08-19 23:52 29 -> anon_inode:inotify
lrwx--64 reverier 2023-08-19 23:52 30 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 31 -> /memfd:pulseaudio (deleted)
lrwx--64 reverier 2023-08-19 23:52 32 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 33 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 34 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 35 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 36 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 37 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 38 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 39 -> anon_inode:[eventfd]
lrwx--@   64 reverier 2023-08-19 23:52 40 -> socket:[104945]
lrwx--64 reverier 2023-08-19 23:52 41 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 42 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 43 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 44 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 45 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 46 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 47 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 48 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 49 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 50 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 51 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 52 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 53 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 54 -> anon_inode:[eventfd]
lrwx--64 reverier 2023-08-19 23:52 55 -> /memfd:kwayland-shared
(deleted)
lrwx--64 reverier 2023-08-19 23:52 56 -> anon_inode:[eventfd]
lr-x--64 reverier 2023-08-19 23:52 57 -> anon_inode:inotify
lr-x--64 reverier 2023-08-19 23:52 58 -> /proc/9741/mounts
lrwx--@   64 reverier 2023-08-19 23:52 59 -> socket:[104961]
lr-x--64 reverier 2023-08-19 23:52 60 -> anon_inode:inotify
lr-x--64 reverier 2023-08-19 23:52 61 ->
/home/reverier/.local/share/kactivitymanagerd/resources/database
lrwx--64 reverier 2023-08-19 23:52 62 ->
/home/reverier/.local/share/kactivitymanagerd/resources/database-wal
lrwx--64 reverier 2023-08-19 23:52 63 ->
/home/reverier/.local/share/kactivitymanagerd/resources/database-shm
lrwx--@   64 reverier 2023-08-19 23:52 64 

[digikam] [Bug 473481] Digikam 8.1 crashes on startup

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473481

--- Comment #3 from caulier.gil...@gmail.com ---
It crash in Breeze widget style theme for Qt, not digiKam.

It's typically a problem in this components from your system.

Gilles Caulier

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

[plasmashell] [Bug 473535] Plasmashell open thousands of pipes and crashing continuously

2023-08-19 Thread Reverier Xu
https://bugs.kde.org/show_bug.cgi?id=473535

--- Comment #2 from Reverier Xu  ---
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Archlinux Plasma 5.27.7
KDE Plasma Version: 5.27.7 on wayland
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

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

[plasmashell] [Bug 473535] Plasmashell open thousands of pipes and crashing continuously

2023-08-19 Thread Reverier Xu
https://bugs.kde.org/show_bug.cgi?id=473535

--- Comment #1 from Reverier Xu  ---
STEP TO REPRODUCE:

1. Open some games runs in wine, such as Osu! or MuseDash..
2. the plasmashell runs slow until freeze, the taskbar won't responding, and
then crashed.

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

[digikam] [Bug 473481] Digikam 8.1 crashes on startup

2023-08-19 Thread Drumsal
https://bugs.kde.org/show_bug.cgi?id=473481

--- Comment #2 from Drumsal  ---
Reading symbols from digikam...
Starting program: /tmp/.mount_digiKaWyh62O/usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffb65ff700 (LWP 62670)]
[New Thread 0x7fffb49ff700 (LWP 62673)]
[New Thread 0x7fffa65ff700 (LWP 62674)]
[New Thread 0x7fffa5dfe700 (LWP 62676)]
[New Thread 0x7fffa55fd700 (LWP 62677)]
[New Thread 0x7fffa4dfc700 (LWP 62678)]
[New Thread 0x7fff8700 (LWP 62679)]
[New Thread 0x7fff87fff700 (LWP 62680)]
[New Thread 0x7fff8f7fe700 (LWP 62681)]
[New Thread 0x7fff8effd700 (LWP 62682)]
[New Thread 0x7fff8e7fc700 (LWP 62683)]
[New Thread 0x7fff8dffb700 (LWP 62685)]
[New Thread 0x7fff8d7fa700 (LWP 62686)]
[New Thread 0x7fff8cff9700 (LWP 62687)]
[New Thread 0x7fff877fe700 (LWP 62688)]
[New Thread 0x7fff86ffd700 (LWP 62689)]
[New Thread 0x7fff867fc700 (LWP 62690)]
[New Thread 0x7fff85ffb700 (LWP 62691)]
[New Thread 0x7fff857fa700 (LWP 62692)]
[New Thread 0x7fff84ff9700 (LWP 62693)]
[New Thread 0x7fff4700 (LWP 62694)]
[New Thread 0x7fff4f7fe700 (LWP 62695)]
[New Thread 0x7fff4effd700 (LWP 62696)]
[New Thread 0x7fff4e7fc700 (LWP 62697)]
[New Thread 0x7fff4dffb700 (LWP 62698)]
[New Thread 0x7fff4d7fa700 (LWP 62699)]
[New Thread 0x7fff4cff9700 (LWP 62700)]
[New Thread 0x7fff2700 (LWP 62701)]
[New Thread 0x7fff277fe700 (LWP 62702)]
[New Thread 0x7fff2f7fe700 (LWP 62703)]
[New Thread 0x7fff2effd700 (LWP 62704)]
[New Thread 0x7fff2e7fc700 (LWP 62705)]
[New Thread 0x7fff2dffb700 (LWP 62706)]
[New Thread 0x7fff2d7fa700 (LWP 62707)]
[New Thread 0x7fff2cff9700 (LWP 62724)]
[New Thread 0x7fff27fff700 (LWP 62725)]
[New Thread 0x7fff07fff700 (LWP 62727)]
[Thread 0x7fff07fff700 (LWP 62727) exited]
[New Thread 0x7fff07fff700 (LWP 62749)]
[New Thread 0x7ffef79ff700 (LWP 62750)]
[Detaching after fork from child process 62751]
[New Thread 0x7ffecb3ff700 (LWP 63309)]
[0819/174121.374266:WARNING:resource_bundle_qt.cpp(119)]
locale_file_path.empty() for locale 
[New Thread 0x7ffec97ff700 (LWP 63335)]
[Detaching after fork from child process 63336]
[Detaching after fork from child process 63337]
[Detaching after fork from child process 63338]
[0819/174121.527123:WARNING:resource_bundle_qt.cpp(119)]
locale_file_path.empty() for locale 
[0819/174121.527145:WARNING:resource_bundle_qt.cpp(119)]
locale_file_path.empty() for locale 
[New Thread 0x7ffec8ffe700 (LWP 63361)]
[New Thread 0x7ffebbfff700 (LWP 63362)]
[New Thread 0x7ffebb7fe700 (LWP 63363)]
[New Thread 0x7ffebaffd700 (LWP 63364)]
[New Thread 0x7ffeba7fc700 (LWP 63365)]
[New Thread 0x7ffeb9ffb700 (LWP 63366)]
[New Thread 0x7ffeb97fa700 (LWP 63367)]
[New Thread 0x7ffeb8ff9700 (LWP 63368)]
[New Thread 0x7ffea3fff700 (LWP 63369)]
[New Thread 0x7ffea37fe700 (LWP 63370)]
[New Thread 0x7ffea2ffd700 (LWP 63371)]
[New Thread 0x7ffea27fc700 (LWP 63372)]
[New Thread 0x7fffe700 (LWP 63394)]
[Thread 0x7fffe700 (LWP 63394) exited]
[New Thread 0x7ffea1ffb700 (LWP 63395)]
[Thread 0x7ffea1ffb700 (LWP 63395) exited]
[New Thread 0x7ffea1ffb700 (LWP 63396)]
[Thread 0x7ffea1ffb700 (LWP 63396) exited]
[New Thread 0x7ffea1ffb700 (LWP 63399)]
[New Thread 0x7fff8c3ff700 (LWP 63403)]
[New Thread 0x7fff843ff700 (LWP 63405)]
[Thread 0x7fff843ff700 (LWP 63405) exited]
[Thread 0x7fff8c3ff700 (LWP 63403) exited]
[Thread 0x7ffea1ffb700 (LWP 63399) exited]
[New Thread 0x7ffea1ffb700 (LWP 63409)]
[New Thread 0x7ffea17fa700 (LWP 63410)]
[New Thread 0x7ffea0ff9700 (LWP 63411)]
[New Thread 0x7ffe83fff700 (LWP 63412)]
[New Thread 0x7ffe837fe700 (LWP 63413)]
[New Thread 0x7ffe82ffd700 (LWP 63414)]
[New Thread 0x7ffe827fc700 (LWP 63415)]
[New Thread 0x7ffe81ffb700 (LWP 63416)]
[New Thread 0x7ffe817fa700 (LWP 63417)]
[New Thread 0x7ffe80ff9700 (LWP 63418)]
[New Thread 0x7ffe5bfff700 (LWP 63426)]
[Detaching after fork from child process 63427]
[0819/174124.012606:WARNING:resource_bundle_qt.cpp(119)]
locale_file_path.empty() for locale 
[New Thread 0x7ffe5b7fe700 (LWP 63458)]
unknown: Unhandled container to remove :  Digikam::DigikamApp
[New Thread 0x7ffe5a3ff700 (LWP 63497)]
[New Thread 0x7ffe59bfe700 (LWP 63498)]
[New Thread 0x7ffe593fd700 (LWP 63499)]
[New Thread 0x7ffe58bfc700 (LWP 63500)]
[New Thread 0x7ffe43fff700 (LWP 63501)]
[New Thread 0x7ffe437fe700 (LWP 63502)]
[Thread 0x7ffe5a3ff700 (LWP 63497) exited]
[Thread 0x7ffe59bfe700 (LWP 63498) exited]
[Thread 0x7ffe43fff700 (LWP 63501) exited]
[Thread 0x7ffe593fd700 (LWP 63499) exited]
[Thread 0x7ffe437fe700 (LWP 63502) exited]
[Thread 0x7ffe58bfc700 (LWP 63500) exited]
[New Thread 0x7ffe58bfc700 (LWP 63523)]
--Type  for more, q to quit, c to continue without paging--c

Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
0x73b62e7c in ?? () from /lib/x86_64-linux-gnu/libbreezecommon5.so.5
(gdb) backtrace
#0  0x73b62e7c in ?? ()
   from /lib/x86_64-linux-gnu/libbreezecommon5.so.5
#1  0x73b62cde in 

[plasmashell] [Bug 473535] New: Plasmashell open thousands of pipes and crashing continuously

2023-08-19 Thread Reverier Xu
https://bugs.kde.org/show_bug.cgi?id=473535

Bug ID: 473535
   Summary: Plasmashell open thousands of pipes and crashing
continuously
Classification: Plasma
   Product: plasmashell
   Version: 5.27.7
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: reverier...@outlook.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 161060
  --> https://bugs.kde.org/attachment.cgi?id=161060=edit
fd in plasmashell's proc

SUMMARY

Plasma shell will freeze for a while and then crash when I open some wine-games
on wayland. If I close the game immediately when the shell is frozen, the
plasmashell could be resumed. not tested on X11.

I found logs in journal below:

```
Aug 19 19:35:47 Reverier-Arch systemd[1691]: Starting KDE Plasma Workspace...
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]: Checking screens: available:
(QScreen(0x555c1bdf2100, name="eDP-1")) redundant: QHash() fake: QSet() all:
(QScreen(0x555c1bdf2100, name="eDP-1"))
Aug 19 19:35:47 Reverier-Arch systemd[1691]: Started KDE Plasma Workspace.
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]: kf.plasma.quick: Applet
preload policy set to 1
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]: kf.kio.core: Malformed JSON
protocol file for protocol: "trash" , number of the ExtraNames fields should
match the number of ExtraTypes fields
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]:
org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment
to AppletsLayout
Aug 19 19:35:47 Reverier-Arch kioslave5[4304]: kf.kio.core: Malformed JSON
protocol file for protocol: "trash" , number of the ExtraNames fields should
match the number of ExtraTypes fields
Aug 19 19:35:47 Reverier-Arch kioslave5[4304]: QObject::connect: No such slot
DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
Aug 19 19:35:47 Reverier-Arch kioslave5[4304]: QObject::connect: No such slot
DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Aug 19 19:35:47 Reverier-Arch plasmashell[4269]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: Trying to use rootObject
before initialization is completed, whilst using setInitializationDelayed.
Forcing completion
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: org.kde.plasma.kicker: Entry
is not valid "org.kde.kontact.desktop" QSharedPointer(0x555c1ce7d040)
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: org.kde.plasma.kicker: Entry
is not valid "ktp-contactlist.desktop" QSharedPointer(0x555c1ce72910)
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: org.kde.plasma.kicker: Entry
is not valid "org.kde.discover.desktop" QSharedPointer(0x555c1ce7d2a0)
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: org.kde.plasma.kicker: Entry
is not valid "org.kde.kontact.desktop" QSharedPointer(0x555c1ce7ce50)
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: org.kde.plasma.kicker: Entry
is not valid "ktp-contactlist.desktop" QSharedPointer(0x555c1ce7bd10)
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: org.kde.plasma.kicker: Entry
is not valid "org.kde.discover.desktop" QSharedPointer(0x555c1ce73230)
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: Cyclic dependency detected
between
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml"
and
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]: Cyclic dependency detected
between
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml"
and
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95:
TypeError: Cannot read property 'airplaneModeAvailable' of null
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95:
TypeError: Cannot read property 'airplaneModeAvailable' of null
Aug 19 19:35:48 Reverier-Arch plasmashell[4269]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:18:1:
QML MouseArea (parent or ancestor of QQuickLayoutAttached): 

[kwin] [Bug 473005] Firefox always openes non-fullscreen

2023-08-19 Thread Henning
https://bugs.kde.org/show_bug.cgi?id=473005

--- Comment #4 from Henning  ---
So my fix was to set the programs window properties to "vertically maximised"
and "horizontally maximized".

But in a former issue I already mentioned how extremely confusing the "set
window properties" dialog is (hard to find, unclear whats given properties and
whats wanted properties)

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

[kmymoney] [Bug 473522] Description of woob import

2023-08-19 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473522

Jack  changed:

   What|Removed |Added

  Component|website |importer

--- Comment #1 from Jack  ---
Whenever asking for help, please include your Operating System and/or
Distribution.  (platform in the bugheader)  I have no idea if Woob is available
on Windows or MacOS.  Also, the website component is used for bugs in the
KMyMoney website.  I've adjusted to importer.
Unfortunately, the handbook is known to be out of date.  I am actually working
on a complete review and  update, but that has just begun, and will not likely
be available until the eventual release of 5.2.  
For instructions, have you looked at the woob web site at all?  The site
referenced in the doc is correct https://woob.tech.  It is just the particular
page which has changed or removed.
The woob plugin for KMyMoney was added by a developer who is no longer actively
participating with the project, and I don't believe anyone else on the team has
actually used it.
My best advice for now is to be sure you have woob set up and functional from
command line for use with your bank.
The woob plugin is activated at runtime only if woob is found on your system. 
If it is installed and not found, there might be some hint of why it can't find
it in the console output.

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

[dolphin] [Bug 390631] On middle-click, open file with second application in list with applications for this file type

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=390631

kin...@proton.me changed:

   What|Removed |Added

 CC||kin...@proton.me

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

[frameworks-kio] [Bug 467308] Filesystem Browser: "Open with" always asks for application to open with

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467308

kin...@proton.me changed:

   What|Removed |Added

 CC||kin...@proton.me

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

[digikam] [Bug 473534] Metadata tags not written to HEIF files

2023-08-19 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=473534

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||8.2.0

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

[digikam] [Bug 473534] Metadata tags not written to HEIF files

2023-08-19 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=473534

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #1 from Maik Qualmann  ---
Our main metadata engine is Exiv2, but this is limited to read only in HEIF.
To write metadata to HEIF images, go to the digiKam setup under Metadata and
enable writing with ExifTool.
Now metadata in Exif and XMP can be written in HEIF images. Note that when you
interact with Windows Explorer, it writes the metadata into a QuickTime
container, which in principle would be possible with ExifTool, but we don't
support it at the moment. We already have a bug report for this.

Maik

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

[krita] [Bug 473527] Text-in-shape layout is different from Inkscape

2023-08-19 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=473527

--- Comment #4 from Alvin Wong  ---
Changing that to 1e-6 only makes a very minor difference (the whole text block
is shifted up by 1px).

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

[digikam] [Bug 473534] New: Metadata tags not written to HEIF files

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473534

Bug ID: 473534
   Summary: Metadata tags not written to HEIF files
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: car...@web.de
  Target Milestone: ---

SUMMARY
Tags are not written to HEIF files if enabled in settings (not to exif, iptc,
or xmp).
This works fine with the same setup using JPEG files.

STEPS TO REPRODUCE
1. Enable writing of image tags (Settings > configure digiKam > Metadata >
Behaviour > Check "Image Tags")
2. Assign a tag to a HEIF file
3. Write to file (Item > Write Metadata to File)

OBSERVED RESULT
No metadata written.

EXPECTED RESULT
metadata written to exif, iptc, and xmp - same as for jpeg

SOFTWARE/OS VERSIONS
Windows: Windows 11 22H2

ADDITIONAL INFORMATION
[10720] digikam.metaengine: Loading metadata with "Exiv2" backend from
"C:/img/test1.heic"
[10720] digikam.general: Writing tags
[10720] digikam.general: One job is done
[10720] digikam.general: -- New Keywords ("Wien")
[10720] digikam.metaengine: "C:/img/test1.heic"  ==> New Iptc Keywords: 
("Wien")
[10720] digikam.metaengine: MetaEngine::metadataWritingMode 0
[10720] digikam.general: One job is done
[10720] digikam.metaengine: Will write Metadata to file "C:/img/test1.heic"
[10720] digikam.general: One job is done
[10720] digikam.general: One job is done
[10720] digikam.metaengine: wroteComment:  false
[10720] digikam.metaengine: wroteEXIF:  false
[10720] digikam.metaengine: wroteIPTC:  false
[10720] digikam.metaengine: wroteXMP:  false
[10720] digikam.metaengine: Writing metadata is not supported for file
"test1.heic"
[10720] digikam.metaengine: ExifTool "Load Metadata" "-json -G:0:1:2:4:6 -l
C:\\img\\test1.heic"
[10720] digikam.metaengine: Loading metadata with "Exiv2" backend from
"C:/img/test1.heic"
[10720] digikam.general: Metadata loading with Exiv2 took 1 ms ( true )
[10720] digikam.general: "Standard Exif Tags" decoding took 0 ms ( false )
[10720] digikam.general: "MakerNote Exif Tags" decoding took 0 ms ( false )
[10720] digikam.general: "IPTC Records" decoding took 0 ms ( true )
[10720] digikam.general: "XMP Schema" decoding took 0 ms ( true )
[10720] digikam.general: One job is done
[10720] digikam.general: List of Pending Jobs is empty
[10720] digikam.general: Event is dispatched through a passive pop-up
[10720] QLayout: Attempting to add QLayout "" to QWidget "", which already has
a layout
[10720] digikam.general: Cancel Main Thread
[10720] digikam.general: Finish Main Thread
[10720] digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command
completed
[10720] digikam.metaengine: ExifTool complete command for action "Load
Metadata" with elasped time (ms): 20
[10720] digikam.metaengine: ExifTool Json map size: 177
[10720] digikam.metaengine: ExifTool parsed command for action "Load Metadata"
157 properties decoded
[10720] digikam.metaengine: ExifTool complete "Load Metadata" for
"C:/img/test1.heic"

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

[kwin] [Bug 473115] clientFullScreenSet signal is not being emitted on Wayland

2023-08-19 Thread William Franco Abdul Hai
https://bugs.kde.org/show_bug.cgi?id=473115

William Franco Abdul Hai  changed:

   What|Removed |Added

 CC||haiwilli...@gmail.com

--- Comment #1 from William Franco Abdul Hai  ---
I can confirm that I'm also facing the same problem on Wayland. Same Plasma and
Frameworks versions as OP, and QT version 5.15.9. I'm running NixOS unstable.

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

[plasmashell] [Bug 472003] Clicking on apps' systray icons have no effect (regular applets work fine)

2023-08-19 Thread Yuking
https://bugs.kde.org/show_bug.cgi?id=472003

--- Comment #17 from Yuking  ---
(In reply to Kai Uwe Broulik from comment #16)
> Qt bug, potential fix submitted at
> https://codereview.qt-project.org/c/qt/qtdeclarative/+/497473

Solved with this patch. THX.

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

[kwin] [Bug 473533] New: Graphics artifacts on transparent objects

2023-08-19 Thread ray
https://bugs.kde.org/show_bug.cgi?id=473533

Bug ID: 473533
   Summary: Graphics artifacts on transparent objects
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: r...@deepmail.cc
  Target Milestone: ---

SUMMARY
***
When i using transparent panels, (default breeze), transparent menus,
transparent terminal with blur effect enabled there is lot of graphics
artifacts like flashing boxes, lines. Usually when object is active. Terminal
behind active window making most of this annoying glitches. I started using
wayland and this effect is more intensive. Hope plasma 6 will fix this problem
***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(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.

[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm

2023-08-19 Thread Alois Wohlschlager
https://bugs.kde.org/show_bug.cgi?id=449265

--- Comment #10 from Alois Wohlschlager  ---
> Thanks a lot. I tried to mail hostap but it keeps blocking my mail for some
> reason and I couldn't figure out where I should report them the bug.

I have no experience with this list in particular, but it is likely that the
first message sent from a new email address needs moderator approval (this is a
common process to prevent spam).

> Also, I have issue with both WPA2 and WPA3 encryption.

You actually don't. When you tell NetworkManager to create a WPA2 access point,
it actually creates a hybrid WPA2/WPA3 access point. Your other device prefers
to connect to WPA3 and subsequently fails.

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

[plasmashell] [Bug 456453] When using Qt scaling on X11, windows in the 2nd screen are placed outside visible area when a panel is placed between screens

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=456453

--- Comment #6 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kwindowsystem/-/merge_requests/113

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

[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=449265

--- Comment #9 from sk.griffi...@gmail.com ---
(In reply to Alois Wohlschlager from comment #8)
> My adapter broke, and I cannot reproduce the bug with the new device any
> more. Since we already figured out the bug is likely not in Plasma, I'd try
> the hostap mailing list. The problem appears to be that some
> device/driver/wpa_supplicant combinations fail to set up a WPA3 access point
> properly.

Thanks a lot. I tried to mail hostap but it keeps blocking my mail for some
reason and I couldn't figure out where I should report them the bug.

Also, I have issue with both WPA2 and WPA3 encryption.

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

[lattedock] [Bug 473532] New: Does not Respect "Primary" screen on Wayland

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473532

Bug ID: 473532
   Summary: Does not Respect "Primary" screen on Wayland
Classification: Plasma
   Product: lattedock
   Version: git (master)
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: st...@techxero.com
  Target Milestone: ---

SUMMARY

Running latest Latte-Dock built from source. I have 3 Monitors,
2xHDMI(HDMI-A-1+HDMI-A-2) +1xDP-1, On Wayland although I set it to be shown on
Primary display in the center (DP-1) it keeps showing on Right Monitor
(HDMI-A-1). If I set it to specifically show on DP-1 when I log back into X11
Latte will not show at all until I go to its settings and put it back to
"Primary"

Any help would be appreciated

STEPS TO REPRODUCE
1.  Set Latte to show on "Primary" in settings
2. In a 2 or more Monitor setup will not respect position

OBSERVED RESULT

On Wayland although I set it to be shown on Primary display in the center
(DP-1) it keeps showing on Right Monitor (HDMI-A-1).

EXPECTED RESULT

For it to open on actual Primary monitor

SOFTWARE/OS VERSIONS

Linux : ArchLinux
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109
Qt Version: 5.15.10

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

[kwin] [Bug 473005] Firefox always openes non-fullscreen

2023-08-19 Thread Henning
https://bugs.kde.org/show_bug.cgi?id=473005

Henning  changed:

   What|Removed |Added

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

--- Comment #3 from Henning  ---
I mean maximized. I always click on their CSD "fullscreen" button and have it
in fullscreen. But "macos ugly like" it always opens vertically fullscreen,
horizontally with a bit of space. It never seems to remember my sizing. Is this
something Firefox has to change or Plasma can enforce?

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

[gwenview] [Bug 443168] gwenview ignores settings in initial sort order

2023-08-19 Thread Robin Bankhead
https://bugs.kde.org/show_bug.cgi?id=443168

--- Comment #12 from Robin Bankhead  ---
(In reply to Christoph Cullmann from comment #11)
> The first thing I need to do is always to set the order twice. It shows sort
> by name, but doesn't do that, I need to set an other one and set it back.
> 
> I think the old behaviour was a lot saner, I fail to see why it should be in
> sync with Dolphin at all, e.g. Kate or even our file open dialogs are not in
> sync and that makes sense.

Very small clarification: You don't need to flip to another selection and back;
clicking on the (already-selected) radio causes it to take its correct effect.

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

[Bluedevil] [Bug 473264] Disabling Bluetooth with still connected device causes the applet to grey out, soft crash if any

2023-08-19 Thread Henning
https://bugs.kde.org/show_bug.cgi?id=473264

--- Comment #5 from Henning  ---
It seems to work normally now, some journalctl logs

Aug 19 14:12:50 fedora bluetoothd[1051]: src/profile.c:record_cb() Unable to
get Hands-Free Voice gateway SDP record: Host is down
Aug 19 14:12:57 fedora bluetoothd[1051]:
profiles/gap/gas.c:foreach_gap_service() More than one GAP service exists for
this device
Aug 19 14:13:06 fedora kernel: Bluetooth: hci0: ACL packet for unknown
connection handle 256
Aug 19 14:13:10 fedora flatpak[2188]: [14:13:10.753] [DBG]
PwPipelineManager::on_registry_global: Audio/Sink 74
bluez_output.00_E0_4C_B9_00_B9.1 with serial 371 has been added
Aug 19 14:13:10 fedora flatpak[2188]: [14:13:10.753] [DBG]
PipewireAudioService::PipewireAudioService$ctor::: device
bluez_card.00_E0_4C_B9_00_B9 has changed its output route to: headset-output
Aug 19 14:13:10 fedora flatpak[2188]: [14:13:10.774] [DBG]
PwPipelineManager::on_metadata_property: new metadata property: 0,
default.audio.sink, Spa:String:JSON,
{"name":"bluez_output.00_E0_4C_B9_00_B9.1"}
Aug 19 14:13:10 fedora flatpak[2188]: [14:13:10.774] [DBG]
PipewireAudioService::PipewireAudioService$ctor::: new default output
device: bluez_output.00_E0_4C_B9_00_B9.1
Aug 19 14:13:10 fedora flatpak[2188]: [14:13:10.779] [DBG]
PwBasePlugin::connect_to_pw: @PwJamesDspPlugin: JamesDsp successfully connected
to PipeWire graph
Aug 19 14:13:10 fedora wireplumber[1516]: RFCOMM receive command but modem not
available: AT+CHLD=?
Aug 19 14:13:10 fedora kernel: input: BT Elite 4000 (AVRCP) as
/devices/virtual/input/input17
Aug 19 14:13:10 fedora systemd-logind[1061]: Watching system buttons on
/dev/input/event16 (BT Elite 4000 (AVRCP))
Aug 19 14:13:11 fedora flatpak[2188]: [14:13:11.219] [DBG]
FilterContainer::on_link_changed::: No app linked to our device wants
to play. Unlinking our filters.
Aug 19 14:13:11 fedora flatpak[2188]: [14:13:11.219] [DBG]
FilterContainer::disconnect_filters: disconnecting the JamesDsp filter from
PipeWire
Aug 19 14:13:11 fedora wireplumber[1516]: RFCOMM receive command but modem not
available: AT+BTRH?
Aug 19 14:13:11 fedora wireplumber[1516]: RFCOMM receive command but modem not
available: AT+CCWA=1
Aug 19 14:13:11 fedora wireplumber[1516]: RFCOMM receive command but modem not
available: AT+CGMI
Aug 19 14:13:11 fedora wireplumber[1516]: RFCOMM receive command but modem not
available: AT+CGMM
Aug 19 14:13:11 fedora wireplumber[1516]: Failed to register battery provider.
Error: org.freedesktop.DBus.Error.UnknownMethod
Aug 19 14:13:11 fedora wireplumber[1516]: BlueZ Battery Provider is not
available, won't retry to register it. Make sure you are running BlueZ 5.56+
with experimental features to use Battery Provider.
Aug 19 14:13:21 fedora systemd[1]: Starting systemd-rfkill.service - Load/Save
RF Kill Switch Status...
Aug 19 14:13:21 fedora systemd[1]: Started systemd-rfkill.service - Load/Save
RF Kill Switch Status.
Aug 19 14:13:21 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Aug 19 14:13:23 fedora kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Aug 19 14:13:23 fedora kernel: usb 3-1: USB disconnect, device number 6
Aug 19 14:13:26 fedora systemd[1]: systemd-rfkill.service: Deactivated
successfully.
Aug 19 14:13:26 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Aug 19 14:13:31 fedora bluetoothd[1051]: src/profile.c:ext_io_disconnected()
Unable to get io data for Hands-Free Voice gateway: getpeername: Transport
endpoint is not connected (107)
Aug 19 14:13:31 fedora kernel: Bluetooth: hci0: HCI reset during shutdown
failed
Aug 19 14:13:31 fedora flatpak[2188]: [14:13:31.365] [DBG]
PwPipelineManager::on_destroy_node_proxy: Audio/Sink 74
bluez_output.00_E0_4C_B9_00_B9.1 has been removed
Aug 19 14:13:31 fedora flatpak[2188]: [14:13:31.365] [WRN]
PwPipelineManager::on_core_error: Remote error res: Datei oder Verzeichnis
nicht gefunden
Aug 19 14:13:31 fedora flatpak[2188]: [14:13:31.365] [WRN]
PwPipelineManager::on_core_error: Remote error message: unknown resource 45
op:2
Aug 19 14:13:31 fedora flatpak[2188]: [14:13:31.369] [DBG]
PwPipelineManager::on_metadata_property: new metadata property: 0,
default.audio.sink, Spa:String:JSON,
{"name":"alsa_output.pci-_04_00.6.analog-stereo"}
Aug 19 14:13:31 fedora flatpak[2188]: [14:13:31.369] [DBG]
PipewireAudioService::PipewireAudioService$ctor::: new default output
device: alsa_output.pci-_04_00.6.analog-stereo
Aug 19 14:13:31 fedora flatpak[2188]: [14:13:31.373] [DBG]
PwBasePlugin::connect_to_pw: @PwJamesDspPlugin: JamesDsp successfully connected
to PipeWire graph
Aug 19 14:13:31 fedora bluetoothd[1051]: No matching connection for device
Aug 19 14:13:31 

[kde] [Bug 473531] New: Audio widget does not change volume/duplicate audio devices

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473531

Bug ID: 473531
   Summary: Audio widget does not change volume/duplicate audio
devices
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: maxbar...@tutanota.com
  Target Milestone: ---

Created attachment 161059
  --> https://bugs.kde.org/attachment.cgi?id=161059=edit
audio widget and audio system settings does not have the same audio channels

SUMMARY
Different audio devices form system settings and widget.
Widget has two times the same device.
If trying to change to other audio devices it gets tick as selected but does
not get selected.
I can not change to other devices nor change volume via scrolling on widget or
widget panel.
If I change sound in the other name it does change volume, I can change volume
in the headset too.

STEPS TO REPRODUCE
Don't know / It appeared 1 weak~ ago. 

OBSERVED RESULT
As mentioned above


EXPECTED RESULT
All working correctly.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.9
Kernel Version: 6.4.10-100.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i7-10700KF CPU @ 3.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
Manufacturer: ASUS
Headsets: WH-1000XM3

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

[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm

2023-08-19 Thread Alois Wohlschlager
https://bugs.kde.org/show_bug.cgi?id=449265

--- Comment #8 from Alois Wohlschlager  ---
My adapter broke, and I cannot reproduce the bug with the new device any more.
Since we already figured out the bug is likely not in Plasma, I'd try the
hostap mailing list. The problem appears to be that some
device/driver/wpa_supplicant combinations fail to set up a WPA3 access point
properly.

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

[Bluedevil] [Bug 473264] Disabling Bluetooth with still connected device causes the applet to grey out, soft crash if any

2023-08-19 Thread ratijas
https://bugs.kde.org/show_bug.cgi?id=473264

--- Comment #4 from ratijas  ---
Likely is related to that pipewire bug which was reported, like, 100 times for
the past two weeks

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

[kdeconnect] [Bug 463247] Unable to create new KDE CONNECT SMS messages with "+New" - button greyed out

2023-08-19 Thread Simon Redman
https://bugs.kde.org/show_bug.cgi?id=463247

Simon Redman  changed:

   What|Removed |Added

 CC||si...@ergotech.com

--- Comment #11 from Simon Redman  ---
@himcesjf

If you have a code change, feel free to make a merge request and we can discuss
on the MR itself. If I understand the suggestion in your comment (#10) then it
seems like it's just forcing enabled to be true always, which defeats the point
of having validation.

In general I'm not happy with how this button works. I think the only quick fix
here is to update the tooltip to tell users to enter a phone number in the
search box. A bigger fix would be to create a new .qml view, similar to the
view you get when you click the "New Conversation" in Google messages, which
allows users to search their contacts as well as enter a number, and change the
behavior of this button to open that view.

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

[krunner] [Bug 473528] KRunner doesn't follow mouse cursor

2023-08-19 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=473528

--- Comment #1 from Fushan Wen  ---
Caused by
https://invent.kde.org/plasma/plasma-workspace/-/commit/26724f30133164bdcb8e0d7a3ab315bfaf9e2148

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

[Powerdevil] [Bug 452492] external screen brightness is not restored after wakeup

2023-08-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=452492

gudvinr+...@gmail.com changed:

   What|Removed |Added

 CC||gudvinr+...@gmail.com

--- Comment #4 from gudvinr+...@gmail.com ---
I have same issue with AMD GPU and 2 external displays (DP and HDMI). Those
displays also happen to be only displays I have since it's desktop.

However, for some reason brightness only gets reset to 0 only sometimes and
it's not fully reproducible.

Operating System: Arch Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.1.46-1-lts (64-bit)
Graphics Platform: X11
Graphics Processor: AMD Radeon RX Vega M GL Graphics

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

[krita] [Bug 473527] Text-in-shape layout is different from Inkscape

2023-08-19 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=473527

--- Comment #3 from wolthera  ---
Probably caused by this line in specific:
https://invent.kde.org/graphics/krita/-/blob/master/libs/flake/text/KoSvgTextShapeLayoutFunc_inShape.cpp#L104

I haven't had the energy to figure out the ideal value for that.

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

[plasma-pa] [Bug 473493] Wrong volume changes across all controls

2023-08-19 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=473493

--- Comment #2 from Ismael Asensio  ---
(In reply to surlaget from comment #1)
> Created attachment 161053 [details]
> The applet in a bugged state. The three "Headphone" sinks all come from the
> same headphone. The two 40% cannot be changed, but the 30% can
> 
> I am also experiencing this bug. It did not occur from upgrading the
> applet's version. I believe it might have been caused by my upgrading
> Pipewire 0.3.74 -> 0.3.77 but I am not 100% sure.
> 
> I am experiencing it from connecting & disconnecting my bluetooth
> headphones. Every time they connect, a new sink appears in the applet, but
> the old one is not removed. Sometimes, multiple sinks appear to be selected.
> The volume of the newest sink can be changed, and this does actually affect
> the headphones, but the other ones cannot. The volume keys pop up saying
> that they changed from one of the duplicate volumes by +/- 5%, but the
> volume is not actually changed.
> 
> Operating System: NixOS
> KDE Plasma Version: 5.27.7
> KDE Frameworks Version: 5.108.0
> Qt Version: 5.15.9
> Kernel Version: 6.4.8 (64-bit)
> Graphics Platform: X11
> Pipewire: 0.3.77

Hi! 

The issue you're describing is a different one than the bug reported here, and
it's tracked in https://bugs.kde.org/show_bug.cgi?id=473093. As you suspect, it
was caused by the update on pipewire, but they've already fixed it for their
next version (https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3414)

I'll hide your and my comments to not confuse readers of this bug report.
Thanks!

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

[kmail2] [Bug 473530] KMail crashes in QtWaylandClient::WlCallback::callback_done (...) at qwaylandinputdevice.cpp:185 when opening a file

2023-08-19 Thread sudden6
https://bugs.kde.org/show_bug.cgi?id=473530

--- Comment #1 from sudden6  ---
Created attachment 161058
  --> https://bugs.kde.org/attachment.cgi?id=161058=edit
Backtrace of crash with KMail

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

[kmail2] [Bug 473530] New: KMail crashes in QtWaylandClient::WlCallback::callback_done (...) at qwaylandinputdevice.cpp:185 when opening a file

2023-08-19 Thread sudden6
https://bugs.kde.org/show_bug.cgi?id=473530

Bug ID: 473530
   Summary: KMail crashes in
QtWaylandClient::WlCallback::callback_done (...) at
qwaylandinputdevice.cpp:185 when opening a file
Classification: Applications
   Product: kmail2
   Version: 5.23.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: sudd...@gmx.at
  Target Milestone: ---

SUMMARY

KMail crashes reproducibly for me whenever a file dialog is shown, but only for
2-5 times after I rebooted my PC, afterwards it's fine.

I have the same problem with other KDE Applications an Firefox, but decided to
file it here, because it's the most reproducible and most annoying to me.

It seems to me this crash is strongly related to Wayland, because it didn't
happen on X11.

STEPS TO REPRODUCE
1. Freshly booted my system
2. Open KMail
3. Go to "File" -> "Open"

OBSERVED RESULT

KMail crashes with the attached backtrace.

EXPECTED RESULT

KMail doesn't crash and I can select a file to open.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20230816
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

ADDITIONAL INFORMATION

This might be irrelevant, but since it's unusual I'll mention it:
I use an external 1080p monitor with my Thinkpad T470, which runs at 120Hz. The
internal display is also used, but runs at 60Hz.

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

[kwin] [Bug 461886] Waking screen causes application windows to disappear

2023-08-19 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=461886

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

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

[kate] [Bug 473529] New: Crash when toggling code folding tags

2023-08-19 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=473529

Bug ID: 473529
   Summary: Crash when toggling code folding tags
Classification: Applications
   Product: kate
   Version: Git
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: justin.zo...@gmail.com
  Target Milestone: ---

#0  QList::size (this=) at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/tools/qlist.h:378
#1  QTextLayout::lineCount (this=0x0) at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/gui/text/qtextlayout.cpp:826
#2  0x7f6ecf990a05 in KateLayoutCache::updateViewCache(KTextEditor::Cursor,
int, int) () from /lib64/libKF6TextEditor.so.6
#3  0x7f6ecf9f3d82 in KateViewInternal::updateView(bool, int) () from
/lib64/libKF6TextEditor.so.6
#4  0x7f6ecf9f4a02 in KateViewInternal::slotRegionVisibilityChanged() ()
from /lib64/libKF6TextEditor.so.6
#5  0x7f6ed01de394 in QtPrivate::QSlotObjectBase::call (a=0x7fff8dc2ae18,
r=0x55d493c25380, this=0x55d493c391f0)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobjectdefs_impl.h:363
#6  doActivate (sender=0x55d493c24628, signal_index=3,
argv=0x7fff8dc2ae18) at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobject.cpp:3992
#7  0x7f6ecf8c9dd6 in
Kate::TextFolding::updateFoldedRangesForNewRange(Kate::TextFolding::FoldingRange*)
[clone .part.0] () from /lib64/libKF6TextEditor.so.6
#8  0x7f6ecf8cf76b in
Kate::TextFolding::newFoldingRange(KTextEditor::Range,
QFlags) () from
/lib64/libKF6TextEditor.so.6
#9  0x7f6ecf9cd155 in KTextEditor::ViewPrivate::foldLine(int) () from
/lib64/libKF6TextEditor.so.6
#10 0x7f6ecf9cd1ae in KTextEditor::ViewPrivate::slotFoldToplevelNodes() ()
from /lib64/libKF6TextEditor.so.6
#11 0x7f6ed01de394 in QtPrivate::QSlotObjectBase::call (a=0x7fff8dc2b0f0,
r=0x55d493c24460, this=0x55d4942c3570)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobjectdefs_impl.h:363
#12 doActivate (sender=0x55d4942c2f40, signal_index=7,
argv=0x7fff8dc2b0f0) at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobject.cpp:3992
#13 0x7f6ed01d4e17 in QMetaObject::activate
(sender=sender@entry=0x55d4942c2f40, m=m@entry=0x7f6ed110e580
, local_signal_index=local_signal_index@entry=4, 
argv=argv@entry=0x7fff8dc2b0f0) at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobject.cpp:4052
#14 0x7f6ed0e16be4 in QAction::triggered (this=this@entry=0x55d4942c2f40,
_t1=)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/redhat-linux-build/src/gui/Gui_autogen/include/moc_qaction.cpp:638
#15 0x7f6ed0e19d2b in QAction::activate (this=0x55d4942c2f40,
event=) at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/gui/kernel/qaction.cpp:1104
#16 0x7f6ed159f654 in QMenuPrivate::activateCausedStack
(this=0x55d49434b780, causedStack=..., action=0x55d4942c2f40,
action_e=QAction::Trigger, self=)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/widgets/qmenu.cpp:1398
#17 0x7f6ed15a7a50 in QMenuPrivate::activateAction (this=0x55d49434b780,
action=0x55d4942c2f40, action_e=QAction::Trigger, self=)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/widgets/qmenu.cpp:1480
#18 0x7f6ed141cdd0 in QWidget::event (this=0x55d493d49a70,
event=0x7fff8dc2b7f0) at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/kernel/qwidget.cpp:9317
#19 0x7f6ed13c0af8 in QApplicationPrivate::notify_helper
(this=this@entry=0x55d492f0fba0, receiver=receiver@entry=0x55d493d49a70,
e=e@entry=0x7fff8dc2b7f0)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/kernel/qapplication.cpp:3287
#20 0x7f6ed13cab5e in QApplication::notify (this=,
receiver=0x55d493d49a70, e=)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/kernel/qapplication.cpp:2774
#21 0x7f6ed017cdb8 in QCoreApplication::notifyInternal2
(receiver=0x55d493d49a70, event=0x7fff8dc2b7f0)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1118
#22 0x7f6ed017cfcd in QCoreApplication::sendSpontaneousEvent
(receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1550
#23 0x7f6ed13c961e in QApplicationPrivate::sendMouseEvent
(receiver=0x55d493d49a70, event=event@entry=0x7fff8dc2b7f0, alienWidget=0x0,
nativeWidget=0x55d493d49a70, 
buttonDown=buttonDown@entry=0x7f6ed19b2830 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false)
at
/usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/kernel/qapplication.cpp:2358
#24 0x7f6ed14309e3 in QWidgetWindow::handleMouseEvent (this=0x55d494545e20,
event=event@entry=0x7fff8dc2bab0)
at

[krunner] [Bug 473528] New: KRunner doesn't follow mouse cursor

2023-08-19 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=473528

Bug ID: 473528
   Summary: KRunner doesn't follow mouse cursor
Classification: Plasma
   Product: krunner
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: qt6, regression
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: qydwhotm...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
In Plasma 6, KRunner doesn't follow mouse cursor and always opens on the
primary screen.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  plasma-workspace at
0266d25228412eb1ca898ec88cda053918ba2943
KDE Frameworks Version: krunner at be79689e8060b90e737303a3043ef140e34da353
Qt Version: 6.5.2

ADDITIONAL INFORMATION

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

[neon] [Bug 473426] Windows don't work properly after latest update on 2023-08-14

2023-08-19 Thread Valter Mura
https://bugs.kde.org/show_bug.cgi?id=473426

--- Comment #16 from Valter Mura  ---
After some searches, the issue is supposed (*only supposed*) to come from the
packages "libkwinglutils14" and "libkwineffect14", that are responsible of:

"KWin (pronounced as one syllable "kwin") is the window manager for the KDE
Plasma Desktop. It gives you complete control over your windows, making sure
they're not in the way but aid you in your task. It paints the window
decoration, the bar on top of every window with (configurable) buttons like
close, maximize and minimize. It also handles placing of windows and switching
between them."

I can see that there are available "libkwinglutils13" and "libkwineffect13" as
dummy packages in the repositories, but I won't even try to install them next
to 14 series.

HTH, will wait for some input from developers/packagers, thank you.

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

  1   2   >