date:20231101

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

Bug ID: 476396
   Summary: Discover: "The PackageKit daemon has crashed"
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: m...@apache.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY

After a recent Neon 5.27 package update (maybe a month or so ago) Discover
started to throw up a dialog telling me "The PackageKit daemon has crashed"
(cf. attached screenshot).

This was reported to Discover a few times already but always closed as "please
tell your Distro". Well, Neon is my distro, here you go. I actually doubt that
this is a distro related issue since 
(a) it was reported for various distros (including Neon)
(b) it started happening only after some KDE Neon package update (there might
have been a PackageKit update involved though)

STEPS TO REPRODUCE
This is the way it happens to me:
1. Be notified about updates
2. Open Discover
3. Deselect the Neon packages, keep only the Flatpak updates
4. Press Apply or whatever that button is labeled with
5. A dialog will pop up telling you PackageKit has crashed
6. The Flatpak updates will actually suceed. At least it looks like that.

OBSERVED RESULT
A dialog "The PackageKit daemon has crashed" pops up

EXPECTED RESULT
No such dialog

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon User Edition 5.27
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION

coredumpctl says:

TIME  PID UID GID SIG COREFILE EXE 
SIZE
Mon 2023-10-30 13:22:59 CET  9575   0   0 SIGABRT inaccessible
/usr/libexec/packagekitd  n/a
Mon 2023-10-30 13:23:00 CET 10331   0   0 SIGABRT inaccessible
/usr/libexec/packagekitd  n/a
Mon 2023-10-30 14:02:58 CET 12922   0   0 SIGABRT inaccessible
/usr/libexec/packagekitd  n/a
Wed 2023-11-01 09:01:55 CET  1656   0   0 SIGABRT inaccessible
/usr/libexec/packagekitd  n/a

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

[digikam] [Bug 476397] New: Trash status not update if you use the context menu to delete

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

Bug ID: 476397
   Summary: Trash status not update if you use the context menu to
delete
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Albums-Trash
  Assignee: digikam-bugs-n...@kde.org
  Reporter: benedekppe...@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
***
Trash status not update in the left sidebar if you use the context menu to
delete.

STEPS TO REPRODUCE
1. Click right click on the trash icon in the left sidebar. 
2. Chose delete items

OBSERVED RESULT
digiKam performs the delete operation, but the icon still shows the number of
items waiting to be deleted.
video attached.

EXPECTED RESULT
At the end of the operation, digiKam should show the real status of the trash.

SOFTWARE/OS VERSIONS
Windows: 10
Linux/KDE Plasma: Linux Mint 21.2 (digikam 8.2.0 appimage)

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

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed"

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

Malte S. Stretz  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=433457,
   ||https://bugs.kde.org/show_b
   ||ug.cgi?id=448463,
   ||https://bugs.kde.org/show_b
   ||ug.cgi?id=476065

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

[Discover] [Bug 433457] "The PackageKit daemon has crashed" double error

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

Malte S. Stretz  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=476396

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

[Discover] [Bug 476065] The PackageKit daemon has crashed

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

Malte S. Stretz  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=476396

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

[Discover] [Bug 448463] The PackageKit daemon has crashed

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

Malte S. Stretz  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=476396

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

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

--- Comment #58 from caulier.gil...@gmail.com ---
I started to compile with cmake VERBOSE mode and non parallelized. First file
compiled is this one :
CustomBuild:
  Building Custom Rule
C:/Users/gilles/Documents/digikam/core/libs/database/CMakeLists.txt
ClCompile:
  C:\Program Files\Microsoft Visual
Studio\2022\Community\VC\Tools\MSVC\14.37.32822\bin\HostX64\x64\CL.exe /c
/IC:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\database
/IC:\Users\gilles\Documents\digikam\core\libs\database
/IC:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\database\core_digikamdatabase_obj_autogen\include_Debug
/IC:\Users\gilles\Documents\digikam\core\libs\album\engine
/IC:\Users\gilles\Documents\digikam\core\libs\album\manager
/IC:\Users\gilles\Documents\digikam\core\libs\album\treeview
/IC:\Users\gilles\Documents\digikam\core\libs\album\widgets
/IC:\Users\gilles\Documents\digikam\core\libs\database\collection
/IC:\Users\gilles\Documents\digikam\core\libs\database\coredb
/IC:\Users\gilles\Documents\digikam\core\libs\database\dbjobs
/IC:\Users\gilles\Documents\digikam\core\libs\database\engine
/IC:\Users\gilles\Documents\digikam\core\libs\database\haar
/IC:\Users\gilles\Documents\digikam\core\libs\database\history
/IC:\Users\gilles\Documents\digikam\core\libs\database\item\containers
/IC:\Users\gilles\Documents\digikam\core\libs\database\item\lister
/IC:\Users\gilles\Documents\digikam\core\libs\database\item\query
/IC:\Users\gilles\Documents\digikam\core\libs\database\item\scanner
/IC:\Users\gilles\Documents\digikam\core\libs\database\models
/IC:\Users\gilles\Documents\digikam\core\libs\database\server
/IC:\Users\gilles\Documents\digikam\core\libs\database\similaritydb
/IC:\Users\gilles\Documents\digikam\core\libs\database\tags
/IC:\Users\gilles\Documents\digikam\core\libs\database\thumbsdb
/IC:\Users\gilles\Documents\digikam\core\libs\database\utils\ifaces
/IC:\Users\gilles\Documents\digikam\core\libs\database\utils\scan
/IC:\Users\gilles\Documents\digikam\core\libs\database\utils\widgets
/IC:\Users\gilles\Documents\digikam\core\libs\dialogs
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\color
/IC:\Users\gilles\Documents\digikam\core\libs\dimg
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\auto
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\bcg
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\bw
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\cb
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\curves
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\decorate
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\film
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\fx
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\greycstoration\cimg
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\greycstoration
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\hotpixels
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\hsl
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\icc
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\lc
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\lens
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\levels
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\nr
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\raw
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\redeye
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\sharp
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\transform
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\filters\wb
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\history
/IC:\Users\gilles\Documents\digikam\core\libs\dimg\loaders
/IC:\Users\gilles\Documents\digikam\core\libs\dngwriter
/IC:\Users\gilles\Documents\digikam\core\libs\dplugins\core
/IC:\Users\gilles\Documents\digikam\core\libs\dplugins\iface
/IC:\Users\gilles\Documents\digikam\core\libs\dplugins\setup
/IC:\Users\gilles\Documents\digikam\core\libs\dplugins\webservices
/IC:\Users\gilles\Documents\digikam\core\libs\dplugins\widgets
/IC:\Users\gilles\Documents\digikam\core\libs\dragdrop
/IC:\Users\gilles\Documents\digikam\core\libs\dtrash
/IC:\Users\gilles\Documents\digikam\core\libs\facesengine\common
/IC:\Users\gilles\Documents\digikam\core\libs\facesengine\detection
/I"C:\Users\gilles\Documents\digikam\core\libs\facesengine\detection\opencv-dnn"
/IC:\Users\gilles\Documents\digikam\core\libs\facesengine\facedb
/IC:\Users\gilles\Documents\digikam\core\libs\facesengine\preprocessing
/IC:\Users\gilles\Documents\digikam\core\libs\facesengine\preprocessing\recognition
/I"C:\Users\gilles\Documents\digikam\core\libs\facesengine\preprocessing\shape-predictor"
/IC:\Users\gilles\Documents\digikam\core\libs\facesengine\recognition
/I"C:\Users\gilles\Documents\digikam\core\libs\facesengine\recognition\opencv-dnn"
/IC:\

[digikam] [Bug 476397] Trash status not update if you use the context menu to delete

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

--- Comment #1 from Peter  ---
Created attachment 162785
  --> https://bugs.kde.org/attachment.cgi?id=162785&action=edit
Deletion status of trash is not updated

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

[kinfocenter] [Bug 476398] New: KInfoCenter UI jumps around with some window sizes

2023-11-01 Thread Yonatan Avhar

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

Bug ID: 476398
   Summary: KInfoCenter UI jumps around with some window sizes
Classification: Applications
   Product: kinfocenter
   Version: 5.27.9
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: yonatan3...@outlook.com
CC: sit...@kde.org
  Target Milestone: ---

SUMMARY
When I open KInfoCenter and go to the Energy panel with the window at just the
right size for the text to nearly clip the bottom edge of the screen, it seems
there's a small margin created at the bottom of the window, causing the whole
UI to jump around


STEPS TO REPRODUCE
1. Open KInfoCenter's Energy panel
2. Play around with the window size

OBSERVED RESULT
The UI jumps around at some sizes

EXPECTED RESULT
The UI stays stable

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
Here are 2 videos showing the behavior when resizing the window and when
maximizing it
https://youtu.be/VT-NIrPGwjc
https://youtu.be/n96rHSkUqww

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

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed"

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

--- Comment #1 from Malte S. Stretz  ---
Created attachment 162786
  --> https://bugs.kde.org/attachment.cgi?id=162786&action=edit
Output of journalctl --boot | grep -i packagekit

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

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed"

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

--- Comment #2 from Malte S. Stretz  ---
Created attachment 162787
  --> https://bugs.kde.org/attachment.cgi?id=162787&action=edit
Output of journalctl --boot -t systemd-coredump

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

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed"

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

--- Comment #3 from Malte S. Stretz  ---
Created attachment 162788
  --> https://bugs.kde.org/attachment.cgi?id=162788&action=edit
