[Powerdevil] [Bug 460230] New: “Power management module could not be loaded”
https://bugs.kde.org/show_bug.cgi?id=460230 Bug ID: 460230 Summary: “Power management module could not be loaded” Classification: Plasma Product: Powerdevil Version: 5.25.5 Platform: PCLinuxOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ajlamb1...@gmail.com CC: m...@ratijas.tk Target Milestone: --- Created attachment 152696 --> https://bugs.kde.org/attachment.cgi?id=152696&action=edit Pictures 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Power management module fails to start. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482609] New: Graphical Bug using Line Chart in System Monitor
https://bugs.kde.org/show_bug.cgi?id=482609 Bug ID: 482609 Summary: Graphical Bug using Line Chart in System Monitor Classification: Applications Product: plasma-systemmonitor Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: averyp...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY The system monitor application has a graphical bug where if any line chart has two or more sensors horizontal lines will form on the y-axis lines. The glitched lines will use the colors applied to the sensors in the line chart. I have restarted the application and my system, as well as checked for updates, and this problem remains. STEPS TO REPRODUCE 1. Open System Monitor 2. Create a new sensor with the Line Chart mode. 3. Add CPU core usage sensors individually (red for core 1, orange for core 2, etc). There must be at least two. 4. Save changes. OBSERVED RESULT I used a Line Chart graph with 8 cores and a graphical bug resulted in perfectly horizontal lines being drawn above and around the sensors data within the graph itself. The lines are spliced up and spread out and lie perfectly on-top of the y-axis lines. And they do not extend past the boundaries of the graph. Enabling or Disabling any of the check-boxes only changes the entire graph equally including both the actual data points and the graphical glitches. In other words, despite the settings, the bug and the actual data seem almost in fixed point to each other. This bug was not limited to CPU cores but this displayed it the greatest in my opinion. EXPECTED RESULT The Line Chart should behave as normal, displaying all 8 of my CPU core sensors. Each one should be given a specific color. and should not overlap with one-another. OPERATING SYSTEM Arch Linux SOFTWARE KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 HARDWARE Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz (4 core with hyper-threading enabled) Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: HP Product Name: HP Laptop 14-dq2xxx -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482609] Graphical Mess using Line Chart in System Monitor
https://bugs.kde.org/show_bug.cgi?id=482609 Joseph changed: What|Removed |Added Summary|Graphical Bug using Line|Graphical Mess using Line |Chart in System Monitor |Chart in System Monitor -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482609] Graphical Mess using Line Chart in System Monitor
https://bugs.kde.org/show_bug.cgi?id=482609 --- Comment #1 from Joseph --- Created attachment 166521 --> https://bugs.kde.org/attachment.cgi?id=166521&action=edit Screencap of 8 core line chart glitching out. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482609] Graphical Mess using Line Chart in System Monitor
https://bugs.kde.org/show_bug.cgi?id=482609 --- Comment #2 from Joseph --- Created attachment 166522 --> https://bugs.kde.org/attachment.cgi?id=166522&action=edit Closeup Higher Quality Screencap of 8 core chart -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439472] Latte dock crashes when attempting to add widgets
https://bugs.kde.org/show_bug.cgi?id=439472 --- Comment #2 from Joseph --- No, this is not happening any more after upgrading to latest versions. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377966] disInstr(arm64): unhandled instruction 0xD50B7425 (dc zva,)
https://bugs.kde.org/show_bug.cgi?id=377966 Joseph changed: What|Removed |Added CC||jga...@hmc.edu --- Comment #7 from Joseph --- Warning: set address range perms: large range -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377966] Error message said to report
https://bugs.kde.org/show_bug.cgi?id=377966 Joseph changed: What|Removed |Added Summary|disInstr(arm64): unhandled |Error message said to |instruction 0xD50B7425 (dc |report |zva,) | --- Comment #8 from Joseph --- valgrind ./test_nng ==66046== Memcheck, a memory error detector ==66046== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==66046== Using Valgrind-3.18.0.GIT-lbmacos and LibVEX; rerun with -h for copyright info ==66046== Command: ./test_nng ==66046== ==66046== Warning: set address range perms: large range [0x7fff20187000, 0x80001ff87000) (defined) ==66046== Warning: set address range perms: large range [0x7fff2045b000, 0x7fff7fe4f000) (defined) ==66046== Warning: set address range perms: large range [0x7fff8e3db000, 0x7fffc0187000) (noaccess) ==66046== Warning: set address range perms: large range [0x7fffc0187000, 0x7fffe2fa7000) (defined) ==66046== Warning: set address range perms: large range [0x7fffe2fa7000, 0x7fe0) (noaccess) --66046-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option --66046-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times) --66046-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times) --66046-- WARNING: unhandled amd64-darwin syscall: unix:228 --66046-- You may be able to write your own handler. --66046-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --66046-- Nevertheless we consider this a bug. Please report --66046-- it at http://valgrind.org/support/bug_reports.html. --66046-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8 times) past compress chan tests before decode read bytes vex amd64->IR: unhandled instruction bytes: 0x62 0xD3 0x45 0x8 0x1E 0xC8 0x6 0x62 0xD3 0x6D 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 ==66046== valgrind: Unrecognised instruction at address 0x10001ca6b. ==66046==at 0x10001CA6B: HuffmanTree_makeFromLengths2 (lodepng.c:1034) ==66046==by 0x15805: lodepng_inflatev (lodepng.c:1216) ==66046==by 0x195A3: lodepng_zlib_decompressv (lodepng.c:1927) ==66046==by 0x100012C94: lodepng_decode (lodepng.c:2878) ==66046==by 0x100017C4E: decode_wrapper (lodepng.c:7565) ==66046==by 0x100033381: test_nng_helper (test_nng_helper.c:37) ==66046==by 0x1252A: main (test.c:14) ==66046== Your program just tried to execute an instruction that Valgrind ==66046== did not recognise. There are two possible reasons for this. ==66046== 1. Your program has a bug and erroneously jumped to a non-code ==66046==location. If you are running Memcheck and you just saw a ==66046==warning about a bad jump, it's probably your program's fault. ==66046== 2. The instruction is legitimate but Valgrind doesn't handle it, ==66046==i.e. it's Valgrind's fault. If you think this is the case or ==66046==you are not sure, please let us know and we'll try to fix it. ==66046== Either way, Valgrind will now raise a SIGILL signal which will ==66046== probably kill your program. ==66046== ==66046== Process terminating with default action of signal 4 (SIGILL) ==66046== Illegal opcode at address 0x10001CA6B ==66046==at 0x10001CA6B: HuffmanTree_makeFromLengths2 (lodepng.c:1034) ==66046==by 0x15805: lodepng_inflatev (lodepng.c:1216) ==66046==by 0x195A3: lodepng_zlib_decompressv (lodepng.c:1927) ==66046==by 0x100012C94: lodepng_decode (lodepng.c:2878) ==66046==by 0x100017C4E: decode_wrapper (lodepng.c:7565) ==66046==by 0x100033381: test_nng_helper (test_nng_helper.c:37) ==66046==by 0x1252A: main (test.c:14) ==66046== ==66046== HEAP SUMMARY: ==66046== in use at exit: 0 bytes in 0 blocks ==66046== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==66046== ==66046== All heap blocks were freed -- no leaks are possible ==66046== ==66046== For lists of detected and suppressed errors, rerun with: -s ==66046== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) [1]66046 illegal hardware instruction valgrind ./test_nng -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 439472] New: Latte dock crashes when attempting to add widgets
https://bugs.kde.org/show_bug.cgi?id=439472 Bug ID: 439472 Summary: Latte dock crashes when attempting to add widgets Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dencil...@gmail.com Target Milestone: --- Application: latte-dock (0.10.75) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.14-zen1-1-zen x86_64 Windowing System: X11 Drkonqi Version: 5.22.2 Distribution: Garuda Linux -- Information about the crash: - What I was doing when the application crashed: Latte dock crashes each time when attempting to add widgets using the Add Widget option on Dragonized KDE Garuda Linux. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7fd6306e0840 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7fd630711b1c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7fd6306f83fa in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7fd6306fdd36 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7fd6306fe585 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7fd6306e5602 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7fd6306e5af4 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #11 0x7fd63074bdd3 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #12 0x7fd6307bbd81 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #13 0x7fd63075aa67 in () at /usr/lib/libQt5Quick.so.5 #14 0x7fd63075b447 in () at /usr/lib/libQt5Quick.so.5 #15 0x7fd62e66bfef in () at /usr/lib/libQt5Core.so.5 #16 0x7fd62d923259 in start_thread () at /usr/lib/libpthread.so.0 #17 0x7fd62e1745e3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fd5cdb39640 (LWP 216876) "latte-do:gdrv0"): #1 0x7fd62d929270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7fd61778559c in () at /usr/lib/dri/iris_dri.so #3 0x7fd61777f5f8 in () at /usr/lib/dri/iris_dri.so #4 0x7fd62d923259 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fd62e1745e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fd5cee5d640 (LWP 216875) "QSGRenderThread"): #1 0x7fd62d929270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7fd62e67207c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fd630758f37 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd63075b48b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fd62e66bfef in () at /usr/lib/libQt5Core.so.5 #6 0x7fd62d923259 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fd62e1745e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fd5cf6fe640 (LWP 216874) "latte-do:gdrv0"): #1 0x7fd62d929270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7fd61778559c in () at /usr/lib/dri/iris_dri.so #3 0x7fd61777f5f8 in () at /usr/lib/dri/iris_dri.so #4 0x7fd62d923259 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fd62e1745e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fd5c640 (LWP 216873) "KCupsConnection"): #1 0x7fd62cb44b29 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd62caee871 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd62e8b004f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd62e855d1c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd62e66ae12 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd5e845529b in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fd62e66bfef in () at /usr/lib/libQt5Core.so.5 #8 0x7fd62d923259 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd62e1745e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fd5e8e31640 (LWP 216459) "latte-dock"): #1 0x7fd62a12b524 in () at /usr/lib/libusbmuxd-2.0.so.6 #2 0x7fd62a12c8a9 in () at /usr/lib/libusbmuxd-2.0.so.6 #3 0x7fd62d923259 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd62e1745e3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fd5f4b7f640 (LWP 215571) "QQmlThread"): #1 0x7fd62cb44b29 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd62caee871 in g_main_context_iteration () at /usr/lib/libglib-2
[valgrind] [Bug 424034] New: valgrind (memcheck) causes some programs to fail with SIGILL that do not normally fail
https://bugs.kde.org/show_bug.cgi?id=424034 Bug ID: 424034 Summary: valgrind (memcheck) causes some programs to fail with SIGILL that do not normally fail Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: joseph.jenn...@gmail.com Target Milestone: --- SUMMARY valgrind causes some commands run under it to fail with SIGILL that normally succeed. STEPS TO REPRODUCE 1. Compile python3.10 from the git repo (heads/master:48289b6096) 2. Run `valgrind python3.10 -m json.tool` with an input JSON file provided from stdin and output to `/dev/null` 3. Run the same command without valgrind and observe that it does not fail OBSERVED RESULT usera@kali ~ % valgrind python3.10 -m json.tool < Documents/dump.json > /dev/null ==712008== Memcheck, a memory error detector ==712008== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==712008== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==712008== Command: python3.10 -m json.tool ==712008== vex amd64->IR: unhandled instruction bytes: 0x8F 0xE9 0xF8 0x9B 0x5 0x5B 0x61 0xC 0x0 0xB8 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 ==712008== valgrind: Unrecognised instruction at address 0x6316ac. ==712008==at 0x6316AC: UnknownInlinedFun (getpath.c:0) ==712008==by 0x6316AC: UnknownInlinedFun (getpath.c:1522) ==712008==by 0x6316AC: UnknownInlinedFun (getpath.c:1605) ==712008==by 0x6316AC: UnknownInlinedFun (pathconfig.c:318) ==712008==by 0x6316AC: UnknownInlinedFun (pathconfig.c:336) ==712008==by 0x6316AC: UnknownInlinedFun (pathconfig.c:403) ==712008==by 0x6316AC: config_read (initconfig.c:1752) ==712008==by 0x6316AC: PyConfig_Read (initconfig.c:2536) ==712008==by 0x63FE7E: pyinit_core (pylifecycle.c:928) ==712008==by 0x63FE7E: Py_InitializeFromConfig (pylifecycle.c:1144) ==712008==by 0x420F6D: pymain_init (main.c:66) ==712008==by 0x420D20: pymain_main (main.c:694) ==712008==by 0x41F5FB: UnknownInlinedFun (main.c:727) ==712008==by 0x41F5FB: main (python.c:15) ==712008== Your program just tried to execute an instruction that Valgrind ==712008== did not recognise. There are two possible reasons for this. ==712008== 1. Your program has a bug and erroneously jumped to a non-code ==712008==location. If you are running Memcheck and you just saw a ==712008==warning about a bad jump, it's probably your program's fault. ==712008== 2. The instruction is legitimate but Valgrind doesn't handle it, ==712008==i.e. it's Valgrind's fault. If you think this is the case or ==712008==you are not sure, please let us know and we'll try to fix it. ==712008== Either way, Valgrind will now raise a SIGILL signal which will ==712008== probably kill your program. ==712008== ==712008== Process terminating with default action of signal 4 (SIGILL) ==712008== Illegal opcode at address 0x6316AC ==712008==at 0x6316AC: UnknownInlinedFun (getpath.c:0) ==712008==by 0x6316AC: UnknownInlinedFun (getpath.c:1522) ==712008==by 0x6316AC: UnknownInlinedFun (getpath.c:1605) ==712008==by 0x6316AC: UnknownInlinedFun (pathconfig.c:318) ==712008==by 0x6316AC: UnknownInlinedFun (pathconfig.c:336) ==712008==by 0x6316AC: UnknownInlinedFun (pathconfig.c:403) ==712008==by 0x6316AC: config_read (initconfig.c:1752) ==712008==by 0x6316AC: PyConfig_Read (initconfig.c:2536) ==712008==by 0x63FE7E: pyinit_core (pylifecycle.c:928) ==712008==by 0x63FE7E: Py_InitializeFromConfig (pylifecycle.c:1144) ==712008==by 0x420F6D: pymain_init (main.c:66) ==712008==by 0x420D20: pymain_main (main.c:694) ==712008==by 0x41F5FB: UnknownInlinedFun (main.c:727) ==712008==by 0x41F5FB: main (python.c:15) ==712008== ==712008== HEAP SUMMARY: ==712008== in use at exit: 1,548 bytes in 31 blocks ==712008== total heap usage: 109 allocs, 78 frees, 16,207 bytes allocated ==712008== ==712008== LEAK SUMMARY: ==712008==definitely lost: 188 bytes in 2 blocks ==712008==indirectly lost: 0 bytes in 0 blocks ==712008== possibly lost: 0 bytes in 0 blocks ==712008==still reachable: 1,360 bytes in 29 blocks ==712008== suppressed: 0 bytes in 0 blocks ==712008== Rerun with --leak-check=full to see details of leaked memory ==712008== ==712008== For lists of detected and suppressed errors, rerun with: -s ==712008== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) [1]712008 illegal hardware instruction valgrind python3.10 -m json.tool < Documents/dump.json > /dev/null 132 usera@kali ~ % python3.10 -m json.tool < Documents/dump.json > /dev/null usera@kali ~ % EXPECTED RESULT SOFTWARE/OS V
[valgrind] [Bug 424034] amd64->IR: unhandled instruction bytes: 0x8F 0xE9 0xF8 0x9B 0x5 0x5B 0x61 0xC 0x0 0xB8
https://bugs.kde.org/show_bug.cgi?id=424034 --- Comment #2 from Joseph --- (In reply to Paul Floyd from comment #1) > Can you say what model of CPU this is with? (model name and flags from > /proc/cpuinfo) model name : AMD A9-9425 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 424034] amd64->IR: unhandled instruction bytes: 0x8F 0xE9 0xF8 0x9B 0x5 0x5B 0x61 0xC 0x0 0xB8
https://bugs.kde.org/show_bug.cgi?id=424034 --- Comment #4 from Joseph --- (In reply to Tom Hughes from comment #3) > I'm pretty sure that's one of the AMD specific instructions that we don't > support. Is there a list of those instructions in the docs somewhere? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 426345] New: Konqueror has a rave with jnlp
https://bugs.kde.org/show_bug.cgi?id=426345 Bug ID: 426345 Summary: Konqueror has a rave with jnlp Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: xylonki...@gmail.com Target Milestone: --- Created attachment 131517 --> https://bugs.kde.org/attachment.cgi?id=131517&action=edit a jnlp with credentials removed SUMMARY Opening a .jnlp causes konqueror to rave out with all the buttons flashing. STEPS TO REPRODUCE 1. Open the attached file in konqueror OBSERVED RESULT Buttons strobing and high CPU usage perpetually EXPECTED RESULT I don't normally expect a program to have a rave when I open a file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubunto 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION This made my day! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491685] Inconsistent App Launcher behaviour when using floating panel and not using it
https://bugs.kde.org/show_bug.cgi?id=491685 --- Comment #2 from Joseph --- Created attachment 172641 --> https://bugs.kde.org/attachment.cgi?id=172641&action=edit Floating panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491685] Inconsistent App Launcher behaviour when using floating panel and not using it
https://bugs.kde.org/show_bug.cgi?id=491685 --- Comment #3 from Joseph --- Created attachment 172642 --> https://bugs.kde.org/attachment.cgi?id=172642&action=edit Floating panel with a fullscreen app -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491685] Inconsistent App Launcher behaviour when using floating panel and not using it
https://bugs.kde.org/show_bug.cgi?id=491685 --- Comment #4 from Joseph --- Created attachment 172643 --> https://bugs.kde.org/attachment.cgi?id=172643&action=edit Non-floating panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491685] Inconsistent App Launcher behaviour when using floating panel and not using it
https://bugs.kde.org/show_bug.cgi?id=491685 --- Comment #5 from Joseph --- (In reply to Nate Graham from comment #1) > I think this might be intentional, but can you attach a screenshot of the > issue so I can be sure? Pictures added. I believe the bug is the launcher icon padding discrepancy between floating fullscreen and not floating. As you can see, the fullscreen floating panel has way more padding from the left side. I also included a floating non-fullscreen screenshot, which behaves correctly in my opinion (Same as the not floating panel). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491685] Inconsistent App Launcher behaviour when using floating panel and not using it
https://bugs.kde.org/show_bug.cgi?id=491685 Joseph changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491685] New: Inconsistent App Launcher behaviour when using floating panel and not using it
https://bugs.kde.org/show_bug.cgi?id=491685 Bug ID: 491685 Summary: Inconsistent App Launcher behaviour when using floating panel and not using it Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: happypepi...@gmail.com Target Milestone: --- SUMMARY The Application Launcher (start menu) icon is weirdly padded from the left side when using the floating panel and a fullscreen app. When not using a floating panel, the icon is centered with no issues. The appearance of the "squashed" panel and the completely non-floating panel should in my opinion be consistent. STEPS TO REPRODUCE 1. Default KDE 6 settings 2. Maximize any application OBSERVED RESULT Application Launcher icon is padded from the left side as opposed to the non-floating panel. EXPECTED RESULT Launcher icon should have the same padding as disabling floating panel. (No padding) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 414534] New: Desk effects affect app launching
https://bugs.kde.org/show_bug.cgi?id=414534 Bug ID: 414534 Summary: Desk effects affect app launching Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: axel...@gmail.com Target Milestone: --- SUMMARY I'm on EndeavourOS, I uninstalled xfce to install KDE, and since then, when I launch an app, it only shows a black windows or nothing at all. Actually to display correctly the window of an app, I have to disable the desk effects and re-enable them and it displays correctly, but sometimes, it doesn't work and my apps window stay invisible or black STEPS TO REPRODUCE 1. Install EndeavourOS 2. Uninstall xfce and install KDE 3. Launch a session with KDE enabled 4. Try to launch an app OBSERVED RESULT All the launched apps windows are invisible or black and you have to disable desk effect to display them correctly EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 390869] org_kde_powerde using sound devices after suspend - no sound
https://bugs.kde.org/show_bug.cgi?id=390869 Joseph changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 390869] New: org_kde_powerde using sound devices after suspend - no sound
https://bugs.kde.org/show_bug.cgi?id=390869 Bug ID: 390869 Summary: org_kde_powerde using sound devices after suspend - no sound Product: Powerdevil Version: 5.12.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joseph.nguyen2...@gmail.com Target Milestone: --- Sometimes when I resume from suspend, videos do not play and audio does not work because org_kde_powerde is using my sound device(s). I discovered this by running 'fuser -v /dev/snd/*'. After I kill org_kde_powerde, videos play and sound works but power management icon in system tray is gone. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 390869] org_kde_powerde using sound devices after suspend - no sound
https://bugs.kde.org/show_bug.cgi?id=390869 --- Comment #1 from Joseph --- Created attachment 110906 --> https://bugs.kde.org/attachment.cgi?id=110906&action=edit fuser output when sound does not work -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 390869] org_kde_powerde using sound devices after suspend - no sound
https://bugs.kde.org/show_bug.cgi?id=390869 --- Comment #2 from Joseph --- temporary workaround: kill org_kde_powerde and restart by running /usr/lib/org_kde_powerdevil -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389111] New: black screen flickering using OpenGL
https://bugs.kde.org/show_bug.cgi?id=389111 Bug ID: 389111 Summary: black screen flickering using OpenGL Product: kwin Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: glx Assignee: kwin-bugs-n...@kde.org Reporter: josephjamesc...@gmail.com Target Milestone: --- Using Arch Linux (4.14.13-1-ARCH) as well as the nvidia drivers from 'extra' repository (I am currently using a GTX 1070 for a GPU), the screen occasionally flickers with black flickering artifacts. Upon opening a subwindow, the flickering increases dramatically, and covers the whole screen save for the opened window. This can be temporarily solved by dragging the window around the screen, upon which the black flickering areas will disappear if the window crosses it. To reproduce, set your Rendering backend to OpenGL 2.0, or OpenGL 3.1 Setting to XRender eliminates the problem. Here is the output of 'qdbus org.kde.KWin /KWin supportInformation': == Version === KWin version: 5.11.5 Qt Version: 5.10.0 Qt compile version: 5.10.0 XCB compile version: 1.12 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11906000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 2 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 0 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: DVI-D-0 Geometry: 0,0,1920x1080 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: XRender Loaded Effects: --- zoom kwin4_effect_translucency kwin4_effect_morphingpopups kwin4_effect_dialogparent kwin4_effect_fade kwin4_effect_logout kwin4_effect_windowaperture kwin4_effect_maximize kwin4_effect_login kwin4_effect_frozenapp slidingpopups slide screenshot minimizeanimation desktopgrid presentwindows highlightwindow screenedge kscreen Currently Active Effects: - Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_translucency: kwin4_effect_morphingpopups: kwin4_effect_dialogparent: kwin4_effect_fade: kwin4_effect_logout: kwin4_effect_windowaperture: kwin4_effect_maximize: kwin4_effect_login: kwin4_effect_froze
[kwin] [Bug 389111] black screen flickering using OpenGL
https://bugs.kde.org/show_bug.cgi?id=389111 --- Comment #3 from Joseph --- Bug appears to occur with proprietary NVIDIA drivers. It is fixed by using the NVIDIA control panel, and turning off "Sync to VBlank". Here is the output regardless. == Version === KWin version: 5.11.5 Qt Version: 5.10.0 Qt compile version: 5.10.0 XCB compile version: 1.12 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11906000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 0 glPlatformInterface: 1 windowsBlockCompositing: false Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: DVI-D-0 Geometry: 0,0,1920x1080 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 387.34 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 387.34 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.19.6 Linux kernel version: 4.14.15 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom kwin4_effect_translucency kwin4_effect_morphingpopups kwin4_effect_dialogparent kwin4_effect_fade kwin4_effect_logout kwin4_effect_windowaperture kwin4_effect_maximize kwin4_effect_login kwin4_effect_frozenapp slidingpopups slide screenshot minimizeanimation desktopgrid colorpicker presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_translucency: kwin4_effect_morphingpopups: kwin4_effect_dialogparent: kwin4_effect_fade: kwin4_effect_logout: kwin4_effect_windowaperture: kwin4_effect_maximize: kwin4_effect_login: kwin4_effect_frozenapp: slidingpopups: fadeInTime: 150 fadeOutTime: 250 slide: screenshot: minimizeanimation: desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true colorpicker: pres
[kwin] [Bug 450615] New: Login desktop effect not working
https://bugs.kde.org/show_bug.cgi?id=450615 Bug ID: 450615 Summary: Login desktop effect not working Product: kwin Version: 5.24.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: josephdegarmo76...@gmail.com 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 *** "Smoothly fade to desktop when logging in" effect does not work when logging in after session lock or wake from suspend. STEPS TO REPRODUCE 1. Log in to load desktop. 2. 3. OBSERVED RESULT Desktop pops up with no smooth transition from the SDDM screen. EXPECTED RESULT Desktop is supposed to fade in. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450615] Login desktop effect not working when waking from suspend
https://bugs.kde.org/show_bug.cgi?id=450615 Joseph DeGarmo changed: What|Removed |Added Summary|Login desktop effect not|Login desktop effect not |working |working when waking from ||suspend -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450615] Login desktop effect not working when waking from suspend
https://bugs.kde.org/show_bug.cgi?id=450615 --- Comment #1 from Joseph DeGarmo --- Uh, hello??? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 450825] New: Login desktop effect not working when resuming from lock or suspend
https://bugs.kde.org/show_bug.cgi?id=450825 Bug ID: 450825 Summary: Login desktop effect not working when resuming from lock or suspend Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: josephdegarmo76...@gmail.com 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 *** "Smoothly fade to desktop when logging in" effect does not work when logging in after session lock or wake from suspend. STEPS TO REPRODUCE 1. Log in to load desktop. 2. 3. OBSERVED RESULT Desktop pops up with no smooth transition from the SDDM screen. EXPECTED RESULT Desktop is supposed to fade in. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466195] New: Missing interface in smb.conf causes Dolphin to freeze upon launch
https://bugs.kde.org/show_bug.cgi?id=466195 Bug ID: 466195 Summary: Missing interface in smb.conf causes Dolphin to freeze upon launch Classification: Applications Product: dolphin Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: josephg...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin freezes on launch for ~6 seconds for every missing network interface added to /etc/samba/smb.conf. STEPS TO REPRODUCE For example, if smb.conf looks like this: ``` [global] interfaces = wtf wtf2 wtf3 wtf4 wtf5 ``` OBSERVED RESULT Then, upon launching `dolphin`, the GUI freezes for ~30 seconds EXPECTED RESULT Dolphin shouldn't freeze. SOFTWARE/OS VERSIONS OS: Arch Linux 6.1.12-zen1-1-zen dolphin: 22.12.2 smbd: 4.17.5 ADDITIONAL INFORMATION The smb/samba daemon doesn't need to be running for this bug to occur. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458321] DPI scaling is way off when using nvidia proprietary drivers instead of nouveau
https://bugs.kde.org/show_bug.cgi?id=458321 Joseph Yasi changed: What|Removed |Added CC||joe.y...@gmail.com --- Comment #21 from Joseph Yasi --- This isn't KDE's fault either for most of the screenshots you provided. Notepadqq has to handle HiDPI properly. So does the Manjaro Settings Manager. The fonts are supposed to be scaled up based on the DPI. 72 point = 1 inch. The UI needs to adjust for that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468299] New: Accent color based on wallpaper uses blue instead of grey
https://bugs.kde.org/show_bug.cgi?id=468299 Bug ID: 468299 Summary: Accent color based on wallpaper uses blue instead of grey Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: josephdegarmo76...@gmail.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 157962 --> https://bugs.kde.org/attachment.cgi?id=157962&action=edit Image file which illustrates the issue. SUMMARY Whenever I set the accent color to be based on the wallpaper, every time I set a black, grey, or white image as wallpaper, the accent color is set to blue instead of a monochrome color. Occurs at least on Wayland. STEPS TO REPRODUCE 1. Set the accent color based on wallpaper in the system settings. 2. Set a monochrome image (black, grey, white) as wallpaper. OBSERVED RESULT Color is set to the default blue palette. EXPECTED RESULT Color should have been set to a shade of grey. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 37 KDE Plasma (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Graphics platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468299] Accent color based on wallpaper uses blue instead of grey
https://bugs.kde.org/show_bug.cgi?id=468299 --- Comment #1 from Joseph DeGarmo --- Occurs on X11 session as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468506] New: Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 Bug ID: 468506 Summary: Copied content not pasting on newly-opened applications on Wayland Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: josephdegarmo76...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When I copy a body of text and/or file on an application, the content does not paste onto an application I launch. For example, when I copy a URL from a text document, when I launch Firefox or Chrome, the paste command is unavailable. Copying a body of text from a website will also not be able to paste onto a text document when I open KWrite. I will have to launch the clipboard manager and copy the contents from there every time. This is disruptive to the standard workflow when multi-tasking. STEPS TO REPRODUCE 1. Copy a group of text on one application. 2. Launch another application. 3. Right-click on a text field, such as a URL bar, with the intention of pasting the text. OBSERVED RESULT When I right-click, the paste command is grayed out and unavailable. EXPECTED RESULT Right-clicking should have given the paste option for applying the contents onto the new application. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 37 KDE (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This bug affects the Plasma Wayland session. X11 is not affected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 --- Comment #2 from Joseph DeGarmo --- (In reply to Nate Graham from comment #1) > Cannot immediately reproduce on Wayland with Plasma 5.27.4. A few questions > to start with: > 1. Do you by any chance have the clipboard history set to only 1 item> > 2. If you pin the clipboard popup open, can you see a new entry being added > to the top of it when you copy the text? > 3. Does the issue reproduce with all apps you've tested (within reason) > being the sending and receiving apps, or only with some apps? Testing this on Q4OS 5 "Aquarius" testing. Issue seems to occur when I copy some text from one application, close the application, then attempt to paste the text onto another application. Only I could paste when the original application remains open. Seems that this is not an issue on X11. Bug appears to be less severe than previously reported. I'll need to test this again on Fedora to confirm this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 --- Comment #3 from Joseph DeGarmo --- (In reply to Joseph DeGarmo from comment #2) > (In reply to Nate Graham from comment #1) > > Cannot immediately reproduce on Wayland with Plasma 5.27.4. A few questions > > to start with: > > 1. Do you by any chance have the clipboard history set to only 1 item> > > 2. If you pin the clipboard popup open, can you see a new entry being added > > to the top of it when you copy the text? > > 3. Does the issue reproduce with all apps you've tested (within reason) > > being the sending and receiving apps, or only with some apps? > > Testing this on Q4OS 5 "Aquarius" testing. Issue seems to occur when I copy > some text from one application, close the application, then attempt to paste > the text onto another application. Only I could paste when the original > application remains open. Seems that this is not an issue on X11. Bug > appears to be less severe than previously reported. I'll need to test this > again on Fedora to confirm this. Tested on Fedora Linux, same thing. I have to be forced to keep applications open. A bit annoying. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 --- Comment #5 from Joseph DeGarmo --- (In reply to Nate Graham from comment #4) > I'm on Fedora 37 as well and can't reproduce the issue as currently > described, so it seems more likely to be a local configuration issue of some > sort. > > Can you please answer the specific 3 questions I asked earlier? > > Additionally, I have a fourth question: can you list *any* non-default > Clipboard settings you're using? 1. No 2. Yes 3. All apps 4. All clipboard settings are at default. Tested this on two distros (one on a live USB) and on two different machines with settings at default. Same issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 --- Comment #8 from Joseph DeGarmo --- (In reply to Vlad Zahorodnii from comment #7) > Can you run firefox with WAYLAND_DEBUG=1 and try to reproduce the bug and > attach the resulting firefox log output to this bug report? > >env WAYLAND_DEBUG=1 firefox > log.txt 2>&1 I ran that command and same result. No log output pops up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 --- Comment #10 from Joseph DeGarmo --- Also happens in Debian 12. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 Joseph DeGarmo changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 488946] New: Invalid CMake syntax for !BUILD_WITH_QT6
https://bugs.kde.org/show_bug.cgi?id=488946 Bug ID: 488946 Summary: Invalid CMake syntax for !BUILD_WITH_QT6 Classification: Applications Product: amarok Version: unspecified Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: joe.y...@gmail.com Target Milestone: kf5 SUMMARY Commit 5cf29c0bd9b0536a04624db15644b175054b8c5e (after 3.0.1) introduced a CMake build option for Qt6. The CMake checks that flag with if(!BUILD_WITH_QT6) in a few places. if(NOT BUILD_WITH_QT6) is the correct syntax. Building without QT6 leads to missing files (e.g. amarok-plugin.desktop, amarok-contextapplet.desktop, amarok_codecinstall.desktop) STEPS TO REPRODUCE 1. Build amarok from git without BUILD_WITH_QT6 set OBSERVED RESULT Missing files from the installation. amarok-plugin.desktop amarok-contextapplet.desktop amarok_codecinstall.desktop amarokurls/amarok.protocol amarokitpc.protocol amarok_collection-mysqlcollection.desktop amarok_storage-mysqlestorage.desktop amarok_storage-mysqlserverstorage.desktop amarok_service_ampache.desktop amarok_service_ampache_config.desktop amarok_service_lastfm.desktop amarok_service_lastfm_config.desktop amaroklastfm.protocol amarok_service_magnatunestore.desktop amarok_service_magnatunestore_config.desktop EXPECTED RESULT The amarok installation includes the missing files. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 24.04 (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I caught this in the nightly builds in my PPA when packaging failed due to the missing files. I tested a fix by changing it from !BUILD_WITH_QT6 to NOT BUILD_WITH_QT6 and that worked. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 489063] New: Invalid for loop syntax in src/services/gpodder/GpodderServiceSettings.cpp
https://bugs.kde.org/show_bug.cgi?id=489063 Bug ID: 489063 Summary: Invalid for loop syntax in src/services/gpodder/GpodderServiceSettings.cpp Classification: Applications Product: amarok Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Services/gpodder.net Assignee: amarok-bugs-d...@kde.org Reporter: joe.y...@gmail.com CC: ste...@derkits.net Target Milestone: kf5 SUMMARY Git commit 82c2626d7d26014de8638dcaf789adfc29178db0 introduced invalid for loop syntax in src/services/gpodder/GpodderServiceSettings.cpp at line 133. foreach( devPtr, ptrList ) for( devPtr : ptrList ) The for loop doesn't declare a type for devPtr and fails to compile. See: https://launchpadlibrarian.net/736302361/buildlog_ubuntu-noble-amd64.amarok_2%3A3.0.0+git202406221530-0+yasi1~17~ubuntu24.04.1_BUILDING.txt.gz STEPS TO REPRODUCE 1. Compile Amarok after git commit 82c2626d7d26014de8638dcaf789adfc29178db0 with gpodder support enabled. OBSERVED RESULT Compilation failure in src/services/gpodder/GpodderServiceSettings.cpp EXPECTED RESULT Compilation succeeds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 24.04 (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I fixed this by removing mygpo::DevicePtr devPtr; at line 128 and declaring const auto& devPtr in the for loop. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482630] New: Cannot edit/overwrite files stored on Windows shared folder
https://bugs.kde.org/show_bug.cgi?id=482630 Bug ID: 482630 Summary: Cannot edit/overwrite files stored on Windows shared folder Classification: Applications Product: okular Version: 23.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: joseph.gr...@nmt.us Target Milestone: --- SUMMARY When you try to annotate and then overwrite a file stored on a Windows network share, from a Windows PC you get an error message related to copying the partial file to the real save location. This only happens when you access the files with the "\\share\location\file" type syntax, it works if you map the share to a letter drive (marked minor because of this workaround). It also works if you save a new file, it's only overwrites that break it. STEPS TO REPRODUCE 1. Open file on network share without mapping the share to a letter drive. E.g. "\\SHARE-PC\SHARE-NAME\test-file.pdf" 2. Overwrite the original file with File->Save As 3. Select Yes when asked to replace the file. OBSERVED RESULT The file is not saved and the following error message is displayed in a popup: File could not be saved in 'file://SHARE-PC/SHARE-NAME/test-file.pdf'. Error: 'Could not rename partial file //SHARE-PC/SHARE-NAME/test-file.pdf. Please check permissions.'. Try to save it to another location. EXPECTED RESULT The file is saved. SOFTWARE/OS VERSIONS Windows: 10 Pro 22H2 macOS: N/A Linux/KDE Plasma: N/A (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.109.0 Qt Version: 5.109.0 ADDITIONAL INFORMATION I got my Okular binaries from the MS store. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482630] Cannot edit/overwrite files stored on Windows shared folder
https://bugs.kde.org/show_bug.cgi?id=482630 Joseph Greef changed: What|Removed |Added CC||joseph.gr...@nmt.us -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 480019] Bird's Eye View doesn't update from original document size
https://bugs.kde.org/show_bug.cgi?id=480019 --- Comment #2 from Joseph Morgan --- Sorry it took so long for me to get back to this. My debug is on (apparently always was). I see the blue rectangle, but not the green one. Could it be because I'm using Ubuntu here? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 480019] Bird's Eye View doesn't update from original document size
https://bugs.kde.org/show_bug.cgi?id=480019 --- Comment #8 from Joseph Morgan --- OK. Got it now! Thanks. I can drag a class from a class diagram all the way outside the green rectangle. The blue one expands, but not the green. I can never drag the blue rectangle in the Bird's Eye View beyond the bounds of the green rectangle as shown in the class diagram. Thanks for the update, as well, on it being an unresolved issue and not so much having to do with Ubuntu. The good news is, there is a work around. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 484521] New: Code Import Wizard doesn't discover nor allow expansion of mounted media
https://bugs.kde.org/show_bug.cgi?id=484521 Bug ID: 484521 Summary: Code Import Wizard doesn't discover nor allow expansion of mounted media Classification: Applications Product: umbrello Version: 2.33.2 (KDE releases 20.12.2) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: umbrello-de...@kde.org Reporter: j...@javajoemorgan.com Target Milestone: --- I have a dedicated drive for all development work. It is always mounted. However, when I try to use the Code -> Code Importing Wizard, that screen doesn't display mount points and won't allow me to expand the /media/. I can import from any directory using the Code -> Import from Directory. STEPS TO REPRODUCE 1. After starting up Umbrello, select Code -> Code Importing Wizard 2. When the wizard opens, notice no mounted drives are present 3. Attempt to expand "/media", shows nothing. OBSERVED RESULT Attempt to expand "/media", shows nothing. EXPECTED RESULT Attempt to expand "/media", should show me (my username) and then the mounts underneath. In my case it is "/media/myusername/Development" SOFTWARE/OS VERSIONS Umbrello 2.38.3 Ubuntu 22.04 Dell Precision 7730 64GB RAM 4 x M2 SSD (OS, home, Development, Media) KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480934] New: Add crashes when entering name on photo view screen
https://bugs.kde.org/show_bug.cgi?id=480934 Bug ID: 480934 Summary: Add crashes when entering name on photo view screen Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: jos...@siegmann.org Target Milestone: --- SUMMARY *** When I try and enter a name when viewing a photo, it always crashes, no character is ever typed, and shortly after clicking into the name box with my mouse, and then typing any charater, the app will crash with no message. *** STEPS TO REPRODUCE 1. View any photo 2. Hover over any face that was detected, but no name was assigned 3. Click in the name box 4. Type any character 5. CRASH! OBSERVED RESULT What I typed above EXPECTED RESULT Name should be typed just like under the people tab SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481102] New: Assigning a name to a face is an issue due to display list
https://bugs.kde.org/show_bug.cgi?id=481102 Bug ID: 481102 Summary: Assigning a name to a face is an issue due to display list Classification: Applications Product: digikam Version: 8.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: jos...@siegmann.org Target Milestone: --- Created attachment 165685 --> https://bugs.kde.org/attachment.cgi?id=165685&action=edit Example of issue SUMMARY *** When typing a name to assign a name for a face, the selection list that is displayed is now wide enough to show text, so long common names are confusing *** STEPS TO REPRODUCE 1. Click on box to fill in a name 2. *names will appear of existing tabs* 3. This list is not wide enough to tell the difference between common names OBSERVED RESULT Very hard to pick the right name, and at times the wrong name is picked due to it being hidden EXPECTED RESULT Box should be wider, or a hover over should show the full name SOFTWARE/OS VERSIONS Windows: 11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] New: Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 Bug ID: 453266 Summary: Flipping the pen no longer erases Product: krita Version: 5.0.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tablets (tablet issues are only very rarely bugs in Krita!) Assignee: krita-bugs-n...@kde.org Reporter: joeno...@protonmail.com Target Milestone: --- Created attachment 148501 --> https://bugs.kde.org/attachment.cgi?id=148501&action=edit Log of drawing a line with the pen tip, then the eraser tip SUMMARY Using a wacom CTH-460, flipping the pen no longer erases. STEPS TO REPRODUCE 1. Draw using the pen 2. Flip the pen over to erase OBSERVED RESULT The pen draws using the same settings. EXPECTED RESULT The pen erases when using the eraser end. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Silverblue 35, Linux 5.17.4-200.fc35.x86_64 (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The issue also occurs on the 5.0.0 and 5.0.6 appimage, but using the 4.4.8 appimage did not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 Joseph Nosie changed: What|Removed |Added CC||joeno...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450825] Login desktop effect should also apply when resuming from lock or suspend
https://bugs.kde.org/show_bug.cgi?id=450825 --- Comment #3 from Joseph DeGarmo --- For various reasons, I switched to a Debian-based distro and went back to Plasma 5.20. Apparently this ticket will never be processed and the issue will never be resolved. I now understand that this desktop effect (as well as the desktop cube) has been discontinued from Plasma 5.24 going forward. You may close this ticket and label it as unresolved.😡 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 271686] Keyboard shortcut to move windows to activities
https://bugs.kde.org/show_bug.cgi?id=271686 Joseph Nosie changed: What|Removed |Added CC|joeno...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450825] Login desktop effect should also apply when resuming from lock or suspend
https://bugs.kde.org/show_bug.cgi?id=450825 --- Comment #2 from Joseph DeGarmo --- (In reply to Nate Graham from comment #1) > The effect doesn't handle that use case; it only works when logging in from > SDDM. When resuming from suspend, SDDM is not involved. It used to work on wake from suspend in Plasma 5.23. Has this ability been removed from 5.24? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450615] Login desktop effect not working when waking from suspend
https://bugs.kde.org/show_bug.cgi?id=450615 --- Comment #3 from Joseph DeGarmo --- (In reply to Nate Graham from comment #2) > Also reported as Bug 450825; no need for a second one. Please do not > intentionally open duplicate bug reports. > > Also please see > https://community.kde.org/Get_Involved/ > Issue_Reporting#Have_realistic_expectations I had to reissue the bug because I waited for a whole week with no response. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #23 from Joseph DeGarmo --- Nope. Still not fixed unless you switch to a different subcategory then back to favorites. On Mon, Oct 25, 2021 at 11:03 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=443975 > > Nate Graham changed: > >What|Removed |Added > > >Version Fixed In||5.23.2 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #25 from Joseph DeGarmo --- X11 On Tue, Oct 26, 2021 at 3:18 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=443975 > > --- Comment #24 from Nate Graham --- > Joseph, are you using the Wayland session, or X11? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #31 from Joseph DeGarmo --- I think someone needs to create a fork of the Kicker menu as a widget. Meanwhile, just use an alternate menu, such as the Application Dashboard or Tiled Menu. On Wed, Oct 27, 2021, 12:01 AM Samuel Reddy wrote: > https://bugs.kde.org/show_bug.cgi?id=443975 > > Samuel Reddy changed: > >What|Removed |Added > > > CC|| > samuelsumukhre...@gmail.com > > --- Comment #30 from Samuel Reddy --- > Plasma 5.23.2 on Arch Linux does not fix the problem for me. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #34 from Joseph DeGarmo --- It appears to have finally been fixed. On Wed, Oct 27, 2021 at 9:41 AM Patrick Silva wrote: > https://bugs.kde.org/show_bug.cgi?id=443975 > > --- Comment #33 from Patrick Silva --- > On Arch Linux, package plasma-desktop 5.23.2-2 fixes the bug on X11. > But there is a bug possibly related to this fix on Wayland, see bug 89. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 443975] New: Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 Bug ID: 443975 Summary: Dragging favorites icons in the application launcher causes overlapping Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: josephdegarmo76...@gmail.com Target Milestone: --- SUMMARY In the application launcher menu, when I drag a favorite icon to move it, it overlaps with another icon. STEPS TO REPRODUCE 1. Hold left click on icon and move cursor to move the icon. 2. 3. OBSERVED RESULT Icon sits on top of another icon. EXPECTED RESULT Icon was supposed to push the other icons out of the way. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #2 from Joseph DeGarmo --- Here is the video recording of the bug. On Mon, Oct 18, 2021 at 11:27 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=443975 > > Nate Graham changed: > >What|Removed |Added > > > Component|general |Application Launcher >||(Kickoff) > CC||mikel5...@gmail.com, >||n...@kde.org, >||plasma-b...@kde.org > Product|kde |plasmashell >Target Milestone|--- |1.0 > Version|unspecified |5.23.0 > Status|REPORTED|NEEDSINFO >Keywords||regression >Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham --- > Cannot reproduce. Can you attach a screen recording, please? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #4 from Joseph DeGarmo --- It occurs on the full Plasma desktop in fullscreen. The video demonstration was using a virtual machine. On Mon, Oct 18, 2021 at 11:40 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=443975 > > --- Comment #3 from Nate Graham --- > That's strange. I see you're using plasmawindowed. Does it reproduce with a > real widget? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #6 from Joseph DeGarmo --- The issue occurs using a mouse. Tested this on my host machine and virtual machine with the same outcome. On Mon, Oct 18, 2021 at 12:09 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=443975 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > CC||noaha...@gmail.com > > --- Comment #5 from Nate Graham --- > Well that's odd then. I can't reproduce the issue with either a pointing > device > or a touchscreen. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #7 from Joseph DeGarmo --- Occurs in Arch Linux after upgrading from Plasma 5.22. Does not occur on the latest KDE Neon live iso image. On Mon, Oct 18, 2021 at 12:15 PM Joseph DeGarmo < josephdegarmo76...@gmail.com> wrote: > The issue occurs using a mouse. Tested this on my host machine and virtual > machine with the same outcome. > > On Mon, Oct 18, 2021 at 12:09 PM Nate Graham > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=443975 >> >> Nate Graham changed: >> >>What|Removed |Added >> >> >> Resolution|WAITINGFORINFO |--- >> Status|NEEDSINFO |REPORTED >> CC||noaha...@gmail.com >> >> --- Comment #5 from Nate Graham --- >> Well that's odd then. I can't reproduce the issue with either a pointing >> device >> or a touchscreen. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444035] Rearranging favourites in KickOff causes the dragged icon to be misplaced
https://bugs.kde.org/show_bug.cgi?id=444035 Joseph DeGarmo changed: What|Removed |Added CC||josephdegarmo76...@gmail.co ||m --- Comment #3 from Joseph DeGarmo --- This issue occurs in Arch Linux as well as EndeavourOS. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #9 from Joseph DeGarmo --- I can confirm that the issue occurs in EndeavourOS as well, so it seems that any Arch-based distro has this issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432494] New: Advanced search select parent album returns nothing
https://bugs.kde.org/show_bug.cgi?id=432494 Bug ID: 432494 Summary: Advanced search select parent album returns nothing Product: digikam Version: 7.2.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Searches-Advanced Assignee: digikam-bugs-n...@kde.org Reporter: yuc...@gmail.com Target Milestone: --- SUMMARY When trying to search a filename using advanced search, digikam only returns the results if exact folder is selected. If the parent folder is selected, digikam return nothing. STEPS TO REPRODUCE 1. Album structure: 2020/01/test1.jpg /02/test2.jpg 2. In advanced search: album: 2020-->01, search field: test1.jpg --> return the file 3. In advanced search: album field: 2020, search field: test1.jpg --> return nothing. OBSERVED RESULT EXPECTED RESULT I would expect we can select a folder in ablum field, digikam will search all subfolders. SOFTWARE/OS VERSIONS Windows: macOS: Big Sur 11.2 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432494] Advanced search album does not search subfolders nothing
https://bugs.kde.org/show_bug.cgi?id=432494 Joseph Chang changed: What|Removed |Added Summary|Advanced search select |Advanced search album does |parent album returns|not search subfolders |nothing |nothing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432494] Advanced search album does not search subfolders nothing
https://bugs.kde.org/show_bug.cgi?id=432494 --- Comment #2 from Joseph Chang --- Thanks for the information. It just seems natural to me if a folder is selected, all the subfolders are also searched. Otherwise, I can just select the subfolder itself, not the parent folder. The only situation I can think of to exclude the subfolders is if the parent folder also contain photos, then it makes sense to select the folder but excludes the subfolders. Thanks, Joseph -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433044] New: In window to select icon file when changing toolbar icons, mouse is disabled
https://bugs.kde.org/show_bug.cgi?id=433044 Bug ID: 433044 Summary: In window to select icon file when changing toolbar icons, mouse is disabled Product: digikam Version: 7.2.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: yuc...@gmail.com Target Milestone: --- SUMMARY When changing toolbar icons, cannot use the mouse in the window to select the icon file. Only keyboard works. STEPS TO REPRODUCE 1. Settings --> Configure Toolbars.. 2. Select one toolbar item in current actions:. For example, Image Editor, and click Change Icon button 3. Select Other icons and then Browse. 4. A window pops up. I can change different directory with keyboard, but no the mouse OBSERVED RESULT EXPECTED RESULT Both keyboard and mouse should be able to select the icons SOFTWARE/OS VERSIONS Windows: macOS: Big Sur 11.2.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Windows 10 works. Digikam 7.2.0-rc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433044] In window to select icon file when changing toolbar icons, mouse is disabled
https://bugs.kde.org/show_bug.cgi?id=433044 --- Comment #2 from Joseph Chang --- Created attachment 135751 --> https://bugs.kde.org/attachment.cgi?id=135751&action=edit Select custom icons -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433044] In window to select icon file when changing toolbar icons, mouse is disabled
https://bugs.kde.org/show_bug.cgi?id=433044 --- Comment #3 from Joseph Chang --- Hi Gilles, Please see the attached screenshot. I just realized that the same behavior when I tried to change the icon for the tag. I can change the directory with keyboard but the mouse was not working at all. Thanks, Joseph -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427797] New: File folder widget desktop icons will not open on single click
https://bugs.kde.org/show_bug.cgi?id=427797 Bug ID: 427797 Summary: File folder widget desktop icons will not open on single click Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: josephdegarmo76...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Drag folder to desktop and select "Add icon". 2. Click on icon in an attempt to open the folder. 3. OBSERVED RESULT Launching *folder name* (Failed) The desktop entry file /home/banzaigtv/.local/share/plasma_icons/*folder name*.desktop is not valid. EXPECTED RESULT Folder should have opened in Dolphin. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427797] File folder widget desktop icons will not open
https://bugs.kde.org/show_bug.cgi?id=427797 --- Comment #2 from Joseph DeGarmo --- I want icons pinned to a hidden panel for quick access without cluttering the desktop with shortcut links, though. This was not an issue in Plasma 5.19.5 and earlier. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427797] Icon widget with folder dragged in from Dolphin does not open on left click (right-click > open with works)
https://bugs.kde.org/show_bug.cgi?id=427797 --- Comment #5 from Joseph DeGarmo --- Takes longer than simply left-clicking the icon on the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427797] Icon widget with folder dragged in from Dolphin does not open on left click (right-click > open with works)
https://bugs.kde.org/show_bug.cgi?id=427797 --- Comment #11 from Joseph DeGarmo --- (In reply to Walther Pelser from comment #10) > It only affects *.desktop files with a line "Type=Link" > If the line is "Type=Application", it works normally. Where do I find the file and change the line? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427797] Icon widget with folder dragged in from Dolphin does not open on left click (right-click > open with works)
https://bugs.kde.org/show_bug.cgi?id=427797 --- Comment #16 from Joseph DeGarmo --- (In reply to Nate Graham from comment #15) > I'll fix it. Working on a patch. Is it possible that it will be patched in the Plasma 5.20.3 release? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 365305] Unable to use gesture typing.
https://bugs.kde.org/show_bug.cgi?id=365305 Joseph Morris changed: What|Removed |Added CC||b...@xenotropic.net --- Comment #6 from Joseph Morris --- Created attachment 137733 --> https://bugs.kde.org/attachment.cgi?id=137733&action=edit Screenshot showing voice typing issue -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 365305] Unable to use gesture typing.
https://bugs.kde.org/show_bug.cgi?id=365305 --- Comment #7 from Joseph Morris --- This seems to also prevent Google voice typing from being an option; see the prior screenshot where the voice typing icon is available in a standard text field, but not within KDE connect. I've tried all the options within GBoard, and as far as I can tell it seems to be related to the type of input in KDE Connect. It'd be pretty sweet to have the option of using Google voice typing in arbitrary applications (e.g., LibreOffice, Thunderbird, Slack, etc.), which as far as I know is not otherwise available on Linux desktop. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 480019] New: Bird's Eye View doesn't update from original document size
https://bugs.kde.org/show_bug.cgi?id=480019 Bug ID: 480019 Summary: Bird's Eye View doesn't update from original document size Classification: Applications Product: umbrello Version: 2.33.2 (KDE releases 20.12.2) Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: j...@javajoemorgan.com Target Milestone: --- SUMMARY When adding elements (to a class diagram anyway) outside of the original bounds of the view, the Bird's eye view does not compensate, making it impossible to scroll to view new components. The main view can be zoomed our, but, if the class diagram is large, zooming only seems to be focused exactly center, requiring scrolling via the Bird's Eye view. STEPS TO REPRODUCE 1. Create a class diagram. 2. Drop a large number of classes into it such that the bounds of the default page size are well exceeded. 3. Try to use the bird's eye view. OBSERVED RESULT One can only scroll to what's in the original bounds. EXPECTED RESULT The bounds of the Bird's Eye view should compensate few newly added elements. SOFTWARE/OS VERSIONS Ubuntu 22.04 Umbrello 2.38.3 (the version list above needs to be updated) QT Version 5.15.11 KDE Frameworks 5.111.0 ADDITIONAL INFORMATION A work-around is to save and close the diagram and then reopen it. As long as the elements remain within the original bounds, everything is fine. But if one adds or moves an element outside of the original bounds, the problem exists. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438788] Coordinated resize for adjacent/tiled windows
https://bugs.kde.org/show_bug.cgi?id=438788 Joseph Graham changed: What|Removed |Added CC||jos...@xylon.me.uk --- Comment #9 from Joseph Graham --- Is there a way to turn this off? I prefer the old behaviour where I can resize windows independently. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0
https://bugs.kde.org/show_bug.cgi?id=373443 Joseph Graham changed: What|Removed |Added CC||jos...@xylon.me.uk --- Comment #15 from Joseph Graham --- I have had a similar experience. I tried moving about 40,000 emails to a folder and aconadi imap process went to 100% CPU for the next 16 hours until I got annoyed with the fan noise. However stoppiing aconadi, moving agent_config_akonadi_imap_resource_0_changes.dat, and starting aconadi again fixed it. Though not all of the emails seems to have actually moved to the folder. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 158920] kdelibs configure script does not check for libasn1 (libtasn1) or libroken
https://bugs.kde.org/show_bug.cgi?id=158920 Joseph Tate changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Joseph Tate --- I haven't compiled from source in at least a decade. No use keeping this open. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 170200] Juk playlist columns not resizable
https://bugs.kde.org/show_bug.cgi?id=170200 Joseph Tate changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from Joseph Tate --- I haven't used Juk in a long time. Closing. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 162485] KDE 4 SSL Certificate support incomplete
https://bugs.kde.org/show_bug.cgi?id=162485 Joseph Tate changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #94 from Joseph Tate --- This bug is so old, and so piled on, it's not useful any more and could never be closed as fixed. New bugs should be filed for modern versions of KDE/Plasma and individual apps that are missing specific expected SSL/TLS/PKI features. One issue per bug report. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 162485] KDE 4 SSL Certificate support incomplete (DO NOT REOPEN)
https://bugs.kde.org/show_bug.cgi?id=162485 Joseph Tate changed: What|Removed |Added Summary|KDE 4 SSL Certificate |KDE 4 SSL Certificate |support incomplete |support incomplete (DO NOT ||REOPEN) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432066] New: Preview does not update when changing the photo using the keyboard
https://bugs.kde.org/show_bug.cgi?id=432066 Bug ID: 432066 Summary: Preview does not update when changing the photo using the keyboard Product: digikam Version: 7.2.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: minor Priority: NOR Component: Geolocation-Editor Assignee: digikam-bugs-n...@kde.org Reporter: yuc...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Select several photos 2. Enter Geolocation Editor. When a photo is selected in the table, the preview of the photo is shown in Details right side tab 3. If I click another photo using mouse, the preview will be updated 4. However, if I change the photo using keyboard arrow key (Up and down), the preview does not be updated OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432066] Preview does not update when changing the photo using the keyboard in geolocation editor
https://bugs.kde.org/show_bug.cgi?id=432066 Joseph Chang changed: What|Removed |Added Summary|Preview does not update |Preview does not update |when changing the photo |when changing the photo |using the keyboard |using the keyboard in ||geolocation editor -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429103] Digikam 7.1.0 does not start up, when using macos big sur
https://bugs.kde.org/show_bug.cgi?id=429103 Joseph Chang changed: What|Removed |Added CC||yuc...@gmail.com --- Comment #84 from Joseph Chang --- I tried the latest build (12/13/2020) and I was not able to start the digikam. The error message is "dyld: Library not loaded: /opt/digikam/lib/libKF5Service.5.dylib Referenced from: /opt/digikam/bin/kbuildsycoca5 Reason: image not found" I checked my /opt/digikam/lib and there is no libKF5Service.5.dylib I did have this problem for the previous build 2 or 3 days ago. Thanks, Joseph (In reply to caulier.gilles from comment #81) > A new version of the pre release 7.2.0 PKG installer is under finalization > after a recompilation from scratch (it take 23 hours to compile!) > > This version include last KDE frameworks 5.77 just released one day ago. > > https://kde.org/announcements/kde-frameworks-5.77.0/ > > The most important part here is Solid which deal with devices detection as > SD-card, Camera, Disk UUID for database, etc. > > Of course other part of KF5 are used in digiKam, but not too much, as we > work a lots to reduce the dependency level with this framework. Another part > which still used a lots is KXMLGui to manage main application windows. > > This version include last changes commited in digiKam source code of course. > > All feeback will be welcome. > > Best > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429103] Digikam 7.1.0 does not start up, when using macos big sur
https://bugs.kde.org/show_bug.cgi?id=429103 --- Comment #85 from Joseph Chang --- Sorry, typo. I did NOT have this problem for the previous build 2 or 3 days ago. (In reply to Joseph Chang from comment #84) > I did have this problem for the previous build 2 or 3 days ago. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461922] New: Installation Failure
https://bugs.kde.org/show_bug.cgi?id=461922 Bug ID: 461922 Summary: Installation Failure Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: joejc...@outlook.com 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. download tar.bz2 dist 2. unzip 3. ./configure 3. make 4. make install 5. valgrind ls -1 OBSERVED RESULT valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION On arch linux downloaded tarball and extracted in /usr/bin -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 490266] New: Amarok fails to build with KF < 5.94 due to KStatefulBrush include
https://bugs.kde.org/show_bug.cgi?id=490266 Bug ID: 490266 Summary: Amarok fails to build with KF < 5.94 due to KStatefulBrush include Classification: Applications Product: amarok Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Playlist Assignee: amarok-bugs-d...@kde.org Reporter: joe.y...@gmail.com Target Milestone: kf5 SUMMARY a151941ed2c9199d6d16ef91f0ecef61c4b03cca added an include of KStatefulBrush to src/playlist/ProgressiveSearchWidget.cpp. The KStatefulBrush header wasn't introduced until KF 5.94. Before that, the class was just in KColorScheme. STEPS TO REPRODUCE 1. Build Amarok after a151941ed2c9199d6d16ef91f0ecef61c4b03cca on Kubuntu 22.04 2. 3. OBSERVED RESULT /<>/src/playlist/ProgressiveSearchWidget.cpp:25:10: fatal error: KStatefulBrush: No such file or directory 25 | #include | ^~~~ compilation terminated. make[4]: *** [src/CMakeFiles/amaroklib.dir/build.make:1067: src/CMakeFiles/amaroklib.dir/playlist/ProgressiveSearchWidget.cpp.o] Error 1 See: https://launchpadlibrarian.net/739316606/buildlog_ubuntu-jammy-amd64.amarok_2%3A3.0.1+git202407132210-0+yasi1~21~ubuntu22.04.1_BUILDING.txt.gz EXPECTED RESULT Compile succeeds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 490650] New: src/musicbrainz/MusicDNSAudioDecoder.cpp fails to build on Ubuntu Jammy with Amarok git
https://bugs.kde.org/show_bug.cgi?id=490650 Bug ID: 490650 Summary: src/musicbrainz/MusicDNSAudioDecoder.cpp fails to build on Ubuntu Jammy with Amarok git Classification: Applications Product: amarok Version: 3.0.81 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: joe.y...@gmail.com Target Milestone: kf5 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY src/musicbrainz/MusicDNSAudioDecoder.cpp fails to compile with Ubuntu Jammy's version of FFMPEG (4.4.2) STEPS TO REPRODUCE 1. Compile Amarok on Ubuntu Jammy from git after 42d249b659253b8970bd870d77a56c869e79bcef and f6143b2df0b251f3e5e5665ea7121e49b0f45d7e. OBSERVED RESULT /<>/src/musicbrainz/MusicDNSAudioDecoder.cpp: In member function ‘int MusicDNSAudioDecoder::decode(const QString&, DecodedAudioData*, int)’: /<>/src/musicbrainz/MusicDNSAudioDecoder.cpp:327:63: error: invalid user-defined conversion from ‘QByteArray’ to ‘const char*’ [-fpermissive] 327 | if( avformat_open_input( &pFormatCtx, fileName.toLocal8Bit(), nullptr, nullptr ) < 0 ) | ^~ See: https://launchpadlibrarian.net/740431669/buildlog_ubuntu-jammy-amd64.amarok_2%3A3.0.1+git202407210215-0+yasi1~22~ubuntu22.04.1_BUILDING.txt.gz EXPECTED RESULT Compilation succeeds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92 Qt Version: 5.15.3 ADDITIONAL INFORMATION fileName.toLocal8Bit().constData() looks like it was made in one of the FFMPEG version branches, but not in the #elif LIBAVCODEC_VERSION_MAJOR >= 54 branch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491718] New: KDE Crashes and Restarts Immediately after Unlocking Desktop
https://bugs.kde.org/show_bug.cgi?id=491718 Bug ID: 491718 Summary: KDE Crashes and Restarts Immediately after Unlocking Desktop Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joseph.dora...@gmail.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-23-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: KDE Crashes and Restarts Immediately after Unlocking Desktop. This is close to a clean install. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 7969 (plasmashell) UID: 1000 (user1) GID: 1000 (user1) Signal: 11 (SEGV) Timestamp: Wed 2024-08-14 07:55:47 MDT (24s 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 (user1) Boot ID: d97a6723a2a14275a6b868835b98d0b0 Machine ID: 83d1934bb93b48fc89d7f0dd3029caec Hostname: debian Storage: /var/lib/systemd/coredump/core.plasmashell.1000.d97a6723a2a14275a6b868835b98d0b0.7969.172364374700.zst (present) Size on Disk: 31.1M Message: Process 7969 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.26-1~deb12u2.amd64 Module libudev.so.1 from deb systemd-252.26-1~deb12u2.amd64 Stack trace of thread 7969: #0 0x7f09a2aa9e2c n/a (libc.so.6 + 0x8ae2c) #1 0x7f09a2a5afb2 raise (libc.so.6 + 0x3bfb2) #2 0x7f09a517db46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f09a2a5b050 n/a (libc.so.6 + 0x3c050) #4 0x7f09a2aa9e2c n/a (libc.so.6 + 0x8ae2c) #5 0x7f09a2a5afb2 raise (libc.so.6 + 0x3bfb2) #6 0x7f09a2a5b050 n/a (libc.so.6 + 0x3c050) #7 0x7f09a2a46660 __errno_location (libc.so.6 + 0x27660) #8 0x7f09a2e3f295 n/a (libQt5Core.so.5 + 0x23f295) #9 0x7f09a2ddd92c _ZNK9QFileInfo6isFileEv (libQt5Core.so.5 + 0x1dd92c) #10 0x7f09a2df6038 _ZN14QStandardPaths6locateENS_16StandardLocationERK7QString6QFlagsINS_12LocateOptionEE (libQt5Core.so.5 + 0x1f6038) #11 0x7f09a538299c n/a (libKF5Plasma.so.5 + 0x8499c) #12 0x7f09a5383a14 n/a (libKF5Plasma.so.5 + 0x85a14) #13 0x7f09a537fc5e _ZNK6Plasma5Theme20currentThemeHasImageERK7QString (libKF5Plasma.so.5 + 0x81c5e) #14 0x7f09a53791b7 n/a (libKF5Plasma.so.5 + 0x7b1b7) #15 0x7f09a536d9cd _ZN6Plasma8FrameSvg12setImagePathERK7QString (libKF5Plasma.so.5 + 0x6f9cd) #16 0x7f0997abd84f n/a (libcorebindingsplugin.so + 0x3984f) #17 0x7f09a46f5986 n/a (libQt5Qml.so.5 + 0x2f5986) #18 0x7f09a46f7890 _ZN17QQmlObjectCreator16setPropertyValueEPK16QQmlPropertyDataPKN3QV412CompiledData7BindingE (libQt5Qml.so.5 + 0x2f7890) #19 0x7f09a46fbe68 _ZN17QQmlObjectCreator18setPropertyBindingEPK16QQmlPropertyDataPKN3QV412CompiledData7BindingE (libQt5Qml.so.5 + 0x2fbe68) #20 0x7f09a46fd8f9 _ZN17QQmlObjectCreator13setupBindingsEb (libQt5Qml.so.5 + 0x2fd8f9) #21 0x7f09a46f979c _ZN17QQmlObjectCreator16populateInstanceEiP7QObjectS1_PK16QQmlPropertyData (libQt5Qml.so.5 + 0x2f979c) #22 0x7f09a46fa4fa _ZN17QQmlObjectCreator14createInstanceEiP7QObjectb (libQt5Qml.so.5 + 0x2fa4fa) #23 0x7f09a46fc18d _ZN17QQmlObjectCreator18setPropertyBindingEPK16QQmlPropertyDataPKN3QV412CompiledData7BindingE (libQt5Qml.so.5 + 0x2fc18d) #24 0x7f09a46fd8f9 _ZN17QQmlObjectCreator13setupBindingsEb (libQt5Qml.so.5 + 0x2fd8f9) #25 0x7f09a46f979c _ZN17QQmlObjectCreator16populateInstanceEiP7QObjectS1_PK16QQmlPropertyData (libQt5Qml.so.5 + 0x2f979c) #26 0x7f09a46fa4fa _ZN17QQmlObjectCreator14createInstanceEiP7QObjectb (libQt5Qml.so.5 + 0x2fa4fa) #27 0x7f09a46fb3e7 _ZN17QQmlObjectCreator6createEiP7QObjectP26QQmlInstantiationInterrupti (libQt5Qml.so.5 + 0x2fb3e7)
[amarok] [Bug 459933] ffmpeg-5 support
https://bugs.kde.org/show_bug.cgi?id=459933 Joseph Yasi changed: What|Removed |Added CC||joe.y...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433551] New: Dolphin crashed when changing viewing modes
https://bugs.kde.org/show_bug.cgi?id=433551 Bug ID: 433551 Summary: Dolphin crashed when changing viewing modes Product: dolphin Version: 20.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: joseph.hallst...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.2) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-44-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: Switch view mode from tree to icons. Dolphin was in full screen mode displaying a directory tree struction with ownership and permissions, I was switching it back to normal (icons) view mode when the crash occured. The directory was on a local disk. No other foreground activities were running. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fc86723a864 in __GI_abort () at abort.c:79 #6 0x7fc86729daf6 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fc8673c5128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #7 0x7fc8672a646c in malloc_printerr (str=str@entry=0x7fc8673c70f0 "munmap_chunk(): invalid pointer") at malloc.c:5389 #8 0x7fc8672a683c in munmap_chunk (p=) at malloc.c:2845 #9 0x7fc8651835a7 in QHashData::free_helper(void (*)(QHashData::Node*)) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc867160221 in KFileItemModel::removeItems(KItemRangeList const&, KFileItemModel::RemoveItemsBehavior) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #11 0x7fc86716baf6 in KFileItemModel::setExpanded(int, bool) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #12 0x7fc86717bc84 in KItemListController::mouseReleaseEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #13 0x7fc86717e749 in KItemListController::processEvent(QEvent*, QTransform const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #14 0x7fc86718e2c1 in KItemListView::event(QEvent*) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #15 0x7fc865ea2013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fc86532a1ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fc8661c070d in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fc8661c0ac1 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fc8661c6300 in QGraphicsScene::mouseReleaseEvent(QGraphicsSceneMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fc8661d2f91 in QGraphicsScene::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fc865ea2013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fc86532a1ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fc8661efe78 in QGraphicsView::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fc865ee330e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fc865f8c2a2 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fc865329ed3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fc865ea2002 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7fc865ea7841 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7fc86532a1ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7fc865ea673a in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fc865efbf32 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7fc865efed8e in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7fc865ea2013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7fc86532a1ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7fc8657bd48b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #36 0x7fc8657932bb in QWindowSystemInter
[elisa] [Bug 407918] Does not find music on other ext4 partition even when added to search paths
https://bugs.kde.org/show_bug.cgi?id=407918 Joseph Nosie changed: What|Removed |Added CC||joeno...@protonmail.com --- Comment #10 from Joseph Nosie --- Created attachment 120545 --> https://bugs.kde.org/attachment.cgi?id=120545&action=edit STDOUT with logging enabled I can also reproduce this with the Elisa nightly flatpak. I have verified that Elisa has been given filesystem permission for the mount point of the partition. If an album exists in both ~/Music and the mount, the album shows up twice in the album listing, but one of them (the one from the mount) is empty. Also, other flatpak apps can access the mount point when given the permissions. (I have a steam library on the same drive.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410518] New: ~4 seconds after exiting with super-q, notice of crash appears
https://bugs.kde.org/show_bug.cgi?id=410518 Bug ID: 410518 Summary: ~4 seconds after exiting with super-q, notice of crash appears Product: digikam Version: 6.1.0 Platform: Homebrew (macOS) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: joseph.2...@reagle.org Target Milestone: --- SUMMARY I've seen this in at least 6.1 and confirmed it is in 6.2 . Seconds after normally quitting, MacOS pops up a dialog "digikam quit unexpectedly", requiring one to ignore, report..., or reopen. STEPS TO REPRODUCE 1. Quit digikam. OBSERVED RESULT Crash dialog. EXPECTED RESULT No crash dialog. CRASH REPORT Process: digikam [32547] Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam Identifier:digikam Version: 6.2.0 (6.2.0) Code Type: X86-64 (Native) Parent Process:??? [1] Responsible: digikam [32547] User ID: 502 Date/Time: 2019-08-02 09:39:40.288 -0400 OS Version:Mac OS X 10.14.6 (18G84) Report Version:12 Bridge OS Version: 3.6 (16P6568) Anonymous UUID:A3B78802-9A75-4BA9-6ADB-E84F5DFAEEF3 Time Awake Since Boot: 75 seconds System Integrity Protection: enabled Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_PROTECTION_FAILURE at 0x7ffee3700330 Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [32547] VM Regions Near 0x7ffee3700330: STACK GUARD7ffedf701000-7ffee2f01000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0 --> Stack 7ffee2f01000-7ffee3701000 [ 8192K] rw-/rwx SM=SHM thread 0 Submap 7fff-7fff8000 [ 2.0G] r--/rwx SM=SHM machine-wide VM submap Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0x7ffee3700330 0 + 140732714189616 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410518] ~4 seconds after exiting with super-q, notice of crash appears
https://bugs.kde.org/show_bug.cgi?id=410518 Joseph Reagle changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #5 from Joseph Reagle --- Crash report still present Process: digikam [29398] Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam Identifier:digikam Version: 6.3.0 (6.3.0-git) Code Type: X86-64 (Native) Parent Process:??? [1] Responsible: digikam [29398] User ID: 502 Date/Time: 2019-08-05 08:19:17.875 -0400 OS Version:Mac OS X 10.14.6 (18G84) Report Version:12 Bridge OS Version: 3.6 (16P6568) Anonymous UUID:A3B78802-9A75-4BA9-6ADB-E84F5DFAEEF3 Time Awake Since Boot: 100 seconds System Integrity Protection: enabled Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_PROTECTION_FAILURE at 0x7ffeea24a330 Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [29398] VM Regions Near 0x7ffeea24a330: STACK GUARD7ffee624b000-7ffee9a4b000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0 --> Stack 7ffee9a4b000-7ffeea24b000 [ 8192K] rw-/rwx SM=SHM thread 0 Submap 7fff-7fff8000 [ 2.0G] r--/rwx SM=SHM machine-wide VM submap Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0x7ffeea24a330 0 + 140732826690352 ... -- You are receiving this mail because: You are watching all bug changes.
