[frameworks-baloo] [Bug 487628] Baloo file indexer crashes on addition of new file

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #9 from Stefan Brüns  ---
Apparently the KFileMetaData PNG extractor crashes when trying to extract
metadata from a file.

The problem is the Qt PBF plugin, notable lines from the backtrace:


#12 0x7c88e588ce5b in QMessageLogger::fatal
(this=this@entry=0x7ffe640369b0, msg=msg@entry=0x7c88e4f00890 "QFontDatabase:
Must construct a QGuiApplication before accessing QFontDatabase") at
/usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:889
#13 0x7c88e48e2220 in QFontDatabasePrivate::ensureFontDatabase () at
/usr/src/debug/qt6-base/qtbase/src/gui/text/qfontdatabase.cpp:1333
#20 0x7c48cf7b599a in Style::load (this=, fileName=...) at
../QtPBFImagePlugin-3.0/src/style.cpp:598
#21 0x7c48cf7aaf66 in PBFPlugin::PBFPlugin (this=0x55b64f663120,
this=) at ../QtPBFImagePlugin-3.0/src/pbfplugin.cpp:16
#23 0x7c88e5b9f6c3 in QLibraryPrivate::pluginInstance (this=0x55b64f6bdb00)
at /usr/src/debug/qt6-base/qtbase/src/corelib/plugin/qlibrary.cpp:516
#27 0x7c88e493fb58 in QImageReader::canRead
(this=this@entry=0x7ffe64038368) at
/usr/src/debug/qt6-base/qtbase/src/gui/image/qimagereader.cpp:1123
---

IMHO, the Qt PBF plugin is misbehaving here, as it violates the contract from
QImageReader:

https://doc.qt.io/qt-6/qimagereader.html#canRead
> canRead() is a lightweight function that only does a quick test to see if the 
> image data is valid.

This is a known problem of the PBF plugin:
https://github.com/tumic0/QtPBFImagePlugin/issues/7

baloo_file_extractor was changed from QGuiApplication to QCoreApplication
recently:
https://invent.kde.org/frameworks/baloo/-/merge_requests/192

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

[kwin] [Bug 482978] Colorblindness Correction effect causes blurs on a 1.25x/1.75x scaled screen

[Stefan Springer]

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

Stefan Springer  changed:

   What|Removed |Added

 CC||stefansp...@gmail.com

--- Comment #2 from Stefan Springer  ---
Possibly related: https://bugs.kde.org/show_bug.cgi?id=483224

Please fix! This breaks customization for every Plasma 6 user with fractional
scaling, especially since being able to scale via specifying font DPI as a
workaround isn't available anymore.

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

[kwin] [Bug 483224] Blurry fonts when global scaling is set to 125%

[Stefan Springer]

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

Stefan Springer  changed:

   What|Removed |Added

 CC||stefansp...@gmail.com

--- Comment #8 from Stefan Springer  ---
@popov895 @Debby are you by chance using Lightlyshaders, KDE-Rounded-Corners,
Colorblindness Correction, Invert or any such kwin effect? Seemingly, kwin
doesn't handle them properly when using fractional scaling on wayland.

Possibly related: https://bugs.kde.org/show_bug.cgi?id=482978

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

[frameworks-baloo] [Bug 343437] Do not Index NFS

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Stefan Brüns  ---
Network shares are excluded in current versions (i.e. for the last ~5 years).

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

[frameworks-baloo] [Bug 481785] Torture testing for Baloo

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WORKSFORME