Screenshot

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

[systemsettings] [Bug 476399] New: Weird behaviour after switch global theme back and forth

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

Bug ID: 476399
   Summary: Weird behaviour after switch global theme back and
forth
Classification: Applications
   Product: systemsettings
   Version: 5.27.8
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: r.arswend...@gmail.com
  Target Milestone: ---

Application: systemsettings (5.27.8)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.0-10-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.10
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
I wanted to compare the theme breeze dark and mcsur dark so I switched back and
forth then some app called Kanqi crashed. After that I changed to mcsur again
Then I opened by desktop edit mode, right clicked on the taskbar then show
alternatives then change to window list. after that I checked "floating icon"
for the taskbar then I resized them. Close the edit mode and then change back
to breeze dark. and then My Mic icon on the task bar duplicated.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault

[KCrash Handler]
#4  0x7f89d847bd48 in
QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*,
QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f89d847bc51 in
QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*,
QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f89d847bc51 in
QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*,
QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f89d847bc51 in
QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*,
QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f89d847ca44 in
QQuickWindowPrivate::deliverToPassiveGrabbers(QVector
> const&, QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7f89d8482eb3 in
QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7f89d8484541 in
QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7f89d84856dd in QQuickWindowPrivate::handleMouseEvent(QMouseEvent*)
() from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7f89da54fe05 in QWindow::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7f89dad6bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f89da0cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f89d8fd1f0b in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from
/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#16 0x7f89dadaeb28 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f89dad6bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f89dad741bd in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f89da0cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f89dad724b2 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f89dadc7da1 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f89dadcb12f in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7f89dad6bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f89da0cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f89da543bdb in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#26 0x7f89da51762c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#27 0x7f89d4f8ff7e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#28 0x7f89d8a5cb2c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7f89d8ab846f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7f89d8a5ad20 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7f89da127daa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7f89da0cb15b in
QEventLoop::exec(QFlags) () from
/lib/x86_64

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed"

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

--- Comment #4 from Malte S. Stretz  ---
It looks like this is a PackageKit bug indeed. Here is the Debian bug which
resulted in this upstream fix which should then be backported for Neon (or
maybe Discover should work around it):
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054026
* https://github.com/PackageKit/PackageKit/issues/656

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

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

--- Comment #59 from caulier.gil...@gmail.com ---
Git commit 7afb2e4d96dc4d972809395ca17defc1ffb1a049 by Gilles Caulier.
Committed on 01/11/2023 at 09:29.
Pushed by cgilles into branch 'master'.

remove MSVC obsolete options now managed by ECM in background. Add new option
for MSVC 2022

M  +1-8CMakeLists.txt

https://invent.kde.org/graphics/digikam/-/commit/7afb2e4d96dc4d972809395ca17defc1ffb1a049

diff --git a/CMakeLists.txt b/CMakeLists.txt
index bde0eeb064..798e49108f 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -149,14 +149,7 @@ set(CMAKE_AUTOMOC ON)

 if(MSVC)
 set(CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS ON)
-
-# These settings comes with ecm 5.88 , so when we bump KF/ecm to 5.88+ we
can remove these
-add_compile_options(/utf-8)
-if (CMAKE_CXX_STANDARD GREATER_EQUAL 11)
-# Ensure __cplusplus is correct, otherwise it defaults to 199711L
which isn't true
-#
https://docs.microsoft.com/en-us/cpp/build/reference/zc-cplusplus?view=msvc-160
-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /Zc:__cplusplus")
-endif()
+   set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /permissive-")
 endif()

 set_property(GLOBAL PROPERTY USE_FOLDERS ON)

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

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

--- Comment #60 from caulier.gil...@gmail.com ---
With my last commit, now the earth turn well:

gilles@Win10 MINGW64 ~/Documents/digikam (master)
$ cd build.vcpkg/

gilles@Win10 MINGW64 ~/Documents/digikam/build.vcpkg (master)
$ cmake --build . --parallel
MSBuild version 17.7.2+d6990bcfa for .NET Framework

  Automatic MOC for target core_digikamdatabase_obj
  Automatic MOC for target core_digikamdialogs_obj
  Automatic MOC for target digikamdatabase_obj
  Automatic MOC for target gui_advancedrename_obj
  core_digikamdatabase_obj.vcxproj ->
C:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\database\core_digikamdatabase_obj.dir\Debug\core_digikamdatabase_obj.lib
  Automatic MOC for target gui_digikam_obj
  Building Custom Rule
C:/Users/gilles/Documents/digikam/core/libs/dialogs/CMakeLists.txt
  Automatic MOC for target gui_digikamalbum_obj
  mocs_compilation_Debug.cpp
  dprogressdlg.cpp
  dbusydlg.cpp
  filesaveoptionsdlg.cpp
  Building Custom Rule
C:/Users/gilles/Documents/digikam/core/libs/database/CMakeLists.txt
  iccprofileinfodlg.cpp
  Automatic MOC for target gui_digikamdatabasemain_obj
  mocs_compilation_Debug.cpp
  imagedialog.cpp
  Generating ui_fillmodifierdialogwidget.h
  Generating ui_rangemodifierdialogwidget.h
  collectionscanner.cpp
  Generating ui_replacemodifierdialogwidget.h
  Building Custom Rule
C:/Users/gilles/Documents/digikam/core/libs/album/CMakeLists.txt
  imagedialog_preview.cpp
  Generating ui_dateoptiondialogwidget.h
  Generating ui_sequencenumberoptiondialogwidget.h
  mocs_compilation_Debug.cpp
C:\Users\gilles\Documents\digikam\core\libs\database\collection\collectionlocation.h(171,23):
warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of
data
[C:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\database\digikamdatabase_obj.vcxproj]
C:\Users\gilles\Documents\digikam\core\libs\database\collection\collectionscanner_p.h(91,34):
warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of
data
[C:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\database\digikamdatabase_obj.vcxproj]
  Building Custom Rule
C:/Users/gilles/Documents/digikam/core/utilities/advancedrename/CMakeLists.txt
  collectionscanner_p.cpp
  mocs_compilation_Debug.cpp
  imagedialog_iconprovider.cpp
C:\Users\gilles\Documents\digikam\core\libs\database\collection\collectionlocation.h(171,23):
warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of
data
[C:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\database\digikamdatabase_obj.vcxproj]
C:\Users\gilles\Documents\digikam\core\libs\database\collection\collectionlocation.h(171,23):
warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of
data
[C:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\album\gui_digikamalbum_obj.vcxproj]
C:\Users\gilles\Documents\digikam\core\libs\database\collection\collectionscanner_p.h(91,34):
warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of
data
[C:\Users\gilles\Documents\digikam\build.vcpkg\core\libs\database\digikamdatabase_obj.vcxproj]
  Building Custom Rule
C:/Users/gilles/Documents/digikam/core/libs/database/CMakeLists.txt
  collectionscanner_scan.cpp
  mocs_compilation_Debug.cpp
...

We will see in few hours when the _very slow_ MSVC complete the task...

Gilles

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

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

--- Comment #61 from caulier.gil...@gmail.com ---
Maik,

MSVC report interresing compilation warnings. I will attach the complete log
here when process will completed.

Gilles

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

[KTechLab] [Bug 473717] Application crashes on adding a subcircuit

2023-11-01 Thread Zoltan Padrah

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

--- Comment #4 from Zoltan Padrah  ---
(In reply to Guillermo González García from comment #3)
> Hello Zoltan,
> 
> I switched to version 50.0. I didn't build it from source, just a rpm. It
> worked for several months but right now I'm experiencing the same issue.
> 
> Regards.

Is it possible that the package has got automatically upgraded to version 50.0,
causing the crashes to appear again? Can you check the version of KTechLab ?

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

[digikam] [Bug 476397] Trash status not update if you use the context menu to delete

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Platform|Other   |Mint (Debian based)

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

[kmix] [Bug 476400] New: Option to disable automatic binding global XF86Audio* shortcuts?

2023-11-01 Thread Milkii B

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

Bug ID: 476400
   Summary: Option to disable automatic binding global XF86Audio*
shortcuts?
Classification: Applications
   Product: kmix
   Version: 23.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: k...@milkmiruku.com
  Target Milestone: ---

When I start Kmix in .xinitrc, it binds to XF86AudioLowerVolume and
XF86AudioRaiseVolume.

But I would like my window manager to bind a script to both of those keys (a
brief one that decreases and increases the level on all devices not just one).

But there is no way currently to disable Kmix from taking control of those keys
before my window manager stops.

Can I please request an Kmix option to disable this behaviour? Thanks!

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

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

--- Comment #62 from caulier.gil...@gmail.com ---
Why we needs to create symlink in face recognition test suite ?

  core_imgqsort_obj.vcxproj ->
C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\imgqsort\core_imgqsort_obj.dir\Debug\core_imgqsort_obj.lib
  Generating ui_sequencenumberoptiondialogwidget.h
  Building Custom Rule
C:/Users/gilles/Documents/8.x/core/utilities/advancedrename/CMakeLists.txt
CUSTOMBUILD : CMake error : failed to create symbolic link
'C:/Users/gilles/Documents/8.x/build.vcpkg/core/tests/facesengine/recognition/data':
A required privilege is not held by the client.
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\tests\facesengine\recognition\datalink_rec.vcxproj]

C:\Program Files\Microsoft Visual
Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(249,5):
error MSB8066: Custom build for
'C:\Users\gilles\Documents\8.x\build.vcpkg\CMakeFiles\e1d3e74fbdd9c78fea53dcc6a037dd4c\datalink_rec.rule;C:\Users\gilles\Documents\8.x\core\tests\facesengine\recognition\CMakeLists.txt'
exited with code 1.
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\tests\facesengine\recognition\datalink_rec.vcxproj]

