[kdeconnect] [Bug 424159] Using smartphone gps via kdeconnect
https://bugs.kde.org/show_bug.cgi?id=424159 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420068] kde connect as phone backup tool
https://bugs.kde.org/show_bug.cgi?id=420068 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 382365] kdeconnect does not connect automatically
https://bugs.kde.org/show_bug.cgi?id=382365 --- Comment #13 from Juha Tuomala --- Same with iPhone, I think there is also a problem that phone-app doesn't start itself automatically. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 382365] kdeconnect does not connect automatically
https://bugs.kde.org/show_bug.cgi?id=382365 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425619] Application: akonadi_imap_resource_5 (akonadi_imap_resource), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425619 --- Comment #10 from Marcel --- Created attachment 158476 --> https://bugs.kde.org/attachment.cgi?id=158476&action=edit New crash information added by DrKonqi akonadi_imap_resource (5.23.0 (23.04.0)) using Qt 5.15.9 I woke up my device from suspend to RAM and pressed "Check Mail" in KMail. -- Backtrace (Reduced): #4 QHash::findNode(QByteArray const&, unsigned int*) const (ahp=, akey=, this=) at /usr/src/debug/akonadi-23.04.0/src/core/attributestorage.cpp:69 #5 QHash::contains(QByteArray const&) const (akey=, this=) at /usr/include/qt5/QtCore/qhash.h:920 #6 Akonadi::AttributeStorage::hasAttribute(QByteArray const&) const (type=..., this=0x40) at /usr/src/debug/akonadi-23.04.0/src/core/attributestorage.cpp:69 #7 Akonadi::Collection::hasAttribute(QByteArray const&) const (this=this@entry=0x557b6d344140, type=...) at /usr/src/debug/akonadi-23.04.0/src/core/collection.cpp:163 #8 0x7ff81da45909 in Akonadi::Collection::hasAttribute() const (this=0x557b6d344140) at /usr/src/debug/akonadi-23.04.0/src/core/collection.h:595 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425619] Application: akonadi_imap_resource_5 (akonadi_imap_resource), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425619 Marcel changed: What|Removed |Added CC||k...@retux.de -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468987] Elisa scan not picking up files from NTFS partition
https://bugs.kde.org/show_bug.cgi?id=468987 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 469033] New: Akonadi crashes at startup after update from 27.4. on open suse
https://bugs.kde.org/show_bug.cgi?id=469033 Bug ID: 469033 Summary: Akonadi crashes at startup after update from 27.4. on open suse Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: branislav.klo...@orava.sk CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.23.0 (23.04.0)) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.12-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Akonadi crashes at startup after update from 27.4. on opene suse. It was just a regular DUP. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x562d10124b23 in Akonadi::Server::Tracer::error (this=0x0, componentName=0x562d10171de9 "DataStore (Database Error)", msg=...) at /usr/src/debug/akonadi-23.04.0/src/server/tracer.cpp:135 #5 0x562d100e4fa1 in Akonadi::Server::DataStore::debugLastDbError (this=, actionDescription=) at /usr/src/debug/akonadi-23.04.0/src/server/storage/datastore.cpp:1295 #6 0x562d100d406a in Akonadi::Server::DataStore::open (this=0x562d11a73d20) at /usr/src/debug/akonadi-23.04.0/src/server/storage/datastore.cpp:116 #7 0x562d100d83db in Akonadi::Server::DataStore::database (this=0x562d11a73d20) at /usr/src/debug/akonadi-23.04.0/src/server/storage/datastore.cpp:138 #8 0x562d100688fe in Akonadi::Server::AkonadiServer::setupDatabase (this=) at /usr/src/debug/akonadi-23.04.0/src/server/akonadi.cpp:257 #9 0x562d1006a75d in Akonadi::Server::AkonadiServer::init (this=0x7fff342f2780) at /usr/src/debug/akonadi-23.04.0/src/server/akonadi.cpp:107 #10 0x7fb70ed18c50 in QObject::event (this=0x7fff342f2780, e=0x562d11a73290) at kernel/qobject.cpp:1347 #11 0x7fb70ecec94d in doNotify (event=0x562d11a73290, receiver=0x7fff342f2780) at kernel/qcoreapplication.cpp:1154 #12 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1140 #13 QCoreApplication::notifyInternal2 (receiver=0x7fff342f2780, event=0x562d11a73290) at kernel/qcoreapplication.cpp:1064 #14 0x7fb70eceff71 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x562d11a69700) at kernel/qcoreapplication.cpp:1821 #15 0x7fb70ed46713 in postEventSourceDispatch (s=0x562d11a6f080) at kernel/qeventdispatcher_glib.cpp:277 #16 0x7fb70d1168d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x7fb70d116ce8 in ?? () from /lib64/libglib-2.0.so.0 #18 0x7fb70d116d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x7fb70ed45f26 in QEventDispatcherGlib::processEvents (this=0x562d11a6eda0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #20 0x7fb70eceb40b in QEventLoop::exec (this=this@entry=0x7fff342f25f0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #21 0x7fb70ecf38a0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #22 0x562d10064688 in AkApplicationBase::exec (this=0x7fff342f2750) at /usr/src/debug/akonadi-23.04.0/src/shared/akapplication.cpp:107 #23 main (argc=, argv=) at /usr/src/debug/akonadi-23.04.0/src/server/main.cpp:65 [Inferior 1 (process 13897) detached] The reporter indicates this bug may be a duplicate of or related to bug 376791, bug 383231, bug 387393, bug 388007, bug 392742, bug 439305, bug 468985. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469032] New: Apps are not respecting manual scaling in wayland session
https://bugs.kde.org/show_bug.cgi?id=469032 Bug ID: 469032 Summary: Apps are not respecting manual scaling in wayland session Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ankushkush...@gmail.com Target Milestone: --- SUMMARY *** Apps are not respecting manual scaling in wayland session*** STEPS TO REPRODUCE 1. Scaling Fcator set to 100 %. Ms edge browser working properly. 2. Scaling factor changed to 125%. Ms edge browser scaled to 200%. OBSERVED RESULT Scaling factor of system according to 125% but browser showing factor scaling similar to 200 %. EXPECTED RESULT Scaling factor of system and browser similar i.e. 125%. This was working previously. Issue seen after update of 25th Apr 23. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kde Neon (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467405] Desktop Icons that were arranged in a custom order become alphabetically sorted automatically after a period of time
https://bugs.kde.org/show_bug.cgi?id=467405 --- Comment #20 from waldostealthm...@tutanota.com --- Nevermind I spoke too soon. A slight change from the alphabetical sorting due to deleting some folders survived one or two reboots, but now that I've tried to take advantage of that to put the icons where I actually wanted them, it has reverted after a several hours and a couple screen locks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467405] Desktop Icons that were arranged in a custom order become alphabetically sorted automatically after a period of time
https://bugs.kde.org/show_bug.cgi?id=467405 waldostealthm...@tutanota.com changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450435] Panels missing after unlocking screen after sleep mode
https://bugs.kde.org/show_bug.cgi?id=450435 --- Comment #26 from Alex --- Created attachment 158475 --> https://bugs.kde.org/attachment.cgi?id=158475&action=edit "Manage Desktops and Panels" window -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450435] Panels missing after unlocking screen after sleep mode
https://bugs.kde.org/show_bug.cgi?id=450435 --- Comment #25 from Alex --- wow, so many hidden gems in KDE :o I opened the "Manage Desktops and Panels" and I fond 6 screens instead of the two I expected: 4 more than the two in use. I was able to delete 2, but not the other two: I attach the screenshot where you can see the "Disconnected screen 3" and 4 that I don't know why are there. Since my KDE desktop upgraded all the way through a very old installation it's possible there was some problem during the migration of the config, as you expect. Maybe I can fix by hand what's wrong? -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 468384] Plasma crashes in PipeWireSourceStream::createStream() during interaction after reboot
https://bugs.kde.org/show_bug.cgi?id=468384 martin-ko...@protonmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from martin-ko...@protonmail.com --- Seems to be resolved as of 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 456140] KDE Connect contacts sync only partially working
https://bugs.kde.org/show_bug.cgi?id=456140 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461050] Bogus scam warning with trailing space
https://bugs.kde.org/show_bug.cgi?id=461050 --- Comment #4 from Laurent Montel --- (In reply to Volker Kuhlmann from comment #2) > You mean an actual email where someone has put a link into the body where > the link text in the HTML is the same as the link except with an added space > at the end? It wouldn't take more than 5 seconds for anyone to make such an > email. Yep :) but it seems that it takes you more than 5 seconds :) Thanks -- You are receiving this mail because: You are watching all bug changes.
[ktextaddons] [Bug 469020] Building with QCH=ON fails
https://bugs.kde.org/show_bug.cgi?id=469020 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||1.3.1 Latest Commit||https://invent.kde.org/libr ||aries/ktextaddons/commit/d8 ||7f5f136a7af6bbeb033cacbd971 ||36d89a76b51 --- Comment #1 from Laurent Montel --- Git commit d87f5f136a7af6bbeb033cacbd97136d89a76b51 by Laurent Montel. Committed on 27/04/2023 at 05:48. Pushed by mlaurent into branch '1.3'. Fix Bug 469020: Building with QCH=ON fails FIXED-IN: 1.3.1 M +1-1textautocorrection/core/CMakeLists.txt https://invent.kde.org/libraries/ktextaddons/commit/d87f5f136a7af6bbeb033cacbd97136d89a76b51 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 --- Comment #2 from juan --- Created attachment 158474 --> https://bugs.kde.org/attachment.cgi?id=158474&action=edit with the "-v -v -d -d" options to run the valgrind -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot on many laptops that support charge limits; need to write it on every boot
https://bugs.kde.org/show_bug.cgi?id=450551 shreyashr267+kde_...@gmail.com changed: What|Removed |Added Version|5.24.1 |5.27.4 Platform|Archlinux |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468146] Discrepancy in Game Framerate Perception and Reported FPS Graphs, VSync magic behaviour.
https://bugs.kde.org/show_bug.cgi?id=468146 Edgars changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #12 from Edgars --- I fixed the stuttering issue by compiling the kernel myself. I'm not sure why it worked, but it did. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468745] Konsole Context Menu: Open File Manager Option Fails to Open
https://bugs.kde.org/show_bug.cgi?id=468745 --- Comment #4 from Edgars --- (In reply to Alfonso Murolo from comment #3) > Hi - I have attempted to replicate this bug in Arch Linux ARM with wayland. > I could not reproduce it. > Did you by any chance miss to install kde applications? Is dolphin > installed? Do you have another file manager? > > The following output could be replicated on my machine and seems to be > unrelated to the reported behaviour; in my case, file manager opens > normally. > kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" > not found Yes, I am installing plasma-meta as usual. It includes those applications. I did a full reinstall and now it's working, although I'm not sure why it randomly broke before. Will report if it breaks again. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409196] Flatpak backend doesn't support proxy servers
https://bugs.kde.org/show_bug.cgi?id=409196 shruti singh changed: What|Removed |Added CC||shrutisinghhh12@gmail.c ||om URL||https://www.sevenmentor.com ||/ccna-course-in-nagpur --- Comment #3 from shruti singh --- CCNA classes in Nagpur https://www.sevenmentor.com/ccna-course-in-nagpur -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467886] Crash when opening image from clipboard, downloading directly from a gmail attachment.
https://bugs.kde.org/show_bug.cgi?id=467886 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469003] When using the space key to move, there's a high likelihood that the cursor icon will change to a grabbing hand, and it cannot be reverted unless the software is restarted.
https://bugs.kde.org/show_bug.cgi?id=469003 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467812] login to X11 session hangs (Arm64 on Raspberry Pi 4B)
https://bugs.kde.org/show_bug.cgi?id=467812 --- Comment #14 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426644] Screens go black / unresponsive after sleep or lock
https://bugs.kde.org/show_bug.cgi?id=426644 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #29 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467806] kdenlive 22.12.3 What it is? I spent four days editing the video!!!!
https://bugs.kde.org/show_bug.cgi?id=467806 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458370] The cursor is not visible when moving the cursor
https://bugs.kde.org/show_bug.cgi?id=458370 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 juan changed: What|Removed |Added CC||j...@nbjetron.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 --- Comment #1 from juan --- arch: mips32 sourceCode: http://sourceware.org/pub/valgrind/ version: 3.20.0.tar.bz2 sha256sum: 8536c031dbe078d342f121fa881a9ecd205cb5a78e639005ad570011bdb9f3c6 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] New: run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393
https://bugs.kde.org/show_bug.cgi?id=469031 Bug ID: 469031 Summary: run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (disInstr_MIPS_WRK_10): Assertion `mode64' failed. Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: j...@nbjetron.com Target Milestone: --- SUMMARY *** RUN command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" report error: admin@OpenWrt:/# valgrind --leak-check=full --show-reachable=yes --trace-childre n=yes /usr/bin/nr_ping_monitor& admin@OpenWrt:/# ==5820== Memcheck, a memory error detector ==5820== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==5820== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info ==5820== Command: /usr/bin/nr_ping_monitor ==5820== ==5820== Conditional jump or move depends on uninitialised value(s) ==5820==at 0x4074630: ??? (in /lib/libc.so) ==5820==by 0x4085A9C: ??? (in /lib/libc.so) ==5820== ==5820== Conditional jump or move depends on uninitialised value(s) ==5820==at 0x4073ABC: ??? (in /lib/libc.so) ==5820==by 0x4074088: ??? (in /lib/libc.so) ==5820== ==5820== Conditional jump or move depends on uninitialised value(s) ==5820==at 0x4074650: ??? (in /lib/libc.so) ==5820==by 0x4085A9C: ??? (in /lib/libc.so) ==5820== vex: priv/guest_mips_toIR.c:23393 (disInstr_MIPS_WRK_10): Assertion `mode64' failed. vex storage: T total 42549728 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==5820==at 0x5803F988: ??? (in /usr/lib/valgrind/memcheck-mips32-linux) ==5820==by 0x5803F974: ??? (in /usr/lib/valgrind/memcheck-mips32-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 5820) ==5820==at 0x48E3C79: ??? (in /lib/libuci.so) ==5820==by 0x48FDF00: ??? (in /usr/lib/libjet_nvram.so) client stack range: [0x7E84 0x7E841FFF] client SP: 0x7E840C60 valgrind stack range: [0x425C5000 0x426C4FFF] top usage: 5752 of 1048576 Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. *** STEPS TO REPRODUCE 1. run valgrind to check memory leak OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: admin@OpenWrt:/# cat /proc/version Linux version 4.14.195 (jli@ubuntu) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r11208-ce6496d796)) #0 SMP Sun Sep 6 16:19:39 2020 admin@OpenWrt:/# (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.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 Noah Davis changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #19 from Noah Davis --- Marked as RESOLVED at the request of the bug reporter. I marked it UPSTREAM because the bug seems to be a graphics driver issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #18 from Noah Davis --- > It's my Nvidia Optimus setting. When I force `spectacle` to run on my Nvidia > card, it's all good - see the attached blurry picture. So you have to use Nvidia for Spectacle to work right? Ouch. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469030] New: running (K)UBUNTU 23.04 but repository settings say "Debian"
https://bugs.kde.org/show_bug.cgi?id=469030 Bug ID: 469030 Summary: running (K)UBUNTU 23.04 but repository settings say "Debian" Classification: Applications Product: Discover Version: 5.27.4 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: dutchgig...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 158473 --> https://bugs.kde.org/attachment.cgi?id=158473&action=edit screenshot Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: X11 Processors: 2 × Intel® Core™2 CPU 6700 @ 2.66GHz Memory: 5.7 GiB of RAM Graphics Processor: NVD9 - I'm running (K)UBUNTU 23.04 but repository settings say "Debian" ... not sure why -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened
https://bugs.kde.org/show_bug.cgi?id=468630 flampin...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from flampin...@gmail.com --- (In reply to Albert Astals Cid from comment #6) > Yes that was the problem and is getting fixed soon-ish Glad to hear it. Apparently "okular-23.04.0-1367-windows-cl-msvc2019-x86_64" already contains a fix and everything works as it should. Thanks! Problem solved. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #17 from pablo --- If you're okay with it, I'd like to close this defect as RESOLVED. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #16 from pablo --- Created attachment 158472 --> https://bugs.kde.org/attachment.cgi?id=158472&action=edit Mucho better! Hi Noah, Thank you so much for your help! I've figured it out. It's my Nvidia Optimus setting. When I force `spectacle` to run on my Nvidia card, it's all good - see the attached blurry picture. Here's a shell script that I cobbled together to run applications on my dGPU: ::: run_on_nvidia ::: #!/bin/bash # # Run GPU intensive applications via our Nvidia card # export __NV_PRIME_RENDER_OFFLOAD=1 export __VK_LAYER_NV_optimus="NVIDIA_only" export __NV_PRIME_RENDER_OFFLOAD_PROVIDER="NVIDIA-G0" export __GLX_VENDOR_LIBRARY_NAME="nvidia" exec "$@" # Never reached exit 0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468936] Home Page and Reports display completely black - Cannot Read
https://bugs.kde.org/show_bug.cgi?id=468936 Jim Ladino changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Jim Ladino --- (In reply to Jack from comment #3) > That seems truncated - I usually see a lot longer output. Is a data file > open? > Also - what distribution are you using, and do the Views other than Home and > Reports look OK or not? Hi Jack. I'm not sure why my last response got lost or something. Thanks for looking at my output file. I am using linux on a distribution called PCLinuxOS - Kernel (6.1.20-pclos1) 2023. The output file I sent in was from opening KmyMoney from the console. It opens right into my datafile. Is there a log file I can send you for further information? All other screens appear to be working correctly. It's just the Home Screen and the Reports that are having this problem. Please let me know what further information I can provide. Thank you. Jim Ladino -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #16 from Nate Graham --- Armando, please don't mark bug reports as resolved when they are being actively worked on by KDE developers but haven't actually been fixed yet. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468957] Crashing when attempting to create countdown timer, now Kden doesn't open
https://bugs.kde.org/show_bug.cgi?id=468957 --- Comment #7 from superdude...@yahoo.com --- Ok, sorry, no that did not work. It still crashes on my end if I start with just importing timer or just creating a timer with the mlt. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468916] Plasma Panel Visually Freezes
https://bugs.kde.org/show_bug.cgi?id=468916 --- Comment #5 from m...@gabby.li --- Hope this gives you something to go on...: ``` Thread 23 (Thread 0x7fa19affd6c0 (LWP 11129) "Thread (pooled)"): #0 0x7fa4048ac625 in () at /lib64/libc.so.6 #1 0x7fa4048af159 in pthread_cond_timedwait () at /lib64/libc.so.6 #2 0x7fa404ad14ac in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fa404aced1b in () at /usr/lib64/libQt5Core.so.5 #4 0x7fa404acbba7 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4048afab3 in () at /lib64/libc.so.6 #6 0x7fa404931d2c in () at /lib64/libc.so.6 Thread 22 (Thread 0x7fa213fff6c0 (LWP 11128) "Thread (pooled)"): #0 0x7fa4048ac625 in () at /lib64/libc.so.6 #1 0x7fa4048af159 in pthread_cond_timedwait () at /lib64/libc.so.6 #2 0x7fa404ad14ac in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fa404aced1b in () at /usr/lib64/libQt5Core.so.5 #4 0x7fa404acbba7 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4048afab3 in () at /lib64/libc.so.6 #6 0x7fa404931d2c in () at /lib64/libc.so.6 Thread 21 (Thread 0x7fa14bfff6c0 (LWP 11127) "Thread (pooled)"): #0 0x7fa4048ac625 in () at /lib64/libc.so.6 #1 0x7fa4048af159 in pthread_cond_timedwait () at /lib64/libc.so.6 #2 0x7fa404ad14ac in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fa404aced1b in () at /usr/lib64/libQt5Core.so.5 #4 0x7fa404acbba7 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4048afab3 in () at /lib64/libc.so.6 #6 0x7fa404931d2c in () at /lib64/libc.so.6 Thread 20 (Thread 0x7fa14ae6b6c0 (LWP 10088) "KIO::WorkerThre"): #0 0x7fa40492437d in ppoll () at /lib64/libc.so.6 #1 0x7fa404cd23b9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa403df92f6 in () at /usr/lib64/libQt5Network.so.5 #3 0x7fa403df6f02 in () at /usr/lib64/libQt5Network.so.5 #4 0x7fa403de81c4 in QAbstractSocket::waitForReadyRead(int) () at /usr/lib64/libQt5Network.so.5 #5 0x7fa4043c4efa in () at /usr/lib64/libKF5KIOCore.so.5 #6 0x7fa4044107db in KIO::SlaveBase::dispatchLoop() () at /usr/lib64/libKF5KIOCore.so.5 #7 0x7fa4044ae2ae in () at /usr/lib64/libKF5KIOCore.so.5 #8 0x7fa404acbba7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fa4048afab3 in () at /lib64/libc.so.6 #10 0x7fa404931d2c in () at /lib64/libc.so.6 Thread 19 (Thread 0x7fa3b701d6c0 (LWP 10079) "KCupsConnection"): #0 0x7fa40492426f in poll () at /lib64/libc.so.6 #1 0x7fa40384ffde in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa4038500fc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa404cd6096 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa404c8281b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa404aca88a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa3b519fa57 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7fa404acbba7 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa4048afab3 in () at /lib64/libc.so.6 #9 0x7fa404931d2c in () at /lib64/libc.so.6 Thread 18 (Thread 0x7fa3b7fff6c0 (LWP 10071) "KIO::WorkerThre"): #0 0x7fa40492437d in ppoll () at /lib64/libc.so.6 #1 0x7fa404cd23b9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa403df92f6 in () at /usr/lib64/libQt5Network.so.5 #3 0x7fa403df6f02 in () at /usr/lib64/libQt5Network.so.5 #4 0x7fa403de81c4 in QAbstractSocket::waitForReadyRead(int) () at /usr/lib64/libQt5Network.so.5 #5 0x7fa4043c4efa in () at /usr/lib64/libKF5KIOCore.so.5 #6 0x7fa4044107db in KIO::SlaveBase::dispatchLoop() () at /usr/lib64/libKF5KIOCore.so.5 #7 0x7fa4044ae2ae in () at /usr/lib64/libKF5KIOCore.so.5 #8 0x7fa404acbba7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fa4048afab3 in () at /lib64/libc.so.6 #10 0x7fa404931d2c in () at /lib64/libc.so.6 Thread 17 (Thread 0x7fa3737fe6c0 (LWP 9954) "KIO::WorkerThre"): #0 0x7fa40492437d in ppoll () at /lib64/libc.so.6 #1 0x7fa404cd23b9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa403df92f6 in () at /usr/lib64/libQt5Network.so.5 #3 0x7fa403df6f02 in () at /usr/lib64/libQt5Network.so.5 #4 0x7fa403de81c4 in QAbstractSocket::waitForReadyRead(int) () at /usr/lib64/libQt5Network.so.5 #5 0x7fa4043c4efa in () at /usr/lib64/libKF5KIOCore.so.5 #6 0x7fa4044107db in KIO::SlaveBase::dispatchLoop() () at /usr/lib64/libKF5KIOCore.so.5 #7 0x7fa4044ae2ae in () at /usr/lib64/libKF5KIOCore.so.5 #8 0x7fa404acbba7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fa4048afab3 in () at /lib64/libc.so.6 #10 0x7fa404931d2c in () at /lib64/libc.so.6 Thread 16 (Thread 0x7fa3af7fe6c0 (LWP 9940
[kwin] [Bug 432123] Libreoffice opens with generic LO icon on panel in wayland, not on X11
https://bugs.kde.org/show_bug.cgi?id=432123 Filipe Mosca changed: What|Removed |Added CC||fil...@moxk.net --- Comment #6 from Filipe Mosca --- (In reply to SoilpH96 from comment #5) > LibreOffice can correctly set its icon if loaded with the gtk3 backend (run > SAL_USE_VCLPLUGIN=gtk3 libreoffice --writer to test). Different LibreOffice > applications also will show in separate icons on the taskbar. So, it is not > a bug affecting LibreOffice as a whole but only its KF5 backend. According > to what I found on the LO bugzilla > (https://bugs.documentfoundation.org/show_bug.cgi?id=125934) this is due to > a missing implementation in Qt5 > (https://bugreports.qt.io/browse/QTBUG-77182) of the Wayland specification, > that has since been properly implemented in GTK. So this seems to be neither > a Plasma nor a LibreOffice bug, rather a Qt bug. It *might* be possible to > work around it with some hacks in Plasma, but it's probably better to try > getting it fixed upstream. I'm having the same issue on a fresh install of fedora 38 with kde plasma 5.27.4. The code you posted workarounded the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 468708] Crash if kdiff3 attempts to auto-exit after auto-applying all non-conflicting merges
https://bugs.kde.org/show_bug.cgi?id=468708 pawel.vese...@gmail.com changed: What|Removed |Added Summary|Crash upon startup |Crash if kdiff3 attempts to ||auto-exit after ||auto-applying all ||non-conflicting merges -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares, "Details" tab in File Properties missing
https://bugs.kde.org/show_bug.cgi?id=452924 deadseasho...@gmail.com changed: What|Removed |Added CC||deadseasho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461050] Bogus scam warning with trailing space
https://bugs.kde.org/show_bug.cgi?id=461050 --- Comment #3 from Volker Kuhlmann --- Created attachment 158471 --> https://bugs.kde.org/attachment.cgi?id=158471&action=edit Email with bogus scam warning Show this email, in kmail - default HTML off. kmail shows "This message may be a scam. (Details...)" and offers to move it to wastebin. Details: "This email contains a link which reads as 'https://status.voyager.nz/ ' in the text, but actually points to 'https://status.voyager.nz/'. This is often the case in scam emails to mislead the recipient" A trailing space in the path part of the link text is not a scam. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 455511] "Failed to start Powerdevil" slowing down log-in in KDE Plasma 5.25.0; error spams "Charge thresholds not supported"
https://bugs.kde.org/show_bug.cgi?id=455511 medin changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #4 from medin --- The same problem happens on my acer laptop with or without battery. Operating System: Manjaro Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.12-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461050] Bogus scam warning with trailing space
https://bugs.kde.org/show_bug.cgi?id=461050 Volker Kuhlmann changed: What|Removed |Added CC||bug...@top.geek.nz --- Comment #2 from Volker Kuhlmann --- You mean an actual email where someone has put a link into the body where the link text in the HTML is the same as the link except with an added space at the end? It wouldn't take more than 5 seconds for anyone to make such an email. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468937] SMS not working
https://bugs.kde.org/show_bug.cgi?id=468937 Simon Redman changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #4 from Simon Redman --- (In reply to Justin from comment #3) > I just tested again - and it worked. huh. > Is there a word limit? > Thanks. Thanks for confirming. There is not an intentional word limit but a massive network call is more likely to get lost or messed up, and possibly a massive message might fail to send. If you can reproduce that, please send a bug report with the details of how long is too long and your phone manufacturer. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461527] Save legible headers for Fcc
https://bugs.kde.org/show_bug.cgi?id=461527 --- Comment #3 from Volker Kuhlmann --- I sent an email but was unsure where kmail saved it. Because of another bug (not removing sent mails from outbox) I thought I could look up where kmail stored the sent copy, but unfortunately it only said X-KMail-Fcc: 380 thus telling me nothing. An actual folder name (without path is better) would have been useful. Instead I need to concoct with find and grep. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #15 from Noah Davis --- Created attachment 158470 --> https://bugs.kde.org/attachment.cgi?id=158470&action=edit Apply effects to inactive windows Do you have "Apply effects to inactive windows" enabled in your color scheme? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #14 from Noah Davis --- (In reply to pablo from comment #12) > Thank you for your test results. > > The biggest difference I see is that in your example, I can see the > spectacle controls. In my case, they're white-ish which makes them > extremely difficult to discern. > > Is it possibly a GPU issue? This rig is an Optimus Nvidia laptop. I have > it set in /Offset/ mode. The primary GPU is the iGPU, Intel. > > What OS are you using? Perhaps I can stand up a VM to run a quick test. > > I'm open to any ideas to test things out. Operating System: openSUSE Tumbleweed 20230422 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Eluktronics Product Name: THINN-15 (In reply to pablo from comment #13) > Would you mind running a test that includes the /KDE System Settings/ in > /Icon View/? Specifically, do the icons blanch after selecting the /Capture > Mode/ > /Rectangular Region/? > > Thx a bundle! They do not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 Armando S. Araujo changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469029] New: Cant Drag and Drop ANY Clips to Timeline
https://bugs.kde.org/show_bug.cgi?id=469029 Bug ID: 469029 Summary: Cant Drag and Drop ANY Clips to Timeline Classification: Applications Product: kdenlive Version: 23.04.0 Platform: Snap OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: diz_gar...@yahoo.com Target Milestone: --- Created attachment 158469 --> https://bugs.kde.org/attachment.cgi?id=158469&action=edit This is it in a nutshell .. from another user having the same exact issue SUMMARY I am unable to drag and drop ANY clip from the project bin into the Timeline. the required video and audio tracks are present, none of the tracks are locked, and prior to My current 23.04 update on both kdenlive and Ubuntu a few days ago, everything was working fine. i also tried installing the ubuntu kdenlive 22.12.03 version AND the 23.04 App-images and the Problem still persists. and i have no idea what the issue is. *** 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. happens on all projects both old and Brand new projects 2. 3. OBSERVED RESULT cant drag and drop any clips to the timeline EXPECTED RESULT cannot edit any projects because i can't get access to any of the clips from the project bin SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 23.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION the only work around to being able to work on my projects is to use the V shortcut on the clips in the timeline, but working this way will make the whole process longer due to the clip being inserted and automatically cutting all the other clips in the project to make space for it. this minor issue can make things a headache when dealing with a large project with multiple clips because things will be moved around unintentionally unless I find an empty space in the whole project JUST to add the clip in then have to manually move the clip to the position i want it in. *** attached is a screencast from another user with the same exact issue i am reporting on -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 --- Comment #15 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kirigami/-/merge_requests/1044 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #22 from Neal Gompa --- Can we look at having the kf6-wayland dependency be made mandatory for kf6-plasma to avoid stuff like this? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 468708] Crash upon startup
https://bugs.kde.org/show_bug.cgi?id=468708 --- Comment #6 from pawel.vese...@gmail.com --- I can reproduce this without `git mergetool`, as long as I run the command as specified in the description. So it's '--auto' to blame. Removing that option avoids the crash. Sadly, fixing this for 'git' is not trivial: https://stackoverflow.com/q/15321472/622266 (i.e., I'd rather not set up an alternative differ for just this). I've tried "ignoring" "--auto" option (as suggested in https://stackoverflow.com/a/61415346/622266), but I couldn't. I tried adding "-auto", "--auto", but all this got me was a message `QCommandLineParser: already having an option named "auto"`, and kdiff3 still tried exiting right away (and crashing). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447119] Summary: Dolphin/Baloo search with symlinks
https://bugs.kde.org/show_bug.cgi?id=447119 --- Comment #17 from Stefan Brüns --- (In reply to tagwerk19 from comment #16) > (In reply to Stefan Brüns from comment #12) > > Dolphin returns the correct result only when the path of the current > > directory is its canonical name. > Meaning that Dolphin should follow any symlinks before doing a search and > (silently) query baloo with the canonical path? Although I'm not sure > whether Dolphin should then show the results relative to the symlink or with > the canonical path. The "Path" column should display the canonical path. After all, that's where the file is actually located. (And in case the symlink started on a different filesystem, also the place where the space is consumed). This is consistent with how directory sizes are calculated, symlinks are not followed, otherwise you may count files several times. > It makes sense ... > > ... although it implies that the index *only* ever contains canonical > paths. > > Would also need to be careful that baloosearch and filenamesearch do the > same thing. > > Edge cases? > > $ balooshow -x path-including-symlink balooshow already handles this correctly, the canonical path is shown in square brackets (if it differs from the specified path): > balooshow -x ~/Sources/testdata/symlink_parent/testdata/hello.txt > 12ccd4a002d 45 19713354 > /home/stefan/Sources/testdata/symlink_parent/testdata/hello.txt > [/home/stefan/Sources/testdata/hello.txt] > $ balooctl index path-including-symlink > $ balooctl clear path-including-symlink > > and then evil baloofilerc includes such as > > folders[$e]=$HOME/Desktop/Documents > > where you've got a symlink on your Desktop to your Documents folder? > > I think the "balooctl index" (and "balooctl clear") does things properly but > I suspect that the evil include does not... In case it is not, this should be trivial to fix. Also, if you break it, you may keep both parts. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #13 from pablo --- Would you mind running a test that includes the /KDE System Settings/ in /Icon View/? Specifically, do the icons blanch after selecting the /Capture Mode/ > /Rectangular Region/? Thx a bundle! -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 373753] import menu action does not do anything
https://bugs.kde.org/show_bug.cgi?id=373753 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/kwalletmanager/commit |ities/kwalletmanager/commit |/5f2e0cfb2874c139f17f975e30 |/e3d4575a71e8f961a1f279a1b4 |c781318109655b |bf9c35abb3b4e8 --- Comment #8 from Albert Astals Cid --- Git commit e3d4575a71e8f961a1f279a1b4bf9c35abb3b4e8 by Albert Astals Cid, on behalf of Francisco Riquelme. Committed on 26/04/2023 at 22:29. Pushed by aacid into branch 'release/23.04'. Fix import menu actions status Disable import/export menu items when starting kwalletmanager and wallet is closed (cherry picked from commit 5f2e0cfb2874c139f17f975e30c781318109655b) M +3-0src/manager/kwalleteditor.cpp https://invent.kde.org/utilities/kwalletmanager/commit/e3d4575a71e8f961a1f279a1b4bf9c35abb3b4e8 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 373753] import menu action does not do anything
https://bugs.kde.org/show_bug.cgi?id=373753 frrc...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/kwalletmanager/commit ||/5f2e0cfb2874c139f17f975e30 ||c781318109655b Status|ASSIGNED|RESOLVED --- Comment #7 from frrc...@gmail.com --- Git commit 5f2e0cfb2874c139f17f975e30c781318109655b by Francisco Riquelme. Committed on 26/04/2023 at 21:38. Pushed by aacid into branch 'master'. Fix import menu actions status Disable import/export menu items when starting kwalletmanager and wallet is closed M +3-0src/manager/kwalleteditor.cpp https://invent.kde.org/utilities/kwalletmanager/commit/5f2e0cfb2874c139f17f975e30c781318109655b -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #12 from pablo --- Thank you for your test results. The biggest difference I see is that in your example, I can see the spectacle controls. In my case, they're white-ish which makes them extremely difficult to discern. Is it possibly a GPU issue? This rig is an Optimus Nvidia laptop. I have it set in /Offset/ mode. The primary GPU is the iGPU, Intel. What OS are you using? Perhaps I can stand up a VM to run a quick test. I'm open to any ideas to test things out. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468987] Elisa scan not picking up files from NTFS partition
https://bugs.kde.org/show_bug.cgi?id=468987 --- Comment #3 from Kris Nelson --- Created attachment 158468 --> https://bugs.kde.org/attachment.cgi?id=158468&action=edit Successful scan after changing to "scan the filesystem directly" -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468987] Elisa scan not picking up files from NTFS partition
https://bugs.kde.org/show_bug.cgi?id=468987 --- Comment #2 from Kris Nelson --- (In reply to Nate Graham from comment #1) > If you switch to the "Scan the filesystem directly" indexer and restart > Elisa, does it find your music files? Just tested that, and yes it did find everything expected from the Music folder (attached screenshot confirmation - "elisa - scan the filesystem directly result.png"). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #11 from Noah Davis --- Created attachment 158467 --> https://bugs.kde.org/attachment.cgi?id=158467&action=edit rectangle selection for me with light background -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #10 from Noah Davis --- Created attachment 158466 --> https://bugs.kde.org/attachment.cgi?id=158466&action=edit rectangle selection for me Does this image also look washed out to you? Making sure it's not a screen issue. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 468708] Crash upon startup
https://bugs.kde.org/show_bug.cgi?id=468708 Loïc Yhuel changed: What|Removed |Added CC||loic.yh...@gmail.com --- Comment #5 from Loïc Yhuel --- I have a similar crash, when kdiff3 is launched by "git mergetool" and it merges the files with no conflicts, so it exits immediately. In this case, KDiff3App::completeInit calls ::exit(0), as in the reporter backtrace. I think the exit handlers destroy the QtFreetypeData, which make one of the worker threads crash. Maybe the main thread needs a way to properly join the threads, or to exit in a more graceful way (something like QMetaObject::invokeMethod(qApp, "quit", Qt::QueuedConnection). The crash doesn't seem to happen when reverting 7c4e929b22 "Show gui before starting comparison", so I suppose the worker threads are created when showing the GUI (even if we didn't QApplication::exec yet). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in multi-xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #18 from Allistar --- If it identifies monitors by something unique (e.g. the GPU or screen number they're on appended with the QScreen name) then it's likely that when plasmashell starts up it will start on both xscreens which would be a bonus. I admit though that running a multiple xscreen environment will be rare. I think the display control panel app should ask us which xscreen to run on if it detects there's more than one xscreen running. I have no idea what this would mean in a Wayland environment or whether that has a concept of "xscreen". -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #9 from pablo --- Created attachment 158465 --> https://bugs.kde.org/attachment.cgi?id=158465&action=edit Vanilla Linux user test Hi, Attached are the results of using a new, vanilla Linux user. The /with-effects/ sub-directory is the true, vanilla Linux user. The /with-no-effects/ sub-directory contains the test results with all the effects disabled. I am having to use my phone's camera to take the pictures. I try to keep it the same distance. ::: Contents ::: $ tar -vcf vanilla_Linux_user.tar vanilla_Linux_user vanilla_Linux_user/ vanilla_Linux_user/with-effects/ vanilla_Linux_user/with-effects/01_b4.png vanilla_Linux_user/with-effects/02_b4_selection.png vanilla_Linux_user/with-effects/03_selection.png vanilla_Linux_user/with-no-effects/ vanilla_Linux_user/with-no-effects/03_selection.png vanilla_Linux_user/with-no-effects/02_b4_selection.png vanilla_Linux_user/with-no-effects/01_b4.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422786] Global Menu requires refocus to display properly for GTK apps
https://bugs.kde.org/show_bug.cgi?id=422786 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #57 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2870 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 373753] import menu action does not do anything
https://bugs.kde.org/show_bug.cgi?id=373753 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kwalletmanager/-/merge_requests/24 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 --- Comment #14 from ratijas --- Git commit 28e6cab939007c54be4ea2b33b4ed7f4aa57bfa8 by ivan tkachenko. Committed on 26/04/2023 at 20:50. Pushed by ratijas into branch 'Plasma/5.27'. applets/digital-clock: Fix broken binding in the list of calendar plugins First rule of the fighting club: never bind to a list. You never know what the heck you're up against. On the other hand, assigning FormData.buddyFor in a procedural way in the Repeater's hook is robust, and there's nothing that could go wrong. See also: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1490 (cherry picked from commit a72ca3acdfc3edb269cdadb979bd2c16bde846b6) M +12 -1applets/digital-clock/package/contents/ui/configCalendar.qml https://invent.kde.org/plasma/plasma-workspace/commit/28e6cab939007c54be4ea2b33b4ed7f4aa57bfa8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468627] Desktop and task manager off after screen waking up
https://bugs.kde.org/show_bug.cgi?id=468627 joseteluisete changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #10 from joseteluisete --- Hi! I'm again testing the first computer. Everything is solved. I don't know how ... maybe some update I've installed. Thanks and greetings! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468873] plasmashell always crashes on start with X11OutputOrderWatcher::refresh() when xrandr isn't available
https://bugs.kde.org/show_bug.cgi?id=468873 --- Comment #6 from Maciej Poleski --- I don't think I could install xorg-server in such a way that RandR is absent. But RandR conflicts with Xinerama, AFAIU, by definition. $ xrandr RandR extension missing My Xorg.0.log has the following entries: [ 315.220] (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the [ 315.220] (WW) NVIDIA: X server. I can disable (not-enable) Xinerama. Then RandR is present. But KDE doesn't seem to honor RandR setup: https://askubuntu.com/questions/894101/how-to-make-kde-use-a-screen-from-xrandr-1-5 I tried it a few months ago. While i3 honored the setting (https://michael.stapelberg.ch/posts/2017-12-11-dell-up3218k/#linux-compatibility--configuration), KDE ignored it. Xinerama seemed to be the only way to go. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464258] plasmashell crashed with the error The Wayland connection experienced a fatal error: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=464258 cach...@yahoo.com changed: What|Removed |Added CC||cach...@yahoo.com --- Comment #10 from cach...@yahoo.com --- I see similar problem in Fedora 38 installed from scratch: [24408.431884] plasmashell[15915]: The Wayland connection experienced a fatal error: Bad file descriptor [24408.472046] systemd[1068]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE [24408.472221] systemd[1068]: plasma-plasmashell.service: Failed with result 'exit-code'. [24409.417436] plasmashell[43463]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [24409.420275] plasmashell[43463]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [24409.712477] plasmashell[43463]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [24409.712645] plasmashell[43463]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [24409.712760] plasmashell[43463]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [24409.860095] plasmashell[43463]: Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion [24409.997285] plasmashell[43463]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [24410.223437] plasmashell[43463]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml" [24410.227251] plasmashell[43463]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml" [24410.497779] plasmashell[43463]: QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 [24410.529348] plasmashell[43463]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [24410.539157] plasmashell[43463]: QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 [24410.680847] plasmashell[43463]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469009] Music player widget acts as music would has been stopped after using "play next"
https://bugs.kde.org/show_bug.cgi?id=469009 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #5 from Patrick Silva --- On my Arch Linux the Media Player applet hides itself in the system tray and it looks like nothing is playing after the provided steps. Possibly duplicate of bug 398967 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469028] New: Kate no longer work as sudoedit editor and closes file immediately
https://bugs.kde.org/show_bug.cgi?id=469028 Bug ID: 469028 Summary: Kate no longer work as sudoedit editor and closes file immediately Classification: Applications Product: kate Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY Since new applications, kate closes the file being edited as sudoedit before being able to edit it STEPS TO REPRODUCE 1. Launch sudoedit with EDITOR=kate sudoedit /etc/somesystemfile OBSERVED RESULT Empty temp file is shown on editor instead of the file being edited and sudoedit tells file has no changes EXPECTED RESULT File being edited show on kate SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-cachyos-bore (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 --- Comment #28 from Roland --- Hi Maik, I have installed digiKam from the repo KDE:Extra. PackMan ffmpeg 4.4.4-1599.1.pm.5 is available. I have just tested the AppImage version, it is working 👍 Perhaps, it's now a task for the package maintainer of the repo. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #8 from pablo --- I'm going to try to rule out my own environment by creating a vanilla Linux user. I'll incrementally add to it: 1) Vanilla 2) Disable all effects 3) Switch to dark theme I should have thought of that before submitting the bug. Sorry about that ... be right back. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432845] Discover doesn't weigh higher keywords appearing in application titles
https://bugs.kde.org/show_bug.cgi?id=432845 Nate Graham changed: What|Removed |Added Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #7 from pablo --- Created attachment 158464 --> https://bugs.kde.org/attachment.cgi?id=158464&action=edit Region is visible with all desktop effects disabled -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #6 from pablo --- Created attachment 158463 --> https://bugs.kde.org/attachment.cgi?id=158463&action=edit After selecting /Rectangular Region/ option Hi Noah, Good call. I hadn't thought of that being an issue. I disabled all effects and for good measure, re-logged in. The bleaching is still there but now it's .. different. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469027] Maximising some apps leaves a thin gap on the right side of my main monitor
https://bugs.kde.org/show_bug.cgi?id=469027 --- Comment #2 from ivb...@proton.me --- *** Bug 469025 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469025] When maximising GTK apps, there is a small gap on the right side of the main monitor
https://bugs.kde.org/show_bug.cgi?id=469025 ivb...@proton.me changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from ivb...@proton.me --- *** This bug has been marked as a duplicate of bug 469027 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469027] Maximising some apps leaves a thin gap on the right side of my main monitor
https://bugs.kde.org/show_bug.cgi?id=469027 --- Comment #1 from ivb...@proton.me --- Created attachment 158462 --> https://bugs.kde.org/attachment.cgi?id=158462&action=edit An example from firefox -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469027] New: Maximising some apps leaves a thin gap on the right side of my main monitor
https://bugs.kde.org/show_bug.cgi?id=469027 Bug ID: 469027 Summary: Maximising some apps leaves a thin gap on the right side of my main monitor Classification: Plasma Product: kwin Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ivb...@proton.me Target Milestone: --- SUMMARY Maximising some apps (Discord, Firefox, Bitwarden) leaves a very thin gap on the right side of the maximised window that shows the desktop underneath. Other apps that are unnafected would be things like Konsole, Discover, Dolphin, Qbittorrent. Firefox, Discord, Bitwarden, and Qbittorrent are installed via Flatpak. All the other apps would be installed via the Arch Linux repos. Please note that this is not an exhuastive list, it is only the apps that I have tested thus far. STEPS TO REPRODUCE 1. Install Firefox (I have the Flatpak version) 2. Maximise the app 3. Observe that there is a very thin gap on the right showing the desktop through it. OBSERVED RESULT EXPECTED RESULT I would expect the app windows to maximise properly with no gaps. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux v6.2.12, KDE Plasma v5.27.4 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I have 3 connected monitors. 2 1080p secondary monitors, and 1 1440p primary monitor. The issue is only on the primary 1440p monitor, and not on the 1080p monitors. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469026] Searching for "iso" doesn't find "Popsicle"
https://bugs.kde.org/show_bug.cgi?id=469026 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469026] New: Searching for "iso" doesn't find "Popsicle"
https://bugs.kde.org/show_bug.cgi?id=469026 Bug ID: 469026 Summary: Searching for "iso" doesn't find "Popsicle" Classification: Applications Product: Discover Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Run `appstreamcli search iso | grep -i popsicle` in a terminal window to make sure Popsicle is available and AppStream sees it 2. Launch Discover with only its PackageKit and Flatpak backends by running `plasma-discover --backends flatpak,packagekit` in a terminal window 3. Search for "iso" OBSERVED RESULT Popsicle isn't in the search results EXPECTED RESULT Popsicle is in the search results SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 AppStream version: 0.16.1 Qt Version: 5.15.9 Kernel Version: 6.2.12-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469025] When maximising GTK apps, there is a small gap on the right side of the main monitor
https://bugs.kde.org/show_bug.cgi?id=469025 --- Comment #1 from ivb...@proton.me --- I accidentally posted this before it was ready. Hitting enter apparently posts the issue. I cannot find the delete button, nor a way to edit the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469025] New: When maximising GTK apps, there is a small gap on the right side of the main monitor
https://bugs.kde.org/show_bug.cgi?id=469025 Bug ID: 469025 Summary: When maximising GTK apps, there is a small gap on the right side of the main monitor Classification: Plasma Product: kwin Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ivb...@proton.me Target Milestone: --- Created attachment 158461 --> https://bugs.kde.org/attachment.cgi?id=158461&action=edit qbittorrent (QT, no issue) SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 --- Comment #13 from ratijas --- Git commit a72ca3acdfc3edb269cdadb979bd2c16bde846b6 by ivan tkachenko. Committed on 26/04/2023 at 19:53. Pushed by ratijas into branch 'master'. applets/digital-clock: Fix broken binding in the list of calendar plugins First rule of the fighting club: never bind to a list. You never know what the heck you're up against. On the other hand, assigning FormData.buddyFor in a procedural way in the Repeater's hook is robust, and there's nothing that could go wrong. See also: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1490 M +13 -1applets/digital-clock/package/contents/ui/configCalendar.qml https://invent.kde.org/plasma/plasma-workspace/commit/a72ca3acdfc3edb269cdadb979bd2c16bde846b6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450435] Panels missing after unlocking screen after sleep mode
https://bugs.kde.org/show_bug.cgi?id=450435 Nate Graham changed: What|Removed |Added Resolution|DOWNSTREAM |WAITINGFORINFO --- Comment #24 from Nate Graham --- (In reply to Alex from comment #23) > What do you want to see exactly? I don't get it. Because... > In this moment for example (I just unlocked my PC), both panels are missing: > if I minimize the windows I just see two completely black screens: no usual > background image either. That's what I was hoping the screenshots showed (or didn't show). I was asking because if the wallpaper is missing too, then the issue isn't actually that your panels went missing; the issue is that the entire desktop containments that the panels live on went missing! So in Plasma 5.27 we implemented a new system for mapping Plasma desktops and panels to screens that is fundamentally more correct by design, and as a result much more robust; ths idea was to prevent this from happening anymore. We also added code to migrate old settings to this new system. Unfortunately, due to the non-determinism baked into the old system, the migration code works better the simpler your arrangement of screens, desktops, and panels was. For complex arrangements, we've seen a few reports that sometimes panels or desktops are swapped or missing, as a result of the old settings being in an inconsistent state at the moment of migration. We do have a UI to recover them in the form of the "Manage Desktops and Panels" window, which should let you manually restore your old setup. You can access it like so: Right-click on desktop > click on "Enter Edit Mode" > a toolbar pops down from the top of the screen > click on "Manage Desktops and Panels" Can you use this to recover your missing desktops and panels? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468917] Settings for Icon-Distance in the Systemtray in tablet-mode not changeable
https://bugs.kde.org/show_bug.cgi?id=468917 --- Comment #5 from Nate Graham --- Making the spacing configurable while in Touch Mode would defeat the purpose of Touch Mode; its reason for existing is to force bigger spacing and sizes to increase touch targets. Touch Mode without larger UI controls and bigger spacing doesn't make conceptual sense. If you're not using the UI with touch, then turning off Touch Mode is the configuration that exists and will allow you to achieve what you're looking for. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #5 from Noah Davis --- (In reply to Noah Davis from comment #4) > Do you have any KWin effects enabled that might also affect the color of > inactive windows? KWin effects/Desktop Effects (same thing, the latter is the name used in system settings) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467819] Plasma crashed out of the blue
https://bugs.kde.org/show_bug.cgi?id=467819 --- Comment #4 from aron...@gmail.com --- Created attachment 158460 --> https://bugs.kde.org/attachment.cgi?id=158460&action=edit New crash information added by DrKonqi plasmashell (5.27.4) using Qt 5.15.9 am I just sending the same thing for no reason again? -- Backtrace (Reduced): #6 0x7f7258fce380 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f7258fce3fa in QSGAreaAllocator::deallocate(QRect const&) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #12 0x7f725907d7c2 in QQuickWindowPrivate::runAndClearJobs(QList*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #16 0x7f72570ce733 in operator() (__closure=, __closure=) at thread/qthread_unix.cpp:350 #18 QThreadPrivate::start(void*) (arg=0x55a48b158bd0) at thread/qthread_unix.cpp:310 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #4 from Noah Davis --- Do you have any KWin effects enabled that might also affect the color of inactive windows? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469009] Music player widget acts as music would has been stopped after using "play next"
https://bugs.kde.org/show_bug.cgi?id=469009 --- Comment #4 from serkon...@pm.me --- Created attachment 158459 --> https://bugs.kde.org/attachment.cgi?id=158459&action=edit Bug_Video Hmm, I have added a short screencast to show my problem. Is there any more debugging or information I could include? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469011] Plasma-discover error during firmware update
https://bugs.kde.org/show_bug.cgi?id=469011 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.27.5 --- Comment #4 from Nate Graham --- Talked to the author of that commit and he confirms that it is. So this should be fixed in Plasma 5.27.5. Ultimately this is actually a bug in the LVFS which made the questionable decision to block all requests fro Mozilla user agents, which Discover happens to use because it uses QtNetwork which has that user agent by default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468777] Touch rotation broken in macOS
https://bugs.kde.org/show_bug.cgi?id=468777 vanyossi changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com --- Comment #2 from vanyossi --- yeah, I'll make some time to fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469009] Music player widget acts as music would has been stopped after using "play next"
https://bugs.kde.org/show_bug.cgi?id=469009 --- Comment #3 from Nate Graham --- Hmm, still cannot reproduce the issue with VLC even after I pause the music with the spacebar from the widget at least once. -- You are receiving this mail because: You are watching all bug changes.