--- Comment #6 from Stefan Brüns  ---
(In reply to Alejandro Nova from comment #0)
> At the request of the maintainer, I’m filling a bug against Baloo to upload
> a file that will be used to torture the File Indexer. 
> 
> File: History of the Chilean Constitution (volume 1)
> License: Public domain (according to Chilean Law)
> Length: 1.155 pages, including accented text

You left out any information what is not working for you ...

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

[frameworks-baloo] [Bug 480665] KDE Neon 5.27.10: baloo significantly slows down file copying to a usb device

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #9 from Stefan Brüns  ---
(In reply to Martin Tlustos from comment #3)
> As I said, copying with cp was a lot faster. I guess, dolphin and baloo have
> some kind of connection that slows dolphin down in copying even when the
> folder is an indexed one.

If copying with cp is faster, the slowdown is obviously not baloo's fault.

But you should use `cp` correctly, it will report 'finished' when everything is
'written' to the cache, not when the data has actually been flushed to the
disk.

Use "cp ... && sync".

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

[Craft] [Bug 486467] MacOS X builds failing on CI due to signing tool not liking files that can't be blacklisted

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

   Assignee|vonr...@kde.org |stefan.gerlach@uni-konstanz
   ||.de
 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from Stefan Gerlach  ---
Signing was done using the qt5-lts branch so blacklist must be changed in this
branch.

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

[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink

[Stefan Krüger]

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

--- Comment #12 from Stefan Krüger  ---
Created attachment 169332
  --> https://bugs.kde.org/attachment.cgi?id=169332=edit
showing the audio systemtray window with selected *default* source

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

[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink

[Stefan Krüger]

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

Stefan Krüger  changed:

   What|Removed |Added

 CC||m...@s-light.eu

--- Comment #11 from Stefan Krüger  ---
i see a very similar pattern:
i have a *combined sink* (to split up my system audio to multiple sources)
and if my audio player is selected to play directly on my usb audio device the
key-shortcuts / systemtray AudioVolume thing does not show / handle the right
device..
if i switch the audio player app and reslecte the default in the widget it
works with the combined one.
i would like to use the shortcuts for the real usb audio  device...
if i then select the USB-Audio Device as *default* and then use application tab
and change the audioplayer to the combined device it works as i like it..

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

[krdc] [Bug 485094] When click Scale button image disappears

[Stefan Becker]

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

Stefan Becker  changed:

   What|Removed |Added

 CC||chemob...@gmail.com

--- Comment #1 from Stefan Becker  ---
When krdc is running in "window mode", i.e. not full screen, there is only the
"Scale" button. When you click that, the (VNC) session output is scaled down to
1x1, i.e. it "disappears".

I happened to switch the session to full screen mode and hold and behold:
**there is a SLIDER right of the scale button!** It shows the wrong setting,
i.e. 0%, but once you move the slider, the session output is correctly scaled.

And the best part is: now krdc remembers the chosen scale value for the
session, i.e. when you next time open krdc and open the session it remembers
the values correctly and the session is scaled. Now I can use my VNC session
again on a high resolution display.

Fedora 40 x86_64
krdc 24.02.2 (with deadlock fix for VNC plugin applied)
KDE Frameworks 
Version 6.1.0
Qt 
Version 6.7.0 (built against 6.7.0)
The wayland windowing system

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

[Craft] [Bug 486467] New: MacOS X builds failing on CI due to signing tool not liking files that can't be blacklisted

[Stefan Gerlach]

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

Bug ID: 486467
   Summary: MacOS X builds failing on CI due to signing tool not
liking files that can't be blacklisted
Classification: Developer tools
   Product: Craft
   Version: unspecified
  Platform: Other
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: vonr...@kde.org
  Reporter: stefan.gerl...@uni-konstanz.de
CC: kde-wind...@kde.org
  Target Milestone: ---

SUMMARY

Current CI build of LabPlot on macOS fail due to signing tool disliking added
files. I was not able to blacklist these files.

2024-04-26 14:39:18,588 DEBUG sftpnotary.util stderr:
b'Executable=/Users/gitlab/ws/builds/GZwHuM5x/0/education/labplot/macos-64-clang/build/kde/applications/labplot/archive/Applications/KDE/labplot2.app/Contents/MacOS/labplot2\nIdentifier=org.kde.labplot\nFormat=app
bundle with Mach-O thin (x86_64)\nCodeDirectory v=20400 size=81683
flags=0x0(none) hashes=2546+3 location=embedded\nSignature
size=8996\nTimestamp=26 Apr 2024 at 14:38:48\nInfo.plist
entries=17\nTeamIdentifier=5433B4KXM8\nSealed Resources version=2 rules=13
files=7337\nInternal requirements count=1 size=176\n'
2024-04-26 14:39:18,588 INFO sftpnotary.util Running ['codesign', '--verify',
'--verbose', '--strict', '--deep',
PosixPath('/Users/gitlab/ws/builds/GZwHuM5x/0/education/labplot/macos-64-clang/build/kde/applications/labplot/archive/Applications/KDE/labplot2.app')]
...
2024-04-26 14:39:20,596 ERROR sftpnotary.util The process exited with 1
2024-04-26 14:39:20,596 DEBUG sftpnotary.util stdout:
b'file added:
/Users/gitlab/ws/builds/GZwHuM5x/0/education/labplot/macos-64-clang/build/kde/applications/labplot/archive/Applications/KDE/labplot2.app/Contents/Frameworks/libhdf5.settings\nfile
added:
/Users/gitlab/ws/builds/GZwHuM5x/0/education/labplot/macos-64-clang/build/kde/applications/labplot/archive/Applications/KDE/labplot2.app/Contents/Frameworks/systemd/user/plasma-kglobalaccel.service\nfile
added:
/Users/gitlab/ws/builds/GZwHuM5x/0/education/labplot/macos-64-clang/build/kde/applications/labplot/archive/Applications/KDE/labplot2.app/Contents/Frameworks/libnetcdf.settings\n'
2024-04-26 14:39:20,596 DEBUG sftpnotary.util stderr:
b'/Users/gitlab/ws/builds/GZwHuM5x/0/education/labplot/macos-64-clang/build/kde/applications/labplot/archive/Applications/KDE/labplot2.app:
a sealed resource is missing or invalid\n'
Error: Running codesign failed

STEPS TO REPRODUCE
1.  Run CI build of LabPlot master (includes macOS builds)
2. 
3. 

OBSERVED RESULT
CI build fails signing

EXPECTED RESULT
CI build not failing

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

ADDITIONAL INFORMATION

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

[krdc] [Bug 486178] VNC plugin deadlocks on connection

[Stefan Becker]

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

--- Comment #5 from Stefan Becker  ---
I can confirm that after applying the patch VNC connections work again with
krdc.

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

[krdc] [Bug 485215] KRDC hangs when trying to connect to VNC host

[Stefan Becker]

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

Stefan Becker  changed:

   What|Removed |Added

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

--- Comment #6 from Stefan Becker  ---
Yeah, that looks like the same issue.

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

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

[krdc] [Bug 486178] VNC plugin deadlocks on connection

[Stefan Becker]

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

Stefan Becker  changed:

   What|Removed |Added

 CC||chemob...@gmail.com

--- Comment #4 from Stefan Becker  ---
*** Bug 485215 has been marked as a duplicate of this bug. ***

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

[LabPlot2] [Bug 485789] Labplot cannot detect latex typesetting engine

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

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

--- Comment #2 from Stefan Gerlach  ---
Should be fixed now in master (upcoming version 2.11). See
https://invent.kde.org/education/labplot/-/merge_requests/517

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

[krdc] [Bug 485215] KRDC hangs when trying to connect to VNC host

[Stefan Becker]

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

--- Comment #3 from Stefan Becker  ---
(In reply to foxfire-auspex from comment #2)
> 
> I'm not sure that I've encountered the exact same bug, but they're
> superficially similar enough that I'll just add my information here.

Your bug is not a bug, I fear. The log clearly shows that FreeRDP crypto
rejects the self-signed certificate offered by the RDP host. After that the
connection is closed. KRDC does *NOT* freeze up as it does with VNC
connections.

> KRDC: Starting RDP session
> [13:52:25:888] [18828:18828] [WARN][com.freerdp.crypto] - Certificate
> verification failure 'self-signed certificate (18)' at stack position 0
> [13:52:25:888] [18828:18828] [WARN][com.freerdp.crypto] - CN =
> SHARED-W10-VM.campoint.net

I'm not sure if KRDC/FreeRDP has an option/dialog to ignore certificate errors.
There may also have been a tightening of system TLS security settings in Fedora
40 (there have been several rounds of that in the last releases), which you
would need to loosen to be able to connect.

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

[LabPlot2] [Bug 485789] Labplot cannot detect latex typesetting engine

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

   Assignee|alexander.se...@web.de  |stefan.gerlach@uni-konstanz
   ||.de
 CC||stefan.gerlach@uni-konstanz
   ||.de
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Stefan Gerlach  ---
Using native apps (like latex) in a Flatpak is not allowed by the sandboxed
design of Flatpaks. There are ways around this (see
https://discourse.flathub.org/t/using-native-texlive-with-flatpak-apps/2363)
but we haven't tried yet what works for using TexLive in a LabPlot Flatpak.
Please let us know if you have any experience.

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

[dolphin] [Bug 486111] New: Dolphin Crash beim Kopieren

[Stefan]

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

Bug ID: 486111
   Summary: Dolphin Crash beim Kopieren
Classification: Applications
   Product: dolphin
   Version: 21.12.3
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: tuxyl...@web.de
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (21.12.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 6.8.0-76060800daily20240311-generic x86_64
Windowing System: X11
Distribution: Pop!_OS 22.04 LTS
DrKonqi: 5.24.5 [KCrashBackend]

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


Es wurden Dateien von einer lokalen SSD auf ein Netzlaufwerk kpopiert.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x7c68706b9bc2 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7c687136c702 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x7c68706b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7c68713b094b in QWidget::setParent(QWidget*, QFlags)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7c68713b0dee in QWidgetPrivate::init(QWidget*,
QFlags) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7c687157c403 in QDialog::QDialog(QWidget*, QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7c68725b27fc in KIO::SkipDialog::SkipDialog(QWidget*,
QFlags, QString const&) () from
/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#11 0x7c68725ba5f1 in KIO::WidgetsAskUserActionHandler::askUserSkip(KJob*,
QFlags, QString const&) () from
/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#12 0x7c68722f8e20 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#13 0x7c68706f1793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7c6871b3fe70 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#15 0x7c6871b443db in KJob::finishJob(bool) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#16 0x7c68706f1793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7c6871b3fe70 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#18 0x7c6871b443db in KJob::finishJob(bool) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#19 0x7c68706f1793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7c687231cd1a in KIO::SlaveInterface::error(int, QString const&) ()
from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#21 0x7c687231ee77 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#22 0x7c687231d47d in KIO::SlaveInterface::dispatch() () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#23 0x7c6872321ba2 in KIO::Slave::gotInput() () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#24 0x7c68706f1793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7c68706e741e in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7c687136c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7c68706b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7c68706bcf27 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7c6870713a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7c686e520d3b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7c686e576258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x7c686e51e3e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x7c68707130b8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x7c68706b875b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#35 0x7c68706c0cf4 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x62b4a6138ade in ?? ()
#37 0x7c686fc29d90 in __libc_start_call_main
(main=main@entry=0x62b4a6133260, argc=argc@entry=1,
argv=argv@entry=0x7ffde7d84588) at ../sysdeps/nptl/libc_start_call_main.h:58
#38 0x7c686fc29e40 in __libc_start_main_impl (main=0x62b4a6133260, argc=1,
argv=0x7ffde7d84588, init=, fini=,
rtld_fini=, stack_end=0x7ffde7d84578) at ../csu/libc-start.c:392
#39 0x62b4a6139265 in ?? ()
[Inferior 1 (process 343850) detached]

[frameworks-baloo] [Bug 484828] [Enhancement] Have Baloo split camelCase words

[Stefan Brüns]

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

--- Comment #5 from Stefan Brüns  ---
(In reply to tagwerk19 from comment #4)
> (In reply to Stefan Brüns from comment #2)

> The question is what "traps for unwary" look like in other languages...

German: BAFöG, MwSt, GmbH ;-)

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

[frameworks-baloo] [Bug 484828] [Enhancement] Have Baloo split camelCase words

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #2 from Stefan Brüns  ---
CamelCase is not actually something which can be trivially split.

Yes, it would work for the cases you presented, but there are too many cases
where it would not work, e.g. mixed-case acronyms. While these are not very
common for english acronyms, baloo also has to work for other languages. Also,
trademark names often have mixed cases (either because they are actually
acronyms, to let them stand out, or to just make them trademark-able at all).

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

[Elisa] [Bug 485262] Only plays one song from playlist and then stops

[Stefan Becker]

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

--- Comment #4 from Stefan Becker  ---
Confirmed: problem is no longer reproducible with 24.02.2.

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

[Elisa] [Bug 485262] Only plays one song from playlist and then stops

[Stefan Becker]

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

--- Comment #2 from Stefan Becker  ---
Reproduced the problem on a 2nd machine with Fedora 40 Beta.

I have tried with Ogg Vorbis (.ogg) and FLAC files.

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

[Elisa] [Bug 485262] New: Only plays one song from playlist and then stops

[Stefan Becker]

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

Bug ID: 485262
   Summary: Only plays one song from playlist and then stops
Classification: Applications
   Product: Elisa
   Version: 24.02.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: chemob...@gmail.com
  Target Milestone: ---

SUMMARY

Elisa stops playing after the end of the current track on the playlist.

STEPS TO REPRODUCE
1. select "Clear All" in playlist side bar
2. select "Play" icon on an album in the albums tab to create new playlist and
start playing first track

OBSERVED RESULT

Elisa plays first track from playlist and then stops.

EXPECTED RESULT

Elisa should continue and play the next song on the playlist

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.2-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

* this seems to be regression compared to Plasma5/Qt5 version. It used to work
fine on Fedora 39
* I tried different playlist repeat modes: same result
* I removed all Elisa related configuration from my home directory and tried
again: same result

When I run Elisa from the command line I get the following message at the end
of the first track from the playlist

. rest of log messages removed
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
# message after song ends:
[vorbis @ 0x55e3d1eeda80] Could not update timestamps for discarded
samples.
# selected the next song on playlist, played that and at the end again...
[vorbis @ 0x55e3d1eeda80] Could not update timestamps for discarded
samples.
...
# cleared the playlist and added an album with FLAC tracks
# no message at the end of the tracks...

It seems that this vorbis message is not the root cause for the problem.

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

[krdc] [Bug 485215] KRDC hangs when trying to connect to VNC host

[Stefan Becker]

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

--- Comment #1 from Stefan Becker  ---
Just found a RDP host @ work. Connection with krdc works, it checks the
certificate and then asks to username & password (I have no login there). So I
assume that the RDP plugin is fully working and only the VNC plugin is broken.

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

[krdc] [Bug 485215] New: [Plasma 6 REGRESSION] KRDC hangs when trying to connect to VNC host

[Stefan Becker]

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

Bug ID: 485215
   Summary: [Plasma 6 REGRESSION] KRDC hangs when trying to
connect to VNC host
Classification: Applications
   Product: krdc
   Version: 24.02.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: VNC
  Assignee: uwol...@kde.org
  Reporter: chemob...@gmail.com
  Target Milestone: ---

SUMMARY

I just upgraded from Fedora 39 to 40, i.e. I moved from KDE Plasma 5 to Plasma
6. KRDC connections using VNC plugin stopped working: KRDC hangs before even
trying to create a network connection.

STEPS TO REPRODUCE
1. start connection to host using vnc protocol

OBSERVED RESULT

Nothing: krdc application stops responding. E.g. disconnect or close window
leads to "krdc application does not respond" dialog.

According to networking status krdc hangs before even trying to create a
network connection. I.e. this problem can even be reproduced by trying to
connect to a non-existing VNC host.

EXPECTED RESULT

Connection to VNC host succeeds.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.2-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

* I tried on two different systems: same result
* I used tigervnc client to connect to VNC host: works fine
* I tried "krdc --platform xcb": no result
* I deleted all KRDC configurations from my home directory and then tried to
create a new connection: same result (i.e. not caused by old Plasma 5 settings)
* I enabled TEST plugin and created a connection using "test:" protocol: works
fine, i.e. I get a window with yellow background (I guess that is what the test
plugin generates). I can successfully disconnect from this connection
* (I don't have a RDP host available for real testing, sorry) I created a RDP
connection to a non-existing host: KRDC tries to connect to the host and
returns after a short while "can't connect to host", i.e. it seems that RDP
plugin works fine.

When I run "krdc" from the konsole the only messages I get are these at
startup:

~~~
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_vncplugin.so"
explicitly states an Id in the embedded metadata, which is different from the
one derived from the filename The Id field from the KPlugin object in the
metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_testplugin.so"
explicitly states an Id in the embedded metadata, which is different from the
one derived from the filename The Id field from the KPlugin object in the
metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_rdpplugin.so"
explicitly states an Id in the embedded metadata, which is different from the
one derived from the filename The Id field from the KPlugin object in the
metadata should be removed
qt.core.qobject.connect: QObject::connect: No such signal
KBookmarkManager::changed(QString,QString)
~~~

There are no additional messages when I try to create the VNC connection

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

[LabPlot2] [Bug 485118] Labplot 2.10.1 Mac silicone arm64 version no Themes and strange behaviour on opening Example files

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||stefan.gerlach@uni-konstanz
   ||.de
 Ever confirmed|0   |1
   Assignee|alexander.se...@web.de  |stefan.gerlach@uni-konstanz
   ||.de

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

[kmymoney] [Bug 485035] New: Cannot enter IBAN for new SEPA transfer - cursor jumps around within text field

[Stefan Seide]

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

Bug ID: 485035
   Summary: Cannot enter IBAN for new SEPA transfer - cursor jumps
around within text field
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ux-ui
  Assignee: kmymoney-de...@kde.org
  Reporter: bugs-...@seide.st
  Target Milestone: ---

SUMMARY

cursor jumps randomly around while trying to enter an IBAN number for a new
SEPA transfer.

STEPS TO REPRODUCE
1. Go to "Ausgang" -> "Neue Übereisung" (english might be "Outbox" -> "New
Transfer")
2. Select bank account and "SEPA Überweisung"
3. Now try to enter the IBAN into the field like DE12340200...
4. As soon as a new digit for the next 4 char block is entered the cursor jumps
back to the space between the current and the last 4-char block making it
impossible to enter the IBAN with keybord. Every four chars you have to stop
entering the IBAN and set cursor back to the position behind last number
entered before next numbers can be typed.

Probably due to some non-working text field auto-formatter to enter spaces for
easier readability?

OBSERVED RESULT

enter DE123 -> the cursor now jumps back to the place after the 2. Just typing
ahaed would give the IBAN "DE1243" instead of "DE1234"

EXPECTED RESULT

The cursor must not jump around and let users enter the IBAN on char after
another.

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

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 485033] New: Server URL not updated in AQBanking user config

[Stefan Seide]

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

Bug ID: 485033
   Summary: Server URL not updated in AQBanking user config
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: onlinebanking
  Assignee: kmymoney-de...@kde.org
  Reporter: bugs-...@seide.st
  Target Milestone: ---

SUMMARY

After changing the user/bank HBCI url it is not used to fetch certificate - the
old URL is used instead as long as i do not close the dialog.

STEPS TO REPRODUCE
1. Have AQBanking with one HBCI user account configured
2. Open "Einstellungen" -> "AQBanking einrichten" -> "Benutzer bearbeiten"
  (english might be: Menu "Settings" -> "Configure AQBanking" -> "Edit user")
3. Change the HBCI server URL to something new
4. Press button "Abruf des Zertifikats" (fetch certificate)

The old server URL is used to fetch the certificate, the newly entered URL is
ignored as long as i do not close the dialog with "OK"and reopen it.

OBSERVED RESULT

Old server URL (as shown on dialog opening) is used to fetch the URL.

EXPECTED RESULT

After changing the server URL the new URL entered should be used to fetch the
certificate.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Debian stable (12 update 5) with XFCE 4.18
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[kwin] [Bug 483998] Image from an IntelliJ window but focus and actions happen on another one (as if 100% transparent but on top)

[Stefan Burnicki]

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

Stefan Burnicki  changed:

   What|Removed |Added

 CC||stefan.burni...@burnicki.ne
   ||t

--- Comment #6 from Stefan Burnicki  ---
I think these bugs are referring to the same problem:
https://bugs.kde.org/show_bug.cgi?id=483532
https://bugs.kde.org/show_bug.cgi?id=483162

For me the workaround is to minimize all windows behind the IDE instance I want
to use.

Maybe also an interesting observation: While all events seem to affect the
window behind the one visible, I can still move the visible window with Meta +
Mouse.

I have no idea who is responsible for what in kwin, but it's not like the
windows are "simply" rendered in the wrong order.

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

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #22 from Stefan Brüns  ---
(In reply to tagwerk19 from comment #21)
> Created attachment 143869 [details]
> pdftotext results from
> https://ipfs.io/ipfs/QmVqWhPuQkE7reTN5F9TiSeA75z62VNaZUSFZz3FdWTLbC
> 
> (In reply to Adam Fontenot from comment #20)
> > ... The file, in their view, is pathological ...
> Applying a modicum of patience, running:
> 
> nice -19 pdftotext QmVqWhPuQkE7reTN5F9TiSeA75z62VNaZUSFZz3FdWTLbC.pdf
> 
> took 37 hours on a machine with 16GB memory 8-]
> 
> The process gradually ate memory, reaching 10 GB. There wasn't an obvious
> impact on performance - but I would expect you'd see that bite when reaching
> the limits/starting to swap.

The long runtime is caused by some algorithmically bad implementation, i.e.
O(n^2) were e.g. O(n log n) is sufficient. The huge memory footprint is caused
by some problematic data arrangement and too greedy pre/overallocation.

I have filed two MRs [1],[2] for poppler, with both applied the extractions
runs in ~50 seconds on my 3 year old laptop, with a peak memory consumption of
1.8 GByte.

[1] https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1514  
[2] https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1515

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

[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist

[Stefan L]

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

Stefan L  changed:

   What|Removed |Added

 CC||stefan.loe...@gmail.com

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

[plasma-mobile] [Bug 480724] Lockscreen can't unlock with non-numeric passwords

[Stefan Murawski]

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

Stefan Murawski  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #2 from Stefan Murawski  ---
Hello,
Sorry for the late reply.
After some more testing using the current kde neon stable version, your
recommendation works and seems acceptable.
Before clicking the button didn't seem to do anything.
But now it loads the on-screen keyboard, after a little moment.
I have a different bug with the plasma-mobile shell, the notification bar is
condensed into a small area in the top middle, but I will analyse that further
and create a new bug report if needed.
Thanks for the work.

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

[kde] [Bug 483532] Window focus not possible with multiple windows of the same application

[Stefan Burnicki]

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

--- Comment #5 from Stefan Burnicki  ---
Is this maybe related to this bug report?
https://bugs.kde.org/show_bug.cgi?id=483162

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

[kde] [Bug 483532] Window focus not possible with multiple windows of the same application

[Stefan Burnicki]

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

Stefan Burnicki  changed:

   What|Removed |Added

 CC||stefan.burni...@burnicki.ne
   ||t

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

[kwin] [Bug 483162] Sometimes wrong window stacking stacking orders with NVIDIA and AMD GPUs

[Stefan Burnicki]

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

--- Comment #10 from Stefan Burnicki  ---
I'm experiencing the same with kwin 6.0.2 on KDE KDE neon, with both X11 and
Wayland. Feels like it would appear more often with Wayland, but that could
also be a wrong feeling. I'm having a laptop with AMD graphics:
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO

I mostly observe this happening with IntelliJ IDEA and not with KDE apps. I'm
not enough into the technical details to know how these applications differ, I
just can say that IntelliJ has it's own window decoration. And I *think* there
was one time where the click would go through the window but I was able to
resize it which also fixed the stack.

If there are any symptoms I can keep an eye on which would help to somehow
narrow down the problem, I'm happy to provide it.

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

[kwin] [Bug 483162] Sometimes wrong window stacking stacking orders with NVIDIA and AMD GPUs

[Stefan Burnicki]

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

Stefan Burnicki  changed:

   What|Removed |Added

 CC||stefan.burni...@burnicki.ne
   ||t

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

[frameworks-kfilemetadata] [Bug 410680] KFileMetaData plain text extractor sometimes fails for non-UTF text files

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

Summary|baloo doesn't index words   |KFileMetaData plain text
   |far down in HTML documents  |extractor sometimes fails
   ||for non-UTF text files

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

[frameworks-kfilemetadata] [Bug 440537] KFileMetaData plain text extractor sometimes fails for non-UTF text files

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

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

--- Comment #1 from Stefan Brüns  ---
In case the non-ASCII character (byte) still forms a valid UTF-8 code sequence
(something which often appears when an UTF-8 text is interpreted as e.g.
ISO8859-1), the file will still be extracted completely, though with some
occasional incorrect codepoints.

As this bug report does not contain anything on top of the information present
in bug 410680 closing as duplicate.

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

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

[frameworks-kfilemetadata] [Bug 410680] baloo doesn't index words far down in HTML documents

[Stefan Brüns]

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

--- Comment #12 from Stefan Brüns  ---
*** Bug 440537 has been marked as a duplicate of this bug. ***

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

[frameworks-kfilemetadata] [Bug 440537] KFileMetaData plain text extractor sometimes fails for non-UTF text files

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

Summary|KFileExtractor doesn't work |KFileMetaData plain text
   |with non-UTF text files |extractor sometimes fails
   ||for non-UTF text files
 CC||stefan.bruens@rwth-aachen.d
   ||e

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

[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #16 from Stefan Brüns  ---
(In reply to Detlef Eppers from comment #13)
> Okular and Gwenview also don't know about Vaults and collect potentially
> sensitive metadata in ~/.local/share/okular/docdata and
> ~/.local/share/gwenview/recentfolders.

Also, thumbnails may leak out. These do not only show the preview, with up to
512x512 pixels, but also contain the full file name.

This only happens when the home directory is on encrypted storage, but when you
use Vaults even though the home directory is encrypted, you probably do for a
reason (i.e. additional confidentiality).

That is a fairly recent change for the worse, and it was mentioned in the MR
(https://invent.kde.org/frameworks/kio/-/merge_requests/1287#note_687728), but
people seem to be fine with this.

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

[kwin] [Bug 474606] Keyboard input doesn't work under Wayland

[Stefan Burnicki]

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

--- Comment #27 from Stefan Burnicki  ---
Just updated to Plasma 6.0.2 on KDE neon and the issue is also resolved for me
- even with my old home folder.

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

[kwin] [Bug 483203] New: Window background color opacity incorrect in KiCad after upgrading from Plasma 5 Wayland to Plasma 6

[Stefan Hamminga]

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

Bug ID: 483203
   Summary: Window background color opacity incorrect in KiCad
after upgrading from Plasma 5 Wayland to Plasma 6
Classification: Plasma
   Product: kwin
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ste...@prjct.net
  Target Milestone: ---

Created attachment 166936
  --> https://bugs.kde.org/attachment.cgi?id=166936=edit
Screenshot of KiCad color theme preview, showing issue

SUMMARY

After the regular Arch upgrades, which included Plasma 6, KiCad is unable to
correctly set the window background color. The attachment shows the problem in
action, where the preview background should be all black on the right (preview)
panel, but is only tinted slightly (as if applying the chosen black color with
0.05 opacity or so). Changing the color does change the tint.

Discussion on this bug on the KiCad side is here:

https://gitlab.com/kicad/code/kicad/-/issues/17341

Both before and after the bug I was using Plasma with Wayland. The issue
disappears when either (a) X11 is used (in Plasma 5 or 6) or (b) when forcing
KiCad to use software rendering. Sadly KiCad's software rendering is _also_
broken on Plasma 6 (in different ways) so that's not a viable workaround.

KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Graphics: Mesa Intel UHD

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

[frameworks-kfilemetadata] [Bug 428967] title field not populated for jpegs

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #7 from Stefan Brüns  ---
Waiting for confirmation

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

[frameworks-kfilemetadata] [Bug 316766] Baloo does not read tags from Windows 7 tagged Images

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |RESOLVED
Product|frameworks-baloo|frameworks-kfilemetadata
Version|unspecified |5.245.0
  Component|Baloo File Daemon   |general

--- Comment #10 from Stefan Brüns  ---
Waiting for confirmation

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

[frameworks-kfilemetadata] [Bug 410680] baloo doesn't index words far down in HTML documents

[Stefan Brüns]

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

--- Comment #11 from Stefan Brüns  ---
If you want the original content (without Wayback inserts/link mangling), you
have to use:

https://web.archive.org/web/20131225011444im_/https://demo.borland.com/testsite/stadyn_largepagewithimages.html

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

[frameworks-kfilemetadata] [Bug 410680] baloo doesn't index words far down in HTML documents

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

Version|5.59.0  |5.115.0
Product|frameworks-baloo|frameworks-kfilemetadata
  Component|Engine  |general

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

[frameworks-baloo] [Bug 439857] baloo only indexes first 4096 bytes of non-UTF-8 text and html files

[Stefan Brüns]

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

--- Comment #2 from Stefan Brüns  ---
Not a baloo bug. The text is not extracted by KFileMetaData's
plaintextextractor, but for that a BR already exists.

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

[LabPlot2] [Bug 481009] Cannot open LabPlot2 after installation via DMG

[Stefan Gerlach]

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

--- Comment #5 from Stefan Gerlach  ---
The quarantine flag is added to the package when downloading so it can't be
avoided by changing settings of the package. What we need is to notarize the
package from Apple which should be possible by the KDE infrastructure. I will
work on this.
In the meantime i added a note on the download page on how to fix this flag.
Thanks for finding this out.

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

[LabPlot2] [Bug 481009] Cannot open LabPlot2 after installation via DMG

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

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

--- Comment #3 from Stefan Gerlach  ---
We now have signed installer for x86_64 and arm64. Due to a bug in XCode they
only work on macOS 14 (Sonoma). The installer can be found on the SourceForge
page https://sourceforge.net/projects/labplot/files/labplot/2.10/
Any comments or bug reports are welcome.

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

[kstars] [Bug 481508] kstars 3.6.9 crashes on launch on macOS 13.6.4 (M2)

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 CC||stefan.gerlach@uni-konstanz
   ||.de

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

[kate] [Bug 476469] Kate crashes when clicking on first "Welcome" widget after creating a new session

[Stefan Jacob]

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

--- Comment #4 from Stefan Jacob  ---
Created attachment 165818
  --> https://bugs.kde.org/attachment.cgi?id=165818=edit
New crash information added by DrKonqi

kate (23.08.4) using Qt 5.15.12

Kate crashes when a text document is open and "Welcome" is clicked in the
document selection under open controls.

-- Backtrace (Reduced):
#4  0x749693e4a0ed in ??? () at
/usr/lib/qt/plugins/ktexteditor/katefiletreeplugin.so
#5  0x7496a02d0e27 in ??? () at /usr/lib/libQt5Core.so.5
#6  0x7496a11e356a in QAbstractItemView::clicked(QModelIndex const&) () at
/usr/lib/libQt5Widgets.so.5
#7  0x7496a11de7d5 in QAbstractItemView::mouseReleaseEvent(QMouseEvent*) ()
at /usr/lib/libQt5Widgets.so.5
#8  0x7496a0faf1a1 in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5

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

[kate] [Bug 476469] Kate crashes when clicking on first "Welcome" widget after creating a new session

[Stefan Jacob]

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

Stefan Jacob  changed:

   What|Removed |Added

 CC||st.ja...@web.de

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

[LabPlot2] [Bug 481009] Cannot open LabPlot2 after installation via DMG

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 CC||stefan.gerlach@uni-konstanz
   ||.de
 Ever confirmed|0   |1
   Assignee|alexander.se...@web.de  |stefan.gerlach@uni-konstanz
   ||.de
 Status|REPORTED|CONFIRMED

--- Comment #1 from Stefan Gerlach  ---
We are currently switching to gitlab for building DMG images which supports
signing. We will publish new installers as soon as this works.

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

[LabPlot2] [Bug 479460] Origin file does not shop up correctly opened with Labplot2.

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
 CC||stefan.gerlach@uni-konstanz
   ||.de

--- Comment #1 from Stefan Gerlach  ---
Alle Probleme mit dem Beispiel wurden inzwischen in der Entwicklerversion
behoben (bis auf den Pfeil, da Zeichenobjekte bisher nicht unterstützt werden).
Das Beispiel befindet sich jetzt auch auf der Referenzseite
https://invent.kde.org/education/labplot/-/wikis/Import/OPJ für zukünftige
Tests.
Zusätzliche Achsen werden ebenfalls in der Entwicklerversion unterstützt.
Für LibreOffice und Word wird ein OPJ-Import sicherlich nie möglich sein. Diese
Programme haben andere Ziele. Das ist aber auch nicht unsere Baustelle.

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

[LabPlot2] [Bug 480593] Multiple axes Placement not stored

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

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

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

[LabPlot2] [Bug 480593] Multiple axes Placement not stored

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 CC||stefan.gerlach@uni-konstanz
   ||.de

--- Comment #5 from Stefan Gerlach  ---
The "nightly" Flatpak will now be updated with every change in the development
version (master), so please try again.

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

[LabPlot2] [Bug 479460] Origin file does not shop up correctly opened with Labplot2.

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

   Assignee|alexander.se...@web.de  |stefan.gerlach@uni-konstanz
   ||.de

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

[LabPlot2] [Bug 476355] Diagram two y-axis not opened correctly.

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

   Assignee|alexander.se...@web.de  |stefan.gerlach@uni-konstanz
   ||.de

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

[LabPlot2] [Bug 476355] Diagram two y-axis not opened correctly.

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #9 from Stefan Gerlach  ---
The import in the development version is now much improved. See gallery at
https://invent.kde.org/education/labplot/-/wikis/Import/OPJ.
Remaining issues are documented now in
https://invent.kde.org/education/labplot/-/issues/860.

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

[plasma-mobile] [Bug 480724] New: Lockscreen can't unlock with non-numeric passwords

[Stefan Murawski]

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

Bug ID: 480724
   Summary: Lockscreen can't unlock with non-numeric passwords
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: stevew...@googlemail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Use a password not containing only numbers
2. Lock the device
3. Try to unlock the device

OBSERVED RESULT
The unlock screen only allows the numbers from 0-9 and unlocking is not
possible anymore without an external keyboard.

EXPECTED RESULT
Allow unlocking for normal passwords without using an external keyboard.
Either by offering letters and symbols in that widget or automatically showing
an on-screen keyboard.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kde neon
(available in About System)
KDE Plasma Version: RC2
KDE Frameworks Version: RC2
Qt Version: 6.6.1

ADDITIONAL INFORMATION
The offending code for the Pin Input is in this file:
https://invent.kde.org/plasma/plasma-mobile/-/blob/master/lookandfeel/contents/lockscreen/Keypad.qml
It's hardcoded to only allow the numbers from 0-9.
I have kde neon installed on a x86 tablet and currently have to activate
caffeine so it will not automatically lock at the moment, I have the system set
to automatically log in on boot.

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

[LabPlot2] [Bug 476355] Diagram two y-axis not opened correctly.

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED
 CC||stefan.gerlach@uni-konstanz
   ||.de

--- Comment #8 from Stefan Gerlach  ---
 Figure_19_beispiel.opj is now properly imported into LabPlot development
version (see https://invent.kde.org/education/labplot/-/issues/839). We will
also take a look at the other projects soon.

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

[LabPlot2] [Bug 480250] In the plot, I can not set no digit separator (,)

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED
   Assignee|alexander.se...@web.de  |stefan.gerlach@uni-konstanz
   ||.de
 CC||stefan.gerlach@uni-konstanz
   ||.de

--- Comment #1 from Stefan Gerlach  ---
The separator can be disabled in the Settings -> Configure LabPlot by checking
"Omit group separator" in the General tab under Number options.

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

[systemsettings] [Bug 477238] Display resolution and scaling settings not persistent

[Stefan Hoffmeister]

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

Stefan Hoffmeister  changed:

   What|Removed |Added

 CC||stefan.hoffmeister@econos.d
   ||e

--- Comment #10 from Stefan Hoffmeister  ---
Sounds like https://invent.kde.org/plasma/kwin/-/merge_requests/4913 which was
only recently merged.

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

[KPipeWire] [Bug 478309] Pipewire format negotiation fails on Wayland with NVIDIA GPU and 545 drivers

[Stefan Hoffmeister]

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

--- Comment #13 from Stefan Hoffmeister  ---
The Pipewire output suggests the following:

* the preview source data (i.e. "the window" == output) offers only format
DRM_FORMAT_ARGB (VideoFormat:BGRA, VideoFormat:BGRx)
* the preview sink data (i.e. "the preview" == input) accepts only format
VideoFormat:RGBx

That is not compatible. That causes the failure with "Invalid argument (input
format (no more input formats))".

Now, the _output_ offers DRM_FORMAT_ARGB because of special-case code.

And on the input side (in KPipewire) the implementation of queryDmaBufModifiers
may have a logic defect which incorrectly short-circuits processing of _all_
spa_video_formats ("break" vs "continue")

With a bit of hackery in queryDmaBufModifiers, the input will now successfully
accept DRM_FORMAT_ARGB, will use the "memfd" path ...

... and will silently _not work_, without any errors / diagnostics, and without
a preview.

TL;DR: whenever kwin forces DRM_FORMAT_ARGB in the screencast plugin,
kpipewire is not prepared to handle that.

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

[gwenview] [Bug 474653] rotation image

[stefan pofahl]

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

stefan pofahl  changed:

   What|Removed |Added

 CC||ste...@pofahl.de

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

[KPipeWire] [Bug 478309] Pipewire format negotiation fails on Wayland with NVIDIA GPU and 545 drivers

[Stefan Hoffmeister]

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

--- Comment #12 from Stefan Hoffmeister  ---
To reconfirm my challenge on vmwgfx, this is the log output with KDE Plasma 6
from git master (kdesrc-build plasma-desktop) with the commit included
---
```
Jan 05 08:59:58 fedora kwin_wayland[1829]: kwin_core: authorized
"/home/stefan/kde/usr/bin/plasmashell" "zkde_screencast_unstable_v1"
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: params
Spa:Enum:ParamId:EnumFormat: 0:0 Invalid argument (input format (no more input
formats))
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Object: size 160, type
Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:EnumFormat (3)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:mediaType (1), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 2   
(Spa:Enum:MediaType:video)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:mediaSubtype (2), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 1   
(Spa:Enum:MediaSubtype:raw)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:format (131073), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 7   
(Spa:Enum:VideoFormat:RGBx)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:size (131075), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Choice: type
Spa:Enum:Choice:Range, flags  40 8
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Rectangle 1x1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Rectangle 1x1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Rectangle -1x-1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:modifier (131074), flags 0008
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Long 72057594037927935
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Object: size 136, type
Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:EnumFormat (3)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:mediaType (1), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 2   
(Spa:Enum:MediaType:video)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:mediaSubtype (2), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 1   
(Spa:Enum:MediaSubtype:raw)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:format (131073), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 7   
(Spa:Enum:VideoFormat:RGBx)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:size (131075), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Choice: type
Spa:Enum:Choice:Range, flags  40 8
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Rectangle 1x1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Rectangle 1x1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Rectangle -1x-1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: params
Spa:Enum:ParamId:EnumFormat: 1:0 Invalid argument (output format (no more input
formats))
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Object: size 272, type
Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:EnumFormat (3)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:mediaType (1), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 2   
(Spa:Enum:MediaType:video)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:mediaSubtype (2), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Id 1   
(Spa:Enum:MediaSubtype:raw)
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:size (131075), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Rectangle 1280x728
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:framerate (131076), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Fraction 0/1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:maxFramerate (131077), flags 
Jan 05 08:59:58 fedora pipewire[1826]: pw.context: Choice: type
Spa:Enum:Choice:Range, flags  40 8
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Fraction 60/1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Fraction 1/1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Fraction 60/1
Jan 05 08:59:58 fedora pipewire[1826]: pw.context:   Prop: key
Spa:Pod:Object:Param:Format:Video:format (131073), flags 
Ja

[KPipeWire] [Bug 478309] Pipewire format negotiation fails on Wayland with NVIDIA GPU and 545 drivers

[Stefan Hoffmeister]

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

Stefan Hoffmeister  changed:

   What|Removed |Added

Summary|Pipwire format negotiation  |Pipewire format negotiation
   |fails on Wayland with   |fails on Wayland with
   |NVIDIA GPU and 545 drivers  |NVIDIA GPU and 545 drivers

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

[KPipeWire] [Bug 478309] Pipwire format negotiation fails on Wayland with NVIDIA GPU and 545 drivers

[Stefan Hoffmeister]

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

Stefan Hoffmeister  changed:

   What|Removed |Added

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

--- Comment #11 from Stefan Hoffmeister  ---
Alas, on my vmwgfx driver (see my initial report), the problem persists.

I just ran a fresh kdesrc-build plasma-desktop, the linked commit
5fdfeb18c00ab619d234142d60e922a1f36ae588 is present locally, and I still get
the same behaviour as before, where
* the preview is empty
* there is plenty of log output

It might or might not be fixed for NVIDIA - I cannot tell right now.

So, the recap, on the exact same (virtual) hardware,
* this is faulty for me on Fedora Rawhide (40) with KDE Plasma git master
* this works for me on Arch Linux with KDE Plasma 5.27.10

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

[plasmashell] [Bug 479272] systemdBoot with Plasma 6

[Stefan Schmid]

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

Stefan Schmid  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Stefan Schmid  ---
This bug can be closed, the error is caused by an error in the Gentoo ebuild.
https://bugs.gentoo.org/921224
Sorry for creating a bug report unnecessarily.

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #9 from Stefan Hoffmeister  ---
Created attachment 164620
  --> https://bugs.kde.org/attachment.cgi?id=164620=edit
Left 6.0 Wayland (broken) <-> Right X11 5.27 (working)

Attached a screenshot which shows the material difference(s) between the
working X11 setup on Plasma 5.27 and the equivalent non-working Wayland setup
on Plasma 6 b2+.

Fundamentally, 
* on X11 (right side), there is one backing framebuffer with size 6400x2160
covering both active planes (with offsetting via the SRC_X property)
* on Wayland (left side), there are two distinct framebuffers, one for each
plane, each of the "right size", and each at SRC_X == 0.

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #8 from Stefan Hoffmeister  ---
Created attachment 164619
  --> https://bugs.kde.org/attachment.cgi?id=164619=edit
drm_info with legacy mode setting in broken state (left-extend not working)

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #7 from Stefan Hoffmeister  ---
Created attachment 164618
  --> https://bugs.kde.org/attachment.cgi?id=164618=edit
X11 5.27 left-extend working

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #6 from Stefan Hoffmeister  ---
The matching Fedora Rawhide (40) GNOME setup, which runs in legacy mode (no
atomic mode-setting) exposes the exact same behavior as KDE Plasma 6 b2+ (git
master) on Wayland.

To that extent, there may be a commonality to the multi-monitor Wayland driving
of GNOME and KDE Plasma 6 on Fedora Rawhide (40).

Additional data point: 

I also tried KDE Plasma 5.27.10 in an X11 session on Arch Linux, with the same
virtual graphics "hardware" setup and with legacy mode setting. In that X11
environment, the screens both left-extend and right-extend correctly for
rendering (this was also working previously on F39, do not have this infra at
the moment).

Note that that the KDE X11 setup has challenges in cursor to (virtual) screen
mapping though - but those can be fixed by running a script that uses
kscreen-doctor to "re-layout" the screens in a different sequence (cf
https://github.com/vmware/open-vm-tools/issues/484#issuecomment-1703922094.

So, in theory, given the above, one could argue that Wayland KDE Plasma 6 has
regressed relative to X11 KDE Plasma 5.27.10.

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #5 from Stefan Hoffmeister  ---
No difference in behaviour with KWIN_DRM_NO_AMS _not_ set - right now (on my
kernel) this implies no atomic mode-setting.

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #4 from Stefan Hoffmeister  ---
FWIW, and possibly a separate challenge:

Take the working "extend to the right" setup from above and move the secondary
screen to _extend to the bottom_. This does not render correctly, either (fair
enough - see above).

Do note that the mouse cursor now moves "in an unnatural fashion" - it feels as
if some unsuitable mouse acceleration profile is being applied.

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #3 from Stefan Hoffmeister  ---
Attached drm_info dumps where VMware Workstation adds the monitor "to the left"
and "to the right", respectively, where KDE Desktop Configuration matches the
extend intent exactly

* left-extend == 2.5k screen physically (and mapped through host) to the left
* right-extend == 3k laptop screen physically (and mapped through the host) to
the right

Center screen is always the 4k screen.

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #2 from Stefan Hoffmeister  ---
Created attachment 164617
  --> https://bugs.kde.org/attachment.cgi?id=164617=edit
drm_info in working state (right-extend working well)

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

[kwin] [Bug 479293] Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #1 from Stefan Hoffmeister  ---
Created attachment 164616
  --> https://bugs.kde.org/attachment.cgi?id=164616=edit
drm_info in broken state (left-extend not working)

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

[kwin] [Bug 479293] New: Multi-monitor Wayland surface does not extend to the left (Plasma 6)

[Stefan Hoffmeister]

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

Bug ID: 479293
   Summary: Multi-monitor Wayland surface does not extend to the
left (Plasma 6)
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-drm
  Assignee: kwin-bugs-n...@kde.org
  Reporter: stefan.hoffmeis...@econos.de
  Target Milestone: ---

SUMMARY

In a Wayland multi-monitor setup where the non-primary screen is to the _left_
of the primary screen ("extend to the left"), the content is overlapped into
the primary screen.

In ASCII art, for
* left non-primary == 2.5K resolution
* primary == 4K resolution
this looks like

```
+-++
|   ||
|-+|
|  |
| |
+--|
```

Extending to the right works as expected. This also holds true for a triple
monitor setup, where one screen extends to the left and one screen extends to
the right of the primary screen.

"Display Configuration" shows the intended (correct) layout.

This may be an artefact of running KDE Plasma 6 b2+ (git master) under VMware
Workstation / vmwgfx with `export KWIN_DRM_NO_AMS=0`


STEPS TO REPRODUCE
1. create a multi-monitor setup
2. "physically" place at least one screen to the left of the primary screen
3. use "Display Configuration" to assert that physical left screen is logically
placed to extend the primary screen to the left (i.e. vertically aligned at the
top, offset to the left by resolution of secondary screen)

OBSERVED RESULT

Left screen overlaps primary screen as in ASCII art diagram above.

EXPECTED RESULT

Left screen extends desktop to the left.

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

[plasmashell] [Bug 479272] New: systemdBoot with Plasma 6

[Stefan Schmid]

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

Bug ID: 479272
   Summary: systemdBoot with Plasma 6
Classification: Plasma
   Product: plasmashell
   Version: 5.91.0
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: schmidi...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Since KDE Plasma 6, the "systemdBoot=true" option in the ".config/startkderc"
file no longer seems to have any effect on the way KDE Plasma is started. I
tried an internet search to see if this had been posted but couldn't find
anything. And there is nothing about this in the associated wiki page
(https://invent.kde.org/plasma/plasma-workspace/-/wikis/Plasma-and-the-systemd-boot).


STEPS TO REPRODUCE
1. Set systemdBoot to true with "kwriteconfig6 --file startkderc --group
General --key systemdBoot true"
2. Relogin
3. "systemctl --user status" does not show any plasma services

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.19.0
KDE Frameworks Version:  5.247.0
Qt Version: 6.6.1

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

[kwin] [Bug 479154] Cursor does not scale with output scale (Wayland, Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #3 from Stefan Hoffmeister  ---
Created attachment 164561
  --> https://bugs.kde.org/attachment.cgi?id=164561=edit
Screenshot shows correct rendering, but that's not what is shown

Funny enough, taking a screenshot (with Spectacle) shows _correct_ rendering -
but that screenshot does not reflect what I see on screen.

On screen I do not see the large cursor, but the small (unscaled?) cursor.

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

[kwin] [Bug 479154] Cursor does not scale with output scale (Wayland, Plasma 6)

[Stefan Hoffmeister]

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

Stefan Hoffmeister  changed:

   What|Removed |Added

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

--- Comment #2 from Stefan Hoffmeister  ---
Indeed, a virtual machine, vmwgfx of VMware, with
```
# Force atomic mode-setting
export KWIN_DRM_NO_AMS=0

# Force software cursors
export KWIN_FORCE_SW_CURSOR=1
```

So, I suspect, the software cursor path might be it? I will get to the vmwgfx
GEM / GBM part next week++, but for quite some more time I expect to have to
run with software cursors forced on.

Sorry that I keep forgetting to provide the environment details!

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

[kwin] [Bug 479154] New: Cursor does not scale with output scale (Wayland, Plasma 6)

[Stefan Hoffmeister]

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

Bug ID: 479154
   Summary: Cursor does not scale with output scale (Wayland,
Plasma 6)
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-drm
  Assignee: kwin-bugs-n...@kde.org
  Reporter: stefan.hoffmeis...@econos.de
  Target Milestone: ---

SUMMARY

When changing the scale of an output, all aspect of the cursor should scale as
well, together with the change.

Right now, no scaling appears to take place in a pure Wayland, Plasma 6 beta2+,
KDE stack (i.e. this defect here is not about Xwayland)


STEPS TO REPRODUCE
1. log in
2. "Display Properties" -> set scale to 3 == 300%
3. Apply

OBSERVED RESULT

* Output itself is now scaled, but cursor remains at the previous scale -
typically too small. 
* Cursor hotspot / hitbox is difficult to spot, it does not match where one
expects it to be

EXPECTED RESULT

* cursor is scaled according to output scale
* cursor hotspot / hitbox matches with what is on screen


A good way to see all this is to run on a high-resolution screen with a very
_integral_ scale factor (i.e. 3). This is also not about fractional scaling.

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

[kwin] [Bug 478301] Log spam "drmPrimeHandleToFD() failed: No such file or directory" (Wayland, virtualization)

[Stefan Hoffmeister]

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

--- Comment #2 from Stefan Hoffmeister  ---
The root cause of this is a combination of factors that hit with kwin running
in "legacy mode" (this is the default right now due to driver detection and
workarounds applied), on the DRM backend:

Upon starting the Wayland compositor, output management adds outputs
(WaylandCompositor::addOutput). In there, events are connected to handle
workspace geometry changes and changes to the cursor (updateCursorLayer,
moveCursorLayer).

Lambda updateCursorLayer is responsible for handling cursor "content" change.
It does that by trying to render a hardware cursor first, and, if that fails,
then rendering a fallback.

On vmwgfx as of kernel 6.7.0-rc5, trying to render a hardware cursor will
*always* fail with "drmPrimeHandleToFD() failed" (and more log messages), and
updating the cursor will always enter the fallback path. This causes the log
spam.

There is a way to disable the attempt to perform hardware cursor rendering:
configure environment variable "KWIN_FORCE_SW_CURSOR=1" to enter the
(software-based cursor rendering) fallback path immediately. This stops the
logspam.

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

[kwin] [Bug 478487] VMware Workstation + atomic mode-settings needs KWIN_FORCE_SW_CURSOR=1

[Stefan Hoffmeister]

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

--- Comment #4 from Stefan Hoffmeister  ---
I am currently digging into cursors in general, have already reached out in the
matter of drmCloseBufferHandle (and the TTM/GEM mess) - and have received a
response from Zack Rusin of VMware / Broadcom, see
https://lore.kernel.org/all/cabqx2qpkewdhe6xaaucafh7qwva06xj8bfqrmpqtkm61x-y...@mail.gmail.com/

Once I understand more about "the cursor situation in KDE on top of vmwgfx",
I'll follow up on this.

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

[kwin] [Bug 478487] VMware Workstation + atomic mode-settings needs KWIN_FORCE_SW_CURSOR=1

[Stefan Hoffmeister]

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

Stefan Hoffmeister  changed:

   What|Removed |Added

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

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

[kwin] [Bug 479002] Wayland atomic mode-setting cursors not shown on vmwgfx driver

[Stefan Hoffmeister]

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

Stefan Hoffmeister  changed:

   What|Removed |Added

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

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

[kwin] [Bug 479002] Wayland atomic mode-setting cursors not shown on vmwgfx driver

[Stefan Hoffmeister]

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

--- Comment #1 from Stefan Hoffmeister  ---
Note that for atomic mode-setting and "hardware" cursors to work on the VMware
vmwgfx driver, a kernel patch is required to prevent kernel oopses, see
https://bugs.kde.org/show_bug.cgi?id=478308

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

[kwin] [Bug 478308] VMware kernel oops with KWIN_DRM_NO_AMS=0; desktop does not repaint

[Stefan Hoffmeister]

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

--- Comment #8 from Stefan Hoffmeister  ---
There is a working patch in
https://lore.kernel.org/all/20231225202541.horde.txckv5njboomrzjolmts...@webmail.your-server.de/
which fixes the oops.

With that patch in place, it is now possible to detect that atomic mode-setting
cursors are _not shown_, see https://bugs.kde.org/show_bug.cgi?id=479002

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

[kwin] [Bug 479002] New: Wayland atomic mode-setting cursors not shown on vmwgfx driver

[Stefan Hoffmeister]

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

Bug ID: 479002
   Summary: Wayland atomic mode-setting cursors not shown on
vmwgfx driver
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-drm
  Assignee: kwin-bugs-n...@kde.org
  Reporter: stefan.hoffmeis...@econos.de
  Target Milestone: ---

SUMMARY

When forcing on atomic mode-setting through `export KWIN_DRM_NO_AMS=0` on KDE
Plasma 6 git master (beta2+) in a Wayland session, on VMware Workstation
(vmwgfx kernel driver), no cursor is shown.

Looking at

`watch -n 1 "drm_info | grep -E 'Plane|Connector|FB_ID|\"CRTC'"`

suggests that the plane is assigned to the right CRTC, that the FB_ID changes.
There is no applicable log output at level debug+.

STEPS TO REPRODUCE
1. force atomic mode-setting to on via `export KWIN_DRM_NO_AMS=0`
2. make sure that software cursors are _not_ on (i.e. _not_
KWIN_FORCE_SW_CURSOR=1)
3. log into Plasma Wayland session

OBSERVED RESULT

No cursor visible on screen, but system _acts_ as if there is a cursor present
(clicks etc work)

EXPECTED RESULT

Cursor visible on screen.

ADDITIONAL INFORMATION

Note that right now forcing on of KWIN_DRM_NO_AMS is required due to the Linux
kernel (virtual graphics drivers) lacking some capabilities in version
6.7.0-rc5. With Linux kernel 6.8 these capabilities will be present in the
kernel and kwin will automatically enable atomic mode-setting.

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

[plasmashell] [Bug 477855] Plasmashell consumes CPU time doing nothing until System Tray popup is opened once

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

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

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

[LabPlot2] [Bug 478228] Error when trying to execute python in python notebook

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

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

--- Comment #5 from Stefan Gerlach  ---
A new version which supports Python Notebooks is now available in the MS Store.
It requires Python 3.11.

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

[kwin] [Bug 478308] VMware kernel oops with KWIN_DRM_NO_AMS=0; desktop does not repaint

[Stefan Hoffmeister]

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

--- Comment #7 from Stefan Hoffmeister  ---
VMware have reacted on the dri gitlab issue tracker, ACKed the report,
confirmed reproduction on their end, and noted that they now have an internal
tracking item for this.

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

[systemsettings] [Bug 478842] New: System Crash Settings

[Stefan]

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

Bug ID: 478842
   Summary: System Crash Settings
Classification: Applications
   Product: systemsettings
   Version: 5.27.10
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: stefanconrad...@gmail.com
  Target Milestone: ---

Application: systemsettings (5.27.10)

Qt Version: 5.15.11
Frameworks Version: 5.113.0
Operating System: Linux 6.2.0-39-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Settings crash after I have started the Settings Menu

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x000d0002 in ?? ()
#5  0x7f7da07ddd3a in KupKcm::completelyRemovePlan
(this=this@entry=0x556797144480, pIndex=1) at ./kcm/kupkcm.cpp:300
#6  0x7f7da07ddf90 in operator() (__closure=0x55679723dc20) at
./kcm/kupkcm.cpp:266
#7  QtPrivate::FunctorCall, QtPrivate::List<>, void,
KupKcm::createPlanWidgets(int):: >::call (arg=, f=...)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#8  QtPrivate::Functor,
0>::call, void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#9  QtPrivate::QFunctorSlotObject,
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=0x55679723dc10, r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#10 0x7f7dc4af43e4 in QtPrivate::QSlotObjectBase::call (a=0x7ffe8e5588b0,
r=0x556797144480, this=0x55679723dc10) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x556797374840, signal_index=10,
argv=0x7ffe8e5588b0) at kernel/qobject.cpp:3925
#12 0x7f7dc4af4418 in doActivate (sender=0x556797800850,
signal_index=9, argv=0x7ffe8e5589e0) at kernel/qobject.cpp:3937
#13 0x7f7dc4aed4b7 in QMetaObject::activate
(sender=sender@entry=0x556797800850, m=m@entry=0x7f7dc5c9c280
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe8e5589e0)
at kernel/qobject.cpp:3985
#14 0x7f7dc5862a06 in QAbstractButton::clicked
(this=this@entry=0x556797800850, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#15 0x7f7dc5862c8e in QAbstractButtonPrivate::emitClicked
(this=0x5567977a5720) at widgets/qabstractbutton.cpp:416
#16 0x7f7dc58648b4 in QAbstractButtonPrivate::click (this=0x5567977a5720)
at widgets/qabstractbutton.cpp:409
#17 0x7f7dc5864ad7 in QAbstractButton::mouseReleaseEvent
(this=0x556797800850, e=0x7ffe8e558f70) at widgets/qabstractbutton.cpp:1045
#18 0x7f7dc57af95e in QWidget::event (this=0x556797800850,
event=0x7ffe8e558f70) at kernel/qwidget.cpp:9045
#19 0x7f7dc576c763 in QApplicationPrivate::notify_helper
(this=this@entry=0x556796665390, receiver=receiver@entry=0x556797800850,
e=e@entry=0x7ffe8e558f70) at kernel/qapplication.cpp:3640
#20 0x7f7dc57743a4 in QApplication::notify (this=,
receiver=0x556797800850, e=0x7ffe8e558f70) at kernel/qapplication.cpp:3084
#21 0x7f7dc4abc93a in QCoreApplication::notifyInternal2
(receiver=0x556797800850, event=0x7ffe8e558f70) at
kernel/qcoreapplication.cpp:1064
#22 0x7f7dc5772e87 in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x556797800850, event=event@entry=0x7ffe8e558f70,
alienWidget=alienWidget@entry=0x556797800850, nativeWidget=0x55679687c800,
buttonDown=, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2622
#23 0x7f7dc57c91db in QWidgetWindow::handleMouseEvent (this=0x5567969c00b0,
event=0x7ffe8e559240) at kernel/qwidgetwindow.cpp:684
#24 0x7f7dc57cc535 in QWidgetWindow::event (this=0x5567969c00b0,
event=0x7ffe8e559240) at kernel/qwidgetwindow.cpp:300
#25 0x7f7dc576c763 in QApplicationPrivate::notify_helper (this=, receiver=0x5567969c00b0, e=0x7ffe8e559240) at
kernel/qapplication.cpp:3640
#26 0x7f7dc4abc93a in QCoreApplication::notifyInternal2
(receiver=0x5567969c00b0, event=0x7ffe8e559240) at
kernel/qcoreapplication.cpp:1064
#27 0x7f7dc4f43197 in QGuiApplicationPrivate::processMouseEvent
(e=0x556796ae7cf0) at kernel/qguiapplication.cpp:2278
#28 0x7f7dc4f16dbc in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#29 0x7f7dbfaf6fae in xcbSourceDispatch (source=) at
./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
#30 0x7f7dc3251d3b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7f7dc32a7258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x7f7dc324f3e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 

[kwin] [Bug 478616] System hangs dead on sddm start: "kwin_core: Failed to open /dev/dri/card0 device (Did not receive a reply. ..."

[Stefan Hoffmeister]

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

--- Comment #7 from Stefan Hoffmeister  ---
This does not seem to be related to NVIDIA. Right now I suspect multi-monitor
support on the Intel 11800H iGPU (there is a 4K screen attached to that GPU,
but the monitor has been working very fine going through all of the Plymouth
"nice animated system boot" graphics fun)

Reason:

I have now had a cold boot on this notebook (power on after having been turned
off for six hours) and got the same problem, again. With more logging enabled,
it is now clear that systemd_logind simply does not respond in time:

* 09:35:52 - kwin_wayland (apparently) sends the TakeDevice request via dbus
* 09:35:52 - systemd_logind acks request
[25 secs after request]
* 09:36:17 - kwin_wayland gives up waiting, "Failed to open /dev/dri/card0
device"; sddm is toast
[34 secs after request]
* 09:36:26 - systemd_logind sends response, apparently a success

```
Dec 20 09:35:52 dell.home systemd[2417]: Started dbus-broker.service - D-Bus
User Message Bus.
Dec 20 09:35:52 dell.home dbus-broker-launch[2448]: Ready
Dec 20 09:35:52 dell.home systemd-logind[1531]: Got message type=method_call
sender=:1.36 destination=org.freedesktop.login1
path=/org/freedesktop/login1/session/c1
interface=org.freedesktop.login1.Session member=TakeDevice  cookie=15
reply_cookie=0 signature=uu error-name=n/a error-message=n/a
Dec 20 09:35:54 dell.home kernel: thunderbolt 0-1: new device found,
vendor=0x16b device=0x9010
Dec 20 09:35:54 dell.home kernel: thunderbolt 0-1: i-tec TB3CDUALDPDOCKPD
Dec 20 09:35:54 dell.home boltd[1725]: [004158c8-bd26-TB3CDUALDPDOCKPD 
 ] parent is f07211eb-5a97...
Dec 20 09:35:54 dell.home boltd[1725]: [004158c8-bd26-TB3CDUALDPDOCKPD 
 ] connected: authorized (/sys/devices/pci:00/:00:0d.2/domain0/0-0/0-1)
Dec 20 09:35:54 dell.home boltd[1725]: [004158c8-bd26-TB3CDUALDPDOCKPD 
 ] udev: device changed: authorized -> authorized
Dec 20 09:36:01 dell.home systemd[1]: NetworkManager-dispatcher.service:
Deactivated successfully.
Dec 20 09:36:01 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=NetworkManager-dispatcher comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 20 09:36:17 dell.home sddm-helper-start-wayland[2433]: "kwin_core: Failed
to open /dev/dri/card0 device (Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.)\nkwin_waylan>
Dec 20 09:36:17 dell.home sddm-greeter[2444]: Creating a fake screen in order
for Qt not to crash
Dec 20 09:36:17 dell.home sddm-greeter[2444]: The Wayland connection broke. Did
the Wayland compositor die?
Dec 20 09:36:17 dell.home sddm-helper-start-wayland[2433]: Stopping...
"/usr/bin/sddm-greeter"
Dec 20 09:36:17 dell.home sddm-helper[2323]: pam_unix(sddm-greeter:session):
session closed for user sddm
...
Dec 20 09:36:26 dell.home systemd-logind[1531]: Sent message type=method_return
sender=n/a destination=:1.36 path=n/a interface=n/a member=n/a cookie=73
reply_cookie=15 signature=hb error-name=n/a error-message=n/a
```

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

[kwin] [Bug 478476] Output removal ("remove screen") does not work (Wayland, Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #10 from Stefan Hoffmeister  ---
As far as I can see, this defect only hits systems where an output does not
_physically_ disappear. Or, in other words, if you plug the cable, well, there
is nothing coming down that wire any more, right?

So, this will most likely only detrimentally _affect_ systems with non-physical
screens which allow multi-screen configurations. Such as (confirmed) VMware
Workstation (and most likely all desktop hypervisor products created by VMware,
for instance VMware Fusion). Perhaps GNOME Boxes / qemu / kvm (with
virtio-gpu)? Perhaps VirtualBox? Perhaps whatever is using the qxl driver?
Whatever does virtualization and software abstraction tricks.

It will also only _affect_ users of said systems who turn on and _off_ one more
screens in addition to the primary screen.

So while the defect is universal, after triage, its impact (most likely) is
rather limited.

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

[kwin] [Bug 478476] Output removal ("remove screen") does not work (Wayland, Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #9 from Stefan Hoffmeister  ---
The root cause of this defect is a design challenge in the atomic commit code.

Whenever an output is changed ("DrmGpu::updateOutputs"), among other things,
the 1:1 matched up internal processing pipeline of kwin gets "managed", too.
The GPU _instance_ retains a list of those pipelines in m_pipelines. When a new
pipeline is added, it is added immediately to m_pipelines. When a pipeline is
removed, it is immediately removed from m_pipelines.

After the GPU instance state for pipelines has been altered, all this gets
tested and ends up in DrmGpu::testPipelines(). This then does
commitPipelines(m_pipelines, DrmPipeline::CommitMode::TestAllowModeset. This
will pass, and all is good - new configuration is accepted.

Alas, what is missing is a successful atomic commit to clean up any _removed_
pipeline(s) all the way into the _kernel_. This has the effect that the _DRM
plane_ that was connected to the removed pipeline still has a framebuffer
object attached to it that is now frozen in time, because nothing ever updates
it. And because there is still that framebuffer object around, the VMware
Workstation host will faithfully show that forever.

This behaviour is best illustrated by adding one single log statement to the
implementation:

```
  DrmPipeline::Error DrmPipeline::commitPipelinesAtomic(const QList , CommitMode mode, const QList )
{
+  qCDebug(KWIN_DRM) << "commitPipelinesAtomic is applied to" <<
pipelines.size() << "pipelines";
```

Notice how this will print the number(a) as explained above - numbers that are
not good ;). Also inspect the output of drm_info gathered in attachement "After
removing screen" and notice how plane 2 (which is the removed screen) still has
a non-zero framebuffer buffer ID (FB_ID) value (96)

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

[systemsettings] [Bug 477274] Untranslated string in File Search KCM

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/-/commit/
   ||7ecf315258b4e171ab76d7929ce
   ||7b8db5cfc3011
 Status|ASSIGNED|RESOLVED

--- Comment #12 from Stefan Brüns  ---
Git commit 7ecf315258b4e171ab76d7929ce7b8db5cfc3011 by Stefan Brüns.
Committed on 19/12/2023 at 14:08.
Pushed by bruns into branch 'master'.

Fix hiding of filename label when indexer is idle

This fixes a regression caused by commit 6ea58c0f0ac6 ("kcms/baloo: make
"current indexing" label a full path again"). Prior to this commit, the
condition included the boolean "monitor.currentlyIndexing" property.

Using the filePath.length and completionPercentage is insufficient,
as the filepath value is only valid when the state is *not* idle, and
may show e.g. a placeholder value during idle state.

M  +1-1kcms/baloo/ui/main.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/7ecf315258b4e171ab76d7929ce7b8db5cfc3011

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

[kwin] [Bug 478476] Output removal ("remove screen") does not work (Wayland, Plasma 6)

[Stefan Hoffmeister]

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

--- Comment #8 from Stefan Hoffmeister  ---
Tested the "cycle multiple monitors" feature of VMware Workstation on Fedora
Workstation Rawhide F40 - it works there.

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