I will disable the TEST compilation for the moment...

Gilles

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

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

--- Comment #63 from caulier.gil...@gmail.com ---
What is that :

C:\Users\gilles\Documents\8.x\core\libs\database\collection\collectionlocation.h(171,23):
warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of
data
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\database\gui_digikamdatabasemain_obj.vcxproj]
  albumhistory.cpp
  networkmanager.cpp
  facialrecognition_wrapper_recognize.cpp
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(104,48): error C2039: '_hypot': is
not a member of 'std'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qhashfunctions.h(329,1): message : see
declaration of 'std'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(104,69): message : see reference
to class template instantiation 'QtPrivate::QHypotType' being compiled
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
  dxmlguiwindow.cpp
  diofinders.cpp
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(155,16): error C2039: '_hypot': is
not a member of 'std'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qhashfunctions.h(329,1): message : see
declaration of 'std'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(163,16): error C2039: '_hypot': is
not a member of 'std'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qhashfunctions.h(329,1): message : see
declaration of 'std'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(155,5): error C2873: '_hypot':
symbol cannot be used in a using-declaration
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(163,5): error C2873: '_hypot':
symbol cannot be used in a using-declaration
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(164,12): error C2660: '_hypot':
function does not take 3 arguments
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
C:\Program Files (x86)\Windows
Kits\10\Include\10.0.22621.0\ucrt\corecrt_math.h(515,47): message : see
declaration of '_hypot'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
E:\dk\x64-windows\include\Qt6\QtCore/qmath.h(164,12): message : while trying to
match the argument list '(Tx, Ty, Tz)'
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\rawengine\core_rawengine_obj.vcxproj]
  with
  [
  Generating Code...
  Tx=float
  digikamapp.cpp
  Generating Code...
  ]
  and
C:\Users\gilles\Documents\8.x\core\libs\database\collection\collectionlocation.h(171,23):
warning C4267: 'return': conversion from 'size_t' to 'uint', possible loss of
data
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\database\digikamdatabase_obj.vcxproj]
  [
  Ty=float
  ]
  and
  [
C:\Users\gilles\Documents\8.x\core\libs\album\engine\albumhistory.cpp(44,32):
warning C4267: 'initializing': conversion from 'size_t' to 'uint', possible
loss of data
[C:\Users\gilles\Documents\8.x\build.vcpkg\core\libs\album\gui_digikamalbum_obj.vcxproj]
  Tz=float
  facialrecognition_wrapper_identity.cpp
  ]
  tagcheckview.cpp
  drawdecoder_p.cpp
  scancontroller.cpp

Gilles

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

[kdeconnect] [Bug 432554] Open KDE Connect app on clicking Indicator notification icon?

2023-11-01 Thread Milkii B

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

Milkii B  changed:

   What|Removed |Added

Version|1.10|23.08.2

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

[plasmashell] [Bug 351175] "Auto-Hide" mode does not work when panel is on an edge between two screens

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

Lassi Väätämöinen  changed:

   What|Removed |Added

 CC||lassi.vaatamoi...@gmail.com

