[konqueror] [Bug 421245] Add save tabs feature (like in Dolphin)
https://bugs.kde.org/show_bug.cgi?id=421245 --- Comment #6 from avlas --- Hi Stefano, there is one issue with this new feature (that otherwise is working great!), which is when opening a link while Konqueror is closed. The expected behavior would be to load all previous tabs and the new link in an additional tab. The observed behavior is that only the previous tabs are opened, so I need to open the link again to load the new tab. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470121] Can't run callgrind_control with valgrind 3.21.0 because of perl errors
https://bugs.kde.org/show_bug.cgi?id=470121 --- Comment #4 from Paul Floyd --- Perhaps we should add some tests as well. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443168] gwenview ignores settings in initial sort order
https://bugs.kde.org/show_bug.cgi?id=443168 Freddy Vejen changed: What|Removed |Added CC|fred...@yahoo.com | -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 461505] Plasma Integration in Firefox - Failed to connect to the native host
https://bugs.kde.org/show_bug.cgi?id=461505 --- Comment #9 from jmaspons --- Can be solved with > sudo ln -s /etc/apparmor.d/usr.bin.firefox /etc/apparmor.d/disable/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470195] Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything
https://bugs.kde.org/show_bug.cgi?id=470195 Paul Worrall changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #3 from Paul Worrall --- William, my memory usage also looks normal when bug 469445 occurs. Did you try deleting the [ScreenMapping] section in .config/plasma-org.kde.plasma.desktop-appletsrc as described in that bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470445] [Wayland] Side panels with "auto-hide" enabled "freeze", showing a NON-interactive snapshot of it.
https://bugs.kde.org/show_bug.cgi?id=470445 Rafael Linux User changed: What|Removed |Added Summary|[Wayland] Side panels |[Wayland] Side panels with |"freeze", showing a |"auto-hide" enabled |NON-interactive snapshot of |"freeze", showing a |it. |NON-interactive snapshot of ||it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470481] New: Wish: Option to edit multiple comments at once
https://bugs.kde.org/show_bug.cgi?id=470481 Bug ID: 470481 Summary: Wish: Option to edit multiple comments at once Classification: Applications Product: okular Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: mario.schae...@gmail.com Target Milestone: --- SUMMARY It would be great to have an option to edit multiple comments at once, as it is possible in Adobe Acrobat Reader. BACKGROUND Sometimes there is the need to have a different author name for the annotations in a PDF file (e.g. for an anonymous peer review document) . If you plan ahead, Okular already has you covered, as you can easily change the author name in the "Configure Okular" dialog. However, it happens that one does not plan ahead and has already created numerous comments, that then need to be modified. Currently this is only possible to do for each annotation individually, which can result in a lot of work depending on the amount of annotations. Adobe Acrobat Reader has implemented the option to edit multiple comments at once in the desktop application (which is what I ended up using as a workaround). As it is already possible to delete multiple annotations at once, I assume it should not be too difficult to implement this feature. Okular is already the most feature-rich PDF viewer in the Linux realm and this feature would remove another of the very few reasons to use the Adobe counterpart instead. OBSERVED RESULT When selecting and right-clicking multiple comments in the left "Sidebar" under the "Annotations" tab, the only option that appears is to delete multiple comments. EXPECTED RESULT When selecting and right-clicking multiple comments in the left "Sidebar" under the "Annotations" tab, there is an additional option "Properties" (just as when selecting only one comment). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arco Linux with Qtile (probably irrelevant as it is a wish and not a bug) (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.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469184] 23.04 version lost "blur factor" feature
https://bugs.kde.org/show_bug.cgi?id=469184 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468862] Plasma Browser Integration Broken in Firefox on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=468862 jmaspons changed: What|Removed |Added CC||dbruck...@posteo.de --- Comment #6 from jmaspons --- *** Bug 461505 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 461505] Plasma Integration in Firefox - Failed to connect to the native host
https://bugs.kde.org/show_bug.cgi?id=461505 jmaspons changed: What|Removed |Added Resolution|DOWNSTREAM |DUPLICATE --- Comment #8 from jmaspons --- I think this bug is a duplicated of BUG 468862 , a problem with apparmor *** This bug has been marked as a duplicate of bug 468862 *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469184] 23.04 version lost "blur factor" feature
https://bugs.kde.org/show_bug.cgi?id=469184 hexchain changed: What|Removed |Added CC||k...@hexchain.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470445] [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.
https://bugs.kde.org/show_bug.cgi?id=470445 Rafael Linux User changed: What|Removed |Added CC||niccolo.venera...@gmail.com Component|Task Manager and Icons-Only |Panel |Task Manager| --- Comment #2 from Rafael Linux User --- More info: Panels are "frozen" regardless of the graphic add-ons that are added. The problem is with the panel itself: It happens on panels with "auto-hide" enabled. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 319467] 'load external content' does not always work
https://bugs.kde.org/show_bug.cgi?id=319467 --- Comment #16 from Axel Braun --- (In reply to Axel Braun from comment #15) > As of KMail 5.21.3 > - HTML is displayed in preview pane, ext. content loaded > - HTML is NOT displayed with double click on message and display in separate > window Same issue still in version 5.23.1 (23.04.1) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470480] New: Plasmashell crashes after closing a window from the taskbar preview and then closes every Chromium process.
https://bugs.kde.org/show_bug.cgi?id=470480 Bug ID: 470480 Summary: Plasmashell crashes after closing a window from the taskbar preview and then closes every Chromium process. Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: cont...@robotoskunk.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: To reproduce this, just open two windows of Chromium, then, try to close one of them using the taskbar preview. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1556 (plasmashell) UID: 1000 (robotoskunk) GID: 1000 (robotoskunk) Signal: 11 (SEGV) Timestamp: Wed 2023-05-31 01:42:14 CST (43s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (robotoskunk) Boot ID: f5c76f0d6913486c87f62724096117ed Machine ID: c1c8ba11279c4888914bdf9c65399597 Hostname: RobotoSkunk-PC-Linux Storage: /var/lib/systemd/coredump/core.plasmashell.1000.f5c76f0d6913486c87f62724096117ed.1556.168551893400.zst (present) Size on Disk: 24.3M Message: Process 1556 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.6-1.amd64 Module libudev.so.1 from deb systemd-252.6-1.amd64 Stack trace of thread 1556: #0 0x7fc5924a3ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #1 0x7fc592454ef2 __GI_raise (libc.so.6 + 0x3bef2) #2 0x7fc594f9eb46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7fc592454f90 __restore_rt (libc.so.6 + 0x3bf90) #4 0x7fc5924a3ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #5 0x7fc592454ef2 __GI_raise (libc.so.6 + 0x3bef2) #6 0x7fc592454f90 __restore_rt (libc.so.6 + 0x3bf90) #7 0x7fc59251a4f9 syscall (libc.so.6 + 0x1014f9) #8 0x7fc592acdd9b _ZN10QSemaphore7acquireEi (libQt5Core.so.5 + 0xcdd9b) #9 0x7fc592ce8e99 n/a (libQt5Core.so.5 + 0x2e8e99) #10 0x7fc592ce229f _ZN7QObject9destroyedEPS_ (libQt5Core.so.5 + 0x2e229f) #11 0x7fc592ce7254 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7254) #12 0x7fc515b4163c n/a (libKF5NetworkManagerQt.so.6 + 0x9063c) #13 0x7fc515b41759 n/a (libKF5NetworkManagerQt.so.6 + 0x90759) #14 0x7fc592457435 __run_exit_handlers (libc.so.6 + 0x3e435) #15 0x7fc5924575aa __GI_exit (libc.so.6 + 0x3e5aa) #16 0x7fc591c1f67f _XDefaultIOError (libX11.so.6 + 0x4667f) #17 0x7fc591c1f96f _XIOError (libX11.so.6 + 0x4696f) #18 0x7fc591c1dc30 n/a (libX11.so.6 + 0x44c30) #19 0x7fc591c0b25f XNextRequest (libX11.so.6 + 0x3225f) #20 0x7fc587f57eb6 n/a (KF5WindowSystemX11Plugin.so + 0x16eb6) #21 0x7fc587f504ef n/a (KF5WindowSystemX11Plugin.so + 0xf4ef) #22 0x7fc587f58981 n/a (KF5WindowSystemX11Plugin.so + 0x17981) #23 0x7fc5941d4700 n/a (libKF5WindowSystem.so.5 + 0x2b700) #24 0x7fc5941d0090 _ZN11KWindowInfoC1Ey6QFlagsIN3NET8PropertyEES0_INS1_9Property2EE (libKF5WindowSystem.so.5 + 0x27090) #25 0x7fc57eb90766 n/a (libtaskmanager.so.6abi1 + 0x6f766) #26 0x7fc57eb94e68 _ZNK11TaskManager17XWindowTasksModel4dataERK11QModelIndexi (libtaskmanager.so.6abi1 + 0x73e68) #27 0x7fc592c6cd60 _ZNK19QAbstractProxyModel4dataERK11QModelIndexi (libQt5Core.so.5 + 0x26cd60) #28 0x7fc592c6ef5a _ZNK28QConcatenateTablesProxyModel4dataERK11QModelIndexi (libQt5Core.so.5 + 0x26ef5a) #29 0x7fc57eb5d494 _ZNK11TaskManager20TaskFilterProxyModel10acceptsRowEi (libtaskmanager.so.6abi1 + 0x3c494) #30 0x7fc592c86471 n/a (libQt5Core.so.5 + 0x286471) #31 0x7fc592ce8f7c n/a
[valgrind] [Bug 470121] Can't run callgrind_control with valgrind 3.21.0 because of perl errors
https://bugs.kde.org/show_bug.cgi?id=470121 --- Comment #3 from Paul Floyd --- Created attachment 159364 --> https://bugs.kde.org/attachment.cgi?id=159364=edit More complete patch Only tested with callgrind_control -help -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients
https://bugs.kde.org/show_bug.cgi?id=470329 Andrei Amuraritei changed: What|Removed |Added Platform|Other |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469502] Clicking on save should provide feedback about the screenshot being saved
https://bugs.kde.org/show_bug.cgi?id=469502 Axel changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439864] Dolphin resets to "Home" and forgets paths of all tabs that are not available on start [regression]
https://bugs.kde.org/show_bug.cgi?id=439864 --- Comment #19 from ttrovo --- Can somebody please find the commit that cause this issue again? Maybe this commit should be reverted until its author fix the introduced regression in their commit? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464869] Installing updates corrupts Grub 2 ( unbootable system)
https://bugs.kde.org/show_bug.cgi?id=464869 --- Comment #4 from Lassi Väätämöinen --- This is a very systematic issue and easily reproducible on Virtualbox. I had it reproduced also on a openSUSE Linux host, KDE Neon as guest. On that VM I had the 'grub-theme-breeze' package installed, but I did not check it's install status, if /boot/grub/themes/breeze/theme.txt file was installed. I'll be anyways removing 'grub-theme-breeze' in the future. But also, it is quite hard to believe that native installations would be trouble-free regarding this issue. (Or not too many active users for KDE Neon..?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470445] [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.
https://bugs.kde.org/show_bug.cgi?id=470445 --- Comment #3 from Rafael Linux User --- (In reply to Rafael Linux User from comment #2) > More info: Panels are "frozen" regardless of the graphic add-ons that are > added. The problem is with the panel itself: It happens on panels with > "auto-hide" enabled. Not really. After continuing trying I can say "auto-hide" option doesn't does not influence the reproduction of the problem. I have set up several panels with the same widget but one with "auto-hide" enabled and one without it enabled. Both freeze at different times but I can't identify the cause. From that moment of "freezing" when hovering the mouse over the icons nothing happens, nor are the icons updated according to the active windows. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439864] Dolphin resets to "Home" and forgets paths of all tabs that are not available on start [regression]
https://bugs.kde.org/show_bug.cgi?id=439864 Antonio Rojas changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #20 from Antonio Rojas --- All comments starting from comment 13 are about https://bugs.kde.org/show_bug.cgi?id=469656 which is unrelated to this old bug. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 470485] New: Settings lack persistence
https://bugs.kde.org/show_bug.cgi?id=470485 Bug ID: 470485 Summary: Settings lack persistence Classification: Applications Product: PlasmaTube Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: kde.52...@simplelogin.com CC: espi...@gmail.com Target Milestone: --- SUMMARY You can neither manually save settings in the app nor are input values saved automatically in the current version. If you update the values in settings they will be reset next time you open the application. STEPS TO REPRODUCE 1. Navigate to settings. Update the Invidious instance to something other than the default. 2. Close app. 3. Open the app anew. 4. Navigate to settings. OBSERVED RESULT The instance will be the default value. EXPECTED RESULT The invidious instance should have persisted the edited value. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.3.4-arch2-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470394] Scrolling up on task manager task always maximizes window
https://bugs.kde.org/show_bug.cgi?id=470394 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Can't reproduce. Do you by any chance have any window rules or 3rd-party KWin scripts installed? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470488] New: KDE Connect daemon crashes when receiving the attached image from my Android device
https://bugs.kde.org/show_bug.cgi?id=470488
Bug ID: 470488
Summary: KDE Connect daemon crashes when receiving the attached
image from my Android device
Classification: Applications
Product: kdeconnect
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: zak.wil...@gmail.com
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
Created attachment 159368
--> https://bugs.kde.org/attachment.cgi?id=159368=edit
Photograph taken with my Android device
SUMMARY
***
Sending this image from my Android device to my PC via KDE Connect causes KDE
Connect daemon to crash. This happens whether the file is sent individually or
in a batch, and whether the transfer is initiated inside the KDE Connect
Android app or via the share menu of another app.
***
STEPS TO REPRODUCE
1. Send the attached file from an Android device to a PC using KDE Connect
OBSERVED RESULT
KDE Connect daemon crashes
EXPECTED RESULT
KDE Connect saves the file to the configured directory and does not crash
SOFTWARE/OS VERSIONS
Linux: 6.3.4-arch1-1 (64-bit)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
ADDITIONAL INFORMATION
Backtrace inline:
Application: KDE Connect Daemon (kdeconnectd), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f2a9da9f2d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f2a9da4fa08 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f2a9da38538 in __GI_abort () at abort.c:79
#10 0x7f2a9e0a0098 in qt_message_fatal (message=...,
context=) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7f2a76a80610, msg=msg@entry=0x7f2a9f86e108 "Fatal Error: Got
cmd %d, while waiting for an answer!") at global/qlogging.cpp:893
#12 0x7f2a9f788090 in KIO::SlaveBase::waitForAnswer(int, int, QByteArray&,
int*) (this=this@entry=0x7f2a4c0012e0, expected1=expected1@entry=84,
expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7f2a76a80684) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1149
#13 0x7f2a9f7c8c06 in KIO::SlaveBase::canResume(unsigned long long)
(this=this@entry=0x7f2a4c0012e0, offset=65536) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1116
#14 0x7f2a76a90ec0 in FileProtocol::put(QUrl const&, int,
QFlags) (this=0x7f2a4c0012d0, url=, _mode=-1,
_flags=...) at /usr/src/debug/kio/kio-5.106.0/src/ioslaves/file/file.cpp:550
#15 0x7f2a9f7c8105 in KIO::SlaveBase::dispatch(int, QByteArray const&)
(this=0x7f2a4c0012e0, command=68, data=...) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1289
#16 0x7f2a9f7c02ae in KIO::SlaveBase::dispatchLoop() (this=0x7f2a4c0012e0)
at /usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:342
#17 0x7f2a9f83f0b7 in KIO::WorkerThread::run() (this=0x55b37e881c30) at
/usr/src/debug/kio/kio-5.106.0/src/core/workerthread.cpp:62
#18 0x7f2a9e0f30da in operator() (__closure=) at
thread/qthread_unix.cpp:350
#19 (anonymous
namespace)::terminate_on_exception >
(t=) at thread/qthread_unix.cpp:287
#20 QThreadPrivate::start(void*) (arg=0x55b37e881c30) at
thread/qthread_unix.cpp:310
#21 0x7f2a9da9d44b in start_thread (arg=) at
pthread_create.c:444
#22 0x7f2a9db20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 8 (Thread 0x7f2a7dffb6c0 (LWP 373600) "kdeconnectd"):
#1 __pselect (nfds=5, readfds=0x7f2a7dff2a20, writefds=0x0, exceptfds=0x0,
timeout=, sigmask=) at
../sysdeps/unix/sysv/linux/pselect.c:56
#2 0x7f2a99ab06f9 in () at /usr/lib/libusbmuxd-2.0.so.6
#3 0x7f2a99ab13cc in () at /usr/lib/libusbmuxd-2.0.so.6
#4 0x7f2a9da9d44b in start_thread (arg=) at
pthread_create.c:444
#5 0x7f2a9db20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 7 (Thread 0x7f2a7e7fc6c0 (LWP 373560) "Qt bearer threa"):
#1 __GI___libc_read (fd=15, buf=buf@entry=0x7f2a7e7fb840,
nbytes=nbytes@entry=8) at ../sysdeps/unix/sysv/linux/read.c:24
#2 0x7f2a9c765560 in read (__nbytes=8, __buf=0x7f2a7e7fb840,
__fd=, __fd=, __buf=,
__nbytes=) at /usr/include/bits/unistd.h:38
#3 g_wakeup_acknowledge (wakeup=) at ../glib/glib/gwakeup.c:216
#4 g_wakeup_acknowledge (wakeup=0x7f2a64000df0) at ../glib/glib/gwakeup.c:208
#5 0x7f2a9c711094 in g_main_context_check (context=0x7f2a64000c30,
max_priority=2147483647, fds=0x7f2a640013f0, n_fds=1) at
../glib/glib/gmain.c:4021
#6 0x7f2a9c76d998 in g_main_context_iterate.isra.0
(context=context@entry=0x7f2a64000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #14 from Judah Richardson --- (In reply to caulier.gilles from comment #13) > Maik, > > Do you know why a zombie process under Windows will not visible in Process > Manager and appears in Process Explorer freeware ? It's a question of right, > as admin only can see this kind of executable on the system ? > > Judah, > > Windows provides a CLI tool named tasklist: > > https://superuser.com/questions/914782/how-do-you-list-all-processes-on-the- > command-line-in-windows > > Do you seen the same results than Process explorer with this command line > tool ? > > Gilles Caulier Gilles: thanks for the information. I don't have the time in the near term to test tasklist. Process Explorer is a GUI tool provided by Microsoft & is much easier to use. In any case, me testing would not address the issue that digiKam on Windows leaves orphaned processes running after the user closes the application. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470372] rpm-ostree updates stopped working
https://bugs.kde.org/show_bug.cgi?id=470372 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470488] KDE Connect daemon crashes when receiving the attached image from my Android device
https://bugs.kde.org/show_bug.cgi?id=470488 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470195] Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything
https://bugs.kde.org/show_bug.cgi?id=470195 Paul Worrall changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #4 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 469445 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #11 from Paul Worrall --- *** Bug 470195 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470482] New: Keyboard focus deflecting after first keypress, 10-20 minutes into session, with some XWayland software
https://bugs.kde.org/show_bug.cgi?id=470482 Bug ID: 470482 Summary: Keyboard focus deflecting after first keypress, 10-20 minutes into session, with some XWayland software Classification: Plasma Product: kwin Version: 5.27.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: disso-peach@fedora.email Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open affected software (Renoise in this case) 2. Use for at least 10 minutes, saving modules frequently. Less time is needed if any Electron wrapper application is running (for some reason?) 3. Attempt to input notes on the tracker matrix OBSERVED RESULT One keypress is registered, then keyboard focus is deflected away from Renoise. No idea where it goes. Clicking re-latches it. Renoise does not indicate that the focus has gone elsewhere in Renoise. EXPECTED RESULT Keyboard focus remains persistent on Renoise, allowing the software to be used. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Devuan GNU/Linux (also observed in Arch Linux and Debian Stable) (available in About System) KDE Plasma Version: 5.27.2 (observed as old as 5.7, untested prior) KDE Frameworks Version: Qt Version: 5 ADDITIONAL INFORMATION Observed consistently in KWin wayland sessions for the majority of the history of the history of KWin as a wayland compositor, when using Renoise. Previously seen in Ferdi as well, seems to have been fixed their-end as of the fork to Ferdium. Issue does not present in KWin X11 sessions, nor any other wayland compositor (ruling out a Renoise issue). Issue has been final blocking item to using Plasma in Wayland for multiple years for myself and I had wrongly assumed that it would have already been reported. Bug is more likely to happen quickly if the session has been running for at least four hours, but is always a "matter-of-time" subject, and not a "will-it-happen" subject. Longest I have been able to continually use Renoise for in a Plasma 5 wayland session was 25 minutes, directly after boot and going straight into Renoise. Shortest was 10 seconds, 5 days after boot. If relevant, this has been observed using locally-built from-git mesa on AMD graphics hardware using the amdgpu and radeonsi driver set. This has not been tested with distro mesa on debian or devuan, but was present with distro mesa on arch linux. This has been tested with only one keyboard, which presents one keyboard, two mice, and one controller device, to the operating system. These are mentioned due to feasibility that this bug may be of the "distant ramifications" sort. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470442] Hanging system with Baloo file
https://bugs.kde.org/show_bug.cgi?id=470442 Ben Bonacci changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||b...@benbonacci.com --- Comment #1 from Ben Bonacci --- *** This bug has been marked as a duplicate of bug 470088 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460698] Clipboard actions do not get executed on selection but on copy - regression
https://bugs.kde.org/show_bug.cgi?id=460698 --- Comment #2 from Paul Worrall --- The bug is that you can select the configuration described without also selecting "Keep selection and clipboard the same" and "Text Selection: Always save in history". With those selected, the action is triggered immediately on selection. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464869] Installing updates corrupts Grub 2 ( unbootable system)
https://bugs.kde.org/show_bug.cgi?id=464869 --- Comment #5 from Lassi Väätämöinen --- (In reply to Lassi Väätämöinen from comment #3) > Not sure if these issues with Breeze Grub theme are related: > https://www.reddit.com/r/kdeneon/comments/z0vf4h/ > kde_neon_update_replaced_grub_with_broken_version/ > https://www.reddit.com/r/kde/comments/8nkzvs/ > neon_seems_hardwired_to_look_for_breeze_grub/ > > For what it's worth, I don't even seem to have the Breeze theme on my system > (after running Boot Repair Disc, which is a must with KDE Neon...) > > $ cat /etc/default/grub.d/99_breeze-grub.cfg > GRUB_THEME=/boot/grub/themes/breeze/theme.txt > > $ sudo ls /boot/grub/themes/breeze/theme.txt > ls: cannot access '/boot/grub/themes/breeze/theme.txt': No such file or > directory > In this case 'dpkg -l |grep grub-theme-breeze' showed that the package was installed, but the theme file was missing. Now, every time an upgrade happens, Grub wants to get displayed. On a normal boot it does not show. If the theme is then broken like this, not booting after upgrade might be explained. But the questions: a) why is the theme file missing? b) why does grub want to show up after upgrade, but not on a normal boot? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470432] When entering password after a screen lock the enter key is used as part of the password
https://bugs.kde.org/show_bug.cgi?id=470432 Ben Bonacci changed: What|Removed |Added Product|kde |kscreenlocker CC||b...@benbonacci.com Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Component|general |general Version|unspecified |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 470363] devices, smart state, disk, wrong temperature
https://bugs.kde.org/show_bug.cgi?id=470363 Harald Sitter changed: What|Removed |Added Component|general |general Product|kinfocenter |plasma-disks Version|5.27.5 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470383] Displays connected through USB-C Dock give black display until 24-bit color mode is forced
https://bugs.kde.org/show_bug.cgi?id=470383 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 Summary|Displays connected through |Displays connected through |USB-C Dock give Black |USB-C Dock give black |Display |display until 24-bit color ||mode is forced --- Comment #2 from Nate Graham --- Sounds like a driver bug. Not sure how we could fix this ourselves in KWin. Would it be possible to detect that there's no output and try to switch to 24-bit mode? If not, we probably have to wait for the driver bug to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470369] Add "Pin Screenshot" Functionality to Spectacle
https://bugs.kde.org/show_bug.cgi?id=470369 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- What's the use case for this feature? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470088] baloo thing randomly crashed
https://bugs.kde.org/show_bug.cgi?id=470088 Ben Bonacci changed: What|Removed |Added CC||alessandro.nigris@tiscali.i ||t --- Comment #1 from Ben Bonacci --- *** Bug 470443 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470443] Baloo crash indexing
https://bugs.kde.org/show_bug.cgi?id=470443 Ben Bonacci changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@benbonacci.com Resolution|--- |DUPLICATE --- Comment #1 from Ben Bonacci --- *** This bug has been marked as a duplicate of bug 470088 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470088] baloo thing randomly crashed
https://bugs.kde.org/show_bug.cgi?id=470088 Ben Bonacci changed: What|Removed |Added CC||danielesanna1...@gmail.com --- Comment #2 from Ben Bonacci --- *** Bug 470397 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470397] Baloo crash random
https://bugs.kde.org/show_bug.cgi?id=470397 Ben Bonacci changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@benbonacci.com Resolution|--- |DUPLICATE --- Comment #1 from Ben Bonacci --- *** This bug has been marked as a duplicate of bug 470088 *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470385] Hovering effect in application list doesn't follow when scrolling
https://bugs.kde.org/show_bug.cgi?id=470385 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |INTENTIONAL --- Comment #1 from Nate Graham --- This is actually intentional; we got many complaints about the requested behavior, especially in the case when Kickoff appeared in such a manner that the cursor was below a category that just appeared. So I think we have to keep it the way it is right now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #10 from William Coolman --- My mistake. I'll correct that. On Wed, May 31, 2023, 7:32 AM Federico Dossena wrote: > https://bugs.kde.org/show_bug.cgi?id=469445 > > --- Comment #9 from Federico Dossena --- > Why did you mark this as fixed? That's a workaround, not a solution. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470489] vex amd64->IR: unhandled instruction bytes: 0x62 0xF2 0xFD 0x28 0x7C 0xE0 0x48 0x8D 0x90 0x0
https://bugs.kde.org/show_bug.cgi?id=470489 Tom Hughes changed: What|Removed |Added Status|REPORTED|RESOLVED CC||t...@compton.nu Resolution|--- |DUPLICATE --- Comment #1 from Tom Hughes --- That's an AVX-512 instruction, or an EVEX prefix at least which amount to the same thing from our point of view. *** This bug has been marked as a duplicate of bug 383010 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Tom Hughes changed: What|Removed |Added CC||toitran4...@gmail.com --- Comment #92 from Tom Hughes --- *** Bug 470489 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439864] Dolphin resets to "Home" and forgets paths of all tabs that are not available on start [regression]
https://bugs.kde.org/show_bug.cgi?id=439864 Walerian Walawski - w87.eu changed: What|Removed |Added CC||kde@w87.eu --- Comment #18 from Walerian Walawski - w87.eu --- Same here, Dolphin version 23.04.1 on KDE neon 5.27 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 Ben Bonacci changed: What|Removed |Added CC||b...@benbonacci.com Component|general |balooctl -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 439697] Gwenview crashes in Gwenview::RasterImageItem::paint() when trying to rotate a jpg file quickly multiple times
https://bugs.kde.org/show_bug.cgi?id=439697 Nicolas Fella changed: What|Removed |Added CC||christree4...@outlook.com --- Comment #26 from Nicolas Fella --- *** Bug 470479 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 470479] Gwenview crashed when trying to rotate an image
https://bugs.kde.org/show_bug.cgi?id=470479 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 439697 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] Remember visibility status of Annotations toolbar in Rectangular Region mode across application launches
https://bugs.kde.org/show_bug.cgi?id=468788 Gin changed: What|Removed |Added CC||ginnoka...@gmail.com --- Comment #7 from Gin --- Once this bug is resolved, will it just be the annotation portion of the toolbar that has it's visibility status remembered? Or will there be an option to disable the entire toolbar itself? If this needs to be it's own "bug report" I am happy to file one. Reason: In previous versions of spectacle, it was possible to take a rectangular region screenshot without any toolbars that appeared. I was able to hit my shortcut (defined in spectacle), quickly take the region screenshot, and then proceed with my workflow. Now the toolbar is forced to appear every time that I take a screenshot and the bar appears right in the center of my current monitor. This often causes an overlap with what I am trying to screenshot, causing me to first move the toolbar and then select the region. Being able to disable the toolbar in the setting or having a command line arg to disable would fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469301] Kate auto complete minimal word length sitck in 4 letter
https://bugs.kde.org/show_bug.cgi?id=469301 --- Comment #1 from veupragacosei-9...@yopmail.com --- The minimal word length to complet work for name, like name of variable. But the tag autocomplete is allways 4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469151] On Wayland and Plasma 6 with 200% scale, mouse cursor lags when moving over content-containing areas of scrollviews in Plasma 6 panel pop-ups
https://bugs.kde.org/show_bug.cgi?id=469151 --- Comment #3 from Vlad Zahorodnii --- I can't reproduce it on my laptop. I use 200% scale. I have Qt 6.5.1, Arch linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454231] 3-fingers touchpad gesture (to navigate between virtual desktops) should follow touchpad scrolling direction preference
https://bugs.kde.org/show_bug.cgi?id=454231 Nate Graham changed: What|Removed |Added CC||m.k...@irregular.at --- Comment #7 from Nate Graham --- *** Bug 470403 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470403] There is no setting to inverse the direction of three-finger swipe gesture
https://bugs.kde.org/show_bug.cgi?id=470403 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 454231 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454231] 3-fingers touchpad gesture (to navigate between virtual desktops) should follow touchpad scrolling direction preference
https://bugs.kde.org/show_bug.cgi?id=454231 Nate Graham changed: What|Removed |Added Summary|3-fingers touchpad gesture |3-fingers touchpad gesture |(to navigate between|(to navigate between |virtual desktops) doesn't |virtual desktops) should |follow touchpad scrolling |follow touchpad scrolling |direction preference|direction preference Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #9 from Federico Dossena --- Why did you mark this as fixed? That's a workaround, not a solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 Nikolas Spiridakis <1niko...@hotmail.gr> changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #8 from Nikolas Spiridakis <1niko...@hotmail.gr> --- The issue is not fixed, the file is going to get big again if you keep putting files on your desktop. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469534] Crash on startup when offline
https://bugs.kde.org/show_bug.cgi?id=469534 alicehar...@murena.io changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from alicehar...@murena.io --- Whoops, I didn't realise it was the submitter that was supposed to remove NEEDSINFO after providing a backtrace -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470484] Powerdevil crashes multiple times during screen sleep
https://bugs.kde.org/show_bug.cgi?id=470484 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 470363] devices, smart state, disk, wrong temperature
https://bugs.kde.org/show_bug.cgi?id=470363 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470389] Accent mark should be shown before pressing a letter that can be accented
https://bugs.kde.org/show_bug.cgi?id=470389 Nate Graham changed: What|Removed |Added Assignee|plasma-b...@kde.org |unassigned-b...@kde.org Target Milestone|1.0 |--- CC||n...@kde.org Status|REPORTED|NEEDSINFO Product|plasmashell |kde Version|5.27.4 |unspecified Component|general |general Resolution|--- |WAITINGFORINFO Summary|Accents are not shown |Accent mark should be shown |before pressing a letter|before pressing a letter |that can be accented|that can be accented Severity|normal |wishlist --- Comment #1 from Nate Graham --- This might require Qt changes to support it. Not sure we can inject this ourselves in KDE. Does this work *anywhere* in *any* piece of KDE software, such as Dolphin, Discover, Kate, Konsole, or Gwenview? Or do they all lack the requested feature? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 470365] Timer counts down too fast
https://bugs.kde.org/show_bug.cgi?id=470365 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #3 from Nate Graham --- Out of curiosity are you using a 144hz refresh screen? If so, this is Bug 419421, which is fixed in Plasma 6. See the bug report for a workaround on Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470490] New: Kate Is Not Aware If "hunspell-en_gb" Is Installed or Not
https://bugs.kde.org/show_bug.cgi?id=470490 Bug ID: 470490 Summary: Kate Is Not Aware If "hunspell-en_gb" Is Installed or Not Classification: Applications Product: kate Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: encoding Assignee: kwrite-bugs-n...@kde.org Reporter: kdelo...@mozej.com Target Milestone: --- Created attachment 159369 --> https://bugs.kde.org/attachment.cgi?id=159369=edit Kate/Plasma not aware of languages and dictionaries SUMMARY *** Foreword: My Kate setting has always automatic spelling check off. No automatic spelling has been used to trigger this bug. Setting Language for the whole text (e.g. here the text is .md) does nothing. As soon as I go to menu and chose spelling it always reverts to "EN US ver. 2." The reason for this is that all the languages are present in the system and Kate, but no "hunspell-en_gb" has been installed. Attached screnshot is worth a 1000 words. I cannot explain it better in writing. *** STEPS TO REPRODUCE 1. Go to KDE's application menu at the bottom left , hit meta key and type "spelling". Tick UK/GB 2. Close KATE and reopen Kate to be sure it loads/respects KDEs settings 3. Go to both: the bottom left and right corner of Kate and set language as in the screenshot. 4. Go to Kate's menu and chose spelling (not automatic). OBSERVED RESULT: 1. On the bottom left in Kate it always reverts itself to US ver.2. No EN/UK spelling can be checked. It always reverts back to EN US ver2. The text is always treated as EN/US and nothing can be done. EXPECTED RESULT: Make Kate (and Plasma) not show options in multiple places for a given language when this language dictionary is not installed (here "hunspell-en_gb"). Let Kate (and Plasma) show only installed langueages in order not to confuse users when they use this languages/spell checking throughout system: A. Scenario 1: "hunspell-en_gb" has not been installed. Kate should not show to spell check or use GB/UK, because its reverting imediately back to EN/US B. Scenario 2: "hunspell-en_gb" is installed. Kate now is allowed to show GB and GB/UK English in those two places (see screenshot) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION UK stands for United Kingdom, not Ukraine. Its very confusing in plasma/kate/hunspell. I know about GB, but GB does not contain Northern Ireland which uses UK spelling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #6 from William Coolman --- (In reply to William Coolman from comment #5) > Created attachment 159362 [details] > attachment-3610397-0.html > > I don't think this is the same bug. My memory usage looks normal. > > On Wed, May 24, 2023 at 9:35 AM Paul Worrall > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=469445 > > > > Paul Worrall changed: > > > >What|Removed |Added > > > > > > CC||wcool...@gmail.com > > > > --- Comment #4 from Paul Worrall --- > > *** Bug 470195 has been marked as a duplicate of this bug. *** > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. Ok, removing the ScreenMapping entry made things work again. I'll close this ticket. Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470383] Displays connected through USB-C Dock give black display until 24-bit color mode is forced
https://bugs.kde.org/show_bug.cgi?id=470383 --- Comment #3 from sfal...@cloverleaf-linux.org --- (In reply to Nate Graham from comment #2) > Sounds like a driver bug. Not sure how we could fix this ourselves in KWin. > Would it be possible to detect that there's no output and try to switch to > 24-bit mode? If not, we probably have to wait for the driver bug to be fixed. *shrug* I wasn't sure where the bug actually was, or if this is something that can be "fixed" via kwin or not. It appears that the proximal cause is in the amdgpu drm driver. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464165] How to search geographical tags in the digiKam catalog.
https://bugs.kde.org/show_bug.cgi?id=464165 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||8.1.0 --- Comment #4 from caulier.gil...@gmail.com --- Fixed with bug 433391 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470486] New: Can't update system
https://bugs.kde.org/show_bug.cgi?id=470486 Bug ID: 470486 Summary: Can't update system Classification: Applications Product: Discover Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: plasma-b...@kde.org Reporter: pbuy...@gmail.com CC: aleix...@kde.org Target Milestone: --- Dependency resolution failed:The following packages have unmet dependencies: kdesdk-devenv-dependencies: Depends: libkf5wallet-dev but it is not going to be installed libkf5kdelibs4support-dev: Depends: libkf5wallet-dev (= 5.51) but it is not going to be installed libkf5khtml-dev: Depends: libkf5wallet-dev (= 5.51.0~) but it is not going to be installed libkf5mailtransport-dev: Depends: libkf5wallet-dev (= 5.19.0~) but it is not going to be installed -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 465582] Kde Connect doen't reconnect
https://bugs.kde.org/show_bug.cgi?id=465582
--- Comment #4 from Michael ---
well, seems nobody has interest in solving this, I can understand that there
are not much people using it, but since kdeconnect is there it should work,
agree?
in fact, it doesn't seem to have a reconnect routine and that should be
corrected
a cmd line like "/usr/bin/kdeconnect-cli -n Moto E7 --refresh" does it, but for
some reason I can not automate it, I believe that is so because udev runs as
root and the command needs to be run as the user
inside the script to be run from udev_rule (as root) this command should, but
is not working
su hm -c '/usr/bin/kdeconnect-cli "-n Moto E7 --refresh"'
the options are interpreted as two, or as a diretcory depends on how I set the
quotes
that's in my udev_rules file
KERNEL=="rndis_host", ACTION=="add", ENV{ID_SERIAL}=="0e8d:2005",
RUN+="/usr/sbin/kdeconnect.sh"
the kernel event in my case:
rndis_host 1-2:1.0 usb0: register 'rndis_host' at usb-:00:12.2-2, RNDIS
device, 5a:c0:6b:31:9a:5c
rndis_host 1-2:1.0 enx5ac06b319a5c: renamed from usb0
the kdeconnect reconnect should run after the renaming of usb0, the device ID
"enx*' is random
if somebody here has a better idea or knows how to make it work from udev, it
would be nice
thanks
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 William Coolman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #7 from William Coolman --- Removing [ScreenMapping] entry from /home/[user]/.config/plasma-org.kde.plasma.desktop-appletsrc fixed the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470483] New: Only the active window becomes translucent when adjusting custom tiles
https://bugs.kde.org/show_bug.cgi?id=470483 Bug ID: 470483 Summary: Only the active window becomes translucent when adjusting custom tiles Classification: Plasma Product: kwin Version: 5.27.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: char...@binkle.co.uk Target Milestone: --- Created attachment 159366 --> https://bugs.kde.org/attachment.cgi?id=159366=edit screenshot showing what happens when resizing tiles SUMMARY When clicking and dragging the border between two tiles, only the active window* has the translucency effect applied to it; even if there are multiple windows being resized. *or if the active window is not among those being resized, the closest tile to it. STEPS TO REPRODUCE 1. ensure the translucency effect is enabled via "workspace behaviour>desktop effects>translucency" 2. set up a tile layout with more than one tile using meta+t 3. put one window on each tile (doesn't matter which application) using shift+dragging 4. click and drag the border between two windows OBSERVED RESULT only the active window becomes translucent (if the active window was not one of the resized windows, the nearest resized window to it will become translucent) EXPECTED RESULT When resizing multiple windows using custom tiling, all the resized windows should become translucent. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I am not entirely sure whether the bug is still present in the latest builds, (I have not been able to test them yet). I am also not entirely sure whether this is an issue with the effect itself, or the tiling, or the way that kwin handles windows and resizing in general -- I don't know much about the implementation of any of them. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 469895] Cannot change laptop display brightness when connected to external monitor with ddcutil support
https://bugs.kde.org/show_bug.cgi?id=469895 Albert Vaca changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/commit/ddca ||baf93712b953e3ec327416e0332 ||d7e44fc40 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #10 from Albert Vaca --- Git commit ddcabaf93712b953e3ec327416e0332d7e44fc40 by Albert Vaca Cintora, on behalf of Quang Ngô. Committed on 31/05/2023 at 11:24. Pushed by albertvaka into branch 'Plasma/5.27'. Fix ddcutil for laptop user This will prioritize usage of backlight helper over ddcutil. If backlight helper fail, fall back to ddcutil. Expected result: * Laptop users can now change the brightness of the internal display. External display will use its own controls. * Does not affect desktop users. M +71 -76 daemon/backends/upower/powerdevilupowerbackend.cpp https://invent.kde.org/plasma/powerdevil/-/commit/ddcabaf93712b953e3ec327416e0332d7e44fc40 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470484] New: Powerdevil crashes multiple times during screen sleep
https://bugs.kde.org/show_bug.cgi?id=470484 Bug ID: 470484 Summary: Powerdevil crashes multiple times during screen sleep Classification: Plasma Product: Powerdevil Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 159367 --> https://bugs.kde.org/attachment.cgi?id=159367=edit dr konqi screenshot SUMMARY Every day when I leave my computer idle with the screen powered off, powerdevil keeps regularly crashing and dumping core It's a desktop and it's not configured to suspend after a certain time STEPS TO REPRODUCE 1. turn off the computer monitor 2. wait 3. powerdevil will have crashed multiple times, plasma seems unaffected OBSERVED RESULT System log will be filled with stack traces from powerdevil EXPECTED RESULT Same but without crashes SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.3.3 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I'm using plasma on wayland, with a radeon GPU, mesa drivers and one monitor connected through displayport Taking a look at those crashes on dr konqi, I noticed that every crash happens around 25min from each other. It's the same amount of time I have set on powerdevil's KCM for screen switch off STACK TRACE Stack trace of thread 110517: #0 0x7f54074a43c8 __GI___pthread_sigmask (libc.so.6 + 0x8e3c8) #1 0x7f540744fcad __GI___sigprocmask (libc.so.6 + 0x39cad) #2 0x7f5408a7820b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x520b) #3 0x7f5408a7a816 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7816) #4 0x7f540744fab0 __restore_rt (libc.so.6 + 0x39ab0) #5 0x7f540011a97c _ZN9QtWayland17org_kde_kwin_dpms3setEj (libKF5ScreenDpms.so.8 + 0x797c) #6 0x7f540011bcc4 _ZN7KScreen4Dpms10switchModeENS0_4ModeERK5QListIP7QScreenE (libKF5ScreenDpms.so.8 + 0x8cc4) #7 0x7f54001266ca _ZN10PowerDevil14BundledActions4DPMS13onIdleTimeoutEi (powerdevil_dpmsaction.so + 0x56ca) #8 0x7f5408a45a51 _ZN10PowerDevil4Core21onKIdleTimeoutReachedEii (libpowerdevilcore.so.2 + 0x17a51) #9 0x7f5407cd01a3 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d01a3) #10 0x7f540869833d _ZN9KIdleTime14timeoutReachedEii (libKF5IdleTime.so.5 + 0x433d) #11 0x7f5408698ee1 _ZN9QtPrivate18QFunctorSlotObjectIZN9KIdleTimeC4EvEUliE_Li1ENS_4ListIJiEEEvE4implEiPNS_15QSlotObjectBaseEP7QObjectPPvPb (libKF5IdleTime.so.5 + 0x4ee1) #12 0x7f5407ccffe7 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2cffe7) #13 0x7f5408698226 _ZN20AbstractSystemPoller14timeoutReachedEi (libKF5IdleTime.so.5 + 0x4226) #14 0x7f5407ccffe7 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2cffe7) #15 0x7f5408a8e4f6 n/a (libffi.so.8 + 0x74f6) #16 0x7f5408a8af5e n/a (libffi.so.8 + 0x3f5e) #17 0x7f5408a8db73 ffi_call (libffi.so.8 + 0x6b73) #18 0x7f5408a99645 wl_closure_invoke (libwayland-client.so.0 + 0x7645) #19 0x7f5408a99e73 dispatch_event (libwayland-client.so.0 + 0x7e73) #20 0x7f5408a9a13c dispatch_queue (libwayland-client.so.0 + 0x813c) #21 0x7f54024efc06 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x72c06) #22 0x7f5407cc2834 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c2834) #23 0x7f5407c9ab18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29ab18) #24 0x7f5407c9fa7b _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x29fa7b) #25 0x7f5407ce6088 postEventSourceDispatch (libQt5Core.so.5 + 0x2e6088) #26 0x7f5406710981 g_main_context_dispatch (libglib-2.0.so.0 + 0x5a981) #27 0x7f540676db39 n/a (libglib-2.0.so.0 + 0xb7b39) #28 0x7f540670e032 g_main_context_iteration (libglib-2.0.so.0 + 0x58032) #29 0x7f5407ce9f0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e9f0c) #30 0x7f5407c99824 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x299824) #31 0x7f5407c9acc3 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x29acc3)
[kdeconnect] [Bug 470487] New: KDE Connect daemon crashes when receiving a specific jpeg image from my Android device
https://bugs.kde.org/show_bug.cgi?id=470487
Bug ID: 470487
Summary: KDE Connect daemon crashes when receiving a specific
jpeg image from my Android device
Classification: Applications
Product: kdeconnect
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: zak.wil...@gmail.com
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
Application: kdeconnectd (23.04.1)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.4-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
KDE connect daemon crashes when receiving a specific image. It does not crash
when receiving other files. This is true whether the image is sent as a single
file, or in a batch, and whether the transfer is initiated from within KDE
Connect on the Android device or the share menu of another app.
The crash can be reproduced every time.
-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7fc5e9c9f2d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7fc5e9c4fa08 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7fc5e9c38538 in __GI_abort () at abort.c:79
#10 0x7fc5ea2a0098 in qt_message_fatal (message=...,
context=) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7fc5a2215610, msg=msg@entry=0x7fc5eb9a1108 "Fatal Error: Got
cmd %d, while waiting for an answer!") at global/qlogging.cpp:893
#12 0x7fc5eb8bb090 in KIO::SlaveBase::waitForAnswer(int, int, QByteArray&,
int*) (this=this@entry=0x7fc5940012e0, expected1=expected1@entry=84,
expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7fc5a2215684) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1149
#13 0x7fc5eb8fbc06 in KIO::SlaveBase::canResume(unsigned long long)
(this=this@entry=0x7fc5940012e0, offset=65536) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1116
#14 0x7fc5a2a26ec0 in FileProtocol::put(QUrl const&, int,
QFlags) (this=0x7fc5940012d0, url=, _mode=-1,
_flags=...) at /usr/src/debug/kio/kio-5.106.0/src/ioslaves/file/file.cpp:550
#15 0x7fc5eb8fb105 in KIO::SlaveBase::dispatch(int, QByteArray const&)
(this=0x7fc5940012e0, command=68, data=...) at
/usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:1289
#16 0x7fc5eb8f32ae in KIO::SlaveBase::dispatchLoop() (this=0x7fc5940012e0)
at /usr/src/debug/kio/kio-5.106.0/src/core/slavebase.cpp:342
#17 0x7fc5eb9720b7 in KIO::WorkerThread::run() (this=0x55bcdf18bb00) at
/usr/src/debug/kio/kio-5.106.0/src/core/workerthread.cpp:62
#18 0x7fc5ea2f30da in operator() (__closure=) at
thread/qthread_unix.cpp:350
#19 (anonymous
namespace)::terminate_on_exception >
(t=) at thread/qthread_unix.cpp:287
#20 QThreadPrivate::start(void*) (arg=0x55bcdf18bb00) at
thread/qthread_unix.cpp:310
#21 0x7fc5e9c9d44b in start_thread (arg=) at
pthread_create.c:444
#22 0x7fc5e9d20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 8 (Thread 0x7fc5c9ffb6c0 (LWP 8860) "kdeconnectd"):
#1 __pselect (nfds=5, readfds=0x7fc5c9ff2a20, writefds=0x0, exceptfds=0x0,
timeout=, sigmask=) at
../sysdeps/unix/sysv/linux/pselect.c:56
#2 0x7fc5e5be36f9 in () at /usr/lib/libusbmuxd-2.0.so.6
#3 0x7fc5e5be43cc in () at /usr/lib/libusbmuxd-2.0.so.6
#4 0x7fc5e9c9d44b in start_thread (arg=) at
pthread_create.c:444
#5 0x7fc5e9d20e40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 7 (Thread 0x7fc5ca7fc6c0 (LWP 2025) "Qt bearer threa"):
#1 0x7fc5e8910f8a in g_main_context_check (context=0x7fc5b8000c30,
max_priority=, fds=, n_fds=) at
../glib/glib/gmain.c:4103
#2 0x7fc5e896d998 in g_main_context_iterate.isra.0
(context=context@entry=0x7fc5b8000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4273
#3 0x7fc5e890e032 in g_main_context_iteration (context=0x7fc5b8000c30,
may_block=1) at ../glib/glib/gmain.c:4343
#4 0x7fc5ea4e9f2f in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc5b8000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5 0x7fc5ea499824 in
QEventLoop::exec(QFlags) (this=0x7fc5ca7fbac0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#6 0x7fc5ea2f6eb6 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7 0x7fc5ea2f30da in operator() (__closure=) at
thread/qthread_unix.cpp:350
#8 (anonymous
[Breeze] [Bug 470398] Add window borders to match the kwin theme
https://bugs.kde.org/show_bug.cgi?id=470398 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||n...@kde.org --- Comment #1 from Nate Graham --- Unfortunately this is not feasible due to the inherent differences between server-side decoration apps (e.g. KDE apps) and client-side-decoration apps (e.g. GNOME apps). Anything we could do here would be a huge hack that would randomly break all the time and not work properly for many CSD apps. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 402028] Setting shortcut keys to Ctrl+< or Ctrl+> breaks shortcuts for Ctrl+Z & Ctrl+X
https://bugs.kde.org/show_bug.cgi?id=402028 dimin21...@gmail.com changed: What|Removed |Added CC||dimin21...@gmail.com --- Comment #24 from dimin21...@gmail.com --- Experiencing the same issue with ctrl+shift for language switching, on latest neon. However, this ppa fixes it if you are using x11: https://launchpad.net/%7Enrbrtx/+archive/ubuntu/xorg-hotkeys -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460698] Clipboard actions do not get executed on selection but on copy - regression
https://bugs.kde.org/show_bug.cgi?id=460698 Paul Worrall changed: What|Removed |Added Version|5.26.1 |5.27.5 CC||p.r.worr...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Paul Worrall --- Can reproduce: 1. Create an action with a simple match pattern, e.g. a+ 2. Select "Show action popup menu Immediately on selection" 3. Open Kate and select some text that matches the pattern, e.g. aaa OBSERVED RESULT Nothing happens ADDITIONAL INFORMATION Action is triggered only when selected text is copied to clipboard Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.4-arch1-1 (64-bit) Graphics Platform: both (X11 or Wayland) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 470312] krunner crashed when typing in 4000000
https://bugs.kde.org/show_bug.cgi?id=470312 --- Comment #4 from Andrei Rybak --- Created attachment 159365 --> https://bugs.kde.org/attachment.cgi?id=159365=edit demonstration of krunner closing unexpectedly Originally, the crash happened just after typing "40" or "400". On 2023-05-26 I managed to reproduce the _crash_ (with drkonqi) a couple of times. Since then, I've installed debug symbols for libqalculate22. Now, after an upgrade and restart I'm not able to reproduce the crash, but there's still some weird behavior going on – krunner closes unexpectedly, but drkonqi doesn't appear. drkonqi itself seems to be working, e.g. I'm able to reproduce the crash from https://bugs.kde.org/show_bug.cgi?id=469919 and drkonqi reports the crash in Spectacle. Unfortunately, I can't pin down the exact steps to reproduce the weird behavior. As far as I can tell, it has something to do with having a quote-unquote "incomplete" math expression in history. In my case, it's a trailing minus sign. For example: 1. Open krunner (in my case, via shortcut Alt+F2) 2. Type `1000-` (one thousand and a trailing minus) 3. Press Enter 4. Press Esc 5. Open krunner again 6. Start typing some number In some cases, during step 6 krunner closes unexpectedly. As an example, on the attached screen recording (kde-krunner-glitch-2023-05-31.mp4) at the very end I'm trying to type "3" (thirty thousand), but I'm only able to type in "3000" (three thousand). krunner closes unexpectedly just after I press the fourth zero. The screen recording includes a demo of the keys being pressed via an application called "screenkey". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470088] baloo thing randomly crashed
https://bugs.kde.org/show_bug.cgi?id=470088 Ben Bonacci changed: What|Removed |Added CC||mnstam...@mail.ru --- Comment #3 from Ben Bonacci --- *** Bug 470442 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470445] [Wayland] Side panels "freeze", showing a NON-interactive snapshot of it.
https://bugs.kde.org/show_bug.cgi?id=470445 Rafael Linux User changed: What|Removed |Added Summary|[Wayland] Side panels with |[Wayland] Side panels |"auto-hide" enabled |"freeze", showing a |"freeze", showing a |NON-interactive snapshot of |NON-interactive snapshot of |it. |it. | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] Remember visibility status of Annotations toolbar in Rectangular Region mode across application launches
https://bugs.kde.org/show_bug.cgi?id=468788 --- Comment #8 from Aurora Robb Kristiansen --- That would be ideal, and is what this bug report was originally about, so I still believe at least a command line option to hide it for power users makes a lot of sense. I hate to sound demanding, and on a FOSS project no less, but still. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470489] New: vex amd64->IR: unhandled instruction bytes: 0x62 0xF2 0xFD 0x28 0x7C 0xE0 0x48 0x8D 0x90 0x0
https://bugs.kde.org/show_bug.cgi?id=470489 Bug ID: 470489 Summary: vex amd64->IR: unhandled instruction bytes: 0x62 0xF2 0xFD 0x28 0x7C 0xE0 0x48 0x8D 0x90 0x0 Classification: Developer tools Product: valgrind Version: 3.16.0 Platform: RedHat Enterprise Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: toitran4...@gmail.com Target Milestone: --- SUMMARY Could not start binary under valgrind and got the "Unrecognised instruction" error ==7844== Memcheck, a memory error detector ==7844== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==7844== Using Valgrind-3.16.0 and LibVEX; rerun with -h for copyright info ==7844== Command: ./gnb_cu_cp ==7844== Parent PID: 7629 ==7844== vex amd64->IR: unhandled instruction bytes: 0x62 0xF2 0xFD 0x28 0x7C 0xE0 0x48 0x8D 0x90 0x0 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==7844== valgrind: Unrecognised instruction at address 0x7bf277. ==7844==at 0x7BF277: rte_power_ethdev_pmgmt_init (in /home/automation/CUREPO_CP/gNB_CU/build/cucp_bin/bin/gnb_cu_cp) ==7844==by 0x1BE457C: __libc_csu_init (in /home/automation/CUREPO_CP/gNB_CU/build/cucp_bin/bin/gnb_cu_cp) ==7844==by 0xA124C7D: (below main) (in /usr/lib64/libc-2.28.so) ==7844== Your program just tried to execute an instruction that Valgrind ==7844== did not recognise. There are two possible reasons for this. ==7844== 1. Your program has a bug and erroneously jumped to a non-code ==7844==location. If you are running Memcheck and you just saw a ==7844==warning about a bad jump, it's probably your program's fault. ==7844== 2. The instruction is legitimate but Valgrind doesn't handle it, ==7844==i.e. it's Valgrind's fault. If you think this is the case or ==7844==you are not sure, please let us know and we'll try to fix it. ==7844== Either way, Valgrind will now raise a SIGILL signal which will ==7844== probably kill your program. ==7844== ==7844== Process terminating with default action of signal 4 (SIGILL) ==7844== Illegal opcode at address 0x7BF277 ==7844==at 0x7BF277: rte_power_ethdev_pmgmt_init (in /home/automation/CUREPO_CP/gNB_CU/build/cucp_bin/bin/gnb_cu_cp) ==7844==by 0x1BE457C: __libc_csu_init (in /home/automation/CUREPO_CP/gNB_CU/build/cucp_bin/bin/gnb_cu_cp) ==7844==by 0xA124C7D: (below main) (in /usr/lib64/libc-2.28.so) objdump -d gnb_cu_cp |grep "62 f2 fd 28 7c e0" 7bf277: 62 f2 fd 28 7c e0 vpbroadcastq %rax,%ymm4 SOFTWARE/OS VERSIONS Linux/KDE Plasma: rhel 8.6 ADDITIONAL INFORMATION The binary can start successfully without valgrind. I tried to use latest valgrind version 3.21 but facing the same issue -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470491] New: Broken Capitalizing Function in Kate
https://bugs.kde.org/show_bug.cgi?id=470491 Bug ID: 470491 Summary: Broken Capitalizing Function in Kate Classification: Applications Product: kate Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kdelo...@mozej.com Target Milestone: --- SUMMARY *** Capitalizing in Kate is broken in English language. *** STEPS TO REPRODUCE 1. Write the following text in Kate "what you don't do" 2. Highlight the text 3. To capitalize this "text/title" press 'ctrl+alt+u" OBSERVED RESULT 1. This is what is generated: "What You Don'T Do" EXPECTED RESULT 1. This is what should be generated instead: "What You Don't Do" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 X11 -- You are receiving this mail because: You are watching all bug changes.
