[kwin] [Bug 443723] "Display geometry when moving or resizing" feature is missing

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||rybak@gmail.com

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

[neon] [Bug 487374] Missing icons

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||and...@amateescu.me

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

[dolphin] [Bug 432530] Files with long filename not behaving properly (name overflow)

[Andrei Rybak]

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

--- Comment #18 from Andrei Rybak  ---
*** Bug 470593 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 470593] Particularly named files show end of the filename outside the selection in "Icons view mode"

[Andrei Rybak]

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

--- Comment #2 from Andrei Rybak  ---


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

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

[dolphin] [Bug 432530] Files with long filename not behaving properly (name overflow)

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||rybak@gmail.com

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

[dolphin] [Bug 485558] New: Dolphin crash

[Andrei Tescula]

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

Bug ID: 485558
   Summary: Dolphin crash
Classification: Applications
   Product: dolphin
   Version: 24.02.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: atesc...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (24.02.2)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.5-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.3 [CoredumpBackend]

-- Information about the crash:
Dragging a file from dolphin, when reaching the location bar, crash happens

The crash can be reproduced every time.

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


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 6928]
[New LWP 6929]
[New LWP 6934]
[New LWP 6932]
[New LWP 6931]
[New LWP 6935]
[New LWP 6933]
[New LWP 6930]
[New LWP 6980]
[New LWP 6936]
[New LWP 6985]
[New LWP 6986]
[New LWP 6988]
[New LWP 9743]
[New LWP 9744]
[New LWP 10052]
[New LWP 10051]
[New LWP 10050]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/dolphin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x761b94aab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x761b8ef459c0 (LWP 6928))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x761b8ef459c0 (LWP 6928))]

Thread 18 (Thread 0x761b75e006c0 (LWP 10050)):
#0  0x761b94aa5ebe in ??? () at /usr/lib/libc.so.6
#1  0x761b94aa8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x761b952b8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x761b952b2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x761b952adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x761b94aa955a in ??? () at /usr/lib/libc.so.6
#6  0x761b94b26a3c in ??? () at /usr/lib/libc.so.6

Thread 17 (Thread 0x761b6cc006c0 (LWP 10051)):
#0  0x761b94aa5ebe in ??? () at /usr/lib/libc.so.6
#1  0x761b94aa8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x761b952b8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x761b952b2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x761b952adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x761b94aa955a in ??? () at /usr/lib/libc.so.6
#6  0x761b94b26a3c in ??? () at /usr/lib/libc.so.6

Thread 16 (Thread 0x761b57e006c0 (LWP 10052)):
#0  0x761b94aa5ebe in ??? () at /usr/lib/libc.so.6
#1  0x761b94aa8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x761b952b8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x761b952b2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x761b952adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x761b94aa955a in ??? () at /usr/lib/libc.so.6
#6  0x761b94b26a3c in ??? () at /usr/lib/libc.so.6

Thread 15 (Thread 0x761b74a006c0 (LWP 9744)):
#0  0x761b94aa5ebe in ??? () at /usr/lib/libc.so.6
#1  0x761b94aa8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x761b952b8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x761b952b2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x761b952adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x761b94aa955a in ??? () at /usr/lib/libc.so.6
#6  0x761b94b26a3c in ??? () at /usr/lib/libc.so.6

Thread 14 (Thread 0x761b754006c0 (LWP 9743)):
#0  0x761b94aa5ebe in ??? () at /usr/lib/libc.so.6
#1  0x761b94aa8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x761b952b8b24 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x761b952b2d52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x761b952adcd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x761b94aa955a in ??? () at /usr/lib/libc.so.6
#6  0x761b94b26a3c in ??? () at /usr/lib/libc.so.6

Thread 13 (Thread 0x761b60e006c0 (LWP 6988)):
#0  0x761b94b19616 in ppoll () at /usr/lib/libc.so.6
#1  0x761b952a6123 in qt_safe_poll(pollfd*, unsigned long, QDeadlineTimer)
() at /usr/lib/libQt6Core.so.6
#2  0x761b9434cc02 in ??? () at /usr/lib/libQt6Network.so.6
#3  0x761b942e04b3 in ??? () at /usr/lib/libQt6Network.so.6
#4  0x761b942d8789 in QAbstractSocket::waitForReadyRead(int) () at
/usr/lib/libQt6Network.so.6
#5  0x761b97208d8a in ??? () at 

[kwin] [Bug 478137] Desktop grid is not available as an option for screen edges/corners

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||rybak@gmail.com

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

[plasmashell] [Bug 481636] New: Custom date format doesn't respect regional settings

[Andrei Habalau]

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

Bug ID: 481636
   Summary: Custom date format doesn't respect regional settings
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: andreihaba...@gmail.com
  Target Milestone: 1.0

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. Set language to American English in the settings app
2. Set time format to anything else, in my case it's set to Romanian
3. Select custom date format in Digital clock settings ", dd  "

OBSERVED RESULT
Date format is set to English
ex: Wednesday, 21 February 2024

EXPECTED RESULT
Date format should respect the selected regional setting in the settings app.
ex: miercuri, 21 februarie 2024

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 40 Kinoite/6.0 RC2
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
All the other options (long date, short date) respect the regional settings,
just the custom date format is defaulting to english locale.

Not entirely sure if this any effect, but everything else in the regional
settings is set to Romanian except the language.

Output from localectl:
System Locale: LANG=en_GB.UTF-8
VC Keymap: us
   X11 Layout: us
X11 Model: pc105

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

[Discover] [Bug 481399] New: license message NO_PUBKEY when starting discover

[Andrei]

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

Bug ID: 481399
   Summary: license message NO_PUBKEY when starting discover
Classification: Applications
   Product: Discover
   Version: 5.27.10
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: ans...@yandex.ru
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
***

STEPS TO REPRODUCE
1. each time I start discover

OBSERVED RESULT
modal message appears:
W: Произошла ошибка при проверке подписи. Репозиторий не обновлён, и будут
использованы предыдущие индексные файлы. Ошибка GPG: https://repo.waydro.id
jammy InRelease: Следующие подписи не могут быть проверены, так как недоступен
открытый ключ: NO_PUBKEY 0E406D181DCEE19C
E: https://repo.waydro.id jammy InRelease is not (yet) available (Следующие
подписи не могут быть проверены, так как недоступен открытый ключ: NO_PUBKEY
0E406D181DCEE19C)


EXPECTED RESULT
started without the message

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

[krusader] [Bug 481169] Krusader crash (segmentation fault) when switching between KDE Desktops

[Andrei Korshikov]

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

Andrei Korshikov  changed:

   What|Removed |Added

Version|unspecified |Git
   Platform|Compiled Sources|Arch Linux

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

[krusader] [Bug 481169] New: Krusader crash (segmentation fault) when switching between KDE Desktops

[Andrei Korshikov]

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

Bug ID: 481169
   Summary: Krusader crash (segmentation fault) when switching
between KDE Desktops
Classification: Applications
   Product: krusader
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: andrej.s.korshi...@gmail.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.9.0-dev "Bleeding Edge" (gitrev: 681a8f03))

Qt Version: 5.15.12
Frameworks Version: 5.114.0
Operating System: Linux 6.7.0-zen3-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
I have four coufigured KDE desktops. When I use only one - I see no problems at
all.

When at least two desktops are in use, Krusader crashes intermittently.
Krusader crashes several times a day when:
a). I go from one desktop to another;
b). I start an application (for some reason, most problematic are Konsole and
Geequie) on another deskop, while Krusader is running on the first desktop.

I used Krusader 2.8.0, couple days ago I compiled from source (well, I've
installed krusader-git Arch Linux AUR package), still no luck.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x72559932fb7e in
QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at
/usr/lib/libQt5Core.so.5
#7  0x72559a9f9f62 in QWeakPointer::QWeakPointer
(ptr=0x62fc315ccb90, this=, this=,
ptr=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:685
#8  QPointer::QPointer (p=0x62fc315ccb90, this=,
this=, p=) at
/usr/include/qt/QtCore/qpointer.h:62
#9  operator() (__closure=) at
/usr/src/debug/kjobwidgets5/kjobwidgets-5.114.0/src/kuiserverv2jobtracker.cpp:206
#10 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KUiServerV2JobTracker::registerJob(KJob*):: >::call (arg=, f=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146
#11 QtPrivate::Functor,
0>::call, void> (arg=, f=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#12
QtPrivate::QFunctorSlotObject,
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=, r=, a=, ret=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#13 0x7255994d0e27 in ??? () at /usr/lib/libQt5Core.so.5
#14 0x7255994d0e27 in ??? () at /usr/lib/libQt5Core.so.5
#15 0x72559a768b74 in QDBusServiceWatcher::serviceOwnerChanged(QString
const&, QString const&, QString const&) () at /usr/lib/libQt5DBus.so.5
#16 0x72559a76cfcf in ??? () at /usr/lib/libQt5DBus.so.5
#17 0x72559a76d2f3 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call,
int, void**) () at /usr/lib/libQt5DBus.so.5
#18 0x72559a72c76e in ??? () at /usr/lib/libQt5DBus.so.5
#19 0x7255994c3964 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#20 0x72559a1788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x72559949bef8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#22 0x7255994a0e5b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#23 0x7255994e6ec8 in ??? () at /usr/lib/libQt5Core.so.5
#24 0x725597f0df69 in g_main_dispatch (context=0x72558c000ec0) at
../glib/glib/gmain.c:3476
#25 0x725597f6c3a7 in g_main_context_dispatch_unlocked
(context=0x72558c000ec0) at ../glib/glib/gmain.c:4284
#26 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x72558c000ec0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4349
#27 0x725597f0c162 in g_main_context_iteration (context=0x72558c000ec0,
may_block=1) at ../glib/glib/gmain.c:4414
#28 0x7255994ead0c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#29 0x72559949ac04 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#30 0x72559949c0a3 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#31 0x62fc2dcf6f82 in ??? ()
#32 0x725598c45cd0 in ??? () at /usr/lib/libc.so.6
#33 0x725598c45d8a in __libc_start_main () at /usr/lib/libc.so.6
#34 0x62fc2dcf8cc5 in ??? ()
[Inferior 1 (process 553935) detached]

Reported using DrKonqi

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

[gwenview] [Bug 178616] enable/disable auto rotate image

[Andrei Ivnitskii]

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

Andrei Ivnitskii  changed:

   What|Removed |Added

 CC||ivnitsk...@gmail.com

--- Comment #24 from Andrei Ivnitskii  ---
[ImageView]
ApplyExifOrientation=false 

works for modern gwenview

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

[konqueror] [Bug 190127] can't remove search bar from location bar

[Andrei A. Lomov]

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

Andrei A. Lomov  changed:

   What|Removed |Added

 CC||lo...@math.nsc.ru

--- Comment #5 from Andrei A. Lomov  ---
Sorry but the bug is still relevant 
Debian 12 
KDE Frameworks 5.103.0
Qt 5.15.8

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

[konqueror] [Bug 141488] google support for Konqueror

[Andrei A. Lomov]

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

Andrei A. Lomov  changed:

   What|Removed |Added

 CC||lo...@math.nsc.ru

--- Comment #2 from Andrei A. Lomov  ---
Sorry but the bug is still relevant 
Debian 12 
KDE Frameworks 5.103.0
Qt 5.15.8

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

[digikam] [Bug 466455] "Open In File Manager" doesn't work

[Andrei]

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