--- Comment #64 from Lassi Väätämöinen  ---
(In reply to Nate Graham from comment #63)
>  So let's consider that fixed, at least as of Plasma 6 Wayland.
> 

Reproduces on 5.27 with Wayland, at least.

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.2.0-33-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i7-11850H @ 2.50GHz
Memory: 46,7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 20YRS21300
System Version: ThinkPad P15 Gen 2i

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

[dolphin] [Bug 454044] Add option to unmount an sftp connection

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

kimim...@posteo.net changed:

   What|Removed |Added

 CC||kimim...@posteo.net

--- Comment #2 from kimim...@posteo.net ---
Created attachment 162789
  --> https://bugs.kde.org/attachment.cgi?id=162789&action=edit
Mockup of Dolphin network unmount

Any updates about this one? Specifically, the lack of an option to unmount has
been bugging me for all types of network shares available in Dolphin: SMB,
SFTP, WebDav, and so on.

As mentioned in the report, the Nemo file manager handles this very well by
showing the network share as a mount. Unmounting it disconnects the connection.

I would be happy with see a similar approach in Dolphin. I've attached a mockup
of what it could look like (keeping in mind a generic network connection).

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

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed" when updating a Flatpak

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

Malte S. Stretz  changed:

   What|Removed |Added

Summary|Discover: "The PackageKit   |Discover: "The PackageKit
   |daemon has crashed" |daemon has crashed" when
   ||updating a Flatpak

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

[plasmashell] [Bug 351175] "Auto-Hide" mode does not work when panel is on an edge between two screens

2023-11-01 Thread Uwe Dippel

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

--- Comment #65 from Uwe Dippel  ---
To Lassi, #64: It was mentioned to be fixed in Plasma 6. For Plasma 5 the bug
is confirmed. 
Or is it anything else that you wanted to say?

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

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed" when updating a Flatpak

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

Malte S. Stretz  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Malte S. Stretz  ---
I can reproduce this reliably by downgrading the zoom flatpak and updating it
again.

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

[lokalize] [Bug 476040] crash when changing a plural from fuzzy to ok

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

--- Comment #3 from Freek de Kruijf  ---
Created attachment 162790
  --> https://bugs.kde.org/attachment.cgi?id=162790&action=edit
New crash information added by DrKonqi

lokalize (23.08.2) using Qt 5.15.11

Busy editing .../nl/messages/krita/krita.po in plural element. Left single
allone, was OK, and tried to enter %1 in front of plural and to change single
word in plural word, but crashed already when entering %.

-- Backtrace (Reduced):
#4  0x7f8bc4d8610c in std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x30) at
/usr/include/c++/13/bits/atomic_base.h:505
#5  QAtomicOps::loadRelaxed (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=0x30) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
[...]
#8  QString::operator= (this=0x5622bc5539b0, other=...) at
text/qstring.cpp:2408
#9  0x5622b7bb9c3e in MergeCatalog::copyFromBaseCatalog
(this=0x5622bc500700, pos=..., options=0) at
/usr/src/debug/lokalize-23.08.2/src/mergemode/mergecatalog.cpp:51

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

[lokalize] [Bug 476040] crash when changing a plural from fuzzy to ok

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

Freek de Kruijf  changed:

   What|Removed |Added

 CC||freekdekru...@kde.nl

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

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

--- Comment #64 from caulier.gil...@gmail.com ---
Nice. With VCPKG, ffmpeg 6 is installed, and configure is wrong:

-- digiKam MediaPlayer dependencies checks:
--
-- FFMPEG_FOUND= TRUE
-- FFMPEG_INCLUDE_DIRS = E:/dk/x64-windows/include
-- FFMPEG_LIBRARIES=
E:/dk/x64-windows/lib/avcodec.lib;E:/dk/x64-windows/lib/avdevice.lib;E:/dk/x64-windows/lib/avfilter.lib;E:/dk/x64-windows/lib/avformat.lib;E:/dk/x64-windows/lib/avutil.lib;E:/dk/x64-windows/lib/swscale.lib;E:/dk/x64-windows/lib/swresample.lib
-- FFMPEG_DEFINITIONS  =
-- Could NOT find FFmpeg (missing: AVRESAMPLE_LIBRARIES
AVRESAMPLE_INCLUDE_DIRS)
-- FFMPEG_FOUND= FALSE
-- FFMPEG_INCLUDE_DIRS = E:/dk/x64-windows/include
-- FFMPEG_LIBRARIES=
E:/dk/x64-windows/lib/avcodec.lib;E:/dk/x64-windows/lib/avdevice.lib;E:/dk/x64-windows/lib/avfilter.lib;E:/dk/x64-windows/lib/avformat.lib;E:/dk/x64-windows/lib/avutil.lib;E:/dk/x64-windows/lib/swscale.lib;E:/dk/x64-windows/lib/swresample.lib
-- FFMPEG_DEFINITIONS  =
-- Direct2D_INCLUDE_DIRS: C:/Program Files (x86)/Windows
Kits/10/Include/10.0.22621.0/um
-- Direct2D_D2D1_LIBRARY: C:/Program Files (x86)/Windows
Kits/10/Lib/10.0.22621.0/um/x64/d2d1.lib
-- Direct2D_DWRITE_LIBRARY: C:/Program Files (x86)/Windows
Kits/10/Lib/10.0.22621.0/um/x64/dwrite.lib
-- Could NOT find GDIPLUS (missing: GDIPLUS_INCLUDE_DIR)
-- SSE2 support   : 1
-- SSE3 support   : false
-- SSSE3 support  : false
-- SSE4.1 support : false
-- SSE4.2 support : false
-- FFMpeg AVCodec(required) : TRUE ()
-- FFMpeg AVDevice   (required) : TRUE ()
-- FFMpeg AVFilter   (required) : TRUE ()
-- FFMpeg AVFormat   (required) : TRUE ()
-- FFMpeg AVUtil (required) : TRUE ()
-- FFMpeg SWScale(required) : TRUE ()
-- FFMpeg SWResample (required) : TRUE ()
-- FFMpeg AVResample (optional) : FALSE ()
-- MediaPlayer support is enabled   : yes
-- MediaPlayer will use FFMpeg 5 API: no   
  <=== 
-- MediaPlayer will be compiled with SSE2 support   : yes
-- MediaPlayer will be compiled with LibASS support : no
-- MediaPlayer will be compiled with UCharDet support   : no
-- MediaPlayer will be compiled with OpenAL support : no
-- MediaPlayer will be compiled with PortAudio support  : no
-- MediaPlayer will be compiled with PulseAudio support : no
-- MediaPlayer will be compiled with OpenSLES support   : no
-- MediaPlayer will be compiled with VaAPI support  : no
-- MediaPlayer will be compiled with X11 support: no
-- MediaPlayer will be compiled with XV support : no
-- MediaPlayer will be compiled with OpenGL support : yes
-- MediaPlayer will be compiled with OpenGL-EGL support : no
-- MediaPlayer will be compiled with GDI+ support   : no
-- MediaPlayer will be compiled with Direct3D11 support : yes
-- MediaPlayer will be compiled with DirectSound support: no
-- MediaPlayer will be compiled with XAudio2 support: no
-- MediaPlayer will be compiled with Direct2D support   : yes
-- MediaPlayer libraries  :
E:/dk/x64-windows/lib/avcodec.lib;E:/dk/x64-windows/lib/avdevice.lib;E:/dk/x64-windows/lib/avfilter.lib;E:/dk/x64-windows/lib/avformat.lib;E:/dk/x64-windows/lib/avutil.lib;E:/dk/x64-windows/lib/swscale.lib;E:/dk/x64-windows/lib/swresample.lib;opengl32;glu32;Qt6::OpenGL;Qt6::OpenGLWidgets;d3dcompiler;d3d11;dxgi;dxguid;C:/Program
Files (x86)/Windows Kits/10/Lib/10.0.22621.0/um/x64/d2d1.lib;C:/Program Files
(x86)/Windows Kits/10/Lib/10.0.22621.0/um/x64/dwrite.lib
-- MediaPlayer definitions:
-D__STDC_CONSTANT_MACROS;-DQTAV_HAVE_CAPI=1;-DQTAV_HAVE_VDA=0;-DAUTO_REGISTER=0;-DFF_API_OLD_MSMPEG4=0;-DFF_API_AC_VLC=0;-DQTAV_HAVE_SSE4_1=0;-DQTAV_HAVE_SSE2=1;-DQTAV_HAVE_DXVA=1;-DQTAV_HAVE_LIBASS=0;-DQTAV_HAVE_GL=0;-DQTAV_HAVE_X11=0;-DQTAV_HAVE_XV=0;-DQTAV_HAVE_OPENAL=0;-DQTAV_HAVE_PORTAUDIO=0;-DQTAV_HAVE_PULSEAUDIO=0;-DQTAV_HAVE_OPENSL=0;-DQTAV_HAVE_D3D11VA=1;-DQTAV_HAVE_XAUDIO2=0;-DQTAV_HAVE_DSOUND=0;-DQTAV_HAVE_GDIPLUS=0;-DQTAV_HAVE_DIRECT2D=1;-DQTAV_HAVE_SWR_AVR_MAP=0;-DQTAV_HAVE_VIDEOTOOLBOX=0;-DQTAV_HAVE_DLLAPI_CUDA=0;-DQTAV_HAVE_CUDA=1;-DQTAV_HAVE_AVCODEC=1;-DQTAV_HAVE_AVDEVICE=1;-DQTAV_HAVE_AVFILTER=1;-DQTAV_HAVE_AVUTIL=1;-DQTAV_HAVE_SWSCALE=1;-DQTAV_HAVE_SWRESAMPLE=1;-DQTAV_HAVE_AVRESAMPLE=0;-DQTAV_HAVE_EGL_CAPI=0;-DQTAV_HAVE_VAAPI=0
-- MediaPlayer flags  :

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

[kwin] [Bug 475322] A GPU reset (amdgpu) causes Xwayland to hang kwin if an app interacts with X11

2023-11-01 Thread Peter Eszlari

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

Peter Eszlari  changed:

   What|Removed |Added

 CC||peter.eszl...@gmail.com

--- Comment #2 from Peter Eszlari  ---
I don't know if this makes a difference, but note that Mesa 23.2.1 lacks an AMD
GPU reset fix:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25023

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

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

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

m...@mwsys.mine.bz changed:

   What|Removed |Added

 CC||m...@mwsys.mine.bz

--- Comment #10 from m...@mwsys.mine.bz ---
wow, the bug kio not handling btrfs is old..
The only thing that made me notice that a kdevelop crash triggered by a new
method isOnCifs that could not handle "not found" mountpoints, the very same
root cause of this issue..

anyhow https://invent.kde.org/frameworks/kio/-/merge_requests/1422 would
implement btrfs handling:
"subvolume-less" roots and explicitly mounted subvolumes are straight forward.
What I also do is search for implicitly mounted subvolume "roots" and return
that as mountpoint, so cross mountpoint moves should not occur

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

[Merkuro] [Bug 476401] New: Kalendarac notifications no longer direct towards event

2023-11-01 Thread Naxdy

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

Bug ID: 476401
   Summary: Kalendarac notifications no longer direct towards
event
Classification: Applications
   Product: Merkuro
   Version: 23.08.2
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: xna...@hydra-development.net
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Since the rebrand from "Kalendar" to "Merkuro", kalendarac no longer functions
when directly clicking on a reminder notification (i.e. invoking its default
behavior). Previously it would open Kalendar if not already opened, and if
already opened, it would redirect to the event that produced the notification.


STEPS TO REPRODUCE
1. Create an event in Merkuro with a reminder
2. Wait for the reminder to occur
3. Click on the reminder notification to invoke its default behavior

OBSERVED RESULT
The notification disappears, but nothing else happens.

EXPECTED RESULT
Merkuro opens if not already open. If already open, Merkuro navigates to the
event belonging to the notification

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
-

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

[dolphin] [Bug 476402] New: Change-Date of copied file is wrong

2023-11-01 Thread H.H.

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

Bug ID: 476402
   Summary: Change-Date of copied file is wrong
Classification: Applications
   Product: dolphin
   Version: 21.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cyberb...@gmx.de
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

When I copy a local file to a sftp destination, only its displayed change-date
is used for the destination, not its real change-date.

STEPS TO REPRODUCE
1. have a local file /path/to/file
2. overwrite the file with a new version from another program than dolphin
(change date in dolphin is not always automatically refreshed, that may be a
separate problem, but seems related)
3. copy file to a sftp destination (other destinations may also work)
4. the old displayed change date is used for the destination file

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

[kmail2] [Bug 476403] New: Mail Preview is completely white

2023-11-01 Thread Thorben Kaufmann

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

Bug ID: 476403
   Summary: Mail Preview is completely white
Classification: Applications
   Product: kmail2
   Version: 5.24.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: i...@itc-kaufmann.de
  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. start setup KMAIL
2. go to inbox and select any mail
3. Preview is opened already

OBSERVED RESULT
preview is completely white in plain and html mode. No text to mark or copy

EXPECTED RESULT
preview would display mail content

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.8-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2

ADDITIONAL INFORMATION

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

[kate] [Bug 443543] Unicode/XCompose input characters doesn't work

2023-11-01 Thread Jan Rathmann

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

Jan Rathmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||jan.rathm...@gmx.de

--- Comment #1 from Jan Rathmann  ---


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

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

[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755

2023-11-01 Thread Jan Rathmann

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

Jan Rathmann  changed:

   What|Removed |Added

 CC||ekotekbi...@gmail.com

--- Comment #25 from Jan Rathmann  ---
*** Bug 443543 has been marked as a duplicate of this bug. ***

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

[lokalize] [Bug 474685] Ctrl+Alt+B in lokalize no longer works

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

Freek de Kruijf  changed:

   What|Removed |Added

Version|23.08.1 |22.08.2

--- Comment #7 from Freek de Kruijf  ---
Still present in version 22.08.2 in openSUSE Tumbleweed

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

[lokalize] [Bug 432238] Crash van lokalize after pressing ++

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

Freek de Kruijf  changed:

   What|Removed |Added

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

--- Comment #1 from Freek de Kruijf  ---
Apparently fixed

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

[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755

2023-11-01 Thread Jan Rathmann

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

Jan Rathmann  changed:

   What|Removed |Added

 CC||jan.rathm...@gmx.de
 Status|RESOLVED|REOPENED
 Resolution|UPSTREAM|---

--- Comment #26 from Jan Rathmann  ---
Reopening.
Verified that entering unicode chars (in Kate) still doesn't work currently on
Kubunu 23.10 (Plasma 5.27.8) and Neon Unstable (Plasma 6).

If it is not on Qt's side to implement this (as Christoph tells in #22), which
component would be correct to assign this bug?

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

[i18n] [Bug 457236] Dutch translation of "Adaptive" in plasma_shell_org.kde.plasma.desktop.pot isn't ideal

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Freek de Kruijf  ---
Changed the translation from "aanpasbaar" in "adaptief" of "adaptieve".

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

[lokalize] [Bug 476040] crash when changing a plural from fuzzy to ok

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

Freek de Kruijf  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1

--- Comment #4 from Freek de Kruijf  ---
See new DrKonqi report.

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

[yakuake] [Bug 476404] New: Fill journalctl with more than 100 messages per second

2023-11-01 Thread a

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

Bug ID: 476404
Summary: Fill journalctl with more than 100 messages per second
Classification: Applications
Product: yakuake
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: h...@kde.org
Reporter: pingo-po...@hotmail.fr
Target Milestone: ---

I'm okay with Yakuake reporting things. But whatever the problem it could be,
it can't fall in a loop sending messages to journals without any kind of
temporization. For example it should pause 1 second every time before sending
anything to journal. Whatever the problem it could complain about. Ideally it
would report only one time per execution about one precise problem. So 10
problems = no more than 10 message in the whole process life

For now I should lack something and it seems to want badly that thing (without
actually needing it but anyway), so it literally spam numbers that I can't even
count, it's more than the buffer can support. But sometime its 100 per second,
sometimes more than 500 per second (can't count more). And it's constant across
whole life of the process whatever you do or not with it. Message is `dpi is
invalid got from xsettings(Qt/DPI/ and Xft/DPI), fallback to get dpi from
QXcbScreen::logicalDpi()`

I repeat. I don't search to correct the actual problem but to limit yakuake
message throughput whatever the problem it experiences

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

OBSERVED RESULT

EXPECTED RESULT

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

ADDITIONAL INFORMATION

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

[yakuake] [Bug 476404] Fill journalctl with more than 100 messages per second

2023-11-01 Thread a

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

a  changed:

   What|Removed |Added

 CC||pingo-po...@hotmail.fr

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

[krita] [Bug 476405] New: Focus does not shift from layer blend mode dropdown until canvas interaction

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

Bug ID: 476405
   Summary: Focus does not shift from layer blend mode dropdown
until canvas interaction
Classification: Applications
   Product: krita
   Version: 5.2.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: rebuilders...@gmail.com
  Target Milestone: ---

SUMMARY
When selecting a blend mode for a layer in the layer docker, the focus remains
on the blendmode selection dropdown until the user interacts with the canvas.
This means that if the user has bound keyboard shortcuts to alphabet keys and
uses them before interacting with the canvas, they will inadvertently change
the blending mode of the layer they are working on.

For example, I have "brush size" bound to "s". This means that almost every
time I select a new layer blend mode, I end up setting the layer to
"saturation" since the first thing I do when I start painting on a layer is to
check my brush size.

STEPS TO REPRODUCE
1. set a layer's blend mode to any blend mode you wish
2. move cursor over the canvas
3. press a shortcut key like 's'.

OBSERVED RESULT
The layer blending mode changes 

EXPECTED RESULT
The blending mode should not change



ADDITIONAL INFORMATION
Ideally, I think focus should shift away from the blendmode selection box as
soon as the cursor is over the canvas. If this can't be done reliably and
quickly (IIRC there is some delay for focus shifting), I at least would prefer
not having the blendmode shortcuts at all, so maybe an option for that.

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

[plasmashell] [Bug 351175] "Auto-Hide" mode does not work when panel is on an edge between two screens

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

--- Comment #66 from Lassi Väätämöinen  ---
(In reply to Uwe Dippel from comment #65)
> It was mentioned to be fixed in Plasma 6. For Plasma 5 the bug is confirmed. 

The previous version that confirmed this for Plasma 5 was:

(In reply to Sergio from comment #18)
> Still an issue as of:
> 
> Operating System: Kubuntu 20.04
> KDE Plasma Version: 5.18.5


> Or is it anything else that you wanted to say?

I was stating that it is still valid at version 5.27.

If there are no intentions on fixing this for Plasma 5, maybe this deserves
some other status than CONFIRMED.

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

[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755

2023-11-01 Thread Bug Janitor Service

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

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |HI

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

[KPipeWire] [Bug 473483] KPipeWire-based Task Manager window previews are blank on Wayland with Nouveau drivers

2023-11-01 Thread Edoardo Lolletti

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

--- Comment #19 from Edoardo Lolletti  ---
Recent versions seems to have fixed it, tho now it broke on my desktop with an
amd RX570

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

[kactivitymanagerd] [Bug 476406] New: Switching between Activities very slow (background takes a second to refresh)

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

Bug ID: 476406
   Summary: Switching between Activities very slow (background
takes a second to refresh)
Classification: Plasma
   Product: kactivitymanagerd
   Version: 5.27.9
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: pi...@gmx.de
CC: plasma-b...@kde.org
  Target Milestone: ---

I have two activities A and B with different backgrounds to tell myself where I
am. When I switch my activities from A to B, the activity switches pretty fast
but the background takes 1 or 2 seconds to refresh.

This is not very smooth when using (or even presenting) this activity feature
in KDE.

Idea: Maybe you can preload all backgrounds and just switch it faster? I don't
know the implementation facts...

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

[kate] [Bug 462821] Replace... dialog's replace all with "alt+a" doesn't replace anything while button does

2023-11-01 Thread remipch

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

remipch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||kde.r...@proton.me
 Status|REPORTED|CONFIRMED

--- Comment #1 from remipch  ---
Hi!

Kate is also my favorite text editor for years :-)

I am able to reproduce this issue on Kate version 23.11.70 and version 23.03.70

On my side, the problem comes from a conflict between multiple buttons sharing
the same accelerator key :
- Alt+A correctly triggers "Replace all" action when no other button have Alt+A
as its accelerator key.
- Alt+A does not work when the "Search & Replace" plugin toolbar is also
visible, the "Search" button has the same Alt+A accelerator key.

I agree that shortcuts could be a good solution :
- they can be configured by users according to their needs
- conflicts are detected (a popup "Ambiguous shortcut detected" indicates what
to do to solve it)

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

[krita] [Bug 468082] Vanishing Point assistant doesn't follow canvas rotation

2023-11-01 Thread Rebecca Breu

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

Rebecca Breu  changed:

   What|Removed |Added

 CC||rebe...@rbreu.de

--- Comment #4 from Rebecca Breu  ---
Yeah, I also just stumbled upon this behaviour with the 5.2 appimage. All other
assistants draw their lines according to the coordinate system of the canvas,
while the single vanishing point seems to use the screen coordinate system for
its radial lines instead. This is not very intuitive, imo, and it gets pretty
confusing when the VP's center is way off to the canvas rotation origin, since
the VP's center itself of course does rotate with the canvas. It gives the
optical illusion of the VP's radial lines rotating the opposite direction.

https://youtu.be/M3NkDaK-wK8

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

[kmail2] [Bug 476407] New: Configuring the connection to the MS Exchange server

2023-11-01 Thread Dmitry Litvinov

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

Bug ID: 476407
   Summary: Configuring the connection to the MS Exchange server
Classification: Applications
   Product: kmail2
   Version: 5.24.2
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: config dialog
  Assignee: kdepim-b...@kde.org
  Reporter: dima_17_h...@mail.ru
  Target Milestone: ---

SUMMARY
***
NOTE: Configuring the connection to the MS Exchange server. The certificate
cannot be accepted. There is no response to pressing "Forever", "only for the
current session", "Cancel", "Close".
***
Video in the attachment.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 12
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[kmail2] [Bug 476407] Configuring the connection to the MS Exchange server

2023-11-01 Thread Dmitry Litvinov

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

Dmitry Litvinov  changed:

   What|Removed |Added

 CC||dima_17_h...@mail.ru

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

[krita] [Bug 468082] Vanishing Point assistant doesn't follow canvas rotation

2023-11-01 Thread wolthera

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

wolthera  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #5 from wolthera  ---
ah, I see my problem: If you use the shortcuts to rotate, it rotates 15°, which
makes it 'snap' to the default radial line count. I can confirm when using
shift+pan.

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

[kate] [Bug 476408] New: "Show Non-Printable Spaces" does not show Tabs and Spaces.

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

Bug ID: 476408
   Summary: "Show Non-Printable Spaces" does not show Tabs and
Spaces.
Classification: Applications
   Product: kate
   Version: 22.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: mad.cat@gmail.com
  Target Milestone: ---

SUMMARY
***
Whitespaces are not displayed when "Show Non-Printable Spaces" is ON
***


STEPS TO REPRODUCE
1. Open a new tab
2. Type some text with tabs and spaces
3. Toggle "Show Non-Printable Spaces" on

OBSERVED RESULT
Whitespaces are not displayed

EXPECTED RESULT
Whitespaces are displayed

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian 12
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Reproducible on Kate 23.08.2, Windows 10

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

[digikam] [Bug 476397] Trash status not update if you use the context menu to delete

2023-11-01 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
I can't reproduce the issue here with my current developer version and
AppImage.

Maik

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

[digikam] [Bug 476397] Trash status not update if you use the context menu to delete

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

--- Comment #3 from Peter  ---
Tested in: digiKam-8.2.0-20231029T182058-x86-64.appimage

The error only occurs when deleting more than one image in the trash.

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

[dolphin] [Bug 469316] With multiple tabs, closing split view doesn't update tab name

2023-11-01 Thread medin

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

medin  changed:

   What|Removed |Added

 CC||med.medin.2...@gmail.com

--- Comment #1 from medin  ---
Confirm it on Manjaro 

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.5.9-1-MANJARO (64-bit)
Graphics Platform: Wayland

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

[kalzium] [Bug 476409] New: Kalzium Crashes After Clicking Molecule Editor

2023-11-01 Thread nick

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

Bug ID: 476409
   Summary: Kalzium Crashes After Clicking Molecule Editor
Classification: Applications
   Product: kalzium
   Version: 22.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kalz...@kde.org
  Reporter: salo.pr...@gmail.com
  Target Milestone: ---

Application: kalzium (22.12.3)

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

-- Information about the crash:
When i click on the "Molecule Editor" button, the Kalzium application crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Kalzium (kalzium), signal: Aborted

   PID: 101013 (kalzium)
   UID: 1000 (nick)
   GID: 1000 (nick)
Signal: 6 (ABRT)
 Timestamp: Wed 2023-11-01 04:54:08 PDT (21s ago)
  Command Line: /usr/bin/kalzium
Executable: /usr/bin/kalzium
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fkalzium-7af3a2bae58b439fa7499802bc743c46.scope
  Unit: user@1000.service
 User Unit:
app-\x2fusr\x2fbin\x2fkalzium-7af3a2bae58b439fa7499802bc743c46.scope
 Slice: user-1000.slice
 Owner UID: 1000 (nick)
   Boot ID: 99813076a52e4f6cb9abf5fc2f92680a
Machine ID: f4b7c67cfbce4b70b84a3f1ee0412c92
  Hostname: Pro
   Storage:
/var/lib/systemd/coredump/core.kalzium.1000.99813076a52e4f6cb9abf5fc2f92680a.101013.169883964800.zst
(present)
  Size on Disk: 8.2M
   Message: Process 101013 (kalzium) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64
Stack trace of thread 101013:
#0  0x7fde31ea9d3c n/a (libc.so.6 + 0x8ad3c)
#1  0x7fde31e5af32 raise (libc.so.6 + 0x3bf32)
#2  0x7fde309b583d _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x583d)
#3  0x7fde31e5afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7fde31ea9d3c n/a (libc.so.6 + 0x8ad3c)
#5  0x7fde31e5af32 raise (libc.so.6 + 0x3bf32)
#6  0x7fde31e45472 abort (libc.so.6 + 0x26472)
#7  0x7fde31e45395 n/a (libc.so.6 + 0x26395)
#8  0x7fde31e53e32 __assert_fail (libc.so.6 + 0x34e32)
#9  0x7fde33895a83
_ZN8Avogadro4Core12LayerManager10layerCountEv (libAvogadroCore.so.1 + 0x8da83)
#10 0x7fde3475f8fe n/a (libAvogadroQtPlugins.so.1 +
0x15f8fe)
#11 0x7fde322e8f7c n/a (libQt5Core.so.5 + 0x2e8f7c)
#12 0x7fde347627a3 n/a (libAvogadroQtPlugins.so.1 +
0x1627a3)
#13 0x7fde322e8f7c n/a (libQt5Core.so.5 + 0x2e8f7c)
#14 0x7fde33066891 _ZN9QComboBox19currentIndexChangedEi
(libQt5Widgets.so.5 + 0x266891)
#15 0x7fde33068052 n/a (libQt5Widgets.so.5 + 0x268052)
#16 0x7fde3306b8cb n/a (libQt5Widgets.so.5 + 0x26b8cb)
#17 0x7fde3306bc6f _ZN9QComboBox15setCurrentIndexEi
(libQt5Widgets.so.5 + 0x26bc6f)
#18 0x7fde322e8f7c n/a (libQt5Core.so.5 + 0x2e8f7c)
#19 0x7fde3224bd5e
_ZN18QAbstractItemModel12rowsInsertedERK11QModelIndexiiNS_14QPrivateSignalE
(libQt5Core.so.5 + 0x24bd5e)
#20 0x7fde3225445a _ZN18QAbstractItemModel13endInsertRowsEv
(libQt5Core.so.5 + 0x25445a)
#21 0x7fde32b2185e n/a (libQt5Gui.so.5 + 0x52185e)
#22 0x7fde3306fff7
_ZN9QComboBox10insertItemEiRK5QIconRK7QStringRK8QVariant (libQt5Widgets.so.5 +
0x26fff7)
#23 0x7fde34761be2 n/a (libAvogadroQtPlugins.so.1 +
0x161be2)
#24 0x7fde3491b4d3
_ZN8Avogadro8QtOpenGL8GLWidget11setMoleculeEPNS_5QtGui8MoleculeE
(libAvogadroQtOpenGL.so.1 + 0x74d3)
#25 0x55fc7ec8be19 _ZN15KalziumGLWidgetC2EP7QWidget
(kalzium + 0x94e19)
#26 0x55fc7ec89f0b n/a (kalzium + 0x92f0b)
#27 0x55fc7ec8804f n/a (kalzium + 0x9104f)
#28 0x55fc7ecd001c n/a (kalzium + 0xd901c)
#29 0x7fde322e8f4f n/a (libQt5Core.so.5 + 0x2e8f4f)
#30 0x7fde32f5c782 _ZN7QAction9triggeredEb
(libQt5Widgets.so.5 + 0x15c782)
#31 0x7fde32f5f3ab _ZN7QAction8activateENS_11ActionEventE
(libQt5Widgets.so.5 + 0x15f3ab)
#32 0x7fde33056e8a n/a (libQt5Widgets.so.5 + 0x256e8a)
#33 0x7fde33056fd7
_ZN15QAbstractButton17mouseReleaseEventEP11QMouseEvent (libQt5Widgets.so.5 +
0x256fd7)

[digikam] [Bug 476397] Trash status not update if you use the context menu to delete

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

--- Comment #4 from Peter  ---
If digiKam's main window loses and then regains focus, the trash icon is also
updated and correctly shows the empty state.
If you resize digiKam's main window, the correct status (empty) will be
displayed.
If you click on the empty area after deletion in the middle of the digiKam
window, the trash can icon will refresh and show the empty value.

After deleting multiple items, the trash can icon does not refresh, you have to
click somewhere.

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

[krita] [Bug 476300] Brush outline not fully rendered on cursor movement

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

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

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

[krita] [Bug 440399] Focus between UI elements and canvas doesn't switch properly, often leading to clashing functionality of hotkeys

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

Summary|Focus between UI elements   |Focus between UI elements
   |and canvas doesn't switch   |and canvas doesn't switch
   |fast enough, often leading  |properly, often leading to
   |to clashing functionality   |clashing functionality of
   |of hotkeys  |hotkeys

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

[kalzium] [Bug 476409] Kalzium Crashes After Clicking Molecule Editor

2023-11-01 Thread Antonio Rojas

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

Antonio Rojas  changed:

   What|Removed |Added

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

--- Comment #1 from Antonio Rojas  ---


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

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

[kalzium] [Bug 457191] Kalzium crashes after clicking the Molecular Editor button

2023-11-01 Thread Antonio Rojas

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||salo.pr...@gmail.com

--- Comment #7 from Antonio Rojas  ---
*** Bug 476409 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 476405] Focus does not shift from layer blend mode dropdown until canvas interaction

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||tomtomtomreportingin@gmail.
   ||com

--- Comment #1 from tomtomtomreportin...@gmail.com ---


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

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

[krita] [Bug 440399] Focus between UI elements and canvas doesn't switch properly, often leading to clashing functionality of hotkeys

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

--- Comment #13 from tomtomtomreportin...@gmail.com ---
*** Bug 476405 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 440399] Focus between UI elements and canvas doesn't switch properly, often leading to clashing functionality of hotkeys

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

--- Comment #14 from tomtomtomreportin...@gmail.com ---
The above report brings up the case of the layer blending mode dropdown, which
I often find to be very annoying. Generally after I press space after selecting
a new blending mode, it will open the dropdown again, instead of panning the
canvas.

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

[neon] [Bug 476410] New: Packages have unmet dependencies building poppler in PIM image

2023-11-01 Thread Gert Oja

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

Bug ID: 476410
   Summary: Packages have unmet dependencies building poppler in
PIM image
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages Unstable Edition
  Assignee: neon-b...@kde.org
  Reporter: ge...@pm.me
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 162791
  --> https://bugs.kde.org/attachment.cgi?id=162791&action=edit
output of "apt list --installed"

SUMMARY
Running `apt build-dep poppler` gives the following error message:
```
The following packages have unmet dependencies:
 libharfbuzz-dev : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3.1) but
6.0.0+dfsg-3+22.04+jammy+unstable+build2 is to be installed
E: Unable to correct problems, you have held broken packages.
```
CMake error log provides this:
```
-- Could NOT find TIFF (missing: TIFF_LIBRARY TIFF_INCLUDE_DIR) (Required is at
least version "4.1")
CMake Error at CMakeLists.txt:162 (MESSAGE):
  Could not find the 4.1 version of TIFF.  If you're not interested in the
  features it provides set the cmake ENABLE_LIBTIFF option to OFF
Call Stack (most recent call first):
  CMakeLists.txt:169 (find_soft_mandatory_package)

-- Configuring incomplete, errors occurred!

```

STEPS TO REPRODUCE
1. Set up KDE PIM Docker image and ./run.sh as instructed on
https://community.kde.org/KDE_PIM/Docker
2. Install build-deps for kmail
3. Attempt to build pim

OBSERVED RESULT
Above error message.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon unstable
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.111.0
Qt Version: 6.6.0

ADDITIONAL INFORMATION

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

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

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

--- Comment #11 from m...@mwsys.mine.bz ---
(In reply to mike from comment #10)
> wow, the bug kio not handling btrfs is old..
> The only thing that made me notice that a kdevelop crash triggered by a new
> method isOnCifs that could not handle "not found" mountpoints, the very same
> root cause of this issue..
> 
> anyhow https://invent.kde.org/frameworks/kio/-/merge_requests/1422 would
> implement btrfs handling:
> "subvolume-less" roots and explicitly mounted subvolumes are straight
> forward.
> What I also do is search for implicitly mounted subvolume "roots" and return
> that as mountpoint, so cross mountpoint moves should not occur

I have good and bad news for you:
with the MR above the .Trash-$UID directory is created (if permissions allow of
course).
It seems that when the file is moved to the trash the solid framework is used
to find the "storage media". That has no idea what to do with subvolumes of any
kind. It would be probably possible for solid to find every explicitly mounted
subvolume, but enumerating every subvolume is simply not possible, so this will
never fully work is the "move to trash" is based on solid.

The simplest case (external btrfs, only one subvolume mounted) works. Put
simply: if you see a drive icon in dolpin, exactly that subvolume will work,
every other will land in .local/share... even though the .Trash-$UID
directories are created

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

[kmail2] [Bug 476411] New: KMail crashes after removing SMTP accounts

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

Bug ID: 476411
   Summary: KMail crashes after removing SMTP accounts
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: k...@trummer.xyz
  Target Milestone: ---

Application: kmail (5.24.2 (23.08.2))

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.5.8-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
When removing multiple SMTP accounts at once, KMail crashes.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x7f9e6b8f4f70 in
MailTransport::TransportManagementWidgetPrivate::removeClicked()
(this=) at
/usr/src/debug/kmailtransport-23.08.2/src/kmailtransport/widgets/transportmanagementwidget.cpp:146
#5  0x7f9e6d325442 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff21f94e30, r=0x562c46285b70, this=0x562c462e7a50) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#6  doActivate(QObject*, int, void**) (sender=0x562c462839a0,
signal_index=9, argv=0x7fff21f94e30) at kernel/qobject.cpp:3925
#7  0x7f9e6d31e0af in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x562c462839a0, m=m@entry=0x7f9e6e4c0280
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff21f94e30)
at kernel/qobject.cpp:3985
#8  0x7f9e6e096ae2 in QAbstractButton::clicked(bool)
(this=this@entry=0x562c462839a0, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#9  0x7f9e6e096d4a in QAbstractButtonPrivate::emitClicked()
(this=0x562c462839e0) at widgets/qabstractbutton.cpp:416
#10 0x7f9e6e098587 in QAbstractButtonPrivate::click() (this=0x562c462839e0)
at widgets/qabstractbutton.cpp:409
#11 0x7f9e6e098797 in QAbstractButton::mouseReleaseEvent(QMouseEvent*)
(this=0x562c462839a0, e=0x7fff21f953c0) at widgets/qabstractbutton.cpp:1045
#12 0x7f9e6dfe6d58 in QWidget::event(QEvent*) (this=0x562c462839a0,
event=0x7fff21f953c0) at kernel/qwidget.cpp:9045
#13 0x7f9e6dfa519e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x562c3c338f50, receiver=receiver@entry=0x562c462839a0,
e=e@entry=0x7fff21f953c0) at kernel/qapplication.cpp:3640
#14 0x7f9e6dfad5cf in QApplication::notify(QObject*, QEvent*)
(this=, receiver=, e=0x7fff21f953c0) at
kernel/qapplication.cpp:3084
#15 0x7f9e6d2ed198 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x562c462839a0, event=0x7fff21f953c0) at
kernel/qcoreapplication.cpp:1064
#16 0x7f9e6d2ed36e in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#17 0x7f9e6dfab92e in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool)
(receiver=receiver@entry=0x562c462839a0, event=event@entry=0x7fff21f953c0,
alienWidget=, nativeWidget=0x562c41e50ce0,
buttonDown=buttonDown@entry=0x7f9e6e4f2330 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2622
#18 0x7f9e6dfff7ed in QWidgetWindow::handleMouseEvent(QMouseEvent*)
(this=this@entry=0x562c489d55a0, event=event@entry=0x7fff21f95670) at
kernel/qwidgetwindow.cpp:684
#19 0x7f9e6e002d0f in QWidgetWindow::event(QEvent*) (this=0x562c489d55a0,
event=0x7fff21f95670) at kernel/qwidgetwindow.cpp:300
#20 0x7f9e6dfa519e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x562c489d55a0, e=0x7fff21f95670) at
kernel/qapplication.cpp:3640
#21 0x7f9e6d2ed198 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x562c489d55a0, event=0x7fff21f95670) at
kernel/qcoreapplication.cpp:1064
#22 0x7f9e6d2ed36e in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#23 0x7f9e6d77d0db in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
(e=0x562c4588daa0) at kernel/qguiapplication.cpp:2285
#24 0x7f9e6d75038c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#25 0x7f9e5eaf854a in xcbSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at qxcbeventdispatcher.cpp:105
#26 0x7f9e69124ef0 in  () at /lib64/libglib-2.0.so.0
#27 0x7f9e69126b18 in  () at /lib64/libglib-2.0.so.0
#28 0x7f9e691271cc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#29 0x7f9e6d3460d6 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x562c3c417480, flags=...) at kernel/qeventdispatcher_glib

