[digikam] [Bug 479242] New: Adding a Face Tag instantly crashes DK8.2
https://bugs.kde.org/show_bug.cgi?id=479242 Bug ID: 479242 Summary: Adding a Face Tag instantly crashes DK8.2 Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@wolki.de Target Milestone: --- when adding a face tag, digikam reliably crashes on my machine. I have been tagging a lot of pictures with 8.1 in november successfully, I'm fairly certain that this is a regression. STEPS TO REPRODUCE 1. Open any image from your albums in the preview 2. Ctrl+Click/Drag a region (this step still works fine, and the region itself is preserved even after the crash!) 3. Type any single letter into the face tag input box that turns up. The first keystroke will reliably crash Digikam 8.2 for me. OBSERVED RESULT The whole application crashes on the first keystroke. Re-Opening DK8.2 takes a lot of time, but after the restart, the newly created region still exists (so it must have been saved before). EXPECTED RESULT The input box should bring up the usual search results and let me choose from existing options. SOFTWARE/OS VERSIONS Windows: Windows 11 22H2 / Build 22621.2861 (default latest version at the time of writing) KDE Frameworks Version: 5.256.0 (Windows Binary default?) Qt Version: 6.6.0 (Windows Binary default?) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446468] Selected folder icon becomes white in selected list items
https://bugs.kde.org/show_bug.cgi?id=446468 --- Comment #29 from Claudius --- I had the Folder icon (default Breeze) turn completely black when I selected the blue accent color from the palette in system settings. It looks a bit broken then. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446468] Selected folder icon becomes white in selected list items
https://bugs.kde.org/show_bug.cgi?id=446468 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 467452] KDevelop XDebug Support cannot be built because duchain/safetycounter.h is missing
https://bugs.kde.org/show_bug.cgi?id=467452 --- Comment #1 from Claudius --- If I just comment out the include file. The Plugin builds fine. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 467452] New: KDevelop XDebug Support cannot be built because duchain/safetycounter.h is missing
https://bugs.kde.org/show_bug.cgi?id=467452 Bug ID: 467452 Summary: KDevelop XDebug Support cannot be built because duchain/safetycounter.h is missing Classification: Developer tools Product: kdevplatform Version: git master Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: language Assignee: kdevelop-bugs-n...@kde.org Reporter: claudius+...@hausnetz.lettenbach.com Target Milestone: --- SUMMARY language/duchain/safetycounter.h seems to have been removed from kdevplatform. I use version kdevelop 22.12.3-1 from the archlinux repo STEPS TO REPRODUCE 1. get https://invent.kde.org/kdevelop/kdev-xdebug 2. cmake and build OBSERVED RESULT kdev-xdebug/stringhelpers.cpp:20:10: fatal error: language/duchain/safetycounter.h: No such file or directory 20 | #include | ^~ compilation terminated. make[2]: *** [CMakeFiles/kdevxdebug.dir/build.make:234: CMakeFiles/kdevxdebug.dir/stringhelpers.cpp.o] Error 1 Is this a bug or should I manually grab an older version of kdevplatform? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 462418] Android app cannot connect, TLS 1.0 suspected
https://bugs.kde.org/show_bug.cgi?id=462418 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary
https://bugs.kde.org/show_bug.cgi?id=460985 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com --- Comment #22 from Claudius --- Thanks to Nate for directing me to the proper bug (I didn't find it via the search, because I looked in dolphin, sorry). I often used the old dialog quite often for starting a database file that required a parameter on the command line. This was super handy since the command line history was saved in Dolphin's config file. So I would just choose the correct one from the dropdown. Krusader still works this way (it has its own history though). -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 466148] Dolphin, "Open with" dialog doesn't work
https://bugs.kde.org/show_bug.cgi?id=466148 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com --- Comment #7 from Claudius --- Are there plans to bring back custom command lines with history or a more condensed list of applications? The new Portal is a pretty big step backwards while adding a lot of complexity. (also a launch in Terminal checkbox would be awesome) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451936] Rendering with chapters
https://bugs.kde.org/show_bug.cgi?id=451936 --- Comment #2 from Claudius --- As a first step, this export dialog could likely be enhanced to produce the `FFMETADATAFILE` directly: https://invent.kde.org/multimedia/kdenlive/-/blob/master/src/dialogs/exportguidesdialog.cpp -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451936] Rendering with chapters
https://bugs.kde.org/show_bug.cgi?id=451936
--- Comment #1 from Claudius ---
My current workflow is:
Right-Clicking the timeline, exporting the guides as `{{frame}} {{comment}}`
And the next step I do by hand (which is okayish for a handful of chapters).
I turn this list from
```
0 Name of Chapter 1
1230 Name of Chapter 2
5321 Name of Chapter 3
```
into
```
;FFMETADATA1
[CHAPTER]
TIMEBASE=1/30
START=0
END=1229
title=Name of Chapter 1
[CHAPTER]
TIMEBASE=1/30
START=1230
END=5320
title=Name of Chapter 2
[CHAPTER]
TIMEBASE=1/30
START=5321
END=8000
title=Name of Chapter 3
```
(assuming 30 fps, hence the somewhat uncommon TIMEBASE=1/30)
Which I then integrate with ffmpeg after the fact, (as written by mau in the
previous comment)
It would be amazing to have this as a checkable box within the render interface
instead.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 451936] Rendering with chapters
https://bugs.kde.org/show_bug.cgi?id=451936 Claudius changed: What|Removed |Added CC||kde.b...@wolki.de -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 464421] I cannot find the Cache settings
https://bugs.kde.org/show_bug.cgi?id=464421 --- Comment #2 from Claudius --- Ah I see. Thank you for the quick reply. The "wallpaper/picture of the day" also still uses it. 8 months of wallpapers makes the cache pretty big. A way to configure it would still be useful I think. kio_http_cache_cleaner apparently runs on my install but it doesn't seem to do anything. If I use it to query cache contents I can see an expiry date from last year on most items. (I guess that is a different topic/bug report though) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 464421] New: I cannot find the Cache settings
https://bugs.kde.org/show_bug.cgi?id=464421 Bug ID: 464421 Summary: I cannot find the Cache settings Classification: Applications Product: konqueror Version: 22.12.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: claudius+...@hausnetz.lettenbach.com Target Milestone: --- SUMMARY In the FAQ 12.4. https://docs.kde.org/stable5/en/konqueror/konqueror/faq.html#idm3234 "If you select Web Browsing → Cache in the dialog launched by selecting Settings → Configure Konqueror... , you will be presented with a dialog box that lets you disable the cache, clear it or set its size, and change the caching policy" Is my installation broken or does this section no longer exist? If the latter: Where are users supposed to set cache settings for kio-http? SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.6-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 462706] Since updating to 5.100 kded segfaults in Packagekit (likely during update check)
https://bugs.kde.org/show_bug.cgi?id=462706 --- Comment #4 from Claudius --- (In reply to Bernhard Übelacker from comment #3) > I tried to bring this to the attention of packagekit-qt Thank you! I didn't have the time to report it to upstream yet. It also doesn't seem to happen every time. It might be some sort of race condition. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 462706] New: Since updating to 5.100 kded segfaults in Packagekit (likely during update check)
https://bugs.kde.org/show_bug.cgi?id=462706
Bug ID: 462706
Summary: Since updating to 5.100 kded segfaults in Packagekit
(likely during update check)
Classification: Frameworks and Libraries
Product: frameworks-kded
Version: 5.100.0
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: claudius+...@hausnetz.lettenbach.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
Konqi reports a crash in the tray after login. Updates notification does not
appear.
I have not experienced any other problems during daily use however.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.11-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor
Memory: 15.5 GiB of RAM
ADDITIONAL INFORMATION
Backtrace:
Application: kded5 (kded5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f854a28 in PackageKit::Transaction::role() const () at
/usr/lib/libpackagekitqt5.so.1
#7 0x7f854bf1450e in TransactionWatcher::watchTransaction(QDBusObjectPath
const&, bool) (this=this@entry=0x55f791044070, tid=...,
interactive=interactive@entry=false) at
/usr/src/debug/apper-1.0.0/apperd/TransactionWatcher.cpp:104
#8 0x7f854bf1478f in
TransactionWatcher::transactionListChanged(QStringList const&)
(this=0x55f791044070, tids=) at
/usr/src/debug/apper-1.0.0/apperd/TransactionWatcher.cpp:85
#9 0x7f85c28bda51 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff9194c420, r=, this=0x7f85b8068460, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate(QObject*, int, void**) (sender=0x55f791042890,
signal_index=8, argv=0x7fff9194c420) at kernel/qobject.cpp:3919
#11 0x7f854a87caba in
PackageKit::Daemon::transactionListChanged(QStringList const&) () at
/usr/lib/libpackagekitqt5.so.1
#12 0x7f85c28bdc00 in doActivate(QObject*, int, void**)
(sender=0x55f791042790, signal_index=5, argv=0x7fff9194c570) at
kernel/qobject.cpp:3931
#13 0x7f854a8953a9 in () at /usr/lib/libpackagekitqt5.so.1
#14 0x7f854a896393 in () at /usr/lib/libpackagekitqt5.so.1
#15 0x7f85c3b4845f in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) [clone .constprop.0]
(this=, object=, msg=,
metaTypes=, slotIdx=) at
/usr/src/debug/qt5-base/qtbase/src/dbus/qdbusintegrator.cpp:1001
#16 0x7f85c28b0be0 in QObject::event(QEvent*) (this=0x55f791042790,
e=0x7f85b8068310) at kernel/qobject.cpp:1347
#17 0x7f85c3578b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55f791042790, e=0x7f85b8068310) at
kernel/qapplication.cpp:3637
#18 0x7f85c288cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55f791042790, event=0x7f85b8068310) at
kernel/qcoreapplication.cpp:1064
#19 0x7f85c288daa3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55f790607f00) at
kernel/qcoreapplication.cpp:1821
#20 0x7f85c28d3e68 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55f7907f5860) at kernel/qeventdispatcher_glib.cpp:277
#21 0x7f85c171687b in g_main_dispatch (context=0x7f85b8005010) at
../glib/glib/gmain.c:3444
#22 g_main_context_dispatch (context=0x7f85b8005010) at
../glib/glib/gmain.c:4162
#23 0x7f85c176d299 in g_main_context_iterate.constprop.0
(context=0x7f85b8005010, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4238
#24 0x7f85c1715132 in g_main_context_iteration (context=0x7f85b8005010,
may_block=1) at ../glib/glib/gmain.c:4303
#25 0x7f85c28d7c4c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55f7907f6690, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#26 0x7f85c288573c in
QEventLoop::exec(QFlags) (this=0x7fff9194cb90,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#27 0x7f85c2890269 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#28 0x7f85c2d3a112 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#29 0x7f85c3576f2a in QApplication::exec() () at
kernel/qapplication.cpp:2829
#30 0x55f78e833040 in main(int, char**) (argc=,
argv=) at /usr/src/debug/kded/kded-5.100.0/src/kded.cpp:770
[Inferior 1 (process 1116) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 458837] When connecting to pptp vpn DNS Servers are set in resolv.conf even if disabled
https://bugs.kde.org/show_bug.cgi?id=458837 --- Comment #1 from Claudius --- I can confirm this is still an issue with Plasma 5.26.3 and Frameworks 5.99.0. A workaround is manually restoring resolv.conf or running: nmcli general reload dns-rc -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #81 from Claudius Ellsel --- Alright! I'll have another look at it when I test again. Likely, it's not a bug in KWin, but not sure :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #79 from Claudius Ellsel --- (In reply to Nate Graham from comment #78) > Unfortunately I got confused and duped a bunch of X11 bugs to this, and that > issue has been fixed. Sorry for that. At this point it's confusing to > re-open the original issue given that it was (unfortunately incorrectly) > marked as the parent for 9 duplicate reports, so let's keep this one closed. > > Regardless, apps don't do their own positioning on Wayland, so your original > issue was purely a KWin problem. So for simplicity's sake, if you're still > experiencing it with Plasma 5.26 (which made improvements here) please > submit a bug report on KWin. Thanks! Works for me! As has asked before, it seems that https://bugs.kde.org/show_bug.cgi?id=15329 already might be about this exact problem? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #77 from Claudius Ellsel --- (In reply to Viktor Jägersküpper from comment #76) > (In reply to Nate Graham from comment #10) > > The feature to remember window sizes and positions using KXMLGui is not used > > on Wayland. > > > > Remembering window positions on Wayland requires implementing Bug 15329. > > There was some confusion here about Wayland vs X11, but I think this means > bug 15329 is for Wayland. Nate, can you confirm? Also fine. But If you read my original comment here, I specifically said that it happened on Wayland for me and that I haven't tested on X11. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 Claudius Ellsel changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #75 from Claudius Ellsel --- Reopening for now as this is still not fixed for Wayland. Also see https://invent.kde.org/frameworks/kconfig/-/merge_requests/129#note_527114 for details. Please let me know in case the Wayland problems should be treated in another report. Repurposing bugs that were for Wayland originally and then extended for X11 to be only about X11 probably can happen by accident, though is far from ideal, IMHO. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 458837] New: When connecting to pptp vpn DNS Servers are set in resolv.conf even if disabled
https://bugs.kde.org/show_bug.cgi?id=458837 Bug ID: 458837 Summary: When connecting to pptp vpn DNS Servers are set in resolv.conf even if disabled Product: plasma-nm Version: 5.25.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: claudius+...@hausnetz.lettenbach.com CC: jgrul...@redhat.com Target Milestone: --- SUMMARY When connecting to pptp vpn DNS Servers are set in resolv.conf even if disabled STEPS TO REPRODUCE 1. create pptp vpn 2. set IPv4 - Method: Automatic (Only addresses) 3. connect OBSERVED RESULT DNS Servers get replaced in /etc/resolv.conf EXPECTED RESULT DNS Server stay like they are SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.7-arch1-1 (available in About System) Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.7-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Logs: > pppd[17099]: Plugin /usr/lib/pppd/2.4.9/nm-pptp-pppd-plugin.so loaded. > NetworkManager[17099]: Plugin /usr/lib/pppd/2.4.9/nm-pptp-pppd-plugin.so > loaded. > pppd[17099]: pppd 2.4.9 started by root, uid 0 > kernel: PPP generic driver version 2.4.2 > pptp[17105]: nm-pptp-service-17092 log[main:pptp.c:353]: The synchronous pptp > option is NOT activated > pppd[17099]: Using interface ppp0 > NetworkManager[17099]: Using interface ppp0 > NetworkManager[17099]: Connect: ppp0 <--> /dev/pts/1 > pppd[17099]: Connect: ppp0 <--> /dev/pts/1 > NetworkManager[735]: [1662555212.9226] manager: (ppp0): new Ppp > device (/org/freedesktop/NetworkManager/Devices/6) > kernel: nf_conntrack: default automatic helper assignment has been turned off > for security reasons and CT-based firewall rule not found. Use the iptables > CT target to attach helpers instead. > pptp[17111]: nm-pptp-service-17092 log[ctrlp_rep:pptp_ctrl.c:258]: Sent > control packet type is 1 'Start-Control-Connection-Request' > pptp[17111]: nm-pptp-service-17092 log[ctrlp_disp:pptp_ctrl.c:781]: Received > Start Control Connection Reply > pptp[17111]: nm-pptp-service-17092 log[ctrlp_disp:pptp_ctrl.c:815]: Client > connection established. > pptp[17111]: nm-pptp-service-17092 log[ctrlp_rep:pptp_ctrl.c:258]: Sent > control packet type is 7 'Outgoing-Call-Request' > pptp[17111]: nm-pptp-service-17092 log[ctrlp_disp:pptp_ctrl.c:900]: Received > Outgoing Call Reply. > pptp[17111]: nm-pptp-service-17092 log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing > call established (call ID 63941, peer's call ID 10010). > pppd[17099]: CHAP authentication succeeded > NetworkManager[17099]: CHAP authentication succeeded > kernel: PPP BSD Compression module registered > kernel: PPP Deflate Compression module registered > audit[735]: USYS_CONFIG pid=735 uid=0 auid=4294967295 ses=4294967295 > msg='op=statistics interface="enp39s0" ifindex=2 args=0 pid=1139 uid=1000 > result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? > res=success' > NetworkManager[735]: [1662555214.0852] audit: op="statistics" > interface="enp39s0" ifindex=2 args="0" pid=1139 uid=1000 result="success" > audit[735]: USYS_CONFIG pid=735 uid=0 auid=4294967295 ses=4294967295 > msg='op=statistics interface="enp39s0" ifindex=2 args=500 pid=1345 uid=1000 > result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? > res=success' > NetworkManager[735]: [1662555214.0873] audit: op="statistics" > interface="enp39s0" ifindex=2 args="500" pid=1345 uid=1000 result="success" > kernel: audit: type= audit(1662555214.083:234): pid=735 uid=0 > auid=4294967295 ses=4294967295 msg='op=statistics interface="enp39s0" > ifindex=2 args=0 pid=1139 uid=1000 result=success > exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=?> > kernel: audit: type= audit(1662555214.083:235): pid=735 uid=0 > auid=4294967295 ses=4294967295 msg='op=statistics interface="enp39s0" > ifindex=2 args=500 pid=1345 uid=1000 result=success > exe="/usr/bin/NetworkManager" hostname=? addr=? terminal> > pppd[17099]: Cannot determine ethernet address for proxy ARP > NetworkManager[17099]: Cannot determine ethernet address for proxy ARP > NetworkManager[17099]: local IP address 192.168.xxx > NetworkManager[17099]: remote IP address 192.168.xxx > NetworkManager[17099]: primary DNS address 212.121.xxx > NetworkManager[17099]: secondary DNS address 212.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 --- Comment #9 from Claudius Ellsel --- I cannot reproduce anymore, so might have gotten fixed somewhere in the meantime. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427805] Highlight changed settings has problems with localized places locations
https://bugs.kde.org/show_bug.cgi?id=427805 --- Comment #6 from Claudius Ellsel --- With German, this works for me. Is this still an issue with other locales? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #68 from Claudius Ellsel --- (In reply to evea from comment #65) > I do not understand why the title still mentions, and the bug is limited to > X11. The exact same symptoms happen with Wayland. It isn't. The X11 part is just an addition of what is needed to trigger this bug on X11, as far as I see it. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 448935] Kde Handbook is hard to read, missing spaces
https://bugs.kde.org/show_bug.cgi?id=448935 Claudius changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||claudius+kde@hausnetz.lette ||nbach.com Ever confirmed|0 |1 --- Comment #3 from Claudius --- I can confirm this issue. Changing the "sans serif font" from "Noto Sans" to a monospaced font (Luxi Mono) has fixed the issue. This makes the text boxes overflow and causes misaligned highlights but the text is readable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #29 from Claudius --- Something I just tried: I have a pesky single org.kde.plasma.notifications widget that never saved its position (even when re-creating it). When I manually edited the Containment's ItemGeometries- line by appending an entry of where I wanted it and did a shell restart. It worked. And now all of a sudden the entry is updated when moving the widget. Before the Entry was missing and I had the widget in the upper left corner (like the other reports). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Claudius changed: What|Removed |Added CC|claudius+kde@hausnetz.lette | |nbach.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437883] the Terminal options for adding a startup application have no effect
https://bugs.kde.org/show_bug.cgi?id=437883 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com --- Comment #5 from Claudius --- I had the same issues. I disabled systemd-autostart using > kwriteconfig5 --file startkderc --group General --key systemdBoot false and everything went back to normal. KeePass now also always starts properly instead of only sometimes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427124] Window sizes are not correctly restored on Wayland
https://bugs.kde.org/show_bug.cgi?id=427124 --- Comment #8 from Claudius Ellsel --- (In reply to Vlad Zahorodnii from comment #7) > Should be fixed in 5.24 Hm, not sure. I think I didn't see improvement when I checked. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436516] Kopete does nto start as "online" even when configured to do so
https://bugs.kde.org/show_bug.cgi?id=436516 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com --- Comment #1 from Claudius --- So it is not only me. I thought I was doing something wrong. This still seems to be an issue. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 450209] Put Download Link on website
https://bugs.kde.org/show_bug.cgi?id=450209 --- Comment #1 from Claudius --- (that latter link is only found in the gitlab README.md) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 450209] New: Put Download Link on website
https://bugs.kde.org/show_bug.cgi?id=450209 Bug ID: 450209 Summary: Put Download Link on website Product: kdiff3 Version: 1.9.4 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: kde.b...@wolki.de Target Milestone: --- Currently, The kdiff3 website (https://apps.kde.org/kdiff3/) only lists flathub and appstream buttons and a link to the binary-factory jenkins https://binary-factory.kde.org/ where I then have to filter myself to find some nightly build for kdiff3. There are, however, well-working release builds for kdiff3 here: https://download.kde.org/stable/kdiff3/?C=M;O=D I would like to suggest replacing the binary-factory link with the download.kde.org link, because that actually lists releases. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 --- Comment #11 from Claudius --- Same issue here. When it happens all of my Google Calendar items are missing. Opening the Google Groupware config dialog in Korganizer and pressing OK or Apply without changing anything makes everything reappear. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 Claudius changed: What|Removed |Added CC||claudius+kde@hausnetz.lette ||nbach.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382179] Keep in Add a Face Tag mode after adding a face tag
https://bugs.kde.org/show_bug.cgi?id=382179 --- Comment #13 from Claudius --- after working ~3 minutes with Ctrl+Click I am now pretty convinced that this should be the standard behaviour. I just went through 40 images in the time I usually need for 10. no tooltip, no ctrl+click, just: I press that button, and it toggles on into add face tag. (just like the button right next to it, that displays or hides the existing face tags). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382179] Keep in Add a Face Tag mode after adding a face tag
https://bugs.kde.org/show_bug.cgi?id=382179 --- Comment #12 from Claudius --- I was reffered to this ticket because I created a duplicate (sorry, I did not find this one myself). I think, the ctrl shortcut absolutely needs a tooltip or something. I don't think I would ever have tried that on my own. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442014] Request: Keyboard Shortcut for "add face tag"
https://bugs.kde.org/show_bug.cgi?id=442014 --- Comment #3 from Claudius --- thanks for the heads up! Didn't find that one while searching. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442014] New: Request: Keyboard Shortcut for "add face tag"
https://bugs.kde.org/show_bug.cgi?id=442014 Bug ID: 442014 Summary: Request: Keyboard Shortcut for "add face tag" Product: digikam Version: 7.3.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@wolki.de Target Milestone: --- Created attachment 141298 --> https://bugs.kde.org/attachment.cgi?id=141298&action=edit add face tag button in preview mode In Digikam's preview mode, there is this button to add a face tag (see screenshot below, I might have the wrong name for it). This is a thing I use frequently and I would like to assign a keyboard shortcut to this functionality. Currently, it does not come up in the keyboard shortcut list. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438831] Regression: speech recognition setup fails with "The speech script was not found, check your install."
https://bugs.kde.org/show_bug.cgi?id=438831 --- Comment #2 from Claudius --- I tried `kdenlive-master-797-windows-mingw_64-gcc.7z` (build on 2021-06-20) and it also gives me the "script was not found" message. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438306] Speech to text doesn't work
https://bugs.kde.org/show_bug.cgi?id=438306 --- Comment #7 from Claudius --- windows 10 20H2 Build 19042.1052 to be precise -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438306] Speech to text doesn't work
https://bugs.kde.org/show_bug.cgi?id=438306 --- Comment #6 from Claudius --- I run windows 10, but I _also_ had problems with 21.04.2. Could you try 21.04.1 instead? I reported my exact error here: https://bugs.kde.org/show_bug.cgi?id=438831 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438306] Speech to text doesn't work
https://bugs.kde.org/show_bug.cgi?id=438306 Claudius changed: What|Removed |Added CC||kde.b...@wolki.de --- Comment #4 from Claudius --- @emohr: I can report that I have vosk 0.3.30 running here. (I also successfully used 0.3.27 before that) Both in kdenlive 21.04.1 on a windows machine. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438831] New: Regression: speech recognition setup fails with "The speech script was not found, check your install."
https://bugs.kde.org/show_bug.cgi?id=438831 Bug ID: 438831 Summary: Regression: speech recognition setup fails with "The speech script was not found, check your install." Product: kdenlive Version: 21.04.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: kde.b...@wolki.de Target Milestone: --- Created attachment 139451 --> https://bugs.kde.org/attachment.cgi?id=139451&action=edit script not found error message in 21.04.2 SUMMARY I did use the speech recognition successfully on the same machine with 21.04.1. After uninstalling and updating to 21.04.2, this stopped working. The configuration screen now has an orange error message at the bottom that reads "The speech script was not found, check your install." I would like to emphasize that it _did_ in fact work before, and that I _do_ have vosk and srt installed. I also saw #438306 but this seems to be a different error. I also tried installing various versions of vosk (including the previously working 0.3.27, the latest version 0.3.30 and the one mentioned in the other ticket 0.3.22). STEPS TO REPRODUCE 1. Install kdenlive 21.04.2 2. Install vosk and srt via pip3 3. Open kdenlive 4. Go to configuration screen / speech to text 5. Add a speech model 6. click "check configuration" OBSERVED RESULT There's an error telling me > The speech script was not found, check your install. but no information which script this might be. Also starting any recognition (of course) yields a note that I'd need to firstly configure speech to text. EXPECTED RESULT Speech recognition should work as in the previous release. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION As pointed out before, this setup used to work in 21.04.1. Downgrading to 21.04.1 immediately fixes this problem (even with vosk 0.3.30). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 --- Comment #5 from Claudius Ellsel --- During further investigation, I made some interesting findings. I did not find a Wayland application with this problem (but I also don't know of one that has a text cursor apart from input fields). While testing with LibreOffice, I managed to reproduce the problem (but only when there was no cursor blinking). Also, I noticed that the problem doesn't happen in Firefox if I have systemsettings open focused with a blinking cursor in the text field. I assume that it doesn't have to be systemsettings. In LibreOffice when there was a blinking "cursor", I noticed that the mouse cursor changed from normal to text after moving from normal content over text content in the frequency of the "cursor" blinking in the text field (the same happens the other way around when moving the mouse from text over normal content). There is a delay for changing the mouse cursor that seems to "wait" for the "cursor" in the text field to blink. I thus assume that somehow the text field "cursor" blinking is interfering or limiting some function that checks for the mouse cursor position in order to change it matching the content. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 --- Comment #4 from Claudius Ellsel --- I can also reproduce on other webpages like Wikipedia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 Claudius Ellsel changed: What|Removed |Added Status|NEEDSINFO |REPORTED Keywords||wayland Resolution|WAITINGFORINFO |--- --- Comment #3 from Claudius Ellsel --- Finally, I got around to test a bit further. I cannot reproduce it on Bugzilla with X11, so setting Wayland keyword. Not sure whether it happens on other webpages, I think I mostly noticed it on Bugzilla. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell on wayland in DeclarativeMimeData::DeclarativeMimeData() when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #27 from Claudius Ellsel --- Sounds promising :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #13 from Claudius Ellsel --- Your use cases for the already existing options also apply to the ones I am suggesting, though. On a multi-user system, a user might want to restore his previous used state (and this cannot be done at login screen level). I understand now, though that apart from those use cases it might be better to have the functionality implemented somewhere else, although I am not sure whether it can be done at a central point, so all distributions can benefit, maybe SDDM? But that would be off-topic. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #11 from Claudius Ellsel --- (In reply to Wolfgang Bauer from comment #10) > (In reply to Claudius Ellsel from comment #9) > > Then this issue still remains relevant for KDE in my opinion. Basically I > > think it will be beneficial to for example have a fourth option that will > > use the BIOS setting (or/and another one that restores this setting from the > > previous session). > I'm not sure it's possible from the KDE/Plasma side, and I don't see why > Plasma should change it to be different than on the login screen. > > That's my opinion, of course. It already is possible to set the setting to "on" and "off", so "remember" or "use BIOS value" might also work. If Plasma shouldn't change it to be different from the login screen than even the already existing options are a bit pointless. But if it can be already done at login screen level, that would be even better, I guess. > > Ideally openSUSE would "upstream" the things they do for this and then use > > the setting from KDE instead of relying on a hidden service for this. > That has no relevance to KDE though. It's a service that runs on boot and > also affects text mode. I agree that the service itself has no relevance. But the NumLock features are something I'd really like to see in KDE as well. But I might be wrong here and getting that correct is up to every distribution, because it has to be done at a lower level (unfortunately both distros with KDE that I have used, Manjaro and Tumbleweed, currently don't seem to get this right, so I thought a more centralistic solution might help). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428594] Firefox window thumbnails are sometimes empty
https://bugs.kde.org/show_bug.cgi?id=428594 Claudius Ellsel changed: What|Removed |Added Keywords||wayland CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432350] New: Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 Bug ID: 432350 Summary: Mouse cursor often does not change on Firefox in Wayland Product: plasmashell Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: claudius.ell...@live.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On Firefox (and possible other XWayland applications) the mouse cursor doesn't always change. Examples are when I am over text and the cursor should change to a "text" cursor. Or when I somehow get it to change to that cursor and move away from the text, but it still is a text cursor and doesn't change back to a normal one. STEPS TO REPRODUCE 1. A page where this happens is https://bugs.kde.org/enter_bug.cgi 2. Move the mouse around over the content SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210128 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 This might be unrelated to Wayland or Plasma, haven't thoroughly tested. Maybe this is a Firefox bug in general. Product and component might be wrong. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432349] Switching from Wayland to X11 changes or resets the primary screen there
https://bugs.kde.org/show_bug.cgi?id=432349 --- Comment #1 from Claudius Ellsel --- At some point in the past, but maybe only on a different distribution, this worked fine without this bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432349] New: Switching from Wayland to X11 changes or resets the primary screen there
https://bugs.kde.org/show_bug.cgi?id=432349 Bug ID: 432349 Summary: Switching from Wayland to X11 changes or resets the primary screen there Product: KScreen Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: claudius.ell...@live.de Target Milestone: --- SUMMARY When I switch from a Wayland to an X11 session the primary screen of X11 is not the one it used to be. STEPS TO REPRODUCE 1. Have a multi monitor setup (I have a vertical one on the left and a horizontal one on the right. The right monitor is set as primary on X11). 2. Configure the monitors in X11 to work as written in 1. 3. Logout and login to a Wayland session 4. Due to another bug the vertical screen will have the wrong orientation on Wayland. Change that in KScreen to look normal (might be completely unrelated, though) 5. Logout and login to an X11 session OBSERVED RESULT The left monitor is now the primary screen EXPECTED RESULT The primary screen should stay as it was (the right screen) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210128 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 --- Comment #7 from Claudius Ellsel --- (In reply to Méven Car from comment #6) > Could you run `kscreen-doctor -o` This gives: Output: 33 XWAYLAND0 enabled connected Unknown Modes: 36:2560x1440@60*! Geometry: 1080,240 2560x1440 Scale: 1 Rotation: 1 Output: 35 XWAYLAND1 enabled connected Unknown Modes: 37:1920x1080@60*! Geometry: 0,0 1080x1920 Scale: 1 Rotation: 8 > The issue is somehow KWin screens names are different from > QApplication::screens() Hm. That might have been caused by me running multiple screens. I also switch between X11 and Wayland sessions which might introduce further problems (for example when switching from Wayland to X11 I have to correct the screen orientation of my vertical screen due to a different issue and also X11 currently always makes that one primary). Might not be related at all, though. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Claudius Ellsel changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Claudius Ellsel --- On a second test it worked for me, so most likely a false alarm. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 --- Comment #7 from Claudius Ellsel --- (In reply to David Edmundson from comment #1) > Fixed recently > > b2ebd8f2ca332473f09e589d9e7ee0af0e1c7d98 in drkonqi For convenience: https://invent.kde.org/plasma/drkonqi/-/commit/b2ebd8f2ca332473f09e589d9e7ee0af0e1c7d98 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de --- Comment #6 from Claudius Ellsel --- Any chance this is related to or the same as https://bugs.kde.org/show_bug.cgi?id=429136? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 432319] Crash as soon as typing in the bug description box
https://bugs.kde.org/show_bug.cgi?id=432319 Claudius Ellsel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Claudius Ellsel --- *** This bug has been marked as a duplicate of bug 429136 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 429136] Crash reporting assistant crashes on Wayland when I type anything in "Information about the crash" text box
https://bugs.kde.org/show_bug.cgi?id=429136 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de --- Comment #2 from Claudius Ellsel --- *** Bug 432319 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 432319] New: Crash as soon as typing in the bug description box
https://bugs.kde.org/show_bug.cgi?id=432319 Bug ID: 432319 Summary: Crash as soon as typing in the bug description box Product: drkonqi Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: claudius.ell...@live.de Target Milestone: --- SUMMARY When I want to create a bug report, the application crashes as soon as I type in the bug description. STEPS TO REPRODUCE 1. Have an application crash (like systemsettings) 2. A notification appears and offers to report that crash 3. Dr. Konqi opens and guides through the steps (I selected that I remember what I did when the application crashed) 4. Sign in to the Bugzilla account 5. Select to create a new bug 6. The page for entering the new bug's details opens OBSERVED RESULT Entering the title works but as soon as I type in the bug description box the application crashes. EXPECTED RESULT The application doesn't crash. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210128 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 --- Comment #5 from Claudius Ellsel --- This seems to be unrelated to multiple screens (at least I got the same error in the terminal after deactivating my second monitor in KScreen). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 Claudius Ellsel changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Claudius Ellsel --- (In reply to Andrey from comment #2) > What's in the error message? > Also you could try to run in from terminal to see more prompt output. Basically it just says that it cannot take a screenshot. I did not find an easy way to screenshot that window, as it is Spectacle and usually not wanted on Screenshots. Running from terminal was a good idea. It gives the following error message when trying to create a rectangular screenshot: `Error calling KWin DBus interface: "org.kde.kwin.Screenshot.Error.ScreenMissing" "Screen not found"` (In reply to Méven Car from comment #3) > Where you using multiple screens ? > What is the version of spectacle used ? Yes, I am using multiple screens. Version of Spectacle used is 20.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Claudius Ellsel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Claudius Ellsel --- Alright. I am marking this as waitingforinfo, as everything might be working completely fine. The instance where the screen was still on after I was afk for about 30 Minutes might have been caused by my mouse slightly moving and thus turning the screen on again. I'll have to try again properly, and probably it will also work for me, so false alarm. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #17 from Claudius Ellsel --- Mh, looking at the videos here, the symptoms look different compared to https://bugs.kde.org/show_bug.cgi?id=427127 (and this here seems to also happen on X11). So I am not entirely sure whether that one is actually a duplicate of this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 --- Comment #4 from Claudius Ellsel --- *** This bug has been marked as a duplicate of bug 416048 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #16 from Claudius Ellsel --- *** Bug 432255 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #15 from Claudius Ellsel --- Just to confirm, this only happens on Wayland as on the duplicate, correct? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #14 from Claudius Ellsel --- *** Bug 427127 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427127] Sometimes tooltips of systray applets and widgets placed on Plasma panel are corrupted on Wayland
https://bugs.kde.org/show_bug.cgi?id=427127 Claudius Ellsel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Claudius Ellsel --- *** This bug has been marked as a duplicate of bug 416048 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #13 from Claudius Ellsel --- Since this bug is the older one and contains more information, I am reversing the duplicate direction. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432242] Visual glitch behind integrated terminals on Wayland session
https://bugs.kde.org/show_bug.cgi?id=432242 --- Comment #2 from Claudius Ellsel --- Related to https://bugs.kde.org/show_bug.cgi?id=429025? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432242] Visual glitch behind integrated terminals on Wayland session
https://bugs.kde.org/show_bug.cgi?id=432242 Claudius Ellsel changed: What|Removed |Added Keywords||wayland CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 --- Comment #2 from Claudius Ellsel --- Just tested on X11 and I have a similar experience there. Waited about a minute but nothing changed. However, I am not entirely sure anymore how long it used to take the screens to turn off after locking the screen. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 Claudius Ellsel changed: What|Removed |Added Keywords||wayland --- Comment #1 from Claudius Ellsel --- Wayland only, X11 is fine. Setting keyword. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] New: Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 Bug ID: 432260 Summary: Spectacle fails to create rectangular screenshots Product: Spectacle Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: claudius.ell...@live.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY When I want to create a rectangular screenshot I get an error message. STEPS TO REPRODUCE 1. Launch Spectacle 2. Select the "rectangular area" mode from the dropdown 3. Click the button to create a new screenshot OBSERVED RESULT An error message is displayed EXPECTED RESULT The mode for rectangular screenshots is launched Happens on Wayland, will also test on X11. This might be a regression. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210127 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 --- Comment #1 from Claudius Ellsel --- I am rather sure this is a regression (although I haven't used Tumbleweed Wayland that often). Setting the keyword. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Claudius Ellsel changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] New: Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Bug ID: 432259 Summary: Screen does not seem to turn off when locked Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: claudius.ell...@live.de CC: bhus...@gmail.com Target Milestone: --- SUMMARY On the current Plasma Beta (5.20.90) I noticed that the screen doesn't seem to turn off when I lock it (shortcut Meta + L). Currently only tested on Wayland. STEPS TO REPRODUCE 1. Start a session 2. Lock the screen 3. Wait a short amount of time for the displays to turn off OBSERVED RESULT The displays stay on EXPECTED RESULT The displays are turned off SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210127 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 --- Comment #2 from Claudius Ellsel --- Another affected application is Dolphin, others like systemsettings work fine. Possibly the root cause is at a higher level, but I thought for the beginning I'd file this for a specific app. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 --- Comment #1 from Claudius Ellsel --- I am pretty confident this is a regression, although I cannot say that for sure. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 Claudius Ellsel changed: What|Removed |Added Keywords||regression, usability, ||wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] New: Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 Bug ID: 432256 Summary: Some applications including Konsole don't show resize handles for the lower three edges Product: konsole Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: claudius.ell...@live.de Target Milestone: --- SUMMARY On Wayland some applications don't show resize handles for me on their lower three edges. The top edge works. STEPS TO REPRODUCE 1. Open Konsole 2. Move the mouse to the lower edge OBSERVED RESULT No resize handle appears EXPECTED RESULT A resize handle should appear SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210127 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 --- Comment #2 from Claudius Ellsel --- The "black" or dark bar on the right is in fact not black, but the card turns semi transparent in that region apparently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 Claudius Ellsel changed: What|Removed |Added Keywords||wayland --- Comment #1 from Claudius Ellsel --- Only happens on Wayland, setting keyword. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 Claudius Ellsel changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] New: Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 Bug ID: 432255 Summary: Hovercard background is sometimes not correct Product: plasmashell Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: claudius.ell...@live.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 135270 --> https://bugs.kde.org/attachment.cgi?id=135270&action=edit Screenshot of the problem SUMMARY When hovering from right to left over the icons the background of the hovercards is not correct. I started at the Firefox icon and then moved over the Dolphin icon where you can see a black stripe on the right. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210121 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.7-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #26 from Claudius Ellsel --- (In reply to Shawn from comment #25) > I have a dual monitor setup with both resolutions at 2560x14440. I can't do > any of the coding stuff that you guys do, but if there is something I can > test to help, let me know. I say this because most of the comments I see > are from ppl that have a laptop + some other screen, possibly with different > resolutions. A screenshot of your screen setup (and arrangement) from the systemsettings might be interesting. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425796] Screen rotation is applied the wrong orientation in KCM on Wayland
https://bugs.kde.org/show_bug.cgi?id=425796 Claudius Ellsel changed: What|Removed |Added Platform|Manjaro |openSUSE RPMs Version|5.20.0 |5.20.90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425796] Screen rotation is applied the wrong orientation in KCM on Wayland
https://bugs.kde.org/show_bug.cgi?id=425796 Claudius Ellsel changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Claudius Ellsel --- Reopening here, as I ran into this bug again when testing the 5.20.90 Beta on openSUSE Tumbleweed. Not sure whether this is a regression or only ever was fixed for the compiled from master session I tested with. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432101] Screen rotation mixup bug on Wayland seems to have regressed with the Beta
https://bugs.kde.org/show_bug.cgi?id=432101 Claudius Ellsel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #2 from Claudius Ellsel --- I will reopen and mark this a duplicate then. I wasn't sure whether reopening was the correct thing to do here, as the issue appeared to have been fixed in the past when I tested. But the symptoms are the same. The only difference is that I experience this on openSUSE Tumbleweed (in contrast to Manjaro or a compiled from master session there where it was no longer occurring). *** This bug has been marked as a duplicate of bug 425796 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425796] Screen rotation is applied the wrong orientation in KCM on Wayland
https://bugs.kde.org/show_bug.cgi?id=425796 --- Comment #11 from Claudius Ellsel --- *** Bug 432101 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 Claudius Ellsel changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Severity|normal |wishlist Resolution|INTENTIONAL |--- --- Comment #9 from Claudius Ellsel --- Ah, then I misunderstood your comment on the openSUSE tracker and thought that would generally apply to KDE in general. Then this issue still remains relevant for KDE in my opinion. Basically I think it will be beneficial to for example have a fourth option that will use the BIOS setting (or/and another one that restores this setting from the previous session). This is at least what I as a user would expect, not sure whether it makes sense from an architectural / distribution point of view. Ideally openSUSE would "upstream" the things they do for this and then use the setting from KDE instead of relying on a hidden service for this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #36 from Claudius Ellsel --- (In reply to Greg Lepore from comment #32) > See attachment. NumLock is set to "Turn on" and kreadconfig5 --file > kcminputrc --group Keyboard --key NumLock shows "0". These appear to be > incompatible settings. > > I think my screenshot is accurately portraying the submitters report, isn't > it? Hm, I am not an expert, but it seems as if changes of this preference are not transferred correctly to the settings file? Out of curiosity, does the output of that command change if you change the preference in the settings? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #7 from Claudius Ellsel --- (In reply to Wolfgang Bauer from comment #5) > (In reply to Claudius Ellsel from comment #0) > > Also, Ideally that would already work at either Kernel > > or SDDM level, not sure what causes the problems there. > In that case, it should be reported to the kernel or SDDM though. > > At least SDDM does have a setting for this: > Numlock= > Change numlock state when sddm-greeter starts. Valid values > are on, off > or none. If property is set to none, numlock won't be > changed. Default > value is "none". Yup, just wanted to make sure first that I get the scope of the problem correctly. As I wrote before, NumLock is already off for SDDM. Does the `none` value there also means that it is supposed to read the BIOS value or just that it doesn't touch NumLock at all meaning when the Kernel has turned it off it will just stay at that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #6 from Claudius Ellsel --- (In reply to Wolfgang Bauer from comment #2) > "Don't change" means exactly that: don't change it. > > So I don't see how this can possibly be a KDE bug. Ah, I thought it meant don't change from the previous state (in the boot process), meaning if SDDM or some other previous applications changed it, it will remain unchanged. But apparently that is not what it means, instead it means that the value set in BIOS will be applied? In this case this is indeed intentional (apart from apparently downstream bugs where this does not work like on Tumbleweed or Manjaro). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #1 from Claudius Ellsel --- Copying over my comment from https://bugs.kde.org/show_bug.cgi?id=368063, since that was misplaced there: After witnessing the changes on the NumLock LED (before my keyboard did not have one), I am wondering whether this also has something to do with SDDM or Linux kernel options (at least when the option is set to "leave unchanged"). When booting, the NumLock LED is already off when SDDM shows up. If I remember correctly that is explicitly also the case when one has enabled NumLock to turn on when booting in the BIOS settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #28 from Claudius Ellsel --- Since this bug is (at least originally) about cases where the preference to always turn NumLock on is explicitly set, I created another one generally tracking the problem that this is not the default value: https://bugs.kde.org/show_bug.cgi?id=432107. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Claudius Ellsel changed: What|Removed |Added Summary|NumLock not turned on |NumLock not is not turned ||on at start, although the ||preference for it is set to ||`on` in kcm_keyboard -- You are receiving this mail because: You are watching all bug changes.