--- Comment #6 from Andrei  ---
(In reply to caulier.gilles from comment #5)
> Andrei,
> 
> What's about this file using current 8.2.0 AppImage Linux bundle ? It's
> reproducible ?
> 
> https://files.kde.org/digikam/
> 
> Thanks in advance
> 
> Gilles Caulier

Yes. It's work fine with it. It shows the folder with file but doen't select
the file. If it's possible it will be nice (or may be it should - I don't
know).

And BTW. I checked in the fresh Ubuntu - I have the same problem with installed
version.

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

[dolphin] [Bug 474066] Dolphin crash when adding Nvidia shield TV pro SMB server

[Andrei M.]

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

Andrei M.  changed:

   What|Removed |Added

 CC||and...@maces.eu

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

[Discover] [Bug 397486] Add sort by date installed, for the Installed software view

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||rybak@gmail.com

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

[kwin] [Bug 419176] Keyboard shortcut meta+tab only allows one tab per meta, while alt+tab allows repeated presses of tab

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||rybak@gmail.com

--- Comment #6 from Andrei Rybak  ---
I use:

- Meta+Tab for "Walk Through Windows Alternative" 
- Meta+Shift+Tab for "Walk Through Windows Alternative (Reverse)"

Regardless of the animation selected in dropdown "System Settings > Workspace >
Window Management > Task Switcher > Alternative > Visualisation", for me,
Meta+Tab works fine, but Meta+Shift+Tab only works _once_ (can change only to
the immediately previous window) and only when it is pressed _first_ (i.e.
pressing the reverse after Meta+Tab doesn't do anything).

Version info:

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.2.0-31-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

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

[digikam] [Bug 401458] Rename file name with recognized faces-tags

[Andrei]

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

--- Comment #4 from Andrei  ---
(In reply to Andrei from comment #3)
> I don't think so. Because there are many person on the photo. Better to find
> this photo with a filter. I don't know is it possible now in digiKam or not.
> If not the better the ability to do such a filter.

I agree with you.

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

[Spectacle] [Bug 471830] Spectacle crashes when recording Firefox

[Andrei Rybak]

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

--- Comment #2 from Andrei Rybak  ---
Created attachment 161708
  --> https://bugs.kde.org/attachment.cgi?id=161708=edit
New crash information added by DrKonqi

spectacle (23.04.3) using Qt 5.15.10

I'm trying out Wayland. I've recorded several seconds of Firefox. Spectacle
crashed immediately upon clicking "Finish recording".

-- Backtrace (Reduced):
#4  QScopedPointer
>::operator-> (this=0x8) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:116
[...]
#7  QQuickView::rootObject (this=this@entry=0x0) at items/qquickview.cpp:603
#8  0x558c9e0c9a72 in ViewerWindow::showInlineMessage (this=0x0,
qmlFile=..., properties=...) at ./src/Gui/ViewerWindow.cpp:146
#9  0x558c9e0c0fe6 in ViewerWindow::showSavedVideoMessage
(messageArgument=..., this=0x0) at ./src/Gui/ViewerWindow.cpp:161
#10 operator() (path=..., __closure=0x558c9edb3490) at
./src/SpectacleCore.cpp:225

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

[Spectacle] [Bug 471830] Spectacle crashes when recording Firefox

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||rybak@gmail.com

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

[akregator] [Bug 445351] Akregator always wants to recover the session on boot

[Andrei Ivnitskii]

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

Andrei Ivnitskii  changed:

   What|Removed |Added

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

--- Comment #4 from Andrei Ivnitskii  ---
Same problem every boot. Akregator version 5.19.3

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #14 from Andrei Rybak  ---
Just some thinking out loud:

> Before adding an item to the menu, we check if any items for the same device 
> ID exists and
> we remove them, so I don't see how this could happen.

I took a look at the git log, this logic comes from 2014:
https://invent.kde.org/network/kdeconnect-kde/-/commit/90e9ded92655c26fbbe521982289998183631a50#b5e40816c0cc22bf4a042c2010f48a3423f93b0e_84_85

> the problem. Method `KFilePlacesModel::closestItem` doesn't return the hidden 
> entries

Ten months ago (https://bugs.kde.org/show_bug.cgi?id=461872#c1) I commented
that I _had_ to hide section 'Devices':

> This gets so bad, that I just have to hide the "Devices" section in Dolphin 
> completely.
> 
> Question: is it possible that this is a Dolphin bug?

Maybe there was some other compounding bug (not in Dolphin, maybe in KIO?) that
caused the entries not to be deleted? On the screenshot from matrix43547 --
https://bugs.kde.org/attachment.cgi?id=153763 -- the device names are in color
of a "shown" section.

> All links to tag v5.108.0 in the frameworks/kio repository, because that's 
> the version of KDE Frameworks I'm currently using.

This part of method `KFilePlacesModel::closestItem` hasn't changed since
version 5.103.0, which is visible in video
https://bugsfiles.kde.org/attachment.cgi?id=156717 which was recorded on
2023-02-25:

   
https://invent.kde.org/frameworks/kio/-/blob/v5.103.0/src/filewidgets/kfileplacesmodel.cpp#L733

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #12 from Andrei Rybak  ---
This code comes from the following commits:

1. 74904f0 (KFilePlacesModel: ignore hidden places when computing closestItem,
2020-10-10)
https://invent.kde.org/frameworks/kio/-/commit/74904f0cac872aac2423fe41adb115c3dc330ad5
2. eae7e8f ([KFilePlacesModel] Check group visibility in closestItem,
2021-06-19)
https://invent.kde.org/frameworks/kio/-/commit/eae7e8f5c53b1ea8cf205ee061c6bea39a4a81a1

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

[kdeconnect] [Bug 466416] KDE Connect floods kio places (user-places.xbel) with a ton of entries of the same device causing overall desktop performance degeneration.

[Andrei Rybak]

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

--- Comment #11 from Andrei Rybak  ---
An important discovery has been made thanks to Albert Vaca in the related
ticket. Quote from https://bugs.kde.org/show_bug.cgi?id=461872#c11 :

> I found a problem in the related ticket 
> https://bugs.kde.org/show_bug.cgi?id=466416 --
> the steps to reproduce there aren't precise enough. Step 3 is "3. Unhide the 
> section
> "Devices" in the "Places" panel.", but on the video recording attached to 
> that ticket
> checkbox "Hide section 'Devices'" is enabled and I am using checkbox "Show 
> All Entries"
> to make the overflowing section 'Devices' visible.

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #11 from Andrei Rybak  ---
> I don't know a lot of C++, so I can't really help with code analysis here.

Never mind, I sold myself a little short here. I've found the problem. Method
`KFilePlacesModel::closestItem` doesn't return the hidden entries:

https://invent.kde.org/frameworks/kio/-/blob/v5.108.0/src/filewidgets/kfileplacesmodel.cpp#L733

[...]
for (int row = 0; row < d->items.size(); ++row) {
KFilePlacesItem *item = d->items[row];

if (item->isHidden() || isGroupHidden(item->groupType())) {
continue;
}
[...]
}

I confirmed it by

1. Disable checkbox "Hide section 'Devices'"
2. Repeat steps 2-4 in https://bugs.kde.org/show_bug.cgi?id=461872#c6

I found a problem in the related ticket
https://bugs.kde.org/show_bug.cgi?id=466416 -- the steps to reproduce there
aren't precise enough. Step 3 is "3. Unhide the section "Devices" in the
"Places" panel.", but on the video recording attached to that ticket checkbox
"Hide section 'Devices'" is enabled and I am using checkbox "Show All Entries"
to make the overflowing section 'Devices' visible.

== Notes ==
All links to tag v5.108.0 in the frameworks/kio repository, because that's the
version of KDE Frameworks I'm currently using.

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #10 from Andrei Rybak  ---
Here's how the kdeconnect:// URLs look like in my
`~/.local/share/user-places.xbel`:

```
 
  Pixel 6A
  
   http://freedesktop.org;>

   
   http://www.kde.org;>
1694595218/8
   
  
 
 
  Pixel 6A
  
   http://freedesktop.org;>

   
   http://www.kde.org;>
1694595239/9
   
  
 
 
  Pixel 6A
  
   http://freedesktop.org;>

   
   http://www.kde.org;>
1694631780/10
   
  
 
 
  Pixel 6A
  
   http://freedesktop.org;>

   
   http://www.kde.org;>
1694677298/11
   
  
 
```

The different contents in tag  stick out, but the `deviceId`
(https://invent.kde.org/network/kdeconnect-kde/-/blame/master/plugins/sftp/sftpplugin.cpp#L43)
is the same for every URL.

I don't know a lot of C++, so I can't really help with code analysis here.

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #8 from Andrei Rybak  ---
I am using KDE Connect 23.08:

$ apt show kdeconnect 2>/dev/null | head -2
Package: kdeconnect
Version: 23.08.0-0xneon+22.04+jammy+release+build32

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #6 from Andrei Rybak  ---
Hello, Albert. Thank you for looking into this issue.

> Does this happen even without unpairing/repairing the device? We shouldn't 
> create more than one entry for the same device, and I can't reproduce this.

I've re-run my tests and below are my steps to reproduce as of 2023-09-13. I
don't think "unpairing/repairing" is needed to reproduce this. In fact, KDE
Connect application on the desktop is not involved in my steps to reproduce at
all.

Please also see the video attachment
https://bugsfiles.kde.org/attachment.cgi?id=156717 in
https://bugs.kde.org/show_bug.cgi?id=466416. Nobody is doing this amount of
pairing/unpairing in casual use of KDE Connect.

== Prerequisites ==

1. The phone is Pixel 6a, the workaround "Use device MAC" is enabled in the
settings of the WiFi network in question, as per
https://bugs.kde.org/show_bug.cgi?id=466416#c7
2. The duplicates are cleared from Dolphin as per
https://bugs.kde.org/show_bug.cgi?id=466420#c3
3. KDE Plasma version is 5.27.7

== Steps ==

1. Open Dolphin, ensure panel "Places" is shown, ensure checkbox "Show All
Entries" is enabled (context menu of "Places").
2. Disconnect the phone from the WiFi network, force close KDE Connect on the
phone
3. Connect the phone to the WiFi network, open KDE Connect on the phone
4. Observe the panel in Dolphin
5. Disconnect the phone from the WiFi network, force close KDE Connect on the
phone (repeat of step 2)
6. Connect the phone to the WiFi network, open KDE Connect on the phone (repeat
of step 3)
7. Observe the panel in Dolphin

== Actual result ==
- At step 4 entry "Pixel 6A" appears in the "Places" panel, as expected.
- At step 7 a second, erroneous, entry "Pixel 6A" appears in the "Places"
panel.

== Expected result ==
- At step 4 entry "Pixel 6A" appears in the "Places" panel.
- At step 7 nothing new appears in the "Places" panel.

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

[dolphin] [Bug 453159] Unable to set custom top-level icon in Service Menu

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||tdhj744ra...@opayq.com

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

[gwenview] [Bug 471308] New: Gwenview crashes instantly when opening some jpg from dolphin

[Andrei Tescula]

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

Bug ID: 471308
   Summary: Gwenview crashes instantly when opening some jpg from
dolphin
Classification: Applications
   Product: gwenview
   Version: 23.04.2
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: atesc...@gmail.com
  Target Milestone: ---

Application: gwenview (23.04.2)

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.3.8-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.6 [KCrashBackend]

-- Information about the crash:
Gwenview crashes instantly when opening some jpg from dolphin

The crash can be reproduced sometimes.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x7f29f2bc97ab in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const
() from /usr/lib/libexiv2.so.28
#7  0x7f29f2c42e45 in ?? () from /usr/lib/libexiv2.so.28
#8  0x7f29f2b68050 in ?? () from /usr/lib/libexiv2.so.28
#9  0x7f29f2bc0914 in Exiv2::Exifdatum::write(std::basic_ostream >&, Exiv2::ExifData const*) const () from
/usr/lib/libexiv2.so.28
#10 0x7f29f3a4d1f4 in Exiv2::operator<< (md=warning: RTTI symbol not found
for class 'Exiv2::Exifdatum'
..., os=...) at /usr/include/exiv2/metadatum.hpp:277
#11 Gwenview::ImageMetaInfoModelPrivate::fillExivGroup > (container=...,
group=0x557e54975180, parent=..., this=0x557e54975160) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/imagemetainfomodel.cpp:282
#12 Gwenview::ImageMetaInfoModel::setExiv2Image (this=0x557e549750d0,
image=0x7f29a0001410) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/imagemetainfomodel.cpp:441
#13 0x7f29f3a11c21 in Gwenview::Document::setExiv2Image
(this=0x557e54670c50, image=...) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/document/document.cpp:388
#14 0x7f29f3a1cd8e in Gwenview::AbstractDocumentImpl::setDocumentExiv2Image
(this=0x557e5497a450, image=std::unique_ptr = {...}) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/document/abstractdocumentimpl.cpp:81
#15 Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded (this=0x557e5497a450) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/document/loadingdocumentimpl.cpp:497
#16 0x7f29f16d06a7 in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate (sender=0x557e54968ca8, signal_index=4,
argv=0x7ffd3aefb6b0) at kernel/qobject.cpp:3925
#18 0x7f29f14fd4d5 in QFutureWatcherBase::event (this=,
event=0x7f29a001cba0) at thread/qfuturewatcher.cpp:334
#19 0x7f29f237893f in QApplicationPrivate::notify_helper (this=, receiver=0x557e54968ca8, e=0x7f29a001cba0) at
kernel/qapplication.cpp:3640
#20 0x7f29f169b778 in QCoreApplication::notifyInternal2
(receiver=0x557e54968ca8, event=0x7f29a001cba0) at
kernel/qcoreapplication.cpp:1064
#21 0x7f29f16a06db in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x557e53f67b20) at
kernel/qcoreapplication.cpp:1821
#22 0x7f29f16e6748 in postEventSourceDispatch (s=0x557e5403ebe0) at
kernel/qeventdispatcher_glib.cpp:277
#23 0x7f29ef98c981 in g_main_dispatch (context=0x7f29e4000ee0) at
../glib/glib/gmain.c:3460
#24 g_main_context_dispatch (context=0x7f29e4000ee0) at
../glib/glib/gmain.c:4200
#25 0x7f29ef9e9b39 in g_main_context_iterate.isra.0
(context=context@entry=0x7f29e4000ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#26 0x7f29ef98a032 in g_main_context_iteration (context=0x7f29e4000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#27 0x7f29f16ea5cc in QEventDispatcherGlib::processEvents
(this=0x557e540436c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7f29f169a484 in QEventLoop::exec (this=this@entry=0x7ffd3aefbae0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7f29f169b923 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x7f29f1b3bf12 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1870
#31 0x7f29f2376cda in QApplication::exec () at kernel/qapplication.cpp:2832
#32 0x557e52421a49 in main (argc=, argv=) at
/usr/src/debug/gwenview/gwenview-23.04.2/app/main.cpp:213
[Inferior 1 (process 945746) detached]

Reported using DrKonqi

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

[kfontview] [Bug 471243] New: Add ability to copy characters to Font Viewer

[Andrei Rybak]

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

Bug ID: 471243
   Summary: Add ability to copy characters to Font Viewer
Classification: Applications
   Product: kfontview
   Version: 5.27.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: rybak@gmail.com
  Target Milestone: ---

When viewing fonts that are used for rendering icons, for example, it is
sometimes useful to be able to see the whole font. Preview type "All
Characters" is very useful for that.

However, it isn't possible to select and copy characters while looking at them.

Please consider making the text field with the preview selectable by user to
allow copying characters directly from the preview.

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

[dolphin] [Bug 470593] New: Particularly named files show end of the filename outside the selection in "Icons view mode"

[Andrei Rybak]

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

Bug ID: 470593
   Summary: Particularly named files show end of the filename
outside the selection in "Icons view mode"
Classification: Applications
   Product: dolphin
   Version: 23.04.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: icons mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: rybak@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 159443
  --> https://bugs.kde.org/attachment.cgi?id=159443=edit
Screen recording of the OBSERVED RESULT

SUMMARY
File named "20230602_It's Time To Name And Shame - WAN Show June 2,
2023_ntgYW8LfNfk.ogg" causes visual glitches in "Icons view mode" of Dolphin.


STEPS TO REPRODUCE
1. Open Dolphin
2. Navigate to /tmp
3. Switch Dolphin to "Icons view mode"
4. Create a text file (right click > "Create New" > "Text File...") named
"20230602_It's Time To Name And Shame - WAN Show June 2, 2023_ntgYW8LfNfk.ogg"
– don't forget to delete automatic ".txt" filename extension.
5. Move file to the trash bin by pressing Delete on the keyboard


OBSERVED RESULT
After step 4, the "ogg" part of the filename is wrapped to the fourth line of
text under the icon.
After step 5, the "ogg" part of the filename remains visible for some time,
even though the file isn't in the directory anymore.

EXPECTED RESULT
The "ogg" part of the filename is not wrapped to the fourth line.

ADDITIONAL INFORMATION
I played around with different filenames and couldn't reproduce the issue for
other filenames. My guess would be that is has something to do with the
particular font kerning of this exact string that causes the issue.

VERSION
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-42-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

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

[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients

[Andrei Amuraritei]

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

--- Comment #6 from Andrei Amuraritei  ---
Forgot to mention that Plasma was updated to 5.27.5 in the mean time.

Nate, could you detail why you think this is a duplicate of 466149? I am not
following that. Or, in my case, for the Wayland session, the primary screen
remains primary (DELL) and is always XWAYLAND0 and it is currently set at pos
0x0. Then the other screen is SAMSUNG, at pos +2560 and remains there.

The primary thing does not change as far as I can see, xrandr always says
primary is XWAYLAND0 (maybe because it should be fixed with 5.27.5). However as
noted, the SAMSUNG screen gets a new XWAYLAND ID every time I power it on.

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

[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients

[Andrei Amuraritei]

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

--- Comment #4 from Andrei Amuraritei  ---
Hi Nate, thanks for your input.

The most annoying issue was having the xwayland client getting frozen or
dissapearing (in this case a game window). Then focus/input being stolen from
the active window.

Since opening this report, I have also done more testing and I do not have the
issue of the xwayland window dissapearing. My main guess is that I have cleared
my ~/.local/share/kscreen folder and this fixed the issue.

While testing support of amdgpu for the 7900XTX GPU, I guess there was some
kscreen configs present that broke xwayland (I have several issues opened on
the amdgpu gitlab and currently for Debian 12, support is pretty bad for
7900XTX GPU with current 6.1 LTS kernel).

So, good news, xwayland client does not die anymore, however, when a xwayland
client window is active and I power on my SAMSUNG HDMI screen, the input or
focus goes away from the active window. I think this is still relevant for this
bug report.
I also observe that each time I turn off and on the SAMSUNG screen, xrandr
shows me a different XWAYLAND ID, example from XWAYLAND1 to XWAYLAND2 etc. Why
does this happen (assuming the screens remain the same, so the active kscreen
config does not change)?

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

[krunner] [Bug 470312] krunner crashed when typing in 4000000

[Andrei Rybak]

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

--- Comment #4 from Andrei Rybak  ---
Created attachment 159365
  --> https://bugs.kde.org/attachment.cgi?id=159365=edit
demonstration of krunner closing unexpectedly

Originally, the crash happened just after typing "40" or "400". On 2023-05-26 I
managed to reproduce the _crash_ (with drkonqi) a couple of times.

Since then, I've installed debug symbols for libqalculate22. Now, after an
upgrade and restart I'm not able to reproduce the crash, but there's still some
weird behavior going on – krunner closes unexpectedly, but drkonqi doesn't
appear. drkonqi itself seems to be working, e.g. I'm able to reproduce the
crash from https://bugs.kde.org/show_bug.cgi?id=469919 and drkonqi reports the
crash in Spectacle.

Unfortunately, I can't pin down the exact steps to reproduce the weird
behavior. As far as I can tell, it has something to do with having a
quote-unquote "incomplete" math expression in history. In my case, it's a
trailing minus sign. For example:

1. Open krunner (in my case, via shortcut Alt+F2)
2. Type `1000-` (one thousand and a trailing minus)
3. Press Enter
4. Press Esc
5. Open krunner again
6. Start typing some number

In some cases, during step 6 krunner closes unexpectedly.

As an example, on the attached screen recording
(kde-krunner-glitch-2023-05-31.mp4) at the very end I'm trying to type "3"
(thirty thousand), but I'm only able to type in "3000" (three thousand).
krunner closes unexpectedly just after I press the fourth zero.

The screen recording includes a demo of the keys being pressed via an
application called "screenkey".

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

[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients

[Andrei Amuraritei]

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

Andrei Amuraritei  changed:

   What|Removed |Added

   Platform|Other   |Debian testing

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

[krunner] [Bug 470312] krunner crashed when typing in 4000000

[Andrei Rybak]

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

--- Comment #2 from Andrei Rybak  ---
libqalculate22

installed version is 4.6.1-0xneon+22.04+jammy+release+build9

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

[Falkon] [Bug 408821] "Allow Pepper Plugins (Flash Plugin)" checkbox has the opposite effect

[Andrei Slavoiu]

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

Andrei Slavoiu  changed:

   What|Removed |Added

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

--- Comment #2 from Andrei Slavoiu  ---
Turns out there was a problem with my flash plugin and when the checkbox was
disabled it falled back to HTML5.

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

[kdevelop] [Bug 470428] Kdevelop crashes during background parsing with clang

[Andrei Slavoiu]

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

--- Comment #4 from Andrei Slavoiu  ---
Created attachment 159346
  --> https://bugs.kde.org/attachment.cgi?id=159346=edit
compiler.info

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

[kdevelop] [Bug 470428] Kdevelop crashes during background parsing with clang

[Andrei Slavoiu]

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

--- Comment #3 from Andrei Slavoiu  ---
Hi, first of all, after clearing the cache it no longer crashes. But if it
helps to prevent this in the future:

The entire system is built with CFLAGS="-march=native -ggdb3 -O2 -pipe
-fdiagnostics-color". See attached compiler.info for what -march=native
translates to on my system.

This is the content of stl_algobase.h around that line.

  template
_GLIBCXX20_CONSTEXPR
inline typename
__gnu_cxx::__enable_if<__is_scalar<_Tp>::__value, void>::__type
__fill_a1(_ForwardIterator __first, _ForwardIterator __last,
  const _Tp& __value)
{
  const _Tp __tmp = __value;
930:  for (; __first != __last; ++__first)
*__first = __tmp;
}

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

[kdevelop] [Bug 470428] New: Kdevelop crashes during background parsing with clang

[Andrei Slavoiu]

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

Bug ID: 470428
   Summary: Kdevelop crashes during background parsing with clang
Classification: Applications
   Product: kdevelop
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: ansl...@yahoo.com
  Target Milestone: ---

Application: kdevelop (5.11.230401 (23.04.1))

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.3-gentoo x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Started crashing after I changed the active compiler for the project from GCC
to Clang.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  __memset_avx2_unaligned_erms () at
../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:328
#7  0x7f28322a7daf in std::__fill_a1(unsigned short*,
unsigned short*, int const&) (__value=, __last=,
__first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:930
#8  std::__fill_a(unsigned short*, unsigned short*, int
const&) (__value=, __last=, __first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:977
#9  std::__fill_n_a(unsigned short*, int, int
const&, std::random_access_iterator_tag) (__value=, __n=3277,
__first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:1128
#10 std::fill_n::{unnamed type#3},
int>(KDevelop::Bucket::{unnamed type#3},
KDevelop::Bucket::{unnamed type#3}, int const&)
(__value=,
__n=KDevelop::Bucket::NextBucketHashSize,
__first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:1157


Reported using DrKonqi

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

[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients

[Andrei Amuraritei]

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

--- Comment #2 from Andrei Amuraritei  ---
Also tested with Gnome Wayland, shell version 43.4 and the same game (ex, FFXIV
with Wine via Lutris), closes like on the KDE Wayland session.

I have also tested running a native Linux version of a game, and it does not
close however when the other screen is powered on, desktop flickers and the
game window switches from borderless/fullscreen to where taskbar is visible
(position top) and game loses focus (input).

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

[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients

[Andrei Amuraritei]

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

--- Comment #1 from Andrei Amuraritei  ---
I have tested this further with:

Sway wayland, the same game (ex, FFXIV with Wine via Lutris) does not die in
that session when turning on the HDMI screen.
Plasma X11, the same game (ex, FFXIV with Wine via Lutris), does not die but
the window gets switched (moved?) from fullscreen , where the taskbar is
visible at the top and focus on the game stays.

Also tested with an older kernel from Debian, 6.1.0-3-amd64, so maybe not
drm/amd related.

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

[kwin] [Bug 470329] New: Monitor power on / off results in stolen input and broken xwayland clients

[Andrei Amuraritei]

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

Bug ID: 470329
   Summary: Monitor power on / off results in stolen input and
broken xwayland clients
Classification: Plasma
   Product: kwin
   Version: 5.27.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: and...@posteo.net
  Target Milestone: ---

SUMMARY
***
CPU: AMD 5950x
GPU: 0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX] [1002:744c] (rev c8) Sapphire
Nitro+
System Memory: 32GB DDR4
Display(s): DELL 27" 2560x1440@144 DisplayPort and SAMSUNG 75" 3840x2160@120
HDMI

Debian 12 Bookworm
Kernel: 6.3.3-x64v3-xanmod1 #0~20230517.05b3a98
***

STEPS TO REPRODUCE
1.  Have the HDMI display screen powered off while Displayport screen is
Primary and active, powered on
2. Start Steam, start a game from library via Proton (Wine)
3. Play the game normally
4. Turn on the HDMI display from remote, the whole desktop flickers, the game
client window moves and freezes (depending on game) and loses input.
5. Need to stop (terminate) the frozen game window client and restart

OBSERVED RESULT
First, desktop flickers and all windows (that maybe are on powered off screen)
move to primary screen and then back to screen that was powered on.
It seems some xwayland clients are broken, getting freezed and losing focus.
Focus is lost from active window (screen).

EXPECTED RESULT
Screen powers on and displays the configured desktop for it
No flickering or minimal flickering, no Window moving from active screen to the
other and back.
No changing focus from screen to screen.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.3.3-x64v3-xanmod1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUS

ADDITIONAL INFORMATION
Testing on Windows I see a short flicker when trying the same operation of
turning a screen on / off but the windows do not move.
Testing on Linux, this happens, have observed this desktop flicker when turning
a display on and the current windows getting moved from screen to screen also
while trying Fedora 38 KDE Live 1.6.iso.

Not sure if this strictly a KDE Kwin/Plasma issue, I think it's maybe amd/drm
something, will raise another issue there.

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

[krunner] [Bug 470312] New: krunner crashed when typing in 4000000

[Andrei Rybak]

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

Bug ID: 470312
   Summary: krunner crashed when typing in 400
Classification: Plasma
   Product: krunner
   Version: 5.27.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: rybak@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

Application: krunner (5.27.5)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 5.19.0-41-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
I've tried to start a calculation that started with the number of 4 million.
KRunner crashed several times roughly after typing 400 or 4000.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KRunner (krunner), signal: Segmentation fault

[KCrash Handler]
#4  0x7f553b83b024 in MathStructure::type() const () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#5  0x7f553b835134 in MathStructure::MathStructure(MathStructure const&) ()
from /lib/x86_64-linux-gnu/libqalculate.so.22
#6  0x7f553b7aa101 in CalculateThread::run() () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#7  0x7f553b843534 in Thread::doRun(void*) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#8  0x7f5584694b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
#9  0x7f5584726a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 29 (Thread 0x7f54df7fe640 (LWP 90937) "krunner:gdrv0"):
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0,
clockid=0, expected=0, futex_word=0x7f55349a6240) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x7f55349a6240, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
./nptl/futex-internal.c:139
#3  0x7f5584693ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x7f55349a61f0, cond=0x7f55349a6218) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x7f55349a6218, mutex=0x7f55349a61f0) at
./nptl/pthread_cond_wait.c:627
#5  0x7f557cd0aced in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#6  0x7f557ccbe35b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#7  0x7f557cd0ac1b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#8  0x7f5584694b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
#9  0x7f5584726a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 28 (Thread 0x7f55167fc640 (LWP 37714) "GlobalQueue[16]"):
#1  0x7f55846ea6e7 in __GI___nanosleep (req=, rem=) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2  0x7f553b844264 in sleep_ms(int) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#3  0x7f553b7b526e in Calculator::calculate(MathStructure*,
std::__cxx11::basic_string, std::allocator
>, int, EvaluationOptions const&, MathStructure*, MathStructure*, bool) () from
/lib/x86_64-linux-gnu/libqalculate.so.22
#4  0x7f5541df392f in QalculateEngine::evaluate (this=0x561fb91c0a80,
expression=..., isApproximate=isApproximate@entry=0x7f55167fb9eb,
base=base@entry=10, customBase=...) at
./runners/calculator/qalculate_engine.cpp:155
#5  0x7f5541df4cee in CalculatorRunner::calculate (this=0x561fb932c4f0,
term=..., isApproximate=0x7f55167fb9eb, base=10, customBase=...) at
/usr/include/c++/11/bits/unique_ptr.h:173
#6  0x7f5541df597b in CalculatorRunner::match (this=0x561fb932c4f0,
context=...) at ./runners/calculator/calculatorrunner.cpp:126
#7  0x7f55740b810f in ?? () from /lib/x86_64-linux-gnu/libKF5Runner.so.5
#8  0x7f557407abcd in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f557407bab4 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f5574080226 in ThreadWeaver::Thread::run() () from
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f5584ece733 in operator() (__closure=,
__closure=) at thread/qthread_unix.cpp:350
#12 (anonymous
namespace)::terminate_on_exception >
(t=..., t=...) at thread/qthread_unix.cpp:287
#13 QThreadPrivate::start (arg=0x7f55100029e0) at thread/qthread_unix.cpp:310
#14 0x7f5584694b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
#15 0x7f5584726a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 27 (Thread 0x7f5516ffd640 (LWP 37713) "GlobalQueue[15]"):
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0,
clockid=0, expected=0, futex_word=0x561fb9338700) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64

[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over

[Andrei Rybak]

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

--- Comment #8 from Andrei Rybak  ---
Jose, thank you for the insight. I will try disabling the MAC randomization on
the phone and see if it helps.

What is very surprising, however, if it is indeed the root cause, is that KDE
Connect itself doesn't seem to be confused by the MAC address randomization.
Regardless of the MAC address, KDE Connect seems to be able to keep track of
the "trusted" status of the phone and of all the settings of plugins (e.g. the
commands in "Run commands").

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

[kwin] [Bug 445338] Visual glitch in form of narrow horizontal stripes across animated parts of the screen

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

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

--- Comment #1 from Andrei Rybak  ---
Since 2021, I have

1. upgraded up to KDE 5.27.5.
2. changed my V-sync settings
3. upgraded my monitor

I haven't been able to reproduce the bug, so there's no sense in keeping this
bug open.

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

[Spectacle] [Bug 469919] Spectacle: crash on second launch after pressing Enter in text annotation tool

[Andrei Rybak]

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

--- Comment #1 from Andrei Rybak  ---
Created attachment 159052
  --> https://bugs.kde.org/attachment.cgi?id=159052=edit
Screen recording of the OBSERVED RESULT

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

[Spectacle] [Bug 469919] New: Spectacle: crash on second launch after pressing Enter in text annotation tool

[Andrei Rybak]

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

Bug ID: 469919
   Summary: Spectacle: crash on second launch after pressing Enter
in text annotation tool
Classification: Applications
   Product: Spectacle
   Version: 23.04.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: rybak@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

Application: spectacle (23.04.1)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 5.19.0-41-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
SUMMARY
If a user closes Spectacle by pressing Enter, Shift+Enter, or Ctrl+Enter, the
application closes and notification "A screenshot was saved to your clipboard"
appears. However, if Enter, Shift+Enter, or Ctrl+Enter was pressed during text
input, then the next launch of Spectacle crashes.


STEPS TO REPRODUCE
1. Launch "Capture Rectangular Region" (default shortcut is Meta+Shift+Print)
2. Click on the button for the "Text" annotation tool
3. Click somewhere to start the "Text" annotation tool
4. Press button "Enter" on the keyboard (or Shift+Enter, or Ctrl+Enter)
5. Launch "Capture Rectangular Region" a second time

OBSERVED RESULT
After step 3, notification "A screenshot was saved to your clipboard" appears.
After step 5, notification about Spectacle crashing appears.

I will also attach a screen recording demostrating the crash.

EXPECTED RESULT
The crash after step 5 shouldn't happen. Maybe the behavior after step 4 should
be changed as well (e.g. to just close the text input instead of closing
Spectacle).

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

The crash can be reproduced every time.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x560d82653a1f in SelectedActionWrapper::setEditAction
(this=0x560d83da1c50, action=0x0) at
./src/Gui/Annotations/AnnotationDocument.cpp:561
#5  0x560d8265a7b4 in AnnotationDocument::deselectAction
(this=0x560d83dd0c60) at ./src/Gui/Annotations/AnnotationDocument.cpp:1436
#6  AnnotationDocument::clearAnnotations (this=0x560d83dd0c60) at
./src/Gui/Annotations/AnnotationDocument.cpp:928
#7  0x560d8264a201 in AnnotationDocument::clear (this=0x560d83dd0c60) at
./src/Gui/Annotations/AnnotationDocument.cpp:842
#8  operator() (screenImages=..., __closure=0x560d83dd9330) at
./src/SpectacleCore.cpp:129
#9  QtPrivate::FunctorCall, QtPrivate::List&>, void,
SpectacleCore::SpectacleCore(QObject*)::&)>
>::call (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#10 QtPrivate::Functor&)>, 1>::call const&>,
void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#11
QtPrivate::QFunctorSlotObject&)>, 1, QtPrivate::List&>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=0x560d83dd9320, r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#12 0x7fb22e8f41e4 in QtPrivate::QSlotObjectBase::call (a=0x7fffea53c7c0,
r=0x7fffea53cd20, this=0x560d83dd9320) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x560d83da1bf0, signal_index=6,
argv=0x7fffea53c7c0) at kernel/qobject.cpp:3923
#14 0x7fb22e8ed287 in QMetaObject::activate
(sender=sender@entry=0x560d83da1bf0, m=m@entry=0x560d826b2640
, local_signal_index=local_signal_index@entry=3,
argv=argv@entry=0x7fffea53c7c0) at kernel/qobject.cpp:3983
#15 0x560d82670917 in Platform::newScreensScreenshotTaken (_t1=...,
this=0x560d83da1bf0) at
./obj-x86_64-linux-gnu/src/spectacle_autogen/UWYFJWVAJO/moc_Platform.cpp:298
#16 PlatformXcb::doGrabNow (this=0x560d83da1bf0, theGrabMode=,
theIncludePointer=, theIncludeDecorations=) at
./src/Platforms/PlatformXcb.cpp:713
#17 0x7fb22e8f8306 in QtPrivate::QSlotObjectBase::call (a=0x7fffea53c830,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 QSingleShotTimer::timerEvent (this=0x560d85b8f2b0) at kernel/qtimer.cpp:320
#19 0x7fb22e8e9b0f in QObject::event (this=0x560d85b8f2b0,
e=0x7fffea53c9a0) at kernel/qobject.cpp:1369
#20 0x7fb23016c793 in QApplicationPrivate::notify_helper (this=, receiver=0x560d85b8f2b0, e=0x7fffea53c9a0) at
kernel/qapplication.cpp:3640
#21 0x7fb22e8bc18a in QCoreApplication::notifyInternal2
(receiver=0x560d85b8f2b0, 

[systemsettings] [Bug 469914] System Settings: non-default settings for Software Update are not highlighted

[Andrei Rybak]

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

--- Comment #2 from Andrei Rybak  ---
After more testing I realized that «4. If enabled, click on "Apply"» in "STEPS
TO REPRODUCE" is not needed.

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

[systemsettings] [Bug 469914] System Settings: non-default settings for Software Update are not highlighted

[Andrei Rybak]

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

--- Comment #1 from Andrei Rybak  ---
Created attachment 159048
  --> https://bugs.kde.org/attachment.cgi?id=159048=edit
Screenshot for section EXPECTED RESULT

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

[systemsettings] [Bug 469914] New: System Settings: non-default settings for Software Update are not highlighted

[Andrei Rybak]

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

Bug ID: 469914
   Summary: System Settings: non-default settings for Software
Update are not highlighted
Classification: Applications
   Product: systemsettings
   Version: 5.27.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_updates
  Assignee: plasma-b...@kde.org
  Reporter: rybak@gmail.com
  Target Milestone: ---

Created attachment 159047
  --> https://bugs.kde.org/attachment.cgi?id=159047=edit
Screenshot for section OBSERVED RESULT

SUMMARY
When a user changes a setting in System Settings to a value that isn't a
default, the UI element controlling the value usually gets highlighted.  This
doesn't happen to UI elements in "System Administration > Software Update"


STEPS TO REPRODUCE
1. Open System Settings
2. Navigate to "System Administration > Software Update"
3. If available, click on "Defaults"
4. If enabled, click on "Apply"
5. Change any one setting:
   - radio buttons "Manually"/"Automatically" for "Update software" 
   - dropdown (aka combobox) "Update frequency"
   - checkbox "Use offline updates"

OBSERVED RESULT
After step 5 all UI elements remain "unhighlighted". See the first screenshot.


EXPECTED RESULT
The UI element being changed to a non-default value has a highlight. See the
second screenshot – the panel "System Settings > Workspace > Window Management
> Tasks Switcher > Main" is shown with examples of both default and non-default
values.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

ADDITIONAL INFORMATION
In my color scheme, the UI elements with default values happen to have the blue
highlight, and UI elements with non-default values – orange highlight.

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

[kwin] [Bug 422324] Desktop offset horizontally from display

[Andrei Rybak]

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

--- Comment #12 from Andrei Rybak  ---
The above output of two commands is for clicking on the tiny area of the
desktop with the icon.

Here is the output for the same commands for the area of the screen that is
just black, outside of the desktop:

```
$ xwininfo

xwininfo: Please select the window about which you
  would like information by clicking the
  mouse in that window.

xwininfo: Window id: 0x7b4 (the root window) (has no name)

  Absolute upper-left X:  0
  Absolute upper-left Y:  0
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 2560
  Height: 1440
  Depth: 24
  Visual: 0x21
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x20 (installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +0+0  -0+0  -0-0  +0-0
  -geometry 2560x1440+0+0

```

```
$ xprop
_KDE_WINDOW_HIGHLIGHT(_KDE_WINDOW_HIGHLIGHT) = 0x0
_KDE_KWIN_KSCREEN_SUPPORT(_KDE_KWIN_KSCREEN_SUPPORT) = 0x0
_KDE_SLIDE(_KDE_SLIDE) = 0x0
_KDE_NET_WM_BLUR_BEHIND_REGION(_KDE_NET_WM_BLUR_BEHIND_REGION) = 0x0
InterpRegistry(STRING) = 
_NET_SHOWING_DESKTOP(CARDINAL) = 0
_NET_WORKAREA(CARDINAL) = 0, 0, 2560, 1394, 0, 0, 2560, 1394, 0, 0, 2560, 1394,
0, 0, 2560, 1394, 0, 0, 2560, 1394, 0, 0, 2560, 1394, 0, 0, 2560, 1394, 0, 0,
2560, 1394, 0, 0, 2560, 1394
_NET_CLIENT_LIST_STACKING(WINDOW): window id # 0x520001d, 0x3c7, 0x56c,
0x486, 0x54c, 0x4ec, 0x1e0003e, 0x4cd, 0x520003c
_NET_CLIENT_LIST(WINDOW): window id # 0x4cd, 0x56c, 0x4ec,
0x3c7, 0x486, 0x1e0003e, 0x54c, 0x520001d, 0x520003c
_NET_DESKTOP_GEOMETRY(CARDINAL) = 2560, 1440
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x4cd
_NET_DESKTOP_NAMES(UTF8_STRING) = "top left", "top", "top right", "left",
"centre", "right", "bottom left", "bottom", "bottom right"
_NET_CURRENT_DESKTOP(CARDINAL) = 4
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0
_NET_NUMBER_OF_DESKTOPS(CARDINAL) = 9
_NET_DESKTOP_LAYOUT(CARDINAL) = 0, 3, 3, 0
_NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x5800013
_NET_SUPPORTED(ATOM) = _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK,
_NET_CLIENT_LIST, _NET_CLIENT_LIST_STACKING, _NET_NUMBER_OF_DESKTOPS,
_NET_DESKTOP_GEOMETRY, _NET_CURRENT_DESKTOP, _NET_DESKTOP_NAMES,
_NET_ACTIVE_WINDOW, _NET_WORKAREA, _NET_DESKTOP_LAYOUT, _NET_CLOSE_WINDOW,
_NET_RESTACK_WINDOW, _NET_SHOWING_DESKTOP, _NET_WM_MOVERESIZE,
_NET_MOVERESIZE_WINDOW, _NET_WM_NAME, _NET_WM_VISIBLE_NAME, _NET_WM_DESKTOP,
_NET_WM_WINDOW_TYPE, _NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_DESKTOP,
_NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_TOOLBAR,
_NET_WM_WINDOW_TYPE_MENU, _NET_WM_WINDOW_TYPE_DIALOG,
_NET_WM_WINDOW_TYPE_UTILITY, _NET_WM_WINDOW_TYPE_SPLASH,
_KDE_NET_WM_WINDOW_TYPE_OVERRIDE, _NET_WM_STATE, _NET_WM_STATE_MODAL,
_NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ,
_NET_WM_STATE_SHADED, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_SKIP_PAGER,
_KDE_NET_WM_STATE_SKIP_SWITCHER, _NET_WM_STATE_HIDDEN,
_NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_ABOVE, _NET_WM_STATE_STAYS_ON_TOP,
_NET_WM_STATE_BELOW, _NET_WM_STATE_DEMANDS_ATTENTION, _NET_WM_STATE_FOCUSED,
_NET_WM_STRUT, _NET_WM_STRUT_PARTIAL, _NET_WM_ICON_GEOMETRY, _NET_WM_ICON,
_NET_WM_PID, _NET_WM_PING, _NET_WM_USER_TIME, _NET_STARTUP_ID,
_NET_WM_WINDOW_OPACITY, _NET_WM_FULLSCREEN_MONITORS, _NET_WM_ALLOWED_ACTIONS,
_NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE,
_NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT,
_NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_FRAME_EXTENTS,
_KDE_NET_WM_FRAME_STRUT, _KDE_NET_WM_TEMPORARY_RULES, _NET_WM_FULL_PLACEMENT,
_KDE_NET_WM_ACTIVITIES, _KDE_NET_WM_SHADOW, _NET_WM_OPAQUE_REGION,
_GTK_FRAME_EXTENTS, _GTK_SHOW_WINDOW_MENU
_QT_GET_TIMESTAMP(INTEGER) = 
XFree86_DDC_EDID1_RAWDATA(INTEGER) = 0, -1, -1, -1, -1, -1, -1, 0, 6, -81, -19,
56, 0, 0, 0, 0, 0, 25, 1, 4, -107, 34, 19, 120, 2, 81, 37, -109, 88, 87, -113,
40, 31, 80, 84, 0, 0, 0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 120,
55, -128, -76, 112, 56, 46, 64, 108, 48, -86, 0, 88, -63, 16, 0, 0, 26, 96, 44,
-128, -76, 112, 56, 46, 64, 108, 48, -86, 0, 88, -63, 16, 0, 0, 26, 0, 0, 0,
-2, 0, 50, 56, 72, 56, 48, -128, 66, 49, 53, 54, 72, 84, 78, 0, 0, 0, 0, 0, 0,
65, 2, -106, 0, 16, 0, 0, 10, 1, 10, 32, 32, 0, 9
_QT_SETTINGS_TIMESTAMP_:0(_QT_SETTINGS_TIMESTAMP_:0) = 0x0, 0x0, 0x0, 0x0, 0x0,
0x25, 0x89, 0x96, 0x4, 0xa6, 0x91, 0xf7, 0x0
XIM_SERVERS(ATOM) = @server=ibus
AT_SPI_BUS(STRING) =
"unix:path=/run/user/1000/at-spi/bus_0,guid=6270b983ae75631399d80881644043a8"
GDK_VISUALS(INTEGER) = 1447, 1949
RESOURCE_MANAGER(STRING) =
"*customization:\t-color\nXcursor.

[kwin] [Bug 422324] Desktop offset horizontally from display

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
   Assignee|vlad.zahorod...@kde.org |rybak@gmail.com

--- Comment #11 from Andrei Rybak  ---
Created attachment 158607
  --> https://bugs.kde.org/attachment.cgi?id=158607=edit
Demonstration of a similar bug

Encountered a similar bug after restarting Plasma today (2023-05-01).  Screen
recording is attached. Output of `xwininfo` and `xprop` below:

```
$ xwininfo

xwininfo: Please select the window about which you
  would like information by clicking the
  mouse in that window.

xwininfo: Window id: 0x520001d "Desktop @ QRect(0,0 2560x1440)  — Plasma"

  Absolute upper-left X:  0
  Absolute upper-left Y:  0
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 160
  Height: 160
  Depth: 32
  Visual: 0xc5
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x520001c (not installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +0+0  -2400+0  -2400-1280  +0-1280
  -geometry 160x160+0+0

```


```
$ xprop
_NET_WM_USER_TIME(CARDINAL) = 1027480693
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP
_NET_WM_DESKTOP(CARDINAL) = 4294967295
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_BELOW
_KDE_NET_WM_DESKTOP_FILE(UTF8_STRING) = "org.kde.plasmashell"
XdndAware(ATOM) = BITMAP
WM_NAME(STRING) = "Desktop @ QRect(0,0 2560x1440) "
_NET_WM_NAME(UTF8_STRING) = "Desktop @ QRect(0,0 2560x1440)  — Plasma"
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x1, 0x0, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DESKTOP
_XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1
WM_CLIENT_LEADER(WINDOW): window id # 0x520001f
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
window id # of group leader: 0x520001f
WM_CLIENT_MACHINE(STRING) = "titov"
_NET_WM_PID(CARDINAL) = 743181
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 85983262
WM_CLASS(STRING) = "plasmashell", "plasmashell"
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING,
_NET_WM_SYNC_REQUEST
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified location: 0, 0
user specified size: 2560 by 1440
window gravity: Static
```

Version info:

```
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-38-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570
```

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

[kwin] [Bug 466834] KWin crashes in KWin::Window::isOnOutput() after opening Desktop Grid

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

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

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

[kwin] [Bug 467965] KWin crashes intermittently when switching to a window on a different virtual desktop

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

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

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

[kwin] [Bug 467965] New: KWin crashes intermittently when switching to a window on a different virtual desktop

[Andrei Rybak]

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

Bug ID: 467965
   Summary: KWin crashes intermittently when switching to a window
on a different virtual desktop
Classification: Plasma
   Product: kwin
   Version: 5.27.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rybak@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.27.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 5.19.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
1. Clicked on Chromium icon in Application launcher 
2. While Chromium is still opening switched to a Firefox window on a different
virtual desktop by pressing "Meta+1" - shortcut "Activate Task Manager Entry
1".
3. Once I was ready to use Chromium for what I opened it for, I clicked on its
button in the Task Manager widget
4. KWin crashed and restarted itself.

Notes:
- This isn't the first time KWin crashes in this way.
- I have a bunch of window rules for opening them on specific virtual desktops.
There is one for Firefox, but none for Chromium.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  KWin::OutputMode::size (this=0x7) at ./src/core/output.cpp:50
#5  0x7ff3f7bc4122 in KWin::Output::modeSize
(this=this@entry=0x55f5759eefa0) at ./src/core/output.cpp:194
#6  0x7ff3f7bc4341 in KWin::Output::pixelSize
(this=this@entry=0x55f5759eefa0) at ./src/core/output.cpp:199
#7  0x7ff3f7bc438f in KWin::Output::geometry (this=0x55f5759eefa0) at
./src/core/output.cpp:174
#8  0x7ff3f7ced7d4 in KWin::Window::isOnOutput (this=0x55f576b26e20,
output=) at ./src/window.cpp:428
#9  0x7ff3f7c8f72c in KWin::DesktopBackgroundItem::updateWindow
(this=this@entry=0x55f576cd67d0) at
./src/scripting/desktopbackgrounditem.cpp:112
#10 0x7ff3f7c8fad6 in KWin::DesktopBackgroundItem::setDesktop
(desktop=, this=0x55f576cd67d0) at
./src/scripting/desktopbackgrounditem.cpp:66
#11 KWin::DesktopBackgroundItem::setDesktop (desktop=,
this=0x55f576cd67d0) at ./src/scripting/desktopbackgrounditem.cpp:62
#12 KWin::DesktopBackgroundItem::qt_static_metacall
(_o=_o@entry=0x55f576cd67d0, _c=_c@entry=QMetaObject::WriteProperty,
_id=_id@entry=3, _a=_a@entry=0x7ffe838ea7e0) at
./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:148
#13 0x7ff3f7c8fd93 in KWin::DesktopBackgroundItem::qt_metacall
(this=0x55f576cd67d0, _c=QMetaObject::WriteProperty, _id=3, _a=0x7ffe838ea7e0)
at
./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:197
#14 0x7ff3f70f430e in QQmlPropertyData::writeProperty (flags=...,
value=0x7ffe838ea798, target=, this=) at
../../include/QtQml/5.15.8/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:393
#15 QObjectPointerBinding::write (this=0x55f576d8fdc0, result=...,
isUndefined=, flags=...) at qml/qqmlbinding.cpp:742
#16 0x7ff3f70f5b07 in QQmlNonbindingBinding::doUpdate (this=0x55f576d8fdc0,
watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:258
#17 0x7ff3f70f3664 in QQmlBinding::update (this=0x55f576d8fdc0, flags=...)
at qml/qqmlbinding.cpp:194
#18 0x7ff3f70d0165 in QQmlNotifier::emitNotify (endpoint=,
a=0x0) at qml/qqmlnotifier.cpp:104
#19 0x7ff3f62f3c5b in doActivate (sender=0x55f576db9810,
signal_index=27, argv=0x0) at kernel/qobject.cpp:3815
#20 0x7ff3f62f40d4 in QtPrivate::QSlotObjectBase::call (a=0x7ffe838ec3d0,
r=0x55f576db9810, this=0x55f576db9d40) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x55f575c33c30, signal_index=7,
argv=0x7ffe838ec3d0) at kernel/qobject.cpp:3923
#22 0x7ff3f62ed177 in QMetaObject::activate (sender=,
m=m@entry=0x7ff3f7fcfbc0 ,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffe838ec3d0)
at kernel/qobject.cpp:3983
#23 0x7ff3f7b93ad3 in KWin::VirtualDesktopManager::currentChanged
(this=, _t1=, _t2=) at
./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_virtualdesktops.cpp:622
#24 0x7ff3f7cd8148 in KWin::VirtualDesktopManager::setCurrent
(this=0x55f575c33c30, newDesktop=0x55f575d55620) at ./src/virtualdesktops.h:62
#25 0x7ff3f7bb4f0e in KWin::Workspace::activateWindow (this=0x55f575c0ca10,
window=0x55f575cd8c00, force=) at ./src/activation.cpp:294
#26 0x7ff3f6d29bb4 in NETRootInfo::event(xcb_generic_event_t*,
QFlags*, QFlags*) () from
/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5
#27 0x7ff3f7c61528 in KWin::RootInfoFilter::event (this=,
event=) at ./src/rootinfo_filter.cpp:26
#28 0x7ff3f7c49304 in KWin::Application::dispatchEvent (this=, event=0x7ff3e0031500) at ./src/main.cpp:483
#29 0x7ff3f62b9447 in 

[kwin] [Bug 466834] New: KWin crashes after opening Desktop Grid

[Andrei Rybak]

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

Bug ID: 466834
   Summary: KWin crashes after opening Desktop Grid
Classification: Plasma
   Product: kwin
   Version: 5.27.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rybak@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.27.1)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 5.19.0-32-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.1 [KCrashBackend]

-- Information about the crash:
This morning I noticed that desktop icons were missing (probably caused by
multiple KWin and Plasma restarts yesterday). I pressed Meta+S – shortcut for
"Show Desktop Grid" effect and then a KWin crash was reported.

I am using a laptop in clamshell mode with external monitor. Laptop resolution
is 1920x1080, the resolution of the external monitor is 2560x1440.

The crash does not seem to be reproducible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  KWin::OutputMode::size (this=0x3f80) at ./src/core/output.cpp:50
#5  0x7fa3f5fc3e52 in KWin::Output::modeSize
(this=this@entry=0x7fa3e80091d0) at ./src/core/output.cpp:194
#6  0x7fa3f5fc4071 in KWin::Output::pixelSize
(this=this@entry=0x7fa3e80091d0) at ./src/core/output.cpp:199
#7  0x7fa3f5fc40bf in KWin::Output::geometry (this=0x7fa3e80091d0) at
./src/core/output.cpp:174
#8  0x7fa3f60eb0a4 in KWin::Window::isOnOutput (this=0x561e02859e40,
output=) at ./src/window.cpp:428
#9  0x7fa3f6090d7c in KWin::DesktopBackgroundItem::updateWindow
(this=this@entry=0x561e02769740) at
./src/scripting/desktopbackgrounditem.cpp:112
#10 0x7fa3f6091126 in KWin::DesktopBackgroundItem::setDesktop
(desktop=, this=0x561e02769740) at
./src/scripting/desktopbackgrounditem.cpp:66
#11 KWin::DesktopBackgroundItem::setDesktop (desktop=,
this=0x561e02769740) at ./src/scripting/desktopbackgrounditem.cpp:62
#12 KWin::DesktopBackgroundItem::qt_static_metacall
(_o=_o@entry=0x561e02769740, _c=_c@entry=QMetaObject::WriteProperty,
_id=_id@entry=3, _a=_a@entry=0x7ffdb6383fb0) at
./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:148
#13 0x7fa3f60913e3 in KWin::DesktopBackgroundItem::qt_metacall
(this=0x561e02769740, _c=QMetaObject::WriteProperty, _id=3, _a=0x7ffdb6383fb0)
at
./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:197
#14 0x7fa3f54f430e in QQmlPropertyData::writeProperty (flags=...,
value=0x7ffdb6383f68, target=, this=) at
../../include/QtQml/5.15.8/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:393
#15 QObjectPointerBinding::write (this=0x561e02662330, result=...,
isUndefined=, flags=...) at qml/qqmlbinding.cpp:742
#16 0x7fa3f54f5b07 in QQmlNonbindingBinding::doUpdate (this=0x561e02662330,
watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:258
#17 0x7fa3f54f3664 in QQmlBinding::update (this=0x561e02662330, flags=...)
at qml/qqmlbinding.cpp:194
#18 0x7fa3f54d0165 in QQmlNotifier::emitNotify (endpoint=,
a=0x0) at qml/qqmlnotifier.cpp:104
#19 0x7fa3f46f3c5b in doActivate (sender=0x561e0255cec0,
signal_index=27, argv=0x0) at kernel/qobject.cpp:3815
#20 0x7fa3f46f40d4 in QtPrivate::QSlotObjectBase::call (a=0x7ffdb6385ba0,
r=0x561e0255cec0, this=0x561e0254c0a0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x561e0148acf0, signal_index=7,
argv=0x7ffdb6385ba0) at kernel/qobject.cpp:3923
#22 0x7fa3f46ed177 in QMetaObject::activate (sender=,
m=m@entry=0x7fa3f63cdc00 ,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffdb6385ba0)
at kernel/qobject.cpp:3983
#23 0x7fa3f5f93963 in KWin::VirtualDesktopManager::currentChanged
(this=, _t1=, _t2=) at
./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_virtualdesktops.cpp:622
#24 0x7fa3f60d7bf8 in KWin::VirtualDesktopManager::setCurrent
(this=0x561e0148acf0, newDesktop=0x561e016123a0) at ./src/virtualdesktops.h:62
#25 0x7fa3f5fb4c8e in KWin::Workspace::activateWindow (this=0x561e0141a5c0,
window=0x561e014e0eb0, force=) at ./src/activation.cpp:294
#26 0x7fa3f60b2743 in KWin::WorkspaceWrapper::qt_metacall
(this=this@entry=0x561e025f6f50, _c=_c@entry=QMetaObject::WriteProperty, _id=2,
_a=_a@entry=0x7ffdb6385d30) at
./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_workspace_wrapper.cpp:1047
#27 0x7fa3f60b2895 in KWin::DeclarativeScriptWorkspaceWrapper::qt_metacall
(this=0x561e025f6f50, _c=QMetaObject::WriteProperty, _id=,
_a=0x7ffdb6385d30) at
./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_workspace_wrapper.cpp:1423
#28 0x7fa3f548b46e in QQmlPropertyData::writeProperty (flags=...,
value=, target=, this=) at

[digikam] [Bug 466456] Ability to show filepath to image

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED

--- Comment #2 from Andrei  ---
(In reply to caulier.gilles from comment #1)
> Information is visible in Right sidebar, Properties tab.
> 
> https://i.imgur.com/Yptftby.png
> 
> Gilles Caulier

Thank you but it's hard to find out this info). BTW is it possible to copy full
path to the image to clipboard?

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

[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over

[Andrei Rybak]

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

--- Comment #6 from Andrei Rybak  ---
(In reply to zacharytalis from comment #4)
> you can prune these spam entries by editing "~/.local/share/user-places.xbel" 
> directly.

More instructions for manually cleaning up "~/.local/share/user-places.xbel" in
the Dolphin ticket: https://bugs.kde.org/show_bug.cgi?id=466420#c3

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

[digikam] [Bug 401458] Rename file name with recognized faces-tags

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||avmaksi...@yandex.ru

--- Comment #3 from Andrei  ---
I don't think so. Because there are many person on the photo. Better to find
this photo with a filter. I don't know is it possible now in digiKam or not.
If not the better the ability to do such a filter.

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

[digikam] [Bug 459499] The possibility to disable persons

[Andrei]

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

Andrei  changed:

   What|Removed |Added

   Platform|Kubuntu |unspecified
Version|7.8.0   |7.9.0
 OS|Linux   |All

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

[digikam] [Bug 459499] The possibility to disable persons

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||avmaksi...@yandex.ru

--- Comment #2 from Andrei  ---
I agree it would be nice also for ex wifes and husbands and their
relatives. It's our historym but it have to be in the past.

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

[digikam] [Bug 363724] Request for Search By Face

[Andrei]

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

Andrei  changed:

   What|Removed |Added

Version|5.0.0   |7.9.0
 OS|Linux   |All
   Platform|Other   |unspecified

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

[digikam] [Bug 363724] Request for Search By Face

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||avmaksi...@yandex.ru

--- Comment #1 from Andrei  ---
I think it would be doing automatically as it is in Picasa.

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

[digikam] [Bug 409995] Scan for Faces in video files is not yet supported

[Andrei]

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

Andrei  changed:

   What|Removed |Added

   Platform|Microsoft Windows   |unspecified

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

[digikam] [Bug 409995] Scan for Faces in video files is not yet supported

[Andrei]

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

Andrei  changed:

   What|Removed |Added

Version|6.1.0   |7.9.0

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

[digikam] [Bug 409995] Scan for Faces in video files is not yet supported

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||avmaksi...@yandex.ru

--- Comment #4 from Andrei  ---
About time. I don't see problem with it. I can run it at night.

But I see another problem with shouldn't be done before: to see similar faces
as one with some coefficient.

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

[digikam] [Bug 466455] "Open In File Manager" doesn't work

[Andrei]

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

--- Comment #2 from Andrei  ---
(In reply to caulier.gilles from comment #1)
> It work perfectly here under Kubuntu 22.04:
> 
> https://i.imgur.com/0T36aB8.mp4
> 
> Gilles Caulier

Ok. But what's the problem for my Ubuntu? digiKam doesn't show the problem.

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

[digikam] [Bug 466456] New: Ability to show filepath to image

[Andrei]

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

Bug ID: 466456
   Summary: Ability to show filepath to image
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Preview-Image
  Assignee: digikam-bugs-n...@kde.org
  Reporter: avmaksi...@yandex.ru
  Target Milestone: ---

STEPS TO REPRODUCE
1. Open in Preview
2. See at status bar or image tooltip (in image line)

OBSERVED RESULT
Only filename.

EXPECTED RESULT
Either filename with filepath either filename and filepath separately.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ununtu 22.10.
(available in About System)
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5

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

[digikam] [Bug 466455] New: "Open In File Manager" doesn't work

[Andrei]

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

Bug ID: 466455
   Summary: "Open In File Manager" doesn't work
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Preview-Image
  Assignee: digikam-bugs-n...@kde.org
  Reporter: avmaksi...@yandex.ru
  Target Milestone: ---

STEPS TO REPRODUCE
1. Open image in Preview.
2. Right click mouse and choose "Open In File Manager" by left click.

OBSERVED RESULT
Nothing happened.

EXPECTED RESULT
Opening in Files or Thunar or Dolphin or error message how to fix this error.
May be it would be choosing the File manager to open directory with this file.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 22.10
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5

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

[digikam] [Bug 466452] New: Ability to copy image to clipboard

[Andrei]

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

Bug ID: 466452
   Summary: Ability to copy image to clipboard
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Preview-Image
  Assignee: digikam-bugs-n...@kde.org
  Reporter: avmaksi...@yandex.ru
  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
***
It is very needed possibility. Sometimes when I recognize faces and manage my
albums I need to ask about it from my relatives and need to send the photo. So
the usual way it would be by pressing Ctrl+C but it doesn't work. Even I open
in pressing F4 I can't copy to clipboard (I mean the whole image).
Please add this ability in Preview Image at least.

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

[digikam] [Bug 459543] Feature request: Zoom to width

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||avmaksi...@yandex.ru

--- Comment #3 from Andrei  ---
Hello! If it would be fit only by width the some parts of image will be not
shown.

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

[dolphin] [Bug 466420] Add ability to delete devices from Dolphin faster

[Andrei Rybak]

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

--- Comment #3 from Andrei Rybak  ---
For those who don't mind editing Dolphin's data manually, zacharytalis proposed
a hacky solution over at https://bugs.kde.org/show_bug.cgi?id=466416#c4:

> For the time being, you can prune these spam entries by editing
> "~/.local/share/user-places.xbel" directly. (make sure to be careful and
> take a backup, yada yada)

I looked at the structure of this XML file, which consisted mostly of
 tags. Each bookmark has a  tag, which has the strings which I
was interested in -- the names of the phones. I grepped the file for all
 tags. I noticed that all the erroneous entries are clumped together:

> $ cd ~/.local/share
> $ grep '' user-places.xbel | uniq
> [...]
> Xiaomi
> Pixel 6A
> Xiaomi
> Pixel 6A
> Xiaomi
> Pixel 6A
> Xiaomi
> Pixel 6A
> Xiaomi
> Pixel 6A
> Xiaomi
> Pixel 6A
> Xiaomi
> Pixel 6A

So I did the following:

1. Found the first bookmark with the  of an erroneous entry
2. Started selection
3. Found the last erroneous bookmark
4. Made sure the selection starts at an opening tag  and ends at a
closing tag 
5. Deleted the whole selection

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

[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over

[Andrei Rybak]

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

--- Comment #5 from Andrei Rybak  ---
(In reply to zacharytalis from comment #4)
> For the time being, you can prune these spam entries by editing
> "~/.local/share/user-places.xbel" directly. (make sure to be careful and
> take a backup, yada yada)

It would have taken me a looong time to figure out where this is being stored.
Thank you for saving my sanity when using Dolphin and my time!

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #4 from Andrei Rybak  ---
I have created two new tickets with more details:

1. https://bugs.kde.org/show_bug.cgi?id=466416
2. https://bugs.kde.org/show_bug.cgi?id=466420

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

[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over

[Andrei Rybak]

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

--- Comment #3 from Andrei Rybak  ---
In the video, one can see that the name of the phantom entries in the list is
different for the last couple of dozen items — that's roughly the number of
days that I've had a new phone that connects to the same computer via KDE
Connect.

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

[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over

[Andrei Rybak]

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

--- Comment #2 from Andrei Rybak  ---
> ADDITIONAL INFORMATION
> Right now there is no simple way to delete these phantom entries
> from Dolphin interface in a fast way. I will also create a Dolphin bug
> to add a feature to delete the devices from this panel faster.

Created new bug: https://bugs.kde.org/show_bug.cgi?id=466420

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

[dolphin] [Bug 466420] Add ability to delete devices from Dolphin faster

[Andrei Rybak]

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

--- Comment #2 from Andrei Rybak  ---
Created attachment 156721
  --> https://bugs.kde.org/attachment.cgi?id=156721=edit
Only three panels of Dolphin in Component field on bugs.kde.org

Here are two screenshots showing the missing value for "Component" field for
Dolphin on bugs.kde.org — the issue that I mentioned in the "ADDITIONAL
INFORMATION" section.

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

[dolphin] [Bug 466420] Add ability to delete devices from Dolphin faster

[Andrei Rybak]

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

--- Comment #1 from Andrei Rybak  ---
Created attachment 156720
  --> https://bugs.kde.org/attachment.cgi?id=156720=edit
Four panels in Dolphin

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

[dolphin] [Bug 466420] New: Add ability to delete devices from Dolphin faster

[Andrei Rybak]

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

Bug ID: 466420
   Summary: Add ability to delete devices from Dolphin faster
Classification: Applications
   Product: dolphin
   Version: 22.12.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: rybak@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 156719
  --> https://bugs.kde.org/attachment.cgi?id=156719=edit
screen recording of steps to reproduce and observed result

SUMMARY
There is a bug – https://bugs.kde.org/show_bug.cgi?id=466416 – that causes too
many entries being added to the Dolphin's panel "Places". If that bug is ever
fixed, it would be nice to get rid of the wrong entries. It would be a good
addition to the wonderful UI of Dolphin if it could allow its users to delete
these incorrect entries in some _fast_ way.


STEPS TO REPRODUCE
1. Open Dolphin on a computer affected by
https://bugs.kde.org/show_bug.cgi?id=466416
2. Try selecting multiple devices at once.
3. Try removing a device using the Delete key
4. Remove a device using the context menu

OBSERVED RESULT
For step 2 — there is no way to select multiple devices at once.
For step 3 — the "Selection mode" turns on 
For step 4 — Dolphin freezes. I don't actually know if a device gets removed or
not — I don't know how to count them in an easy way. On the screen recording
I'm trying to 1) resize the window - it doesn't work, 2) click on the "Cancel"
button (it doesn't work) and 3) click on the close application button in the
top right (it doesn't work).

EXPECTED RESULT
- There is a way to select multiple devices at once, similar to how it is
possible to select multiple folders or files in the main panel of Dolphin
- There is some kind of shortcut to delete devices while navigating the panel
"Places" via keyboard, without having to open the context menu
- Dolphin doesn't freeze

SOFTWARE/OS VERSIONS

> $ apt show dolphin 2>/dev/null | head -2
> Package: dolphin
> Version: 4:22.12.2-0xneon+22.04+jammy+release+build16

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-32-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570


ADDITIONAL INFORMATION
Value "panels: places" is missing from the "Component:" field when creating a
new bug on https://bugs.kde.org/enter_bug.cgi?product=dolphin

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

[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over

[Andrei Rybak]

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

--- Comment #1 from Andrei Rybak  ---
> $ apt show kdeconnect 2>/dev/null | head -2
> Package: kdeconnect
> Version: 22.12.2-0xneon+22.04+jammy+release+build21

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

[kdeconnect] [Bug 466416] New: KDE Connect keeps adding devices to Dolphin over and over and over and over and over

[Andrei Rybak]

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

Bug ID: 466416
   Summary: KDE Connect keeps adding devices to Dolphin over and
over and over and over and over
Classification: Applications
   Product: kdeconnect
   Version: 22.12.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: rybak@gmail.com
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

Created attachment 156717
  --> https://bugs.kde.org/attachment.cgi?id=156717=edit
Unusable Dolphin due to overlong "Devices" section in the panel "Places"

SUMMARY
The section "Devices" in Dolphin becomes unusable, because KDE Connect keeps
adding a new line to the section "Devices", it seems, every single time the
phone is connected to the computer.

STEPS TO REPRODUCE
1. Use KDE Connect for a prolonged period of time, make sure that the phone(s)
connect and disconnect from the network that PC is on multiple times.
2. Open Dolphin.
3. Unhide the section "Devices" in the "Places" panel.

OBSERVED RESULT
Watch the screen recording please.

EXPECTED RESULT
Something sensible, that doesn't require you to scroll for how long the video
is.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-32-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

ADDITIONAL INFORMATION
Right now there is no simple way to delete these phantom entries from Dolphin
interface in a fast way. I will also create a Dolphin bug to add a feature to
delete the devices from this panel faster.

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

[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||tdhj744ra...@opayq.com

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

[kdeconnect] [Bug 466256] New: It is hard to distinguish "KDE Connect" app from "KDE Connect" section in Application Launcher

[Andrei Rybak]

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

Bug ID: 466256
   Summary: It is hard to distinguish "KDE Connect" app from "KDE
Connect" section in Application Launcher
Classification: Applications
   Product: kdeconnect
   Version: 22.12.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: rybak@gmail.com
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

Created attachment 156613
  --> https://bugs.kde.org/attachment.cgi?id=156613=edit
State of the Application Launcher after the third step

SUMMARY
When typing "kde connect" in the Application Launcher, it is hard to
distinguish the "KDE Connect" app proper from the section of System Settings
which is also titled "KDE Connect".

STEPS TO REPRODUCE
1. Open Application Launcher
2. Type "kde connect" into the search field
3. Read the top three results

OBSERVED RESULT
Top three search results:
1. The app proper with hint "Device Synchronization".
2. "KDE Connect SMS", easily distinguishable from the other two.
3. The section of System Settings with hint "Connect and sync your devices"

EXPECTED RESULT
Hints that help distinguish the app proper from the section of System Settings.
For example, the System Settings hint could be "Change settings of KDE
Connect".

ADDITIONAL INFORMATION\
- It doesn't seem that the string "Connect and sync your devices" appears
anywhere in the UI of the System Settings, but I could be missing some place
where it is shown, like in a tooltip or something.
- I've found the strings in code:
  -
https://invent.kde.org/network/kdeconnect-kde/-/blob/master/app/org.kde.kdeconnect.app.desktop#L52
  -
https://invent.kde.org/network/kdeconnect-kde/-/blob/master/kcm/kcm_kdeconnect.json#L5
  and don't mind creating a pull request myself.

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

[kaddressbook] [Bug 465888] New: Wrong encoding in address label (ADR;LABEL=...)

[Andrei]

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

Bug ID: 465888
   Summary: Wrong encoding in address label (ADR;LABEL=...)
Classification: Applications
   Product: kaddressbook
   Version: 5.21.1
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: tdhj744ra...@opayq.com
CC: to...@kde.org
  Target Milestone: ---

Created attachment 156343
  --> https://bugs.kde.org/attachment.cgi?id=156343=edit
Test contact

STEPS TO REPRODUCE
1. Consider the following vcard:
```
BEGIN:VCARD
VERSION:4.0
FN:Алиса
N:Алиса
ADR;TYPE=home;LABEL=тест:;;тест
END:VCARD
```
2. Import it
3. Open edit window
4. Go to Location tab
5. Notice 

OBSERVED RESULT
Label for the address in address list is unreadable, has wrong encoding
Screenshot: https://imgur.com/QA6uo5Y

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
If you export this contact, encoding is ok again. But when using some external
sources for contacts (e.g. EteSync), it uploads contact with broken encoding.

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

[krita] [Bug 465714] Assertion failure when attempting to open a PSD

[Andrei Alexeyev]

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

Andrei Alexeyev  changed:

   What|Removed |Added

 CC||ak...@taisei-project.org

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

[krita] [Bug 465714] New: Assertion failure when attempting to open a PSD

[Andrei Alexeyev]

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

Bug ID: 465714
   Summary: Assertion failure when attempting to open a PSD
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: ak...@taisei-project.org
  Target Milestone: ---

Created attachment 156230
  --> https://bugs.kde.org/attachment.cgi?id=156230=edit
Full stack trace with locals

SUMMARY

Attempting to open a particular PSD file crashes Krita with an assertion
failure.


STEPS TO REPRODUCE

Open the affected file with Krita and wait.

Unfortunately, I am not permitted to distribute this file publicly, but I think
I can send it to a verified active Krita developer privately. Please contact me
on IRC (Akari @ libera.chat) or by email (ak...@taisei-project.org), with some
way to verify your identity.


OBSERVED RESULT

ASSERT (krita): "embeddedResources.last().data()" in file
/home/abuild/rpmbuild/BUILD/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp,
line 750

Stack trace from the relevant thread:

#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x75495503 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2  0x75442e16 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7542b89c in __GI_abort () at abort.c:79
#4  0x75abb0db in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#5  QMessageLogger::fatal (this=this@entry=0x7fffbe00,
msg=msg@entry=0x77f7b0ab "%s") at global/qlogging.cpp:893
#6  0x77f76fb3 in kis_assert_common(char const*, char const*, int,
bool, bool) [clone .constprop.0] (assertion=assertion@entry=0x77415970
"embeddedResources.last().data()", file=file@entry=0x77415850
"/home/abuild/rpmbuild/BUILD/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp",
line=line@entry=750, isIgnorable=isIgnorable@entry=false,
throwException=) at
/usr/src/debug/krita-5.1.5/libs/global/kis_assert.cpp:89
#7  0x77f3e7a7 in kis_assert_exception
(assertion=assertion@entry=0x77415970 "embeddedResources.last().data()",
file=file@entry=0x77415850
"/home/abuild/rpmbuild/BUILD/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp",
line=line@entry=750) at
/usr/src/debug/krita-5.1.5/libs/global/kis_assert.cpp:112
#8  0x7739fbe2 in KisAslLayerStyleSerializer::fetchEmbeddedResources
(style=0x5bc5e890) at
/usr/src/debug/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp:750
#9  0x773c0639 in KisPSDLayerStyle::embeddedResources (this=, globalResourcesInterface=...) at
/usr/src/debug/krita-5.1.5/libs/image/kis_psd_layer_style.cpp:396
#10 0x775b4237 in KoResource::requiredResources
(this=this@entry=0x5bc5e890, globalResourcesInterface=...) at
/usr/src/debug/krita-5.1.5/libs/resources/KoResource.cpp:242
#11 0x773c0dd8 in
KisRequiredResourcesOperators::createLocalResourcesSnapshot
(globalResourcesInterface=..., object=0x5bc5e890) at
/usr/src/debug/krita-5.1.5/libs/resources/KisRequiredResourcesOperators.h:60
#12
KisRequiredResourcesOperators::cloneWithResourcesSnapshot,
KisPSDLayerStyle> (globalResourcesInterface=..., object=0x67689060) at
/usr/src/debug/krita-5.1.5/libs/resources/KisRequiredResourcesOperators.h:91
#13 KisPSDLayerStyle::cloneWithResourcesSnapshot
(this=this@entry=0x67689060, globalResourcesInterface=...,
canvasResourcesInterface=...) at
/usr/src/debug/krita-5.1.5/libs/image/kis_psd_layer_style.cpp:335
#14 0x7fffb40ec0d7 in PSDLoader::decode (this=, io=...) at
/usr/src/debug/krita-5.1.5/plugins/impex/psd/psd_loader.cpp:419
#15 0x7fffb40ee8c1 in PSDLoader::buildImage (io=..., this=0x7fffc6c0)
at /usr/src/debug/krita-5.1.5/plugins/impex/psd/psd_loader.cpp:432
#16 psdImport::convert (this=, document=0x5f2e1470,
io=0x7fffc730) at
/usr/src/debug/krita-5.1.5/plugins/impex/psd/psd_import.cc:29
#17 0x77c2201a in KisImportExportManager::doImport
(this=0x5b9a7510, location=..., filter=...) at
/usr/src/debug/krita-5.1.5/libs/ui/KisImportExportManager.cpp:667
#18 0x77c24000 in KisImportExportManager::convert (this=0x5b9a7510,
direction=, location=..., realLocation=..., mimeType=...,
showWarnings=, exportConfiguration=..., isAsync=,
isAdvancedExporting=) at
/usr/src/debug/krita-5.1.5/libs/ui/KisImportExportManager.cpp:376
#19 0x77c24f25 in KisImportExportManager::importDocument
(this=, location=..., mimeType=...) at
/usr/src/debug/krita-5.1.5/libs/global/kis_shared_ptr.h:206
#20 0x77c0b492 in KisDocument::openFile (this=0x5f2e1470) at
/usr/src/debug/krita-5.1.5/libs/ui/KisDocument.cpp:1874
#21 0x77c19749 in KisDocument::openPathInternal 

[plasmashell] [Bug 381266] Icontasks identifying Chrome apps as Chrome windows

[Andrei]

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

--- Comment #19 from Andrei  ---
I've updated my post on this above.
TLDR: no scripts needed, just use separate class and --user-data-dir for
separate apps. E.g.:
`chromium --app=https://example.com --class=webapp-one
--user-data-dir=/tmp/webapp-one`
and
`chromium --app=https://example.com --class=webapp-two
--user-data-dir=/tmp/webapp-two`
— these won't be grouped.

At least this works for me for quite some time.

Example .desktop file:
```
[Desktop Entry]
Name=Gmail
Exec=chromium --app=https://gmail.com --class=webapp-gmail
--user-data-dir=/home/x/.local/share/webapps/gmail
Icon=/home/x/Pictures/Icons/Gmail.png
Type=Application
```

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

[systemsettings] [Bug 415770] Environment variable 'GTK2_RC_FILES' is ignored

[Andrei]

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

Andrei  changed:

   What|Removed |Added

 CC||tdhj744ra...@opayq.com
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #6 from Andrei  ---
Same issue:
Operating System: Kubuntu 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

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

[kwin] [Bug 422324] Desktop offset horizontally from display

[Andrei Rybak]

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

--- Comment #10 from Andrei Rybak  ---
I haven't encountered this bug since 2021, but if I do, I'll make sure to do
both xprop and xwininfo.

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

[systemsettings] [Bug 431960] Add explanatory text to field "Applications to be excluded from sessions"

[Andrei Rybak]

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

--- Comment #5 from Andrei Rybak  ---
Woohoo!

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

--- Comment #3 from Andrei Rybak  ---
Patrick Silva, I'm sorry, there might be some kind of misunderstanding. I
should have made it more clear. Depending on how long the user have been using
KDE Connect, it may have caused hundreds and hundreds of erroneous devices to
appear in Dolphin.

Please watch the video I have attached to this bug report. Manually fixing this
problem one entry at a time is out of the question.

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||dolphin-bugs-n...@kde.org

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

[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager

[Andrei Rybak]

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

Andrei Rybak  changed:

   What|Removed |Added

 CC||rybak@gmail.com

--- Comment #1 from Andrei Rybak  ---
Created attachment 153889
  --> https://bugs.kde.org/attachment.cgi?id=153889=edit
demonstration of the bug

This gets so bad, that I just have to hide the "Devices" section in Dolphin
completely.

Question: is it possible that this is a Dolphin bug?

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

[kwin] [Bug 461626] Applications are not showing fullscreen in Plasma Mobile session

[Andrei Kozlov]

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

--- Comment #8 from Andrei Kozlov  ---
https://invent.kde.org/plasma/kwin/-/merge_requests/3184

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

[kwin] [Bug 461626] Applications are not showing fullscreen in Plasma Mobile session

[Andrei Kozlov]

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

--- Comment #7 from Andrei Kozlov  ---
1. Start Plasma Mobile session
2. Launch kate
3. Select File/Save

Save File dialog is not fullscreen.

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

[kwin] [Bug 461626] Applications are not showing fullscreen in Plasma Mobile session

[Andrei Kozlov]

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

--- Comment #6 from Andrei Kozlov  ---
In other cases app fullscreen

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

[kwin] [Bug 461626] Applications are not showing fullscreen in Plasma Mobile session

[Andrei Kozlov]

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

--- Comment #5 from Andrei Kozlov  ---
not fullscreen only for
1. Start Plasma Mobile session
2. Launch konsole
3. Show virtual keyboard
4. Launch kate from konsole using physical keyboard

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