[neon] [Bug 476410] Packages have unmet dependencies building poppler in PIM image

2023-11-01 Thread Bug Janitor Service

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

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kwin] [Bug 476306] KWin5 crashes when Subnautica from Steam disables Fullscreen mode.

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from David Edmundson  ---


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

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

[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing

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

David Edmundson  changed:

   What|Removed |Added

 CC||rvdois+RVU4Z9@rokejulianloc
   ||khart.anonaddy.com

--- Comment #20 from David Edmundson  ---
*** Bug 476306 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 472729] The brush preview outline, unlike the brush cursor, repositions with the canvas when using rotate hotkeys

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

Summary|The brush preview outline,  |The brush preview outline,
   |unlike the brush cursor,|unlike the brush cursor,
   |rotates with the canvas |repositions with the canvas
   |when using rotate hotkeys   |when using rotate hotkeys

--- Comment #2 from tomtomtomreportin...@gmail.com ---
Yes, the reposition aspect is what I meant to be the distracting part, rather
than rotation. Slightly changed the title to reflect that. It's distracting in
the sense that it can change my impression of the artwork to have this random
"speck" in a place that I don't expect.

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

[kwin] [Bug 476412] New: Display freezes when reconnecting to Lenovo Thunderbolt 4 dock

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

Bug ID: 476412
   Summary: Display freezes when reconnecting to Lenovo
