[konsole] [Bug 432998] New: Color chooser for each single terminal tab
https://bugs.kde.org/show_bug.cgi?id=432998 Bug ID: 432998 Summary: Color chooser for each single terminal tab Product: konsole Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: norman.k...@tu-dresden.de Target Milestone: --- Often, I use a window with many tabs, one of them being an ssh connection to a server. It would really help if one could rightclick a tab and simply choose a color for the background of that tab so that I immidiately see that I'm as root on some server or something, or that I have allocated slurm ressources in that tab with srun and should not close it. Right now, the way of choosing colors for a tab is really tedious and applies to all tabs as far as I can see. This simple change would really improve functionality of konsole a lot imho. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375540] Seg fault on startup
https://bugs.kde.org/show_bug.cgi?id=375540 --- Comment #2 from Norman --- On Saturday, 28 January 2017 19:10:00 GMT you wrote: > https://bugs.kde.org/show_bug.cgi?id=375540 > > Martin Sandsmark changed: > >What|Removed |Added > > CC||martin.sandsm...@kde.org > > --- Comment #1 from Martin Sandsmark --- > Can you run it in gdb and get a stacktrace? > > https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces gdb run typescript attached -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 348012] Opening files arbitrarily switches to other Activities
https://bugs.kde.org/show_bug.cgi?id=348012 Norman changed: What|Removed |Added CC||e.n.stet...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474522] panel defloats while on top when Discover or System Settings is launched (non-maximized)
https://bugs.kde.org/show_bug.cgi?id=474522 --- Comment #8 from Norman McKeown --- Created attachment 163924 --> https://bugs.kde.org/attachment.cgi?id=163924&action=edit Bug and screen layout -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474522] panel defloats while on top when Discover or System Settings is launched (non-maximized)
https://bugs.kde.org/show_bug.cgi?id=474522 Norman McKeown changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #9 from Norman McKeown --- Sorry for the delay. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474522] panel defloats while on top when Discover or System Settings is launched (non-maximized)
https://bugs.kde.org/show_bug.cgi?id=474522 --- Comment #10 from Norman McKeown --- When I disable my upper monitor the panel floats but now I can drag windows against it and below it and it won't defloat. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474522] panel defloats while on top when Discover or System Settings is launched (non-maximized)
https://bugs.kde.org/show_bug.cgi?id=474522 --- Comment #12 from Norman McKeown --- (In reply to Nate Graham from comment #11) > Can both of you please report whether your panel that is exhibiting this > behavior is on a screen edge that has another screen on the other side of it? In my case, I can confirm that the panel is on a screen edge that has another screen on the other side of it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349088] Down arrow (and other arrows) characters display wrong width
https://bugs.kde.org/show_bug.cgi?id=349088 --- Comment #13 from Norman Diamond --- (In reply to Bug Janitor Service from comment #12) > This bug has been in NEEDSINFO status with no change for at least > 15 days. I thought it was closer to 15 years than 15 days, but actually it's only closer to 9 years. The bug caused trouble for me when I edited source files that had been created by others, with downarrows and uparrows in comments. I no longer edit their source files, so I am no longer affected by the bug. This doesn't mean it WORKSFORME, because I don't find out if it works or not. Three years ago Thomas Landauer found similar manifestations of the bug. If he's still active, perhaps you can ask him if it's fixed or not. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 446602] New: settings crashes when doing customizations
https://bugs.kde.org/show_bug.cgi?id=446602 Bug ID: 446602 Summary: settings crashes when doing customizations Product: kde-cli-tools Version: 5.23.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: smno...@live.com Target Milestone: --- Application: kcmshell5 (5.23.4) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-41-generic x86_64 Windowing System: X11 Distribution: Windowsfx 11 DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was customizing desktop so the windows colors are easier for me to see. Got taskbar done and then went to do the breeze light and the warning came up saying settings crashed and a sad face showed up on taskbar. It did it repeatedly. The crash can be reproduced every time. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault [New LWP 6046] [New LWP 6047] [New LWP 6048] [New LWP 6049] [New LWP 6050] [New LWP 6051] [New LWP 6052] [New LWP 6063] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f420c40faff in __GI___poll (fds=0x7ffd8f0b7c38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f4207ad7980 (LWP 6044))] Thread 9 (Thread 0x7f41d97ce700 (LWP 6063)): #0 __GI___libc_read (nbytes=16, buf=0x7f41d97cd9f0, fd=31) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=31, buf=0x7f41d97cd9f0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f420a919b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f420a8d0ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f420a8d1312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f420a8d14a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f420c9dd61b in QEventDispatcherGlib::processEvents (this=0x7f41bc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f420c9818ab in QEventLoop::exec (this=this@entry=0x7f41d97cdc00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f420c79b2c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f420ba05549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f420c79c45c in QThreadPrivate::start (arg=0x557962cb6790) at thread/qthread_unix.cpp:329 #11 0x7f420b2e2609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f420c41c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f41f2849700 (LWP 6052)): #0 0x7f420a91e4d0 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f420a8d1331 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f420a8d14a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f420c9dd61b in QEventDispatcherGlib::processEvents (this=0x7f41d4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f420c9818ab in QEventLoop::exec (this=this@entry=0x7f41f2848c00, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f420c79b2c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f420ba05549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f420c79c45c in QThreadPrivate::start (arg=0x557961ae9f40) at thread/qthread_unix.cpp:329 #8 0x7f420b2e2609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f420c41c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f41fd6ea700 (LWP 6051)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55796199f698) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55796199f648, cond=0x55796199f670) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55796199f670, mutex=0x55796199f648) at pthread_cond_wait.c:638 #3 0x7f41fe834e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f41fe834a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f420b2e2609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f420c41c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f41fdeeb700 (LWP 6050)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55796199f698) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55796199f648, cond=0x55796199f670) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55796199f
[kwin] [Bug 446606] New: uninstalling software I don,t use causes kwin crash
https://bugs.kde.org/show_bug.cgi?id=446606 Bug ID: 446606 Summary: uninstalling software I don,t use causes kwin crash Product: kwin Version: 5.23.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: smno...@live.com Target Milestone: --- Application: kwin_x11 (5.23.4) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-41-generic x86_64 Windowing System: X11 Distribution: Windowsfx 11 DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was uninstalling kodi and another program I installed called muon manager. Sad face appeared and said kwin crashed report bug error. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [New LWP 34661] [New LWP 34662] [New LWP 34663] [New LWP 34664] [New LWP 34665] [New LWP 34666] [New LWP 34673] [New LWP 34877] [New LWP 46080] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fc97689caff in __GI___poll (fds=0x7ffefd2a0378, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fc970b5c080 (LWP 34655))] Thread 10 (Thread 0x7fc94adee700 (LWP 46080)): #0 0x7fc97689cbf6 in __ppoll (fds=fds@entry=0x7fc91c0115d8, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7fc9776d6519 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc91c0115d8) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc91c0115d8) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=0x7fc91c0115d8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7fc9776d7bc3 in QEventDispatcherUNIX::processEvents (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7fc97767e8ab in QEventLoop::exec (this=this@entry=0x7fc94adedbc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7fc9774982c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7fc975542549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fc97749945c in QThreadPrivate::start (arg=0x564f1aa8a900) at thread/qthread_unix.cpp:329 #10 0x7fc974f01609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fc9768a9293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fc960845700 (LWP 34877)): #0 0x7fc97689cbf6 in __ppoll (fds=fds@entry=0x7fc93d78, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7fc9776d6519 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc93d78) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc93d78) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=0x7fc93d78, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7fc9776d7bc3 in QEventDispatcherUNIX::processEvents (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7fc97767e8ab in QEventLoop::exec (this=this@entry=0x7fc960844bc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7fc9774982c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7fc975542549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fc97749945c in QThreadPrivate::start (arg=0x564f1a4369d0) at thread/qthread_unix.cpp:329 #10 0x7fc974f01609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fc9768a9293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fc94a475700 (LWP 34673)): #0 0x7fc97689cbf6 in __ppoll (fds=fds@entry=0x7fc93c000d78, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7fc9776d6519 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc93c000d78) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc93c000d78) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=0x7fc93c000d78, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7fc9776d7bc3 in QEventDispatcherUNIX::processEvents (this=, flags=...) at ../../include/QtC
[frameworks-kio] [Bug 444786] New: upgrading to kde-frameworks to 5.85.0 or 5.8.7.0 from 5.82.0 results in a 20 sec freeze when changing folders in dolphin and kate
https://bugs.kde.org/show_bug.cgi?id=444786 Bug ID: 444786 Summary: upgrading to kde-frameworks to 5.85.0 or 5.8.7.0 from 5.82.0 results in a 20 sec freeze when changing folders in dolphin and kate Product: frameworks-kio Version: 5.85.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: k...@thebacks.co.uk CC: kdelibs-b...@kde.org Target Milestone: --- I made a guess when I selected frameworks-kio as the offending product. Please correct if wrong. SUMMARY kde-frameworks-5.82.0 allows changing folders within dolphin and kate, without any freeze. Using kde-frameworks-5.85.0 and kde-frameworks-5.87.0 results in a 20 sec freeze when changing folders within dolphin and kate. STEPS TO REPRODUCE 1. Install kde-frameworks to 5.85.0 or 5.8.7.0 2. Start dolphin OBSERVED RESULT 1. switch selection between two folder containing a large number of files/folders 2. observe the freeze ( 20 secs on my box ) before dolphin is responsive again. EXPECTED RESULT 1. switch selection between two folder containing a large number of files/folders 2. no freeze occurs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux-5.14.15-gentoo-x86_64-AMD_Ryzen_9_3900X_12-Core_Processor-with-glibc2.33 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 or 5.8.7.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION First reported with at https://bugs.gentoo.org/show_bug.cgi?id=821103 The folders tested were the Documents and Downloads folder in the $HOME directory, formatted with ext4. During the 20 second freeze, high IO ( > 50% ) can be observed on many hard drives via atop. Interestingly typing blkid in konsole takes about 14 secs to return. I upgrade kde to the latest stable release on 13th Sept 2021. Everything seemed to work OK at first but I later found that when I use dolphin or kate the application freezes for 20 secs when changing to a different folder. I downgraded the whole of kde to the release in use prior to the 13th Sept 2021 and the issue disappeared, confirming that the problem was in the latest stable release of kde. After some thought I upgraded all but kde-frameworks to the latest stable release of kde leaving kde-frameworks at 5.82.0. There was no 20 sec freeze. Wondering if the unstable kde-frameworks 5.87.0 might also be OK I upgraded to that but the freeze returned. I also noted that when starting dolphin from the command line with kde-frameworks-5.85.0 a large number of errors were reported on the console. However kde-frameworks-5.87.0 did not manifest this so is not relevant to this issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444786] upgrading to kde-frameworks to 5.85.0 or 5.8.7.0 from 5.82.0 results in a 20 sec freeze when changing folders in dolphin and kate
https://bugs.kde.org/show_bug.cgi?id=444786 --- Comment #1 from Norman Back --- Might be related to https://bugs.kde.org/show_bug.cgi?id=442684 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444786] upgrading to kde-frameworks to 5.85.0 or 5.8.7.0 from 5.82.0 results in a 20 sec freeze when changing folders in dolphin and kate
https://bugs.kde.org/show_bug.cgi?id=444786 --- Comment #2 from Norman Back --- dolphin and kate are at version 21.04.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444786] upgrading to kde-frameworks to 5.85.0 or 5.8.7.0 from 5.82.0 results in a 20 sec freeze when changing folders in dolphin and kate
https://bugs.kde.org/show_bug.cgi?id=444786 --- Comment #3 from Norman Back --- I've realised that vivaldi is also affected. When selecting a folder to download a file it was taking about 20 secs to switch folders but vivaldi itself did not freeze. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444786] upgrading to kde-frameworks to 5.85.0 or 5.8.7.0 from 5.82.0 results in a 20 sec freeze when changing folders in dolphin and kate
https://bugs.kde.org/show_bug.cgi?id=444786 --- Comment #5 from Norman Back --- I have applied the patch at https://invent.kde.org/frameworks/kio/-/commit/221a94a66c4d2f6e4f2dc938ee8a63a6ca739477 to kde-frameworks 5.85 and 5.87 and can report the issue is resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474522] panel defloats while on top when Discover or System Settings is launched (non-maximized)
https://bugs.kde.org/show_bug.cgi?id=474522 Norman McKeown changed: What|Removed |Added CC||normanmcke...@duck.com --- Comment #3 from Norman McKeown --- Created attachment 163135 --> https://bugs.kde.org/attachment.cgi?id=163135&action=edit plasma6 video Occurs on plasma 6. For me any window being open on the screen causes the panel to defloat. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472152] With external screen extended to left, right-aligned panel widgets on main screen inappropriately appear on the sift side of that screen
https://bugs.kde.org/show_bug.cgi?id=472152 Norman McKeown changed: What|Removed |Added CC||normanmcke...@duck.com --- Comment #1 from Norman McKeown --- Created attachment 163137 --> https://bugs.kde.org/attachment.cgi?id=163137&action=edit plasma6 video Occurs on plasma 6. My screens are stacked and permanently attached with the primary being the bottom. Plasma 5 does not have this issue for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472221] New: Wrong Counting of hard driva
https://bugs.kde.org/show_bug.cgi?id=472221 Bug ID: 472221 Summary: Wrong Counting of hard driva Classification: Applications Product: dolphin Version: 22.04.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: conny.nor...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 160266 --> https://bugs.kde.org/attachment.cgi?id=160266&action=edit Dolphin counts wrong SUMMARY Wrong size of counting Mb of HD, see picture -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422417] New: WARNING: unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=422417 Bug ID: 422417 Summary: WARNING: unhandled amd64-linux syscall: 315 Product: valgrind Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: norm...@telus.net Target Milestone: --- SUMMARY Running a QT GUI application, get the message: --24339-- WARNING: unhandled amd64-linux syscall: 315 --24339-- You may be able to write your own handler. --24339-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --24339-- Nevertheless we consider this a bug. Please report --24339-- it at http://valgrind.org/support/bug_reports.html. STEPS TO REPRODUCE 1. Run the QT application (sorry, have not written a minimal application) 2. 3. OBSERVED RESULT The above message EXPECTED RESULT No such message SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux Fedora 32 x86-54 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version:5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422417] WARNING: unhandled amd64-linux syscall: 315
https://bugs.kde.org/show_bug.cgi?id=422417 --- Comment #1 from Norman Goldstein --- Forgot to mention the valgrind version: ==24339== Memcheck, a memory error detector ==24339== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==24339== Using Valgrind-3.16.0 and LibVEX; rerun with -h for copyright info -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375540] New: Seg fault on startup
https://bugs.kde.org/show_bug.cgi?id=375540 Bug ID: 375540 Summary: Seg fault on startup Product: konsole Version: 16.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: k...@thehulls.biz Target Milestone: --- Following system update (pacman -Suy) konsole is now version 16.12.1 Will not run, instead gives a seg fault on startup every time. Tried rebooting just in case - although I didn't expect this to fix it. It didn't Had to install yakuake as a temporary measure, this gave me information not included when run from plasma directly: KCrash: Application 'konsole' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [7fdc80001028] filesystem access error: read error: Bad file descriptor [7fdc80001028] core access error: File reading failed [7fdc80001028] core access error: VLC could not read the file (Bad file descriptor). Unable to start Dr. Konqi Re-raising signal for core dump handling. zsh: segmentation fault (core dumped) konsole -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375540] Seg fault on startup
https://bugs.kde.org/show_bug.cgi?id=375540 --- Comment #5 from Norman Hull --- Created attachment 103770 --> https://bugs.kde.org/attachment.cgi?id=103770&action=edit Shortcut dialog ~/.local/share/kxmlgui5/konsole is empty The reference to shortcuts is interesting. For some time KDE had been pretending that it didn't recognise shortcuts until I went into the shortcuts setting dialog and reset them manually. Since the last update, whenever a KDE application starts it gives a series of annoying error messages that each shortcut is assigned to two actions - each the same (see screenshot). Thanks to the help received here I have told KD to reset shortcuts to the default and konsole starts up without problems. Thank you - now I just have to add in the keystrokes to control my extra desktops! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349088] Down arrow (and other arrows) characters display wrong width
https://bugs.kde.org/show_bug.cgi?id=349088 --- Comment #3 from Norman Diamond --- Created attachment 104106 --> https://bugs.kde.org/attachment.cgi?id=104106&action=edit Screenshot Screenshot -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349088] Down arrow (and other arrows) characters display wrong width
https://bugs.kde.org/show_bug.cgi?id=349088 --- Comment #4 from Norman Diamond --- The problem was consistent in a different installation of OpenSuse 13.2, but the problem is inconsistent in my present installation of the same OS. The screenshot is from my present installation, showing the inconsistency. As shown in the "vi" session, when the cursor is in the middle of a line containing arrow characters, something is greatly confused and the display is completely scrambled. This still makes editing just about impossible. But for unknown reasons, in my present installation, the output of cat displays the arrow characters properly in full-width. In my earlier installation, arrow characters were all displayed as half-width both in vi and the output of cat. This still made editing impossible. In my earlier installation, a Japanese person recommended changing the Konsole setting for fixed-width font. Some fonts displayed arrow characters as full-width and solved the problem consistently. In my present installation, I think I haven't tried such an experiment yet, but I don't know what produced the inconsistency. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349088] Down arrow (and other arrows) characters display wrong width
https://bugs.kde.org/show_bug.cgi?id=349088 Norman Diamond changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #5 from Norman Diamond --- Changing status from Needsinfo back to Unconfirmed. If you disagree, please let me know. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349088] Down arrow (and other arrows) characters display wrong width
https://bugs.kde.org/show_bug.cgi?id=349088 --- Comment #8 from Norman Diamond --- "The down arrow U+2193 is indeed of "ambiguous width" both in Unicode 8.0 and 9.0." Then it's not entirely Konsole's fault, but we still need a workaround for the Unicode consortium's bug. The present behaviour sometimes makes Konsole unusable, just like (retired C language lawyer speaks up now) a C compiler that only compiled one single valid C program would be legal but unusable. How did the Unicode consortium figure out that half-width a, full-width ａ, lower-case a, upper-case A, upper-case Ａ, etc., shouldn't all have ambiguous width, ambiguous casing, etc. But just allowing Konsole to be unfriendly doesn't force Konsole to be unfriendly. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 503908] Credential window closes itself when attempting to add DAV groupware resource calendar source
https://bugs.kde.org/show_bug.cgi?id=503908 Norman Rieß changed: What|Removed |Added CC||nor...@smash-net.org --- Comment #4 from Norman Rieß --- Also same issue. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.1 Kernel Version: 6.15.6 Graphics Platform: Wayland Processors: AMD Ryzen 7 7840HS Memory: 54 GiB of RAM Graphics Processor: Radeon 780M -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388619] New: Wish: Button to download unknown PGP keys from Key Server
https://bugs.kde.org/show_bug.cgi?id=388619 Bug ID: 388619 Summary: Wish: Button to download unknown PGP keys from Key Server Product: kmail2 Version: 5.2.3 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: ko...@gmx.net Target Milestone: --- If I don't have a key of a recipient, Kmail informs me about it but gives me not possibility to changes this. It would be nice if a Button "Download Missing Keys from Server" would be included like its the case in Enigmail and Thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381382] New: Background change (image) in settings not saved when modified
https://bugs.kde.org/show_bug.cgi?id=381382 Bug ID: 381382 Summary: Background change (image) in settings not saved when modified Product: systemsettings Version: 5.10.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: brian...@gmail.com Target Milestone: --- Created attachment 106161 --> https://bugs.kde.org/attachment.cgi?id=106161&action=edit Login screen with white background 1. Overview: When you change the background of the SDDM configuration and save the changes, it does not do it correctly. When the login screen is displayed, it is now blank background (attached file). 2. Steps to Reproduce: 1) In system setup, boot and shutdown, SDDM, select the theme to modify and change the background for an image. 2) Restart the system or test it medainte console, and a blank background screen occurs. 3. Actual Results: Login screen with white background 4. Expected Results: Login screen with background image changed. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 363007] New: Konqueror Crash on opening e-mail from Web.de
https://bugs.kde.org/show_bug.cgi?id=363007 Bug ID: 363007 Summary: Konqueror Crash on opening e-mail from Web.de Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: normankl...@gmail.com Application: konqueror (4.14.18) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Opening e-mail by Konqueror on web.de. That e-mail did not contain any links or attached files. This bug seems to be intermittent. The crash can be reproduced sometimes. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe386cda780 (LWP 8113))] Thread 9 (Thread 0x7fe36d614700 (LWP 8115)): #0 0x7fe384326bbd in poll () at /lib64/libc.so.6 #1 0x7fe381436e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe381436f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe385974fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7fe385946d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7fe385947045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fe3858444df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7fe385928653 in () at /usr/lib64/libQtCore.so.4 #8 0x7fe385846bbf in () at /usr/lib64/libQtCore.so.4 #9 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fe367fff700 (LWP 8124)): #0 0x7fe3855b6a7d in read () at /lib64/libpthread.so.0 #1 0x7fe381477b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe381436999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe381436df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe381436f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe385974fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fe385946d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7fe385947045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7fe3858444df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7fe37b168e7e in () at /usr/lib64/libkio.so.5 #10 0x7fe385846bbf in () at /usr/lib64/libQtCore.so.4 #11 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fe35d4a8700 (LWP 8128)): #0 0x7fe3855b403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe366516eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7fe366516ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fe35cca7700 (LWP 8129)): #0 0x7fe3855b6a7d in read () at /lib64/libpthread.so.0 #1 0x7fe381477b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe381436999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe381436df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe381436f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe385974fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fe385946d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7fe385947045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7fe3858444df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7fe385846bbf in () at /usr/lib64/libQtCore.so.4 #10 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fe317dce700 (LWP 8130)): #0 0x7fe3855b403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe366289b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7fe36653ea06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fe306e9b700 (LWP 8143)): #0 0x7fe3855b403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe301da0d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7fe301da1819 in () at /usr/lib64/java-1_8_0-op
