[frameworks-kio] [Bug 450727] Can't edit an application's desktop entry which is a symlink

[bugzilla_noreply]

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

gabek...@fastmail.com changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 CC||gabek...@fastmail.com

--- Comment #5 from gabek...@fastmail.com ---
Still seeing this behavior on my machine, when editing any field. I'm
particularly interested in adding to the "Environment Variables" field of
Telegram flatpak

Operating System: Nobara Linux 38
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.12-204.fsync.fc38.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: ASUS

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

[kwin] [Bug 472366] Unsnapping a quick-tiled window by dragging may drag the window by a point outside its titlebar

[Zeb Figura]

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

Zeb Figura  changed:

   What|Removed |Added

Version|unspecified |5.27.5

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

[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen

[Rewarp]

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

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #25 from Rewarp  ---
I would like to chime in with a particular setup that makes the lack of an easy
access to the shutdown procedure from the power button from the lock screen
dangerously insecure.

I am setting up servers for schools running openSUSE with docker containers
containing various services, with the Plasma interface. They are designed to be
as easy to use as possible since we are talking about primary and secondary
schools. No one expects any teacher there to be a moonlighting sysadmin.

To shutdown the server properly in such a scenario would be too much of a
hassle for them, so I used the system settings for power management to trigger
a shutdown when the power button is pressed. However, the power button doesn't
work if the screenlock is on. The screenlock should ideally be on so that
teachers and trusted students can access the desktop interface for whatever
reason. The only protection therefore for such a unit thus far in an exposed
environment is the lack of a KVM. I can imagine that's not going to be much of
a barrier for kids determined to do mischief.

So my hope is there will be a user toggle option that allows the power button
to shutdown the system safely should it be necessary from the lockscreen.

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

[plasma-pa] [Bug 472728] Audio Volume plasmoid misses the "Keep open" (pin) button if added separately to a Plasma panel (not to the system tray)

[Murz]

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

Murz  changed:

   What|Removed |Added

 Attachment #160576|0   |1
is obsolete||

--- Comment #1 from Murz  ---
Created attachment 160577
  --> https://bugs.kde.org/attachment.cgi?id=160577=edit
A screenshot with the problem

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

[plasma-pa] [Bug 472728] New: Audio Volume plasmoid misses the "Keep open" (pin) button if added separately to a Plasma panel (not to the system tray)

[Murz]

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

Bug ID: 472728
   Summary: Audio Volume plasmoid misses the "Keep open" (pin)
button if added separately to a Plasma panel (not to
the system tray)
Classification: Plasma
   Product: plasma-pa
   Version: 5.27.4
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: mur...@gmail.com
CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com
  Target Milestone: ---

Created attachment 160576
  --> https://bugs.kde.org/attachment.cgi?id=160576=edit
A screenshot with the problem

STEPS TO REPRODUCE
1. Add the "Audio Volume" plasmoid to the system tray.
2. Click on the icon, and see that the "Keep open" (pin) button is present.
3. Add the "Audio Volume" plasmoid as a separate widget to a Plasma panel.
4. Click on the icon, and see that the "Keep open" (pin) button is missing.

OBSERVED RESULT
The "Keep open" (pin) button is missing.

EXPECTED RESULT
The "Keep open" (pin) button should be present.
Most of the other widgets have this pin button in both modes.

Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-25-generic (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
Memory: 30.8 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: HP
Product Name: HP EliteBook 850 G8 Notebook PC

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

[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[bugzilla_noreply]

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

--- Comment #7 from abh...@gmail.com ---
Doesn't look like driver issue because the crash is here even without hardware
acceleration enabled

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

[Smb4k] [Bug 472467] SMB4K Crash saving bookmarks

[Alexander Reinholdt]

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

Alexander Reinholdt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/netw
   ||ork/smb4k/-/commit/5d43e3e8
   ||adb545651325dff7b77b5dee992
   ||a1a9f

--- Comment #8 from Alexander Reinholdt  ---
Git commit 5d43e3e8adb545651325dff7b77b5dee992a1a9f by Alexander Reinholdt.
Committed on 28/07/2023 at 07:06.
Pushed by areinholdt into branch '3.2'.

Fix crash in the bookmark menu and remove unnecessary/dysfunctional code.

M  +1-89   smb4k/smb4kbookmarkmenu.cpp
M  +0-15   smb4k/smb4kbookmarkmenu.h

https://invent.kde.org/network/smb4k/-/commit/5d43e3e8adb545651325dff7b77b5dee992a1a9f

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

[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[bugzilla_noreply]

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

abh...@gmail.com changed:

   What|Removed |Added

 CC||abh...@gmail.com

--- Comment #6 from abh...@gmail.com ---
Just to add to this, I have a Galaxy Tab S7+ and the crash has been recurring
this whole year based on nightly build.

The easy way to replicate crash is to create a group of layers and select one
layer.

However, i got curious and installed the beta on Xiaomi 11T pro and it has not
crashed yet.

This makes me believe it is more of Samsung specific error (maybe s-pen issue
or GPU driver bug). Both devices are running android 13
,

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

[Powerdevil] [Bug 457859] Powerdevil does not respect sleep inhibitors created with systemd-inhibit by unprivileged users

[bugzilla_noreply]

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

auberg...@outlook.com.au changed:

   What|Removed |Added

 CC||auberg...@outlook.com.au

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

[krunner] [Bug 472727] New: Standalone KRunner has wrong colors with mismatched Plasma and app color schemes

[Nate Graham]

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

Bug ID: 472727
   Summary: Standalone KRunner has wrong colors with mismatched
Plasma and app color schemes
Classification: Plasma
   Product: krunner
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 160575
  --> https://bugs.kde.org/attachment.cgi?id=160575=edit
Wrong text color

STEPS TO REPRODUCE
1. Use Breeze Twilight Global theme, or else manually set Breeze Dark Plasma
style and Breeze Light color scheme
2. Open KRunner


OBSERVED RESULT
Dark text on dark background. See attached screenshot


EXPECTED RESULT
Light text on dark background


ADDITIONAL INFORMATION
Does not affect the Milou widget, so perhaps the here is that the standalone
KRunner binary is missing the magic engine property to use the Kirigami Plasma
style plugin. See
https://invent.kde.org/plasma/kscreen/-/commit/2f824de4550fbde576159867a5b782502d7c79e2
for details.

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

[kde] [Bug 472726] New: Debian12,ThinkPad A485

[cbslu]

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

Bug ID: 472726
   Summary: Debian12,ThinkPad A485
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: cbslual...@proton.me
  Target Milestone: ---

Hi, I recently installed Debian12 along with KDE, and I don't know why the
screen flickers a bit when my computer restarts after hibernation. And, when I
use it for a long time, it will suddenly crash, sddm cannot enter wayland, and
all its special effects on x11 will disappear, which is very strange, my
computer is ThinkPad A485, CPU is AMD Ryzen 5 pro, GPU is ATI vega 8 , KDE
Plasma version is 5.27.5

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

[kmymoney] [Bug 468936] Home Page and Reports display completely black - Cannot Read

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[korganizer] [Bug 472725] New: Creating a New To-do entry does not set the priority even when selected in the creation window

[Andrew A. Adams]

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

Bug ID: 472725
   Summary: Creating a New To-do entry does not set the priority
even when selected in the creation window
Classification: Applications
   Product: korganizer
   Version: 5.23.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: todoview
  Assignee: kdepim-b...@kde.org
  Reporter: cubed...@gmail.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. Select To-do list view
2. Select New To-do
3. Create new To-do entry and set priority in the pop-up options
4. Click OK (or Apply) to create a new To-do entry

OBSERVED RESULT
New entry is created with a blank priority

EXPECTED RESULT
New entry should have the selected priority

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

ADDITIONAL INFORMATION
The priority can then be set from the To-do list view, so this is a minor
annoyance rather than a major problem.

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

[korganizer] [Bug 472724] New: Crash when saving settings

[Andrew A. Adams]

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

Bug ID: 472724
   Summary: Crash when saving settings
Classification: Applications
   Product: korganizer
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: cubed...@gmail.com
  Target Milestone: ---

Application: korganizer (5.23.2 (23.04.2))

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

-- Information about the crash:
Having added new Google calendars to my KOrganizer settings, it crashed when I
clicked "OK" on the settings window.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault

[KCrash Handler]
#4  0x7f6026f6dfec in
EventViews::AgendaView::calendar2(QSharedPointer
const&) const () from /lib64/libKPim5EventViews.so.5
#5  0x7f6026f78e62 in
EventViews::AgendaView::displayIncidence(QSharedPointer
const&, bool) () from /lib64/libKPim5EventViews.so.5
#6  0x7f6026f7a7ab in EventViews::AgendaView::fillAgenda() () from
/lib64/libKPim5EventViews.so.5
#7  0x7f60278e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8  0x7f60294c2473 in CalendarView::updateConfig() () from
/lib64/libkorganizerprivate.so.5
#9  0x7f60278e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f6027bdc170 in KCMultiDialogPrivate::apply() () from
/lib64/libKF5KCMUtils.so.5
#11 0x7f6027bdc248 in KCMultiDialog::slotOkClicked() () from
/lib64/libKF5KCMUtils.so.5
#12 0x7f60278e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#13 0x7f60286a9c64 in QAbstractButton::clicked(bool) () from
/lib64/libQt5Widgets.so.5
#14 0x7f60286a9eef in QAbstractButtonPrivate::emitClicked() () from
/lib64/libQt5Widgets.so.5
#15 0x7f60286ab850 in QAbstractButtonPrivate::click() () from
/lib64/libQt5Widgets.so.5
#16 0x7f60286aba58 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /lib64/libQt5Widgets.so.5
#17 0x7f60285f3688 in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#18 0x7f60285aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#19 0x7f60285b7456 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#20 0x7f60278b4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#21 0x7f60285b56a4 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /lib64/libQt5Widgets.so.5
#22 0x7f602860d1a9 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from
/lib64/libQt5Widgets.so.5
#23 0x7f602861072f in QWidgetWindow::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#24 0x7f60285aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#25 0x7f60278b4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#26 0x7f6027d6cc6b in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib64/libQt5Gui.so.5
#27 0x7f6027d4acfc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib64/libQt5Gui.so.5
#28 0x7f601331b4d6 in xcbSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5XcbQpa.so.5
#29 0x7f602511339c in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#30 0x7f6025171438 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#31 0x7f6025110a23 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#32 0x7f6027906729 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#33 0x7f60278b2b4b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#34 0x7f60278baddb in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#35 0x55a4a4a891dc in main ()
[Inferior 1 (process 1249778) detached]

The reporter indicates this bug may be a duplicate of or related to bug 262310,
bug 270817, bug 280313, bug 323433, bug 327796, bug 327878, bug 328425, bug
329099, bug 332620, bug 453709, bug 470584.

Reported using DrKonqi

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

[krita] [Bug 472723] New: "Align the brush to preview outline to the pixel grid" don't work anymore

[bugzilla_noreply]

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

Bug ID: 472723
   Summary: "Align the brush to preview outline to the pixel grid"
don't work anymore
Classification: Applications
   Product: krita
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: tamuitocalormeud...@gmail.com
  Target Milestone: ---

SUMMARY
Krita version 5.2 BETA (there is no option for 5.2 beta to choose).
Pixel brush do not respect if "Align brush to preview outline to pixel grid" is
selected or not and sometimes align and sometimes don't align the preview to
the pixel grid.

STEPS TO REPRODUCE
1. with pixel brush disable or enable "Align brush to preview outline to pixel
grid"
2. starts to use and make some changes like the size of brush, to eraser mode
etc

OBSERVED RESULT
Sometimes the brush starts to align sometimes stops

EXPECTED RESULT
To respect if it's to align or not to the pixel grid using the option inside
the brush config "Align brush to preview outline to pixel grid"

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: LinuxMint 20.3 XFCE
(available in About System)

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

[konsole] [Bug 168368] tab characters are not copyable with mouse

[Phil]

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

Phil  changed:

   What|Removed |Added

 CC||phils...@phlexo.com

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

[kdenlive] [Bug 472722] New: "Draw box" ignores user selected color

[Rafael Linux User]

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

Bug ID: 472722
   Summary: "Draw box" ignores user selected color
Classification: Applications
   Product: kdenlive
   Version: 23.04.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: j...@kdenlive.org
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

Created attachment 160574
  --> https://bugs.kde.org/attachment.cgi?id=160574=edit
Scrrenshot showing black border color instead white selected

SUMMARY
I tried to add a white frame around pictures in a project, however, "Draw box"
ignore any color selected and always draws border in black.


STEPS TO REPRODUCE
1. Add a picrure to timeline
2. Add "Transform" effect to picture and reduce picture size, to show all
content, and rotate slightly 
3. Add "Draw box" effect to picture and move this effect over "Transform"
4. Select "Draw box" effect properties, change "Thickness" to 15 and color to
white

OBSERVED RESULT
Color of border always black

EXPECTED RESULT
Color should change to selected color

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230718
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.3-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2

ADDITIONAL INFORMATION

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

[krita] [Bug 472721] New: transform bug

[bugzilla_noreply]

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

Bug ID: 472721
   Summary: transform bug
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Microsoft Windows
OS: Other
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: loveig...@icloud.com
  Target Milestone: ---

SUMMARY
crashes every time I try to use the transform tool a second time. I can use to
transform tool once after launching, but if I try to use it a second time the
app closes



STEPS TO REPRODUCE
1. open new document 
2. use transform tool 
3. use transform again 

OBSERVED RESULT
app crashes

EXPECTED RESULT
app crashes

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.

[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash

[bugzilla_noreply]

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

--- Comment #22 from xv...@web.de ---
Way to fix "failed to allocate memory" bug:

1. Edit 
/home/a/.config/plasma-org.kde.plasma.desktop-appletsrc

2. Replace "positions" line, but let YOUR resolution with:
positions={"1920x1080":[]}

3. Reboot

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

[kwin] [Bug 469725] Busy cursor does not animate on Wayland

[bugzilla_noreply]

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

lightofp...@gmail.com changed:

   What|Removed |Added

 CC||lightofp...@gmail.com

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

[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[bugzilla_noreply]

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

--- Comment #5 from xeses16...@tastrg.com ---
Here's another crash:

** Dumping backtrace **
Signal: 11 (SIGSEGV) (Code: 1) Time: Thu Jul 27 22:04:08 2023 GMT Version:
5.2.0-beta1
  #00 pc 003f4914 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QCoreApplication::notifyInternal2(QObject*, QEvent*)+136)
  #01 pc 0042c474 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QTimerInfoList::activateTimers()+572)
  #02 pc 0042ab44 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QEventDispatcherUNIX::processEvents(QFlags)+424)
  #03 pc 0007f804 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so

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

[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash

[bugzilla_noreply]

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

xv...@web.de changed:

   What|Removed |Added

 CC||xv...@web.de

--- Comment #21 from xv...@web.de ---
"failed to allocate memory" 

I have the same problem. :-(

Betriebssystem: Manjaro Linux 
KDE-Plasma-Version: 5.27.6
KDE-Frameworks-Version: 5.108.0
Qt-Version: 5.15.10
Kernel-Version: 6.1.41-1-MANJARO (64-bit)
Grafik-Plattform: Wayland
Prozessoren: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Speicher: 15,2 GiB Arbeitsspeicher
Grafikprozessor: Mesa Intel® UHD Graphics 630 and/or  NVIDIA GeForce GTX
1050 Ti Mobile

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

[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[bugzilla_noreply]

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

--- Comment #4 from xeses16...@tastrg.com ---
Yeah. Here are the last two crashes on my Tab S8+, 64 bit:

** Dumping backtrace **
Signal: 11 (SIGSEGV) (Code: 1) Time: Thu Jul 27 21:45:49 2023 GMT Version:
5.2.0-beta1
  #00 pc 003f4918 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QCoreApplication::notifyInternal2(QObject*, QEvent*)+140)
  #01 pc 0042c474 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QTimerInfoList::activateTimers()+572)
  #02 pc 0042ab44 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QEventDispatcherUNIX::processEvents(QFlags)+424)
  #03 pc 0007f804 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so

** Dumping backtrace **
Signal: 11 (SIGSEGV) (Code: 1) Time: Thu Jul 27 21:49:09 2023 GMT Version:
5.2.0-beta1
  #00 pc 003f4918 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QCoreApplication::notifyInternal2(QObject*, QEvent*)+140)
  #01 pc 0042c474 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QTimerInfoList::activateTimers()+572)
  #02 pc 0042ab44 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libQt5Core_arm64-v8a.so
(QEventDispatcherUNIX::processEvents(QFlags)+424)
  #03 pc 0007f804 
/data/app/~~V8d3VPDg02GwuLCqnowMog==/org.krita-KQdq6mC5MQeH0RfkYQ8guQ==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so

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

[kdeconnect] [Bug 472720] New: Last version of Kdeconnect on mac don't open

[bugzilla_noreply]

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

Bug ID: 472720
   Summary: Last version of Kdeconnect on mac don't open
Classification: Applications
   Product: kdeconnect
   Version: 23.04.3
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: macos-application
  Assignee: turx2...@gmail.com
  Reporter: ernest2...@gmail.com
  Target Milestone: ---

SUMMARY
Last version of Kdeconnect on mac don't open


STEPS TO REPRODUCE
1. Open kdeconnect-indicator.app

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
Open app indicator 

SOFTWARE/OS VERSIONS
macOS: 13.4

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

[kontact] [Bug 472719] New: KMail/Kontact crashes when trying to send a mail

[Daniel Ziltener]

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

Bug ID: 472719
   Summary: KMail/Kontact crashes when trying to send a mail
Classification: Applications
   Product: kontact
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: dzilte...@lyrion.ch
  Target Milestone: ---

Application: kontact (5.23.3 (23.04.3))

Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.4-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.6 [KCrashBackend]

-- Information about the crash:
KMail crashes reliably (and takes Kontact with it) when I try to send a mail by
using the normal "Send" button. It works, however, when I longpress the "Send"
button and choose a sending account.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault

[KCrash Handler]
#4  0x7fa72f40c45b in  () at /lib64/libQt5WaylandClient.so.5
#5  0x7fa72bf49962 in  () at /lib64/libffi.so.8
#6  0x7fa72bf462df in  () at /lib64/libffi.so.8
#7  0x7fa72bf48f26 in ffi_call () at /lib64/libffi.so.8
#8  0x7fa72fce2a23 in  () at /lib64/libwayland-client.so.0
#9  0x7fa72fce3203 in  () at /lib64/libwayland-client.so.0
#10 0x7fa72fce3494 in wl_display_dispatch_queue_pending () at
/lib64/libwayland-client.so.0
#11 0x7fa72f40ca12 in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /lib64/libQt5WaylandClient.so.5
#12 0x7fa739d25743 in  () at /lib64/libQt5Core.so.5
#13 0x7fa739d464c5 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#14 0x7fa739cebf8b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#15 0x7fa73af77475 in KJob::exec() () at /lib64/libKF5CoreAddons.so.5
#16 0x7fa6a693aa1e in Kleo::KeyResolver::lookupContactPreferences(QString
const&) const () at /lib64/libKPim5MessageComposer.so.5
#17 0x7fa6a693273b in Kleo::KeyResolver::getEncryptionItems(QStringList
const&) () at /lib64/libKPim5MessageComposer.so.5
#18 0x7fa6a6932f3b in Kleo::KeyResolver::setPrimaryRecipients(QStringList
const&) () at /lib64/libKPim5MessageComposer.so.5
#19 0x7fa6a6922c3a in
MessageComposer::ComposerViewBase::generateCryptoMessages(bool&) () at
/lib64/libKPim5MessageComposer.so.5
#20 0x7fa6a6923dc7 in
MessageComposer::ComposerViewBase::slotEmailAddressResolved(KJob*) () at
/lib64/libKPim5MessageComposer.so.5
#21 0x7fa739d257a2 in  () at /lib64/libQt5Core.so.5
#22 0x7fa73af6f845 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#23 0x7fa73af73beb in  () at /lib64/libKF5CoreAddons.so.5
#24 0x7fa6a6911900 in MessageComposer::EmailAddressResolveJob::start() ()
at /lib64/libKPim5MessageComposer.so.5
#25 0x7fa6a692186c in MessageComposer::ComposerViewBase::readyForSending()
() at /lib64/libKPim5MessageComposer.so.5
#26 0x7fa6a6921c0e in
MessageComposer::ComposerViewBase::send(MessageComposer::MessageSender::SendMethod,
MessageComposer::MessageSender::SaveIn, bool) () at
/lib64/libKPim5MessageComposer.so.5
#27 0x7fa6a6f7064b in  () at /lib64/libkmailprivate.so.5
#28 0x7fa739d257a2 in  () at /lib64/libQt5Core.so.5
#29 0x7fa73af6f845 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#30 0x7fa73af73beb in  () at /lib64/libKF5CoreAddons.so.5
#31 0x7fa6a6f82fcb in  () at /lib64/libkmailprivate.so.5
#32 0x7fa739d257a2 in  () at /lib64/libQt5Core.so.5
#33 0x7fa73af6f845 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#34 0x7fa73af73beb in  () at /lib64/libKF5CoreAddons.so.5
#35 0x7fa6a6f73235 in  () at /lib64/libkmailprivate.so.5
#36 0x7fa739d257a2 in  () at /lib64/libQt5Core.so.5
#37 0x7fa6a6f74ecb in  () at /lib64/libkmailprivate.so.5
#38 0x7fa739d257a2 in  () at /lib64/libQt5Core.so.5
#39 0x7fa73a99e8b2 in QAction::triggered(bool) () at
/lib64/libQt5Widgets.so.5
#40 0x7fa73a9a142f in QAction::activate(QAction::ActionEvent) () at
/lib64/libQt5Widgets.so.5
#41 0x7fa73aa9862a in  () at /lib64/libQt5Widgets.so.5
#42 0x7fa73aa98777 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /lib64/libQt5Widgets.so.5
#43 0x7fa73ab9102a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/lib64/libQt5Widgets.so.5
#44 0x7fa73a9e6d68 in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#45 0x7fa73a9a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#46 0x7fa73a9ad5cf in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#47 0x7fa739ced4f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#48 0x7fa73a9ab92e in 

[kdiff3] [Bug 472718] Merge conflict resolved to empty is saved as newline

[Karsten Düsterloh]

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

Karsten Düsterloh  changed:

   What|Removed |Added

 CC||mnyro...@tprac.de

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

[kdiff3] [Bug 472718] New: Merge conflict resolved to empty is saved as newline

[Karsten Düsterloh]

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

Bug ID: 472718
   Summary: Merge conflict resolved to empty is saved as newline
Classification: Applications
   Product: kdiff3
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: application
  Assignee: reeves...@gmail.com
  Reporter: mnyro...@tprac.de
  Target Milestone: ---

When resolving a merge conflict in line 1, and picking "no src line" as the
solution, the result saved to file for this conflict is a newline.

This is a very grave problem, especially in automerge mode, since the merge
result is not part of the input data. And in UI mode, the UI is even lying to
you …

STEPS TO REPRODUCE
1. Create two input files "x" and "y" with the four lines of content each:

file "x":
a
b
c
e

file "y":
b
c
d
e

2.  Do a merge of these two files to a new file "z", eg. via

kdiff3 -m -o z x y

kdiff will complain about 2 merge conflicts.

3.  Resolve each conflict by choosing the empty block. Kdiff3 will mark these
in the merge view as 

4. Save and quit Kdiff3.

OBSERVED RESULT

Look into the merge result file "z":
- the conflict solution "" of merge line 1 was falsely written as
an empty line
- the conflict solution "" of merge line 4 was correctly not
written

EXPECTED RESULT

The "" of merge line 1 should not result in any output.


SOFTWARE/OS VERSIONS

KDiff3 Version 1.9.70 (64 bit) (and several older versions)
Lubuntu 23.04, i.e. Ubuntu 23.04 with LXDE desktop environment.

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

[discuss.kde.org] [Bug 472717] Change the subject prefix of emails to [KDE Discuss] on Discourse configuration

[Phu H. Nguyen]

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

Phu H. Nguyen  changed:

   What|Removed |Added

 CC||john@pelago.org.uk

--- Comment #1 from Phu H. Nguyen  ---
*** Bug 468963 has been marked as a duplicate of this bug. ***

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

[discuss.kde.org] [Bug 468963] Site name ambiguous in email messages

[Phu H. Nguyen]

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

Phu H. Nguyen  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||phu.ngu...@kdemail.net

--- Comment #1 from Phu H. Nguyen  ---


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

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

[digikam] [Bug 472683] showFoto ignores icons scale configured for Digikam when launched outside it

[Maik Qualmann]

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

--- Comment #4 from Maik Qualmann  ---
Git commit 6cdc43a9b37b0cff403126cfc2339f49f9387caa by Maik Qualmann.
Committed on 27/07/2023 at 23:17.
Pushed by mqualmann into branch 'master'.

move system settings in showFoto to the last tab

M  +6-6core/showfoto/setup/showfotosetupmisc.cpp
M  +2-2core/showfoto/setup/showfotosetupmisc.h

https://invent.kde.org/graphics/digikam/-/commit/6cdc43a9b37b0cff403126cfc2339f49f9387caa

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

[digikam] [Bug 472683] showFoto ignores icons scale configured for Digikam when launched outside it

[Maik Qualmann]

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

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 472692] Tesseract OCR does not take language selection into account

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
Ok, we're a big step further, the language setting works, we get a text with
German umlauts, but in the Windows codepage format and not UTF8. This is
correct when we view the text file in the Windows text editor, but not in our
preview.
The question now is, do we want codepage or UTF8 on Windows?

Maik

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

[digikam] [Bug 472683] showFoto ignores icons scale configured for Digikam when launched outside it

[Rafael Linux User]

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

Rafael Linux User  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com
 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #3 from Rafael Linux User  ---
I always thought that ShowFoto was integrated in DK and that they shared their
configuration, especially when it happens, as I said, that it only respects the
size of the icons when launched from Digikam (F4 key).

As you suggested, I enabled in showFoto "Preferences, Other, System" HiDPI
parameter and it's working.

Thank you for clarifying how the detail that showFoto is independent of
DigiKam.

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

[discuss.kde.org] [Bug 472717] New: Change the subject prefix of emails to [KDE Discuss] on Discourse configuration

[Fabio C. Barrionuevo]

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

Bug ID: 472717
   Summary: Change the subject prefix of emails to [KDE Discuss]
on Discourse configuration
Classification: Websites
   Product: discuss.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: forum-ad...@kde.org
  Reporter: bna...@gmail.com
CC: kde-...@kde.org
  Target Milestone: ---

SUMMARY

I guess it would be good to rename the email format of the "FROM" field to "KDE
Discuss " and the subject prefix to "[KDE Discuss]" in
order to be able to quickly identify in the email inbox which emails are from
this KDE forum and which are from others.

I participate in a few other forums that use Discourse, and they all use the
same setup, which makes it a little tricky to tell them apart quickly without
actually opening the email.

I guess this change would not be so complicated to make.

1 - It currently shows like this in Gmail:

https://discuss-cdn.kde.org/uploads/default/original/2X/9/9a3c9976600e2b4ae8eec6aa1f04f19172a66efd.png

My suggestion is to configure discourse in order to show like this:

https://discuss-cdn.kde.org/uploads/default/original/2X/c/ced3a78fa1c13e03aaf5c41d180983dca1772e51.png

2 - Same for the "From" field in the email body. This is what we currently
have:

https://discuss-cdn.kde.org/uploads/default/original/2X/1/1bd19df87b1ad59e2b277a9f472780bc9df68ece.png

This is what it should look like in the email raw body after configuration in
the discourse:

https://discuss-cdn.kde.org/uploads/default/original/2X/1/1b2b0127c6ea459a6040cba870fafca5018ef3ad.png


---
You can read the same message on
https://discuss.kde.org/t/initial-feedback-on-forum/34/14

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

[plasma-nm] [Bug 461319] WireGuard connection doesn't save persistent-keepalive value.

[Oliver Freyermuth]

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

Oliver Freyermuth  changed:

   What|Removed |Added

 CC||o.freyerm...@googlemail.com

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

[Spectacle] [Bug 470369] Add "Pin Screenshot" Functionality to Spectacle

[ShellWen]

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

--- Comment #3 from ShellWen  ---
(In reply to Malachi Wu from comment #2)
> (In reply to Nate Graham from comment #1)
> > What's the use case for this feature?
> 
> Copied from https://bugs.kde.org/show_bug.cgi?id=469378 :
> 
> > This is really useful as a way to temporarily hold an image on the screen 
> > to be used as a reference or to even compose new images (e.g. side-by-side 
> > comparisons, before/after shots, mock-ups, etc.)
> 
> This nice feature actually turns Spectacle from a mere screenshot tool into
> a productivity tool: instead of rearranging the layout of windows when
> comparing different content, just take a screenshot - and pin it!
> 
> I also recommend another screenshot software with this feature, Snipaste, to
> see how they demonstrate the impressive convenience:
> https://www.snipaste.com/

This Feature Request seems to be a duplicate of
https://bugs.kde.org/show_bug.cgi?id=469378. Should I mark it as a duplicate?
I'm sorry, my English is not very good, and I'm not very familiar with the
process.

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

[dolphin] [Bug 472716] New: Copying a large selection of files (2000+) often does not copy some of them

[Valeri]

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

Bug ID: 472716
   Summary: Copying a large selection of files (2000+) often does
not copy some of them
Classification: Applications
   Product: dolphin
   Version: 23.04.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: v19930...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Selecting a large number of files and then copying them tends to not copy at
least some without any apparent error or warning message from dolphin. This may
make user erroneously believe that operation (in the sense of copying all files
to destination) succeeded while it actually did not - which is what happened to
me in regards to a large dataset I've been copying.


STEPS TO REPRODUCE
1. Run the following commands in bash to generate a directory with 3000 empty
files:
1.1 mkdir /tmp/dolphin_copy_test_src /tmp/dolphin_copy_test_dst
1.2 cd /tmp/dolphin_copy_test_src
1.3 for ((i=1;i<=3000;i++)); do touch $(uuidgen); done
2. Open Dolphin file manager, preferably from terminal
3. Navigate to /tmp/dolphin_copy_test_src
4. Press Ctrl+A to select all 3000 files in directory
5. Press Ctrl+C to copy files; at this point console will be spammed with

QDBusConnection: error: could not send message to service
"org.freedesktop.portal.Documents" path "/org/freedesktop/portal/documents"
interface "org.freedesktop.portal.FileTransfer" member "AddFiles": Marshalling
failed: Invalid file descriptor passed in arguments

6. Navigate to /tmp/dolphin_copy_test_dst
7. Press Ctrl+V to paste files you've copied

OBSERVED RESULT
Only some files will be copied - target directory will contain less than 3000
files. The exact number I've seen in my tests varies from around 1500 to around
2700. Pasting again will results in the exact same files being copied until one
selects some files to copy again.

EXPECTED RESULT
All 3000 files are copied.

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

ADDITIONAL INFORMATION
None.

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

[krdc] [Bug 472690] FR: Separate account and remote host data and allow to combine them as needed

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[plasmashell] [Bug 470819] Desktop icons appear late after log in

[Balint Toth]

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

Balint Toth  changed:

   What|Removed |Added

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

--- Comment #8 from Balint Toth  ---
Never mind. I've installed fedora (for another reasons), but kept the all the
config in the .config folder and the bug happened in fedora too.
Later I switched back to Tumbleweed, but with clean config, and now the bug is
gone. Sorry for the noise.

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

[gwenview] [Bug 472351] Subliminal white screen interleaved at picture transition

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/graphics/gwenview/-/merge_requests/213

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

[kdialog] [Bug 472715] New: KDialog shows file selector instead of folder selector

[Grósz Dániel]

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

Bug ID: 472715
   Summary: KDialog shows file selector instead of folder selector
Classification: Applications
   Product: kdialog
   Version: 23.04.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: groszdaniel...@gmail.com
  Target Milestone: ---

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

SUMMARY
kdialog --getexistingdirectory shows a regular file dialog instead of a folder
dialog. And it's hard to use if a single click is configured to open a
file/folder, since clicking a folder opens it inside the dialog rather than
selecting it, and Open doesn't work if no folder is selected.

STEPS TO REPRODUCE
1. kdialog --getexistingdirectory
2. Click a folder.
3. Click Open.

OBSERVED RESULT
1. The sort of dialog used to select a regular file.
2. The folder is opened.
3. Nothing.

EXPECTED RESULT
1. A folder selection dialog.
2. The folder is selected.
3. The dialog returns the selected folder.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230724
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.3-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Just like Bug 419874, except that affected more (all?) applications. This time,
I've only seen it in kdialog; the usual folder selection dialog is used both by
KDE applications and Firefox.

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

[kwin] [Bug 472714] Custom Tiling hangs when adjusting vertical split panels' height

[ShellWen]

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

ShellWen  changed:

   What|Removed |Added

 CC||m...@shellwen.com

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

[kwin] [Bug 472714] New: Custom Tiling hangs when adjusting vertical split panels' height

[ShellWen]

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

Bug ID: 472714
   Summary: Custom Tiling hangs when adjusting vertical split
panels' height
Classification: Plasma
   Product: kwin
   Version: 5.27.6
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Custom Tiling
  Assignee: kwin-bugs-n...@kde.org
  Reporter: m...@shellwen.com
CC: notm...@gmail.com
  Target Milestone: ---

SUMMARY
Custom Tiling will hangs when adjusting vertical split panels' height.
I have followed the instructions and used `qdbus org.kde.KWin /KWin
supportInformation` as requested, and pasted the results on
https://invent.kde.org/-/snippets/2753.


STEPS TO REPRODUCE
1. Use Meta+T to open Custom Tiling
2. Click on "Vertical Split."
3. Drag the vertical split divider to its minimum position

OBSERVED RESULT
The entire screen freezes, and after connecting via SSH and using htop, it is
observed that the kwin_wayland process is occupying almost an entire CPU core.


EXPECTED RESULT
Just work, right?


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 

OS: EndeavourOS
`uname -a`: `Linux ShellWens-Tired 6.4.4-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC
Wed, 19 Jul 2023 19:19:14 + x86_64 GNU/Linux`

KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Wayland, BTW

ADDITIONAL INFORMATION

After repeated testing by me and several others, the following factors do not
seem to determine the occurrence of the issue:

- Display resolution (known resolutions like 2560 * 1440, 1920 * 1080, and 1366
* 768 all trigger this problem).
- Display scaling (both 100% and 150% scaling have been observed to trigger
this problem).
- Plasma themes.
- Wayland or Xorg

The following factor is likely to determine the occurrence of the issue:

- System language (based on testing, using C and en_US.UTF-8 languages does not
cause this problem, but using zh_CN.UTF-8 and zh_TW.UTF-8 languages does).

The following is the stack trace information I captured. Due to the entire
kwin_wayland process freezing and being unable to generate a crash report, I
chose to use GDB to attach, and after sending a segmentation fault using `kill
-SEGV`, I forcefully terminated the process using `kill -KILL`. Anyway, here is
the GDB output I obtained. If I made any mistakes, please point them out.

```
[Thread 0x7f88fdffb6c0 (LWP 64442) exited]
[Thread 0x7f8921ffb6c0 (LWP 64435) exited]
[Thread 0x7f8922ffd6c0 (LWP 64433) exited]
[Thread 0x7f8928f3b6c0 (LWP 64429) exited]
[Thread 0x7f88f6c0 (LWP 64438) exited]
[Thread 0x7f892973c6c0 (LWP 64428) exited]
[Thread 0x7f8929f3d6c0 (LWP 64427) exited]
[Thread 0x7f8954bfd6c0 (LWP 63254) exited]
[Thread 0x7f88ff7fe6c0 (LWP 64439) exited]
[Thread 0x7f88fe7fc6c0 (LWP 64441) exited]
[Thread 0x7f8923fff6c0 (LWP 64431) exited]
[Thread 0x7f89227fc6c0 (LWP 64434) exited]
[Thread 0x7f88feffd6c0 (LWP 64440) exited]
[Thread 0x7f8920ff96c0 (LWP 64437) exited]
[Thread 0x7f89217fa6c0 (LWP 64436) exited]
[Thread 0x7f89237fe6c0 (LWP 64432) exited]
[New Thread 0x7f89237fe6c0 (LWP 67702)]

[New Thread 0x7f89217fa6c0 (LWP 68102)]
[New Thread 0x7f8920ff96c0 (LWP 68103)]
[New Thread 0x7f88feffd6c0 (LWP 68104)]
[Thread 0x7f89217fa6c0 (LWP 68102) exited]
[Thread 0x7f8920ff96c0 (LWP 68103) exited]
[New Thread 0x7f8920ff96c0 (LWP 68153)]
[New Thread 0x7f89217fa6c0 (LWP 68154)]
[New Thread 0x7f8928fa76c0 (LWP 68155)]

Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault.
0x7f89736784fb in QQmlNotifier::emitNotify (endpoint=,
a=0x0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlnotifier.cpp:105
Downloading source file
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlnotifier.cpp...
105 if (data.disconnectWatch ==  &&
data.originalSenderPtr) {

Thread 33 (Thread 0x7f8928fa76c0 (LWP 68155) "kwin_wayla:sh2"):
#0  0x7f8971899f0e in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55d4faed1b7c) at
futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55d4faed1b7c,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7f8971899f8f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x55d4faed1b7c, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7f897189c7a0 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55d4faed1b20, cond=0x55d4faed1b50) at pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x55d4faed1b50, mutex=0x55d4faed1b20) at
pthread_cond_wait.c:618
#5  0x7f8969719f8e in  () at /usr/lib/dri/radeonsi_dri.so
#6  0x7f89696c9f8c in  () at /usr/lib/dri/radeonsi_dri.so
#7  

[kde] [Bug 472713] New: Dolphin frequently crashes with "signal: Bus error"; probably a duplicate but still unsure of how to fix.

[bugzilla_noreply]

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

Bug ID: 472713
   Summary: Dolphin frequently crashes with "signal: Bus error";
probably a duplicate but still unsure of how to fix.
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: willa...@yandex.com
  Target Milestone: ---

SUMMARY
Application: dolphin (21.12.3)

Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.14.21-150400.24.69-default x86_64
Windowing System: X11
Distribution: "openSUSE Leap 15.4"
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Usually, as is the case with this specific report, when I'm doing something
that requires frequent invoktion of Dolphin such as saving files to disk in
Firefox.

- Unusual behavior I noticed:
After my system has been up for a while, I frequently encounter a situation in
which Dolphin, regardless of how it's invoked, refuses to open, crashing
immediately with the attached (or similar) bug report. This happens regardless
of whether I open Dolphin directly from the desktop, the shell, or even through
another application that requires an external file selector such as saving
files to disk in Firefox. At first I thought it may be related to some
filesystem corruption but I've ran various fsck tools before and after the
crash and found no issue; plus, I can still traverse the filesystem just fine
from the shell. I suspect (from the crash handler's backtrace) it's a bug in
how "file icons" are cached.

- System:
Operating System: openSUSE Leap 15.4
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.14.21-150400.24.69-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-6500U CPU @ 2.50GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 520

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Bus error

[KCrash Handler]
#4  0x7fec3af1369d in __strncmp_avx2 () from /lib64/libc.so.6
#5  0x7fec3d4d59fa in qstrncmp (len=, str2=,
str1=) at /usr/include/qt5/QtCore/qbytearray.h:97
#6  SharedMemory::findNamedEntry (this=0x7fec229e, key=...) at
/usr/src/debug/kcoreaddons-5.90.0-150400.3.2.3.x86_64/src/lib/caching/kshareddatacache.cpp:768
#7  0x7fec3d4cf1d6 in KSharedDataCache::find (this=0x55d3121fe550, key=...,
destination=destination@entry=0x7ffc1dc365d0) at
/usr/src/debug/kcoreaddons-5.90.0-150400.3.2.3.x86_64/src/lib/caching/kshareddatacache.cpp:1558
#8  0x7fec3ef96fe0 in KIconLoaderPrivate::findCachedPixmapWithPath
(this=0x55d3121fee70, key=..., data=..., path=...) at
/usr/src/debug/kiconthemes-5.90.0-150400.3.2.3.x86_64/src/kiconloader.cpp:976
#9  0x7fec3ef9741c in KIconLoader::loadScaledIcon (this=0x7fec3f1aee40
<(anonymous namespace)::Q_QGS_globalIconLoader::innerFunction()::holder>,
_name=..., group=, group@entry=KIconLoader::Desktop,
scale=scale@entry=1, _size=..., state=, overlays=...,
path_store=0x0, canReturnNull=false, colors=std::optional [no
contained value]) at
/usr/src/debug/kiconthemes-5.90.0-150400.3.2.3.x86_64/src/kiconloader.cpp:1323
#10 0x7fec3ef8d781 in KIconEngine::createPixmap (this=0x55d31235ebf0,
size=..., scale=, scale@entry=1, mode=,
state=) at
/usr/src/debug/kiconthemes-5.90.0-150400.3.2.3.x86_64/src/kiconengine.cpp:114
#11 0x7fec3ef8db95 in KIconEngine::pixmap (this=, size=...,
mode=, state=) at
/usr/src/debug/kiconthemes-5.90.0-150400.3.2.3.x86_64/src/kiconengine.cpp:136
#12 0x7fec3c2508fb in QIcon::pixmap (this=this@entry=0x7ffc1dc36d00,
window=window@entry=0x0, size=..., mode=mode@entry=QIcon::Disabled,
state=state@entry=QIcon::Off) at image/qicon.cpp:905
#13 0x7fec3c2509de in QIcon::pixmap (this=this@entry=0x7ffc1dc36d00,
size=..., mode=mode@entry=QIcon::Disabled, state=state@entry=QIcon::Off) at
image/qicon.cpp:841
#14 0x7fec2812b1c5 in Breeze::Helper::coloredIcon (this=,
icon=..., palette=..., size=..., mode=mode@entry=QIcon::Disabled,
state=QIcon::Off) at
/usr/src/debug/breeze-5.24.4-bp154.1.34.x86_64/kstyle/breezehelper.cpp:1700
#15 0x7fec28149303 in Breeze::Style::drawToolButtonLabelControl
(this=0x55d3121f0930, option=0x7ffc1dc36cb0, painter=0x7ffc1dc36e10,
widget=0x55d312695c40) at
/usr/src/debug/breeze-5.24.4-bp154.1.34.x86_64/kstyle/breezestyle.cpp:4617
#16 0x7fec28147303 in std::function::operator()(Breeze::Style
const&, QStyleOption const*, QPainter*, QWidget const*) const
(__args#3=, __args#2=, __args#1=,
__args#0=..., this=0x7ffc1dc36c20) at
/usr/include/c++/7/bits/std_function.h:706
#17 Breeze::Style::drawControl (this=0x55d3121f0930,
element=QStyle::CE_ToolButtonLabel, 

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

[Igor Kushnir]

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

--- Comment #9 from Igor Kushnir  ---
(In reply to Igor Kushnir from comment #8)
> KDevelop should probably typedef _Float128 to double, not __float128, to
> match GCC's defines.
Or rather to "long double":
> typedef long double _Float64x;

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

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

[Igor Kushnir]

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

--- Comment #8 from Igor Kushnir  ---
From
https://codebrowser.dev/gcc/include/x86_64-linux-gnu/bits/floatn-common.h.html:
> No configurations support _Float128x or, as of GCC 7, have compiler
> support for a type meeting the requirements for _Float128x.

> #   if !__GNUC_PREREQ (7, 0) || defined __cplusplus
> typedef _Float128 _Float64x;
> #   endif
KDevelop should probably typedef _Float128 to double, not __float128, to match
GCC's defines.

It appears that these types are always defined in C++, not limited to C++20.
Maybe the C++ standard version affects something else. After all, GCC's
floatn-common.h header should be parsed by libclang too, but maybe it is parsed
wrongly for some reason. Will have to investigate this.

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

[frameworks-kio] [Bug 472712] New: Filesystem tree jumps to selected folder when expanding a folder

[Grósz Dániel]

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

Bug ID: 472712
   Summary: Filesystem tree jumps to selected folder when
expanding a folder
Classification: Frameworks and Libraries
   Product: frameworks-kio
   Version: 5.108.0
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kio-bugs-n...@kde.org
  Reporter: groszdaniel...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 160572
  --> https://bugs.kde.org/attachment.cgi?id=160572=edit
Screen recording (Kate Filesystem panel)

SUMMARY
This report pertains to the filesystem browser's tree view mode in the
Open/Save dialogs and the Filesystem (or Open File) panels in Kate, KDevelop
and Kile. It doesn't come up in Dolphin(part).

Sometimes a folder gets into a selected state, and from then on, the filesystem
view scrolls to that folder whenever you expand another folder in the tree if
the selected folder off the screen. This is inconvenient because it scrolls
away from the folder you expanded. (It's mostly an issue in the Filesystem
panels, which are persistently open; it's less of an issue in the file
dialogs.)

See attached screen recording.

- If you click a file in (e.g.) the Kate Filesystem panel, it opens, but the
file is immediately deselected, so the problem doesn't occur.
- If you right-click a file or folder to open its context menu, and then close
the context menu, it remains selected, but the selection disappears if you
expand a folder, so the problem doesn't occur.
- If you click on a folder in the Filesystem panel to open it, then use the
Back or Up button to go back, then it stays selected. That's when the problem
occurs. (I'm not sure if there are other ways to trigger it.)

STEPS TO REPRODUCE
0. Go to a folder that contains many files either directly or in subfolders.
1. Click on a subfolder.
2. Click Up or Back to go back to the folder containing it. (The folder you
previously opened stays selected.)
3. Scroll the panel's contents such that the selected folder is off the screen.
(Expand some folders beforehand if necessary.)
4. Click on the + or > sign to expand a folder.

OBSERVED RESULT
The filesystem browser jumps (scrolls) to the selected folder.

EXPECTED RESULT
The filesystem browser's contents stay where they are (except of course
files/folders below the folder you expand are shifted down) so you can see the
contents of the folder you expand immediately, just like when nothing is
selected.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230724
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.3-1-default (64-bit)
Graphics Platform: X11

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

[dolphin] [Bug 472711] Dolphin crashes, on exit selection mode

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

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

[Igor Kushnir]

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

--- Comment #7 from Igor Kushnir  ---
(In reply to Eugene Shalygin from comment #5)
> Yes, definitely. Everything works fine in the C++17 mode.
Strange. Will have to investigate this.

> I haven't tried clang-15, but why would it work if the newer version still
> has no these types? https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html
> says they are a new addition in C.
I thought so. Did "basing on Clang version" in your previous comment refer to a
future Clang version that will contain these types too?

OK, so no limiting to isCpp, because the kdevclang plugin supports only C and
C++, both of which contain these types.

(In reply to Eugene Shalygin from comment #6)
> Although the same GCC page states "These types are not supported when
> compiling C++." I don't understand what's going on then.
Yes, I also noticed that sentence. Maybe C++20 and later (but not C++ 17 or
earlier) includes the C standard version that contains these types?

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

[Smb4k] [Bug 472467] SMB4K Crash saving bookmarks

[Alexander Reinholdt]

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

--- Comment #7 from Alexander Reinholdt  ---
I found the place where the crash happens. It's in the bookmark menu. At the
moment I am investigating why it happens. I hope I can come up with a fix soon.

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

[dolphin] [Bug 472711] New: Dolphin crashes, on exit selection mode

[Steffen]

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

Bug ID: 472711
   Summary: Dolphin crashes, on exit selection mode
Classification: Applications
   Product: dolphin
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Selection Mode
  Assignee: kfm-de...@kde.org
  Reporter: sh...@gmx.de
CC: felixer...@kde.org
  Target Milestone: ---

SUMMARY
Dolphin with split view active, crashes on click on the exit selection mode
button

STEPS TO REPRODUCE
1. open dolphin
2. open split view
3. enter selection mode on left view
4. select a item in the left view
5. click somewhere on the right view
6. click exit selection mode button on left view

OBSERVED RESULT
Dolphin crashes


EXPECTED RESULT
no crash, just exit selection mode


SOFTWARE/OS VERSIONS
Dolphin Version: 23.07.70
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.80
KDE Frameworks Version:  5.240.0
Qt Version:  6.6.0

ADDITIONAL INFORMATION
Terminal output:
steffen@hp-laptop:~$ dolphin 
kf.kio.core: Invalid URL: QUrl("")
kf.moretools: KMoreTools::registerServiceByDesktopEntryName: the
kmt-desktopfile  "fsearch"  is provided but no Exec line is specified. The
desktop file is probably faulty. Please fix. Return nullptr.
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/kio_file.so"
doesn't implement WorkerFactory?
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/kio_file.so"
doesn't implement WorkerFactory?
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/kio_file.so"
doesn't implement WorkerFactory?
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/kio_file.so"
doesn't implement WorkerFactory?
qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
QCoreApplication::postEvent: Unexpected null receiver
kf.kio.core: Invalid URL: QUrl("")
qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
ASSERT: "(!isEnabled && (!m_selectionModeBottomBar ||
!m_selectionModeBottomBar->isEnabled() ||
!m_selectionModeBottomBar->isVisible() || m_selectionModeBottomBar->contents()
== SelectionMode::BottomBar::PasteContents)) || (isEnabled &&
m_selectionModeTopBar && m_selectionModeTopBar->isVisible() &&
m_selectionModeBottomBar && (m_selectionModeBottomBar->isVisible() ||
m_selectionModeBottomBar->contents() ==
SelectionMode::BottomBar::GeneralContents))" in file
./src/dolphinviewcontainer.cpp, line 392
21 -- exe=/usr/bin/dolphin
17 -- platform=wayland
16 -- appname=dolphin
17 -- apppath=/usr/bin
9 -- signal=6
9 -- pid=4136
20 -- appversion=23.07.70
20 -- programname=Dolphin
31 -- bugaddress=sub...@bugs.kde.org
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = dolphin path = /usr/bin pid = 4136
KCrash: Arguments: /usr/bin/dolphin 
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
warning: queue 0x5564d9497bc0 destroyed while proxies still attached:
  wl_display@1 still attached
Aborted (core dumped)
steffen@hp-laptop:~$ 

core dump (via drkonqi-coredump-gui):
   PID: 4136 (dolphin)
   UID: 1000 (steffen)
   GID: 1000 (steffen)
Signal: 6 (ABRT)
 Timestamp: Thu 2023-07-27 20:34:45 CEST (1min 14s ago)
  Command Line: dolphin
Executable: /usr/bin/dolphin
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-14ace62eb5d34412b88577bb0938b78d.scope
  Unit: user@1000.service
 User Unit: app-org.kde.konsole-14ace62eb5d34412b88577bb0938b78d.scope
 Slice: user-1000.slice
 Owner UID: 1000 (steffen)
   Boot ID: d36c7880879845b99b06ef24f749ef36
Machine ID: 1d9cbca8b7254534b04d489accc67c8b
  Hostname: hp-laptop
   Storage:
/var/lib/systemd/coredump/core.dolphin.1000.d36c7880879845b99b06ef24f749ef36.4136.169048288500.zst
(present)
 Disk Size: 5.5M
   Message: Process 4136 (dolphin) of user 1000 dumped core.

Found module linux-vdso.so.1 with build-id:
e193b3bf7f4697d33aa52014d3a0a58f5c3d7da1
Found module libQt6Sql.so.6 with build-id:
58a9e8bc4237a62e8184cf5ad5b5a034144493de
Found module kactivitymanagerd_fileitem_linking_plugin.so with
build-id: ede33f16b4371dab540b60ed4b8df634f8bd23fb
Found module tagsfileitemaction.so with build-id:
7bea755eaf4cb75fdc56db1840b1f4b0ddde67d4
Found module forgetfileitemaction.so with build-id:
be00f2c66fef759a6dd70bf4b70e981181ae713d
Found module plasmavaultfileitemaction.so with build-id:
c1a34f0f4e52015afa7d807bb31c196348e63769
Found module libqsvg.so with build-id:
21398f3f6fb29d288cbab27839c756ab1d7cfad5
Found module 

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

[Eugene Shalygin]

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

--- Comment #6 from Eugene Shalygin  ---
Although the same GCC page states "These types are not supported when compiling
C++." I don't understand what's going on then.

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

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

[Eugene Shalygin]

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

--- Comment #5 from Eugene Shalygin  ---
(In reply to Igor Kushnir from comment #4)
> The failing KDevelop's tests use a default standard and C++14, so the issue
> isn't limited to C++20. Does the standard version make a difference in your
> case?

Yes, definitely. Everything works fine in the C++17 mode.

> What do you typedef these types to?
float, double, and __float128.

> I agree that injecting type aliases would be safer than macros. Do you mean
> this option
> https://clang.llvm.org/docs/ClangCommandLineReference.html#cmdoption-clang-
> include-file ?

Yes, the force-include option.

> Does the Clang version make a difference or only GCC's? If only GCC's, then
> I think the header should be included `if (isCpp)`, similarly to
> https://invent.kde.org/kdevelop/kdevelop/-/commit/
> 35ea746ddd49e872998152cc157152c2cb5b86ea .

I haven't tried clang-15, but why would it work if the newer version still has
no these types? https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html says
they are a new addition in C.

> The header file can be installed with KDevelop, but then the exact path to
> the installed header would have to be found at run-time... Alternatively the
> header file can be stored in resources and copied into a temporary file at
> run-time (similarly to how the define files are stored in /tmp/kdevelop.*).

I see no big difference from the user point of view, and I guess it is not a
big deal to find out own installation prefix at run-time?

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

[krita] [Bug 472710] [5.2 Beta1 Appimage] Instant crash when creating a text selection area

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
The problem is "FT_Get_Transform", which means that the appimage is somehow
using the wrong version of freetype?

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

[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[Freya Lupen]

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

Freya Lupen  changed:

   What|Removed |Added

 CC||penguinflyer2...@gmail.com

--- Comment #3 from Freya Lupen  ---
Can you provide the crash log from 'Help->Show crash log for bug reports.'?

For what it's worth, I've yet to experience any crashes with 5.2.0-beta1 on my
ARM32 Android device, while transforming or otherwise.

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

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

[Igor Kushnir]

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

--- Comment #4 from Igor Kushnir  ---
(In reply to Eugene Shalygin from comment #3)
> Well, the IDE ceases to work as soon as you turn the C++20 mode on. As a
> workaround I provide those types as typedefs in the Language support/Defines
> page of the project settings dialog.
The failing KDevelop's tests use a default standard and C++14, so the issue
isn't limited to C++20. Does the standard version make a difference in your
case?
What do you typedef these types to?

> I'd supply a header file that defines those types basing on Clang version,
> which can be force included.
I agree that injecting type aliases would be safer than macros. Do you mean
this option
https://clang.llvm.org/docs/ClangCommandLineReference.html#cmdoption-clang-include-file
?
Does the Clang version make a difference or only GCC's? If only GCC's, then I
think the header should be included `if (isCpp)`, similarly to
https://invent.kde.org/kdevelop/kdevelop/-/commit/35ea746ddd49e872998152cc157152c2cb5b86ea
.

The header file can be installed with KDevelop, but then the exact path to the
installed header would have to be found at run-time... Alternatively the header
file can be stored in resources and copied into a temporary file at run-time
(similarly to how the define files are stored in /tmp/kdevelop.*).

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

[digikam] [Bug 472692] Tesseract OCR does not take language selection into account

[Maik Qualmann]

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

--- Comment #2 from Maik Qualmann  ---
Git commit 5918439aafb5b2f7387490cb2abc9178fe33f374 by Maik Qualmann.
Committed on 27/07/2023 at 20:49.
Pushed by mqualmann into branch 'master'.

fix language parameter for Tesseract OCR on Windows

M  +11   -0core/dplugins/generic/tools/ocrtextconverter/tesseractbinary.cpp

https://invent.kde.org/graphics/digikam/-/commit/5918439aafb5b2f7387490cb2abc9178fe33f374

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

[krita] [Bug 472710] New: [5.2 Beta1 Appimage] Instant crash when creating a text selection area

[Protoniv]

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

Bug ID: 472710
   Summary: [5.2 Beta1 Appimage] Instant crash when creating a
text selection area
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Tool/Text
  Assignee: krita-bugs-n...@kde.org
  Reporter: ss93...@gmail.com
  Target Milestone: ---

SUMMARY

Appimage, when using text tool to draw a rectangle area on canvas and release
mouse/stylus, krita crash instantly.
(Also tried on Windows 10 portable version, krita will hang for a short while,
and the text window will launch normally.)

STEPS TO REPRODUCE
1. Open a new document
2. Choose text tool and create an area for text on canvas
3. Krita crash

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE 15.5
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Can't get the crashlog backtrace with appimage, but here is the output when
launch from terminal.

***
krita.lib.pigment: Replacing color space factory "LABA" "L*a*b* (16
位元整數/每通道，無色彩管理)" with "LABA" "L*a*b*/Alpha (16 位元整數/每通道)"
krita.lib.pigment: Replacing color space factory "RGBA" "RGB (8
位元整數/每通道，無色彩管理)" with "RGBA" "RGB/Alpha (8 位元整數/每通道)"
krita.lib.pigment: Replacing color space factory "RGBA16" "RGB (16
位元整數/每通道，無色彩管理)" with "RGBA16" "RGB/Alpha (16 位元整數/每通道)"
QObject::startTimer: Timers cannot have negative intervals
Could not find platform independent libraries 
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
/tmp/.mount_krita-FcCHkq/usr/lib/krita-python-libs/krita added to PYTHONPATH
QObject::connect: Cannot connect QAction::triggered(bool) to
(nullptr)::toggle()
QAbstractItemModel::endInsertColumns:  Invalid index ( 0 , 101 ) in model
KisAnimTimelineFramesModel(0x55f253542740)
/tmp/.mount_krita-FcCHkq/usr/bin/krita: symbol lookup error:
/tmp/.mount_krita-FcCHkq/usr/bin/../lib/libraqm.so.0: undefined symbol:
FT_Get_Transform
***

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

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

[Eugene Shalygin]

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

--- Comment #3 from Eugene Shalygin  ---
(In reply to Igor Kushnir from comment #2)

> What are the practical consequences/problems? What workaround do you employ
> for this bug?

Well, the IDE ceases to work as soon as you turn the C++20 mode on. As a
workaround I provide those types as typedefs in the Language support/Defines
page of the project settings dialog.

> Does anyone know how to fix this issue properly? 

I'd supply a header file that defines those types basing on Clang version,
which can be force included.

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

[KDE Itinerary] [Bug 472630] Can't import from Dolphin to Itinerary

[Volker Krause]

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

--- Comment #3 from Volker Krause  ---
Ah, Flatpak is the important thing I was missing here! I need to check if
there's a better way to enable this without having to give apps full file
system access.

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

[tellico] [Bug 472709] New: Video Game collection is badly named Game collection

[Xavier Brochard]

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

Bug ID: 472709
   Summary: Video Game collection is badly named Game collection
Classification: Applications
   Product: tellico
   Version: 3.5.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ro...@periapsis.org
  Reporter: xav...@alternatif.org
  Target Milestone: ---

Hi Robby
The Video Games collection is known in Tellico as Games collection. May be it
is usual in US to understand "video game" when one speak about "game". But in
french the direct translation of Games is "Jeux" which usually means kids games
(like toys) or board games. 
But Tellico comes also with a pre defined Board Games collection. So it is a
bit confusing to remember that the Game collection is for Video Games only.

I suggest to rename it Video Games collection.

Xavier

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

[i18n] [Bug 472708] in Tellico, Video Games is badly translated with "Jeux" in french

[Jazeix Johnny]

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

Jazeix Johnny  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||jaz...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #1 from Jazeix Johnny  ---
Bonsoir, merci pour le retour.
Je viens de faire les modifications dans la révision
https://websvn.kde.org/?view=revision=1656797 (il y a un problème pour
le moment avec le site, il n'est plus mis à jour mais cela devrait être rétabli
d'ici quelques jours j'espère)

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

[kwin] [Bug 472055] Fast reactivation prevention of WindowHeap effects is counter-productive

[Maximilian Böhm]

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

Maximilian Böhm  changed:

   What|Removed |Added

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

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

[i18n] [Bug 472708] New: in Tellico, Video Games is badly translated with "Jeux" in french

[Xavier Brochard]

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

Bug ID: 472708
   Summary: in Tellico, Video Games is badly translated with
"Jeux" in french
Classification: Translations
   Product: i18n
   Version: 20.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: usability
  Severity: normal
  Priority: NOR
 Component: fr
  Assignee: kde-francoph...@kde.org
  Reporter: xav...@alternatif.org
  Target Milestone: ---

SUMMARY
Dans Tellico, la collection de "Jeux Vidéo" est systématiquement traduite par
"Jeux" en français. Or il y a aussi une collection de Jeux de plateau. Ça crée
de la confusion...

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

[gwenview] [Bug 472707] Fractional scaling under gwenview / wayland not correct

[pixelplanetdev]

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

--- Comment #1 from pixelplanetdev  ---
Created attachment 160571
  --> https://bugs.kde.org/attachment.cgi?id=160571=edit
screenshot of gwenview displaying a screenshot

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

[gwenview] [Bug 472707] New: Fractional scaling under gwenview / wayland not correct

[pixelplanetdev]

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

Bug ID: 472707
   Summary: Fractional scaling under gwenview / wayland not
correct
Classification: Applications
   Product: gwenview
   Version: 23.04.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: pixelplanet...@gmail.com
  Target Milestone: ---

SUMMARY

Even thought that i set global scaling to 150%, i expect a 4k image, displayed
on a 4k screen, to be as large as the screen when it's at 100% zoom within
gwenview.
I don't expect the image to be up- or downscaled.

This is not the case in gwenview.

STEPS TO REPRODUCE
1. use wayland on a 4k monitor
2. set scale to 150% (in screen settings)
2.  make fullscreen screenshot (screenshot correctly has 4k resolution)
3.  watch the screenshot with gwenview at 100% scale (in gwenview)

OBSERVED RESULT
Screenshot is scaled to 66%.
If i set gwenview to 150%, i get the correct size but blur from scaling.

EXPECTED RESULT
No weird scaling, no blur.
1px at the screenshot -> 1px at the screen

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.4-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland

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

[krita] [Bug 472706] New: krita brush engine crash

[Ubiratan]

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

Bug ID: 472706
   Summary: krita brush engine crash
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: ubiratanproje...@yahoo.com
  Target Milestone: ---

Created attachment 160570
  --> https://bugs.kde.org/attachment.cgi?id=160570=edit
an annoying crash in krita

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. I open krita that I installed by flatpak;
2. create a new file or open an existing one;
3. I choose the brush and I'm going to change their settings;
4. I can't change it because the functions are locked, they don't move and the
window is worse too.

OBSERVED RESULT
By accessing brush engines and changing brush settings. As picture. It doesn't
change, looks like it's stuck. It only performs the process when switching the
krita window with another application. I also noticed the same issue on ubuntu
23.04.

EXPECTED RESULT
the result I was hoping would be able to change brush functions without this
crash.

SOFTWARE/OS VERSIONS
Fedora Linux 38 (wokstation Edition), Gnome 44.3, bash 5.2.15 ,kernel:
6.4.4-200.fc38.x86_64
CPU: Intel i3-9100F (4) 4.200GHz, NVIDIA Geforce GT 710, 8 Giga DDR4 memory,
SSD 480GB ADATA

ADDITIONAL INFORMATION
I notice the same issue on snap on ubuntu 23.04 and Flatpak. So I switched to
fedora 38 and performed the same test with flatpak.

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

[kate] [Bug 472678] Kate 23.04.3-2097 runs fine; Kate 23.04.3-2104 won't run

[leland]

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

--- Comment #1 from leland  ---
As of build 2106 it is now fixed.  I was able to upgrade without incident
today.  Thanks for the fast fix!

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

[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[bugzilla_noreply]

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

--- Comment #2 from xeses16...@tastrg.com ---
Update: Tested on Galaxy Tab S8 Plus, and the crashes happen there too.

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

[digikam] [Bug 472704] Tags are not saved on exit

[Maik Qualmann]

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

--- Comment #2 from Maik Qualmann  ---
Note this Bug 469015, for new users on digiKam this option is already always
enabled.

Maik

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

[digikam] [Bug 472640] Batch Queue Manager Cannot see resize pixel size when Macintosh Widgets are selected

[Maik Qualmann]

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

--- Comment #9 from Maik Qualmann  ---
Is the Qt style name "macintosh"? Because the "slider bars" should have been
wider now.

Maik

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

[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[bugzilla_noreply]

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

--- Comment #1 from xeses16...@tastrg.com ---
Also: this is using the arm64 apk

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

[digikam] [Bug 472704] Tags are not saved on exit

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

  Component|Geolocation-Engine  |Geolocation-ReverseGeoCodin
   ||g

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

[digikam] [Bug 472704] Tags are not saved on exit

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||metzping...@gmail.com
   Severity|major   |normal
 Status|REPORTED|RESOLVED

--- Comment #1 from Maik Qualmann  ---
Expand the options in the reverse geolocation tool and enable tag writing. You
can now decide whether you only want to write IPTC location metadata and/or
also tags.

Maik

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

[plasmashell] [Bug 467992] Wrong keyboard layout switch hotkey behavior for more than two layouts and per window layout policy

[Michael Lashkevich]

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

--- Comment #10 from Michael Lashkevich  ---
(In reply to Andrey from comment #9)
> No, because we incorporated new platform-agnostic Wayland-capable applet to
> replace the old one since then. There is no way to return back.
> The only way is a proper fix.

I remind again. Maybe somebody else can do it, except you?

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

[krita] [Bug 472705] New: 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments

[bugzilla_noreply]

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

Bug ID: 472705
   Summary: 5.2 Beta 1 Android: App crashes shortly after
transforming multiple layers or at random moments
Classification: Applications
   Product: krita
   Version: unspecified
  Platform: Android
OS: Android 13.x
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: xeses16...@tastrg.com
  Target Milestone: ---

SUMMARY
***
The first thing I wanted to try on 5.2 beta is the new transform multiple
layers feature. All I did was make a new document, create a couple layers, and
made some brush strokes on all of them. Then I transformed them to a different
size by scale. The transformation finishes, but shortly afterwards, the app
will crash. I'm not sure if it's due to the transform tool itself or something
else, but when using the Android version, a crash is very likely after some
time of using it.

Compare this with 5.1.5 stable, which works perfectly and never crashes on my
phone.
***


STEPS TO REPRODUCE
1. Do a clean install of Krita 5.2 beta 1 Android.
2. Make a canvas, and make brush strokes on several layers.
3. Transform all these layers in some way. In my case, I transformed by scale.

OBSERVED RESULT
4. Transformation finishes, but the app will likely crash sometime after that.
EXPECTED RESULT
4. Transformation finishes, and I continue on with my drawing. 

SOFTWARE/OS VERSIONS
-Samsung Galaxy S23 Ultra (yes, I'm aware that tablets are recommended, but I
draw with 5.1.5 on my phone perfectly fine with no problem, lol)
-Android 13 with July 2023 security update
-Samsung One UI 5.1

ADDITIONAL INFORMATION

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

[okular] [Bug 430886] searchbar: add "whole words" option

[Germano Massullo]

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

Germano Massullo  changed:

   What|Removed |Added

 OS|Linux   |All

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

[kalendar] [Bug 472259] The kalendar closed when changing the percentage of a task

[Nathan]

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

Nathan  changed:

   What|Removed |Added

 CC||r3dgam...@gmail.com

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

[kalendar] [Bug 472259] The kalendar closed when changing the percentage of a task

[Nathan]

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

--- Comment #1 from Nathan  ---
Created attachment 160569
  --> https://bugs.kde.org/attachment.cgi?id=160569=edit
New crash information added by DrKonqi

kalendar (22.12.3) using Qt 5.15.8

After creating a new task changing the % complete slider will crash the
application. However the percentage set will remain when reopening the app.

-- Backtrace (Reduced):
#4  0x7f4dd0b9a980 in QDateTime::operator=(QDateTime const&) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#7  0x7f4dd0c537c0 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#10 0x7f4dd0c537c0 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#13 0x7f4dd0c537c0 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#16 0x7f4dd0c537c0 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5

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

[frameworks-qqc2-desktop-style] [Bug 471388] Visual glitches on button icons in apps using qqc2-desktop-style with a fractional scale factor

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
   Severity|normal  |minor
Summary|Visual glitches on toolbar  |Visual glitches on button
   |icons in apps using |icons in apps using
   |qqc2-desktop-style with a   |qqc2-desktop-style with a
   |fractional scale factor |fractional scale factor

--- Comment #5 from Nate Graham  ---
Can confirm.

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

[frameworks-networkmanager-qt] [Bug 452355] A notification asking to log-in to the network is displayed for every single network

[Riccardo Robecchi]

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

Riccardo Robecchi  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #21 from Riccardo Robecchi  ---
Leaving this open then.

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

[kwin] [Bug 470469] Unable to start wayland session NVIDIA 1050 Ti triple monitor setup due to kwin_wayland crashing

[bugzilla_noreply]

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

clichema...@gmail.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #9 from clichema...@gmail.com ---
I have since moved my installation to a new drive and in the process had the
opportunity to try with a stock kde install with no differences in behavior

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

[KDE Itinerary] [Bug 472630] Can't import from Dolphin to Itinerary

[bugzilla_noreply]

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

--- Comment #2 from aron...@gmail.com ---
(In reply to Volker Krause from comment #1)
> Strange, that works here without problems. Does this affect all files or
> just some with certain problematic file names? Does the file printed there
> actually exist or is it getting the wrong path from Dolphin do begin with?

The path works and the error happens with any file. I think it's a problem with
Flatpak, because Itinerary doesn't get filesystem=home access by default, but
after setting it up can import from Dolphin

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

[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402

[William Ashley]

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

William Ashley  changed:

   What|Removed |Added

 CC||w...@amazon.com

--- Comment #1 from William Ashley  ---
Created attachment 160568
  --> https://bugs.kde.org/attachment.cgi?id=160568=edit
Patch to add FEAT_DotProd support

I have implemented support for the dot product instructions (more specifically
those under the FEAT_DotProd feature). The attached patch file applies cleanly
to 'master' as of this writing. I haven't yet figured out the 'correct' process
for submitting changes to the valgrind project.

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

[plasma-systemmonitor] [Bug 446372] Changing polling time makes "Network & System" sections in the main page blank

[Riccardo Robecchi]

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

Riccardo Robecchi  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

--- Comment #11 from Riccardo Robecchi  ---
I have experienced this bug again today.

KDE Plasma version: 5.27.6
KDE Frameworks version: 5.108.0
Qt version: 5.15.10

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

[KDE Itinerary] [Bug 472630] Can't import from Dolphin to Itinerary

[Volker Krause]

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

--- Comment #1 from Volker Krause  ---
Strange, that works here without problems. Does this affect all files or just
some with certain problematic file names? Does the file printed there actually
exist or is it getting the wrong path from Dolphin do begin with?

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

[KDE Itinerary] [Bug 472652] unable te open

[Volker Krause]

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

--- Comment #1 from Volker Krause  ---
>From which repository are you getting the app from, and which version did you
try?

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

[digikam] [Bug 472704] Tags are not saved on exit

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Geolocation-Workflow|Geolocation-Engine
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 472640] Batch Queue Manager Cannot see resize pixel size when Macintosh Widgets are selected

[bugzilla_noreply]

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

--- Comment #8 from caulier.gil...@gmail.com ---
https://i.imgur.com/dgiAdZQ.png

Always reproducible with your last commit Maik...

Gilles

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

[digikam] [Bug 472704] New: Tags are not saved on exit

[Mitch Rauth]

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

Bug ID: 472704
   Summary: Tags are not saved on exit
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Geolocation-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: mi...@rauth.at
  Target Milestone: ---

SUMMARY
After adding tags by ReverseGeoCoding in Geolocation Editor, these are not
saved to the image after exiting.

STEPS TO REPRODUCE 
remark: I use digikam with German as selected language and are translating
back, thus the menues and buttons might be called slighly differently in the
English version.

I updated from 7.10.0 to 8.1.0 and did my normal workflow.

1. Select at least one image with coordinates in the main grid view
2. Open "Geolocation Editor" 
3. select the image, click on "Georeferencing", click on "do reverse geocoding"
=> tags corresponding to the selected setting are added to the image.
4. Click on "Close" and confirm that the changes should be saves "Yes"
5. Hove with the mouse over the image in the main grid view. 

OBSERVED RESULT
The tags have not been saved

EXPECTED RESULT
The tags are saved and visible for the image

SOFTWARE/OS VERSIONS
Windows: Windows 10 Pro 21H2, build 19044.3086

ADDITIONAL INFORMATION
Downgrading to digikam 7.10.0 and repeating the workflow on exactly the same
images yields the expected result

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

[kde] [Bug 472340] OLED subpixel rendering support

[Lukas Kucharczyk]

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

Lukas Kucharczyk  changed:

   What|Removed |Added

 CC||lu...@kucharczyk.xyz

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

[frameworks-kio] [Bug 472703] New: SSLUI presents Server Authentication dialog (sslui.cpp) with no ability to permanently block?

[boeroboy]

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

Bug ID: 472703
   Summary: SSLUI presents Server Authentication dialog
(sslui.cpp) with no ability to permanently block?
Classification: Frameworks and Libraries
   Product: frameworks-kio
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kio-bugs-n...@kde.org
  Reporter: boero...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY

I notice a few apps that occasionally check dodgy trackers or services with
untrusted certs. These apps continuously pop up the SSLUI dialog saying a
server failed authenticity check with the checkbox "do not ask again" which
only has any effect when you hit "Continue" as opposed to traditional Yes/No
buttons. I see in sslui.cpp#L48 a comment
```// ### We don't ask to permanently reject the certificate``` which is
unfortunate as the dialog will just keep popping up. I would love the option to
permanently cancel access to any bad certs from this dialog. Is it up to the
apps to do this instead? I would love to see "yes/no/don't show again" buttons
here and a ban list function if required.

https://github.com/KDE/kio/blob/b685528a6efb5150c379e9353d074c9488038af0/src/widgets/sslui.cpp#L48

Thoughts?

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

[systemsettings] [Bug 154804] Add option for alternative Drag behaviour

[timofej]

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

timofej  changed:

   What|Removed |Added

 CC||yakuts...@gmail.com

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

[plasmashell] [Bug 472702] New: Keyboard layout switcher doesn't work in VS Code

[bugzilla_noreply]

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

Bug ID: 472702
   Summary: Keyboard layout switcher doesn't work in VS Code
Classification: Plasma
   Product: plasmashell
   Version: 5.27.6
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Keyboard Layout
  Assignee: plasma-b...@kde.org
  Reporter: gudvinr+...@gmail.com
CC: butir...@gmail.com
  Target Milestone: 1.0

SUMMARY
When VS Code window is focused, keyboard layout switcher stops working.
It doesn't behave that way with other electron apps (i.e. discord that uses
electron 25).
If I focus other apps or desktop, I don't see the problem too.

VS Code itself uses electron 22.

Restarting app doesn't fix the problem.

STEPS TO REPRODUCE
1. Open VS Code

OBSERVED RESULT
Keyboard switcher hides from tray
Hotkey doesn't work

EXPECTED RESULT
Keyboard switching works

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.1.39-1-lts (64-bit)
Graphics Platform: X11

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

[dolphin] [Bug 472701] New: Dolphin crashes when dragging a file from cifs location

[Kosmas Mackrogamvrakis]

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

Bug ID: 472701
   Summary: Dolphin crashes when dragging a file from cifs
location
Classification: Applications
   Product: dolphin
   Version: 23.04.2
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kos...@kosmas.gr
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (23.04.2)
 (Compiled from sources)
Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.1.41-gentoo-x86_64 x86_64
Windowing System: Wayland
Distribution: "Gentoo Linux"
DrKonqi: 5.27.6 [KCrashBackend]

-- Information about the crash:
While browsing a cifs location (samba server), dragging a pdf file outside (to
thunderbird), it crashes.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x7f602ab65086 in QDrag::dragCursor(Qt::DropAction) const () at
/usr/lib64/libQt5Gui.so.5
#5  0x7f602ab678d9 in QBasicDrag::updateCursor(Qt::DropAction) () at
/usr/lib64/libQt5Gui.so.5
#6  0x7f6027b437bc in  () at /usr/lib64/libQt5WaylandClient.so.5
#7  0x7f602a6b77d4 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f6027b512a7 in
QtWaylandClient::QWaylandDataSource::dndResponseUpdated(bool, Qt::DropAction)
() at /usr/lib64/libQt5WaylandClient.so.5
#9  0x7f6027b4c809 in QtWayland::wl_data_source::handle_target(void*,
wl_data_source*, char const*) () at /usr/lib64/libQt5WaylandClient.so.5
#10 0x7f60252dc23a in  () at /usr/lib64/libffi.so.8
#11 0x7f60252db654 in  () at /usr/lib64/libffi.so.8
#12 0x7f60252dbdad in ffi_call () at /usr/lib64/libffi.so.8
#13 0x7f6028970924 in  () at /usr/lib64/libwayland-client.so.0
#14 0x7f602896cc68 in  () at /usr/lib64/libwayland-client.so.0
#15 0x7f602896e66c in wl_display_dispatch_queue_pending () at
/usr/lib64/libwayland-client.so.0
#16 0x7f6027b23196 in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /usr/lib64/libQt5WaylandClient.so.5
#17 0x7f602a6af734 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7f602b16342e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#19 0x7f602a684328 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x7f602a687863 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#21 0x7f602a6d64a3 in  () at /usr/lib64/libQt5Core.so.5
#22 0x7f602851449c in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x7f6028514748 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x7f60285147dc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x7f602a6d5fa6 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#26 0x7f602a682d4b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#27 0x7f602a68b026 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x55dde3a6ef07 in  ()
#29 0x7f6029e408ca in  () at /usr/lib64/libc.so.6
#30 0x7f6029e40985 in __libc_start_main () at /usr/lib64/libc.so.6
#31 0x55dde3a6f441 in  ()
[Inferior 1 (process 1013399) detached]

Reported using DrKonqi

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

[krita] [Bug 472700] Fill tool in color label reference mode is affected by layers contained in hidden group layers

[Deif Lou]

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

Deif Lou  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

[krita] [Bug 472700] Fill tool in color label reference mode is affected by layers contained in hidden group layers

[Deif Lou]

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

Deif Lou  changed:

   What|Removed |Added

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

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

[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type

[evgeny]

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

evgeny  changed:

   What|Removed |Added

 CC||m...@ch1p.io

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

[Smb4k] [Bug 472467] SMB4K Crash saving bookmarks

[Karl Mulder]

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

--- Comment #6 from Karl Mulder  ---
Alexander,

I used the software repository from your link. I selected Ubuntu and
chose the  *Add repository and install manually *option.
Install went fine, but when i repeated the test it crashed again.  I did go
through the kde crash reporter again.

Process i went through

   1. clicked Bookmarks
   2. clicked Edit Bookmarks
   3. highlighted a bookmark item
   4. changed the Category field
   5. Scrolled down the tree view
   6. selected another bookmark item and again changed the Category
   7. scrolled down the tree view, and changed a third Category field
   8. Clicked OK
   9. crashed

Before the crash the bookmark file contained 465 lines, after 129 lines. (
and yes i did backups ;-)

I just reopened the smb4k app, went into Bookmarks, Edit, and clicked OK
without modification. No crash.

I will reboot my system and try again, after a full os reboot.

On Thu, Jul 27, 2023 at 8:40 AM Alexander Reinholdt <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=472467
>
> --- Comment #3 from Alexander Reinholdt 
> ---
> (In reply to Alexander Reinholdt from comment #2)
> > Thank you for reporting this issue and please excuse my late response.
> Right
> > now my time is limited to work on Smb4K and follow the bug tracker.
> >
> > I will try to reproduce the bug and come up with a fix. Meanwhile, if
> > possible, could you please try the latest version (3.2.1) of Smb4K and
> check
> > if the problem is present there as well? To avoid data loss (I am very
> sorry
> > for the data loss that happened to your co-worker!), please back up the
> file
> > ~/.local/share/smb4k/bookmarks.xml before doing the tests.
>
> You can download the latest version from here (it also includes WS
> Discovery
> Support):
>
> https://software.opensuse.org//download.html?project=home%3Aareinholdt=smb4k
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[krita] [Bug 472700] New: Fill tool in color label reference mode is affected by layers contained in hidden group layers

[bugzilla_noreply]

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

Bug ID: 472700
   Summary: Fill tool in color label reference mode is affected by
layers contained in hidden group layers
Classification: Applications
   Product: krita
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: 010freeze...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Create a document with the following structure.
Layer1. Empty paint layer(Show, No color label)
Layer2. Group layer(Hide, No color label)
Layer3. Inside Layer 2,Paint layer with a something painted on it(Show, blue
color label)
2. Activate the Fill tool, put it in color label reference mode, and select the
blue label.
3. Try a fill on layer 1.

OBSERVED RESULT
The fill is affected by a paint layer (Layer 3) inside a group layer (Layer 2)
that is hidden.

EXPECTED RESULT
Since the group layer (Layer 2) is hidden, the fill tool should function
unaffected by the paint layer (Layer 3) inside it.

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