Thunderbolt 4 dock
Classification: Plasma
   Product: kwin
   Version: git-stable-Plasma/5.27
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lassi.vaatamoi...@gmail.com
  Target Milestone: ---

Created attachment 162792
  --> https://bugs.kde.org/attachment.cgi?id=162792&action=edit
Log from the dock connect - disconnect - reconnect - REISUB-boot

SUMMARY
When disconnecting Lenovo P15 Gen2 laptop from the dock and reconnecting, the
internal display freezes and the only way to rememdy is either a Alt + SysReq +
"REISUB", or a hard reset.  


STEPS TO REPRODUCE
1. Setup Lenovo TB4 Dock with two displays (DP + USB-C as the only working
combination..) 
2. Connect Lenovo P15 laptop, observe two external displays working properly
3. Disconnect from dock
4. Reconnect to dock

OBSERVED RESULT
Nothing displayed on external displays, laptop internal display frozen
Sometimes this  happens already when disconnecting from the dock (step 3.)

EXPECTED RESULT
External displays should work properly, as they did in the first dock
connection. Disconnecting once more and the  internal display should work.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.2.0-33-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i7-11850H @ 2.50GHz
Memory: 46,7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 20YRS21300
System Version: ThinkPad P15 Gen 2i

ADDITIONAL INFORMATION
NVIDIA Driver Version: 535.113.01

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

[kwin] [Bug 476102] [Wayland] Downscaled X11 Windows Look Blocky/Blurry

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 CC||k...@davidedmundson.co.uk
 Status|REPORTED|RESOLVED

--- Comment #1 from David Edmundson  ---
 It's unrelated to being fractional. With apply scaling themselves, we pick one
display and use that scale for both screens. If that matches you get native
rendering. The other screen will be upscaled or downscaled. 

Mixed DPI on X11 was not ever supported and can't be added.

You can override which scale we use for X11, there's also the workraround of
running apps in gamescope to fix the scaling issues.
There's not much else we can do unfortunately. Sorry

>  - A similar issue is also present on text in the Overview effect, on 
> displays with no scaling, text always appears pixelated.

That sounds unrelated, and fixable.

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

[kwin] [Bug 476413] New: Big black border around some GTK apps

2023-11-01 Thread Henning

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

Bug ID: 476413
   Summary: Big black border around some GTK apps
Classification: Plasma
   Product: kwin
   Version: 5.27.9
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: amanita+kdeb...@mailbox.org
  Target Milestone: ---

I posted an image here:
https://www.reddit.com/r/kde/comments/17j4i3s/black_border_around_gtk_app/

The app is a GTK4 (?) app as a Flatpak. In the KDE Flatpak settings, disabling
"direct graphic rendering" fixed that issue. 

--- Software ---
OS: Fedora Linux 38.20231030.0 (Kinoite)
KDE Plasma: 5.27.8
KDE Frameworks: 5.110.0
Qt: 5.15.10
Kernel: 6.5.8-200.fc38.x86_64
Compositor: wayland

--- Hardware ---
CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
RAM: 21.4 GB
GPU: AMD Radeon Vega 8 Graphics
Video memory: 2048MB

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

[kwin] [Bug 476413] Big black border around some GTK apps

2023-11-01 Thread Henning

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

--- Comment #1 from Henning  ---
This is the affected app: https://github.com/flattool/warehouse

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

[kwin] [Bug 476413] Big black border around some GTK apps

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REPORTED|RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #2 from David Edmundson  ---
Please report to GTK.

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

[kwin] [Bug 476412] Display freezes when reconnecting to Lenovo Thunderbolt 4 dock

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

--- Comment #1 from Lassi Väätämöinen  ---
Particularly annoying, when I need to daily disconnect the laptop from the dock
for meetings etc., and all work apps need to be reopened and setup.


Upon disconnect, there is a Wayland segfault, but I think at this point the
laptop internal display still works:

marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE)
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) Backtrace:
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 0: /usr/bin/Xwayland
(0x555e01857000+0x1651c9) [0x555e019bc1c9]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 1: /usr/bin/Xwayland
(0x555e01857000+0x1652d2) [0x555e019bc2d2]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 2:
/lib/x86_64-linux-gnu/libc.so.6 (0x7fd1f280+0x42520) [0x7fd1f2842520]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 3: /usr/bin/Xwayland
(0x555e01857000+0x39389) [0x555e01890389]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 4:
/lib/x86_64-linux-gnu/libffi.so.8 (0x7fd1f2ae6000+0x7e2e) [0x7fd1f2aede2e]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 5:
/lib/x86_64-linux-gnu/libffi.so.8 (0x7fd1f2ae6000+0x4493) [0x7fd1f2aea493]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 6:
/lib/x86_64-linux-gnu/libwayland-client.so.0 (0x7fd1f3059000+0x6b20)
[0x7fd1f305fb20]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 7:
/lib/x86_64-linux-gnu/libwayland-client.so.0 (0x7fd1f3059000+0x72c3)
[0x7fd1f30602c3]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 8:
/lib/x86_64-linux-gnu/libwayland-client.so.0
(wl_display_dispatch_queue_pending+0x7c) [0x7fd1f30604bc]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 9: /usr/bin/Xwayland
(0x555e01857000+0x3e4bb) [0x555e018954bb]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 10: /usr/bin/Xwayland
(0x555e01857000+0x166901) [0x555e019bd901]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 11: /usr/bin/Xwayland
(0x555e01857000+0xa6cb0) [0x555e018fdcb0]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 12: /usr/bin/Xwayland
(0x555e01857000+0x34c63) [0x555e0188bc63]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 13:
/lib/x86_64-linux-gnu/libc.so.6 (0x7fd1f280+0x29d90) [0x7fd1f2829d90]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 14:
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7fd1f2829e40]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) 15: /usr/bin/Xwayland
(0x555e01857000+0x36495) [0x555e0188d495]
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE)
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) Segmentation fault at
address 0x41
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE)
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: Fatal server error:
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE) Caught signal 11
(Segmentation fault). Server aborting
marras 01 14:02:50 mopo kwin_wayland_wrapper[2439]: (EE)
marras 01 14:02:50 mopo kded5[3065]: X connection to :1 broken (explicit kill
or server shutdown).
marras 01 14:02:50 mopo chrome[3422]: The X11 connection broke: I/O error (code
1) 

Around the time of the disconnec there is also a kernel oops, but not sure if
this is related:

marras 01 14:03:15 mopo kernel: BUG: kernel NULL pointer dereference, address:

marras 01 14:03:15 mopo kernel: #PF: supervisor read access in kernel mode
marras 01 14:03:15 mopo kernel: #PF: error_code(0x) - not-present page
marras 01 14:03:15 mopo kernel: PGD 0 P4D 0 
marras 01 14:03:15 mopo kernel: Oops:  [#1] PREEMPT SMP NOPTI
marras 01 14:03:15 mopo kernel: CPU: 11 PID: 1589 Comm: kworker/u32:11 Tainted:
P   O   6.2.0-33-generic #33~22.04.1-Ubuntu
marras 01 14:03:15 mopo kernel: Hardware name: LENOVO 20YRS21300/20YRS21300,
BIOS N37ET46W (1.27 ) 07/12/2023
marras 01 14:03:15 mopo kernel: Workqueue: USBC000:00-con1 ucsi_poll_worker
[typec_ucsi]
marras 01 14:03:15 mopo kernel: RIP: 0010:ucsi_acpi_async_write+0x31/0x60
[ucsi_acpi]
marras 01 14:03:15 mopo kernel: Code: 89 e5 41 56 49 89 ce 41 55 49 89 d5 41 54
53 89 f3 e8 73 8b 2a 00 4c 89 f2 4c 89 ee 89 df 48 03 78 10 49 89 c4 e8 7f 3c
cc d8 <49> 8b 45 00 4c 89 e7 be 01 00 00 00 49 89 44 24 50 e8 b9 fc ff ff
marras 01 14:03:15 mopo kernel: RSP: 0018:b685c2a37d10 EFLAGS: 00010282
marras 01 14:03:15 mopo kernel: RAX: b685c00f5002 RBX: 0002
RCX: 
marras 01 14:03:15 mopo kernel: RDX:  RSI: 
RDI: b685c00f5002
marras 01 14:03:15 mopo kernel: RBP: b685c2a37d30 R08: 
R09: 
marras 01 14:03:15 mopo kernel: R10:  R11: 
R12: a096c33074a8
marras 01 14:03:15 mopo kernel: R13:  R14: 
R15: 000c
marras 01 14:03:15 mopo kernel: FS:  ()
GS:a0a1ef6c() knlGS:
marras 01 14:0

[kwin] [Bug 476412] Display freezes when reconnecting to Lenovo Thunderbolt 4 dock

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

Lassi Väätämöinen  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[plasmashell] [Bug 469889] plasmashell leaks inotify file descriptor

2023-11-01 Thread Joshua Goins

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

Joshua Goins  changed:

   What|Removed |Added

 CC||j...@redstrate.com

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

[plasmashell] [Bug 469889] plasmashell leaks inotify file descriptor

2023-11-01 Thread Johannes Truschnigg

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

Johannes Truschnigg  changed:

   What|Removed |Added

 CC||johannes+kdebugs@truschnigg
   ||.info

--- Comment #2 from Johannes Truschnigg  ---
I can confirm this bug on both Debian 12 and Arch Linux, where it looks like
the following:


$ ls -l /proc/$$/fd/
total 0
lrwx-- 1 colo colo 64  1. Nov 13:37 0 -> /dev/pts/3
lrwx-- 1 colo colo 64  1. Nov 13:37 1 -> /dev/pts/3
lrwx-- 1 colo colo 64  1. Nov 13:37 2 -> /dev/pts/3
lr-x-- 1 colo colo 64  1. Nov 13:37 24 -> anon_inode:inotify
lrwx-- 1 colo colo 64  1. Nov 13:37 255 -> /dev/pts/3
$ pstree -s -p $$
systemd(1)───systemd(616)───plasmashell(754)───konsole(60566)───bash(60581)───pstree(61213)
$ ls -l /proc/60566/fd/24
lr-x-- 1 colo colo 64  1. Nov 14:02 /proc/60566/fd/24 -> anon_inode:inotify
$ ls -l /proc/754/fd/24
lr-x-- 1 colo colo 64  1. Nov 14:02 /proc/754/fd/24 -> anon_inode:inotify
$ sudo ls -l /proc/616/fd/24
lrwx-- 1 colo colo 64  1. Nov 14:03 /proc/616/fd/24 -> 'socket:[18811]'


I stumbled over this because the fd broke another project's test suite I was
running in my Konsole-spawned shell.

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

[kwin] [Bug 454354] nvidia: Java programs running in Plasma Wayland / Xwayland show massive flickering

2023-11-01 Thread Yaroslav Sidlovsky

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

Yaroslav Sidlovsky  changed:

   What|Removed |Added

 CC||zawer...@gmail.com

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

[plasmashell] [Bug 469889] plasmashell leaks inotify file descriptor

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

--- Comment #3 from David Edmundson  ---
I cannot reproduce on my Plasma 6 setup.

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

[krita] [Bug 476414] New: ときどきキャンバスが真っ暗になる。プレビューをみると、しっかり描けてはいるらしい

2023-11-01 Thread kaede

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

Bug ID: 476414
   Summary: ときどきキャンバスが真っ暗になる。プレビューをみると、しっかり描けてはいるらしい
Classification: Applications
   Product: krita
   Version: 5.2.0
  Platform: Compiled Sources
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: omisoomiso...@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. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: surfacelaptop Go2
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.

[krita] [Bug 476415] New: ときどきキャンバスが真っ暗になる。プレビューをみると、しっかり描けてはいるらしい

2023-11-01 Thread kaede

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

Bug ID: 476415
   Summary: ときどきキャンバスが真っ暗になる。プレビューをみると、しっかり描けてはいるらしい
Classification: Applications
   Product: krita
   Version: 5.2.0
  Platform: Compiled Sources
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: omisoomiso...@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. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: surfacelaptop Go2
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 469889] plasmashell leaks inotify file descriptor