[plasmashell] [Bug 468817] Screen energy saving causes multiple problems when waking up
https://bugs.kde.org/show_bug.cgi?id=468817 --- Comment #6 from Steven A. Falco --- I've switched to XFCE. I guess you can just close this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487550] KDevelop crashed just after startup
https://bugs.kde.org/show_bug.cgi?id=487550 --- Comment #2 from Steven Robbins --- When I ran kdev again, I saw a message saying that "crash may have been a result of corrupt cache", with option to clear the cache. I chose to clear the cache and was able to use kdev without further crashes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487550] KDevelop crashed just after startup
https://bugs.kde.org/show_bug.cgi?id=487550 --- Comment #1 from Steven Robbins --- Created attachment 169834 --> https://bugs.kde.org/attachment.cgi?id=169834=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487550] New: KDevelop crashed just after startup
https://bugs.kde.org/show_bug.cgi?id=487550 Bug ID: 487550 Summary: KDevelop crashed just after startup Classification: Applications Product: kdevelop Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: st...@sumost.ca Target Milestone: --- Application: kdevelop (5.12.230801 (23.08.1)) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.11 [CoredumpBackend] -- Information about the crash: I started kdevelop (for the first time in months). It opened as normal, and I was looking through the sessions list, thinking I might want to create a new session. I may have clicked on one of the existing sessions, but I'm not certain. Then the window abruptly vanished. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #3 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #4 0x7fbc39ca6b7f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #5 0x7fbc39c584e2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #6 0x7fbc39c414ed in __GI_abort () at ./stdlib/abort.c:79 [...] #8 0x7fbc39cb0465 in malloc_printerr (str=str@entry=0x7fbc39db9c60 "tcache_thread_shutdown(): unaligned tcache chunk detected") at ./malloc/malloc.c:5765 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 486730] New: Latte crashed when attempting to add widget
https://bugs.kde.org/show_bug.cgi?id=486730 Bug ID: 486730 Summary: Latte crashed when attempting to add widget Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: steven.harmon...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.0-31-generic x86_64 Windowing System: X11 Distribution: Ubuntu 24.04 LTS DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Latte has been crashing about 40% of the time when I try to add a widget; it happens a few seconds after opening the Widgets screen to find a widget, before i even have the opportunity to interact with the widget window, i have Kubuntu 24.04 The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x732f859a1be4 in QSGTexture::setFiltering(QSGTexture::Filtering) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x732f859d1543 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x732f859b94cf in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x732f859bebab in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x732f859bf502 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x732f859a67cf in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x732f859a6ca4 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x732f85a0ccbc in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x732f85a7fb51 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x732f85a1b11d in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x732f85a1c007 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x732f838db674 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x732f8309ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #17 0x732f83129c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 14 (Thread 0x732f120006c0 (LWP 3721) "latte-do:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x5bd167417880) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5bd167417880, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x732f8309b7dd in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5bd167417828, cond=0x5bd167417858) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5bd167417858, mutex=0x5bd167417828) at ./nptl/pthread_cond_wait.c:627 #5 0x732f75f1d6dd in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so #6 0x732f75efc9bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so #7 0x732f75f1d60c in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so #8 0x732f8309ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #9 0x732f83129c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 13 (Thread 0x732f556006c0 (LWP 3722) "QSGRenderThread"): #1 __futex_abstimed_wait_common (cancel=true, private=29486, abstime=0x0, clockid=0, expected=0, futex_word=0x5bd1660e0270) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5bd1660e0270, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x732f8309b7dd in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5bd1660e0220, cond=0x5bd1660e0248) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5bd1660e0248, mutex=0x5bd1660e0220) at ./nptl/pthread_cond_wait.c:627 #5 0x732f838e178c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x732f85a19b34 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x732f85a1c049 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x732f838db674 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x732f8309ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #10 0x732f83129c3c in clone3 ()
[ktorrent] [Bug 283335] UPNP gives 'internal server error' in 'port forwarded' column since upgrade to 4.7.x
https://bugs.kde.org/show_bug.cgi?id=283335 Steven V. Wilson changed: What|Removed |Added CC||funmaker...@yahoo.com --- Comment #5 from Steven V. Wilson --- This bug appears to have returned. Please reopen it. Kubuntu 23.04 Ktorrent version 23.08.1 Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485818] Crash during use of Sublimetext4
https://bugs.kde.org/show_bug.cgi?id=485818 Steven changed: What|Removed |Added CC||geconsult...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485818] Crash during use of Sublimetext4
https://bugs.kde.org/show_bug.cgi?id=485818 --- Comment #1 from Steven --- Created attachment 168694 --> https://bugs.kde.org/attachment.cgi?id=168694=edit debug report -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485818] New: Crash during use of Sublimetext4
https://bugs.kde.org/show_bug.cgi?id=485818 Bug ID: 485818 Summary: Crash during use of Sublimetext4 Classification: I don't know Product: kde Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: geconsult...@proton.me Target Milestone: --- *** 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 During the use of Sublime Text, ((Stable Channel, Build 4169)) when using the package manager of the application to perform a general search of available packages the crash was reported. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 (Wayland) Kernel: 6.1.0-20-amd64 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Application: kfmclient (2.0) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-20-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Sublimetext4 was used during the crash at the time package manager was installed and was being used to search for available packages when the crash occured. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: kfmclient (kfmclient), signal: Aborted [KCrash Handler] #4 0x7f960a8a5e2c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x7f960a856fb2 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7f960a841472 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f9609690c79 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f960aa01a9b in ?? () from /lib/x86_64-linux-gnu/libkdeinit5_kfmclient.so #9 0x7f960aa03088 in ?? () from /lib/x86_64-linux-gnu/libkdeinit5_kfmclient.so #10 0x7f960aa042c5 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_kfmclient.so #11 0x7f960a84224a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #12 0x7f960a842305 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #13 0x563407a20081 in ?? () [Inferior 1 (process 14711) detached] Reported using DrKonqi This report was filed against 'kde' because the product 'kfmclient' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #17 from Richard Steven Hack --- So I turned off "Turn Off Screen" under energy settings. Tonight after I went for a shower and other measures which took longer than 60 minutes, I came back to find the lock screen blank, wiggling the cursor did nothing. I went into virtual terminal 1 and messed around, then tried to go back to the original terminal (F7) but couldn't do it. Then I got this error message which I don't comprehend at all and don't know if it has anything to do with the blank screen issue: localhost login: [112762.275565] [T62483] amdgpu :08:00: [drm: amdgpu_ring_test_helper [amdgpu]] *ERROR ring comp_1.0.1 test failed (-110) [112762.64478211] [T5552] PM: can not get swap writer So enough fooling around, I rebooted. I doublechecked my settings for Session Suspend and Screen Locking. Session Suspend does nothing and the screen is not supposed to be turned off at all. The Screen Lock setting is 60 minutes and that worked - except it's impossible to get back from the blank screen once the mouse is wiggled. The cursor is visible but nothing else. I still haven't tried another theme. For now I'm simply going to turn off Screen Locking because I don't have time for this nonsense. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Richard Steven Hack changed: What|Removed |Added CC||richardstevenh...@gmail.com --- Comment #16 from Richard Steven Hack --- Confirmed on openSUSE Tumbleweed desktop (not laptop) latest snapshot as of this date. I'm on X11 after the Obsidian note-taking app does not work at all with Wayland. (By the way, changing to Wayland without asking was a no-no.) I had my system set to not do session suspend at all being on a desktop, but to turn off the screen and lock the screen after 60 minutes. Then I turn off the monitor at night before bed so I can sleep without waiting for the monitor to turn off itself. In the morning I turn on the monitor, wiggle the mouse and get my login screen. But the last couple days - but not EVERY day - the monitor turns on, but the screen is dark and the mouse wiggle does not have any result. Hitting escape turns the screen from gray to absolute black. I then have to switch to a virtual terminal which appears with no problem and I then log in as root and reboot. I've decided to simply switch off screen turnoff to see if that fixes the issue. I always turn off the monitor manually anyway before bed. so why bother with screen turnoff? During the day I'm usually at the machine anyway so screen turnoff is mostly a nuisance if I'm away for more than 60 minutes. Haven't tried switching themes yet to test. Might try that tonight if the Breeze Twilight theme is acceptable (no Dark theme is for me.) It's interesting that I do NOT have the problem on my second desktop which also does not use session suspend but only turns off the screen and locks the screen. Sometimes I forget to turn off that system's monitor so perhaps I just haven't seen the issue yet on that one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483939] New: Wishlist: add USB devices to Hard Disk Monitor
https://bugs.kde.org/show_bug.cgi?id=483939 Bug ID: 483939 Summary: Wishlist: add USB devices to Hard Disk Monitor Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: steven.e.friedr...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY Please add ability to monitor USB devices, such as a blu-ray player, which I am using with MakeMKV program. SOFTWARE/OS VERSIONS Linux distro: debian12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483619] Floating panel hover effect error
https://bugs.kde.org/show_bug.cgi?id=483619 --- Comment #2 from Steven Kerman --- I checked, it does and also my plasma5 theme wont appear in the global theme configuration setting page, but i can use it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483619] New: Floating panel hover effect error
https://bugs.kde.org/show_bug.cgi?id=483619 Bug ID: 483619 Summary: Floating panel hover effect error Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: steven121...@gmail.com CC: uhh...@gmail.com Target Milestone: --- Created attachment 167225 --> https://bugs.kde.org/attachment.cgi?id=167225=edit bugVideo 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 *** hover effect behavior on floating panel malfunction, it start when my mouse didn't hover. it only happen when using the new floating panel and didn't happen in plasma5.27 i upgraded from plasma 5.27 and found this bug STEPS TO REPRODUCE enable floating panel move mouse next to the panel but not on the panel OBSERVED RESULT the hover effect start + click cause open a new application EXPECTED RESULT nothing happend SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: qt6-5compat 6.6.2-2 qt6-base 6.6.2-4 qt6-declarative 6.6.2-1 qt6-doc 6.6.2-1 qt6-multimedia 6.6.2-1 qt6-multimedia-ffmpeg 6.6.2-1 qt6-positioning 6.6.2-1 qt6-quick3d 6.6.2-1 qt6-quicktimeline 6.6.2-1 qt6-sensors 6.6.2-1 qt6-shadertools 6.6.2-1 qt6-speech 6.6.2-1 qt6-svg 6.6.2-1 qt6-tools 6.6.2-2 qt6-translations 6.6.2-1 qt6-virtualkeyboard 6.6.2-2 qt6-wayland 6.6.2-1 qt6-webchannel 6.6.2-1 qt6-webengine 6.6.2-1 qt6-websockets 6.6.2-1 qt6-webview 6.6.2-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483371] X11 [AMD]: After locking, the screen goes black
https://bugs.kde.org/show_bug.cgi?id=483371 Steven Noonan changed: What|Removed |Added CC||ste...@uplinklabs.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #32 from Steven Noonan --- Tried applying the patch in the powerdevil merge request and rebuilt/installed poweredevil. From what I can tell it had no impact on either the escape key behavior or the blank lock screen render. I notice that when I get the black screen with mouse cursor, I can move the mouse over where the password field should be and it turns into the I-beam cursor, and I am able to type in the field and unlock the screen. Doing so causes it to present a few frames of what the locker *should* have been rendering before the locker exits. And I can run `kscreenlocker_greet --test` (or without `--test`) and it renders fine, so I'm not sure exactly what is causing it to render the black screen. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Steven Noonan changed: What|Removed |Added CC||ste...@uplinklabs.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478936] Unable to bind / use the calculator key in plasma 6
https://bugs.kde.org/show_bug.cgi?id=478936 --- Comment #3 from Steven Eastland --- As I mentioned in the bug I filed that was marked as a duplicate of this one, my calculator key works in an X11 session, but not in a Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 478285] New: Android phone not detected since updating to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=478285 Bug ID: 478285 Summary: Android phone not detected since updating to Plasma 6 Classification: Frameworks and Libraries Product: kio-extras Version: 24.01.80 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: MTP Assignee: unassigned-b...@kde.org Reporter: seastl...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY I can't access my phone in Plasma 6. When I plug it in in and select "File transfer / Android Auto" in the USB settings, the device notifier doesn't see it, nor is it visible in Dolphin's Places panel. It is detected by the kernel: $ lsusb Bus 001 Device 025: ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug) mtp-detect seems to think KDE has access to the device already: $ mtp-detect libmtp version: 1.1.21 Listing raw device(s) Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB). Found 1 device(s): Google Inc: Nexus/Pixel (MTP+ADB) (18d1:4ee2) @ bus 1, dev 27 Attempting to connect device(s) libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device Unable to open raw device 0 OK. I am running Arch with the latest packages installed. I'm comfortable editing config files, etc. but I don't know how or where to look for any debug output for the kio-mtp process. STEPS TO REPRODUCE 1. Plug in Android device and make it available for file transfer via MTP OBSERVED RESULT The device does not show in the device notifier or Dolphin's places panel. EXPECTED RESULT The device should be accessible in the device notifier and Dolphin's places panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel: 6.6.4-arch1-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 478283] New: Calculator key not detected on Wayland
https://bugs.kde.org/show_bug.cgi?id=478283 Bug ID: 478283 Summary: Calculator key not detected on Wayland Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 5.246.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: seastl...@gmail.com Target Milestone: --- SUMMARY The calculator/Launch(1) button on my keyboard (Microsoft Natural Ergonomic 4000) does not respond/is not detected in a Plasma 6 Wayland session. It works as expected in the X11 session. STEPS TO REPRODUCE 1. Use the Wayland session 2. Try to assign the calculator/Launch(1) button to a shortcut. OBSERVED RESULT The calculator button is not detected in a Wayland session. EXPECTED RESULT The calculator button should be detected, and execute the assigned shortcut, in my case launching KCalc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477380] debian12 says bluetooth is disabled. can't enable bluetooth in settings page
https://bugs.kde.org/show_bug.cgi?id=477380 --- Comment #3 from Steven --- The problem was missing firmware. I installed package firmware-realtek and now bluetooth works. On 11/29/23 5:51 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=477380 > > Nate Graham changed: > > What|Removed |Added > > Resolution|--- |NOT A BUG > CC||n...@kde.org > Status|REPORTED|RESOLVED > > --- Comment #1 from Nate Graham --- > Thanks for the bug report! Unfortunately I'm having a hard time figuring out > what bug is being reported here. I'd recommend posting a question at > https://discuss.kde.org/c/help/6, and hopefully the people there can help you > determine what the problem is and whether it's caused by a bug in any KDE > software. If that's determined to be the cause, please don't hesitate to come > back here, re-open this bug report, and describe what the problem was > determined to be. > > Thanks again! > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477874] New: I think all graphing functions should use a y-axis set to the max speed of the device/channel. That way, we could instantly see the percent of utilization.
https://bugs.kde.org/show_bug.cgi?id=477874 Bug ID: 477874 Summary: I think all graphing functions should use a y-axis set to the max speed of the device/channel. That way, we could instantly see the percent of utilization. Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.27 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: steven.e.friedr...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY I think all graphing functions should use a y-axis set to the max speed of the device/channel. That way, we could instantly see the percent of utilization. I am looking at Network speed on my laptop, which only uses Wi-Fi, and the graph y axis is set at lower than full speed of the channel. It looks like quite a bit of network traffic, but I think it's just heartbeat traffic. If the y axis was set at the maximum speed of the wi-fi link, we would see how insignificant the network traffic was/is. SOFTWARE/OS VERSIONS Linux/KDE Plasma: debian12 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I think all graphing functions should use a y-axis set to the max speed of the device/channel. That way, we could instantly see the percent of utilization. BTW, I love KDE widgets, including this one. I set my desktop background to black, and placed widgets for Individual Core Usage, Network speed, and Hard Disk Activity, making my desktop a dashboard showing what my computer is doing. Very useful. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477380] debian12 says bluetooth is disabled. can't enable bluetooth in settings page
https://bugs.kde.org/show_bug.cgi?id=477380 --- Comment #2 from Steven --- I fixed this by installing realtek-firmware package. On 11/29/23 5:51 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=477380 > > Nate Graham changed: > > What|Removed |Added > > Resolution|--- |NOT A BUG > CC||n...@kde.org > Status|REPORTED|RESOLVED > > --- Comment #1 from Nate Graham --- > Thanks for the bug report! Unfortunately I'm having a hard time figuring out > what bug is being reported here. I'd recommend posting a question at > https://discuss.kde.org/c/help/6, and hopefully the people there can help you > determine what the problem is and whether it's caused by a bug in any KDE > software. If that's determined to be the cause, please don't hesitate to come > back here, re-open this bug report, and describe what the problem was > determined to be. > > Thanks again! > -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477380] New: debian12 says bluetooth is disabled. can't enable bluetooth in settings page
https://bugs.kde.org/show_bug.cgi?id=477380 Bug ID: 477380 Summary: debian12 says bluetooth is disabled. can't enable bluetooth in settings page Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_bluetooth Assignee: plasma-b...@kde.org Reporter: steven.e.friedr...@gmail.com CC: now...@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 *** STEPS TO REPRODUCE 1. If bluetooth is enabled, disable it. 2. Now try to re-enable bluetooth OBSERVED RESULT Bluetooth can't be re-enabled. EXPECTED RESULT Bluetooth should be re-enabled SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: debian12 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403770] unified mailbox (folder) not update sometimes
https://bugs.kde.org/show_bug.cgi?id=403770 Steven Robbins changed: What|Removed |Added CC||st...@sumost.ca --- Comment #7 from Steven Robbins --- Bug remains in KMail Version 5.22.3 (22.12.3). I have been using kmail for years with a local imap server. The local mailbox is fed using fetchmail to retrieve mail from my ISP’s imap server. Works a treat. Recently I decided to directly add my upstream isp imap server as a second mailbox. Now I can look at emails on the upstream server directly. And there is a “Unified Mailboxes” pseudo-server that presents an aggregated view of both imap servers. The issue is that of course fetchmail is still periodically moving messages from upstream imap to local. And the unified mailboxes gets very confused. When a message gets moved (removed from upstream imap and added to local imap), I end up with two duplicate entries in “unified mailboxes” and I can’t interact properly with them. Often I can’t delete one or both copies, for example. I end up re-starting kmail a couple times a day to clear things up. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 477253] New: Request ability to select a specific HDD to monitor
https://bugs.kde.org/show_bug.cgi?id=477253 Bug ID: 477253 Summary: Request ability to select a specific HDD to monitor Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: steven.e.friedr...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- System monitor is great, specifically hard disk activity. I need to monitor a specific hdd. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 475668] File Picker Show Preview Pane Option Is Greyed Out During File Saves on Firefox
https://bugs.kde.org/show_bug.cgi?id=475668 --- Comment #1 from Richard Steven Hack --- Created attachment 162328 --> https://bugs.kde.org/attachment.cgi?id=162328=edit Picture of greyed out Show Preview Pane option in KDE File Picker -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 475668] New: File Picker Show Preview Pane Option Is Greyed Out During File Saves on Firefox
https://bugs.kde.org/show_bug.cgi?id=475668 Bug ID: 475668 Summary: File Picker Show Preview Pane Option Is Greyed Out During File Saves on Firefox Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: richardstevenh...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY *** When trying to save a file using the KDE file picker on Firefox, the Show Preview Pane option is greyed out. It cannot be clicked on to activate it and F11 does not work. This only occurs on Firefox - other KDE file dialogs are unaffected. *** STEPS TO REPRODUCE 1. Do a clean install of Firefox - do nothing to modify Firefox except use about:config to set the XDG settings to 1 to enable the KDE file picker instead of the GTK file picker. 2. Run Firefox, browse to an image file on the Internet. 3. Do a Save Page As which opens the KDE File Picker. OBSERVED RESULT The Show Preview Pane option is greyed out and neither a click nor F11 can activate it. EXPECTED RESULT The Show Preview Pane should be available for activation by a mouse click or F11. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed Snapshot 20231012 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform; X11 Processor: Ryzen 5 2600X Ram: 64GB Graphics Processor: AMD Radeon RX 550 Series Note that the Show Preview Pane option functions normally in all file save and open operations in other KDE applications. See attached photo of the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #13 from Steven --- Please take me off the CC list. Since you guys haven't and aren't bothering to fix the consistent crashes on the Samsung Tab S8 series, your emails are just spam at this point. On Sat, Sep 2, 2023, 3:12 AM Kevin Bell wrote: > https://bugs.kde.org/show_bug.cgi?id=472705 > > Kevin Bell changed: > >What|Removed |Added > > > CC||kev.b...@sky.com > > --- Comment #12 from Kevin Bell --- > > > SESSION: 02 Sep 2023 10:08:23 +0100. Executing > > /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so > > Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, > loaded: 5.15.7. Process ID: 21371 > -- -- -- -- -- -- -- -- > 02 Sep 2023 10:08:23 +0100: Style: fusion. Available styles: android, > Windows, > Fusion > 02 Sep 2023 10:08:23 +0100: Creating database from scratch (database didn't > exist, new schema version: 0.0.17). > 02 Sep 2023 10:08:55 +0100: Created image "Unnamed", 2480 * 3508 pixels, > 300 > dpi. Color model: 8-bit integer/channel RGB/Alpha > (sRGB-elle-V2-srgbtrc.icc). > Layers: 2 > 02 Sep 2023 10:15:55 +0100: Autosaving: > > /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra > 02 Sep 2023 10:15:55 +0100: Converting from application/x-krita to > application/x-krita. Location: > > /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra. > Real location: > > /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra. > Batchmode: 0. Configuration: none > 02 Sep 2023 10:15:55 +0100: Completed saving > > /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra > (mime: application/x-krita). Result: OK. Warning: . Size: 737405 > 02 Sep 2023 10:23:02 +0100: Autosaving: > > /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra > 02 Sep 2023 10:23:12 +0100: Autosaving: > > /storage/emulated/0/Android/data/org.krita.next/files/Documents/krita-backup/krita-21371-document_0-autosave.kra > 02 Sep 2023 10:23:14 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in > file > > /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, > line 820 > > KRITA DID NOT CLOSE CORRECTLY > > > SESSION: 02 Sep 2023 10:24:39 +0100. Executing > > /data/app/~~EXaVK6iK281yV29p-fTB0A==/org.krita.next-HnP8v2GoIpxUyfMa2sjgHw==/lib/arm64/libkrita_arm64-v8a.so > > Krita Version: 5.3.0-prealpha (git 27c35ad), Qt version compiled: 5.15.7, > loaded: 5.15.7. Process ID: 24240 > -- -- -- -- -- -- -- -- > 02 Sep 2023 10:24:39 +0100: Style: fusion. Available styles: android, > Windows, > Fusion > 02 Sep 2023 10:24:39 +0100: Database is up to date. Version: 0.0.17, > created by > Krita 5.3.0-prealpha, at Sat Sept 2 10:08:23 2023 > 02 Sep 2023 10:24:58 +0100: Created image "Unnamed", 2480 * 3508 pixels, > 300 > dpi. Color model: 8-bit integer/channel RGB/Alpha > (sRGB-elle-V2-srgbtrc.icc). > Layers: 2 > 02 Sep 2023 10:25:19 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in > file > > /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, > line 820 > 02 Sep 2023 10:26:14 +0100: SAFE ASSERT (krita): "result.isNull() || > m_d->containsOriginal(key)" in file > > /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp, > line 193 > 02 Sep 2023 10:26:23 +0100: SAFE ASSERT (krita): "result.isNull() || > m_d->containsOriginal(key)" in file > > /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/resources/KisResourceThumbnailCache.cpp, > line 193 > 02 Sep 2023 10:26:54 +0100: SAFE ASSERT (krita): "!m_d->readyShortcut" in > file > > /home/user/workspace/Krita_Nightly_Android_arm64-v8a_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, > line 820 > > KRITA DID NOT CLOSE CORRECTLY > > > SESSION: 02 Sep 2023 10:27:56 +0100. Executing > > /data/app/~~EXaVK6iK281y
[krita] [Bug 472705] 5.2 Beta 1 Android: App crashes shortly after transforming multiple layers or at random moments
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #11 from Steven --- Hi. My name is Steven. I use a Galaxy Tab S8 Plus, I can screen record my Krita crashing and I can run you through from setup to crashing and show you each instance within an hour video. Would you like me to go ahead and do that for you? I can have it to you quickly and promptly the moment you send me a reply to this email and just let me know where you would like me to upload it to so that the nightly Bill Developers may be able to correct this problem as I love working in Krita but this crashing is just ridiculous, lol. :-) On Sun, Aug 20, 2023, 8:41 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=472705 > > --- Comment #10 from abh...@gmail.com --- > Hi Freya, tough to say when it incurred cuz i didn't saved the last nightly > that worked. A large window if this help is that it started before merging > of > neq qt. And after that check box for layer selection was added. Not sure if > this helps. Layer selection was working wonderfully > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472993] New: Galaxy Tab s8 plus crash when doing anything after 5.2 beta update
https://bugs.kde.org/show_bug.cgi?id=472993 Bug ID: 472993 Summary: Galaxy Tab s8 plus crash when doing anything after 5.2 beta update Classification: Applications Product: krita Version: unspecified Platform: Android OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: adventuresindraw...@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 *** STEPS TO REPRODUCE 1. Doing anything causes random crashes within minutes 2. No change in settings fixes crashes 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 471514] Need a plasma widget to display progress of data transfer between devices, i.e., usb to/from hdd, etc
https://bugs.kde.org/show_bug.cgi?id=471514 --- Comment #1 from Steven --- I would like to see widgets that display a graph of transfer speed, like Winblows. The y-axis should be the transfer speed of the channel, i.e., SATA-1 is 150 MB/s, SATA-2 is 300 MB/s, and SATA-3 is 600 MB/s. USB 1.0 low speed is 192 kB/s, USB 1.0 full speed is 1.5 MB/s, USB 2.0 high speed is 60 MB/s, USB 3.0 SuperSpeed (aka USB 3.1 Gen 1) is 500 MB/s, USB 3.1 SuperSpeed+ (aka USB 3.1 Gen 2) is 1.212 GB/s, USB 3.2 SuperSpeed+[66] (aka USB 3.2 Gen 2×2) is 2.424 GB/s, USB4 Gen 3×2 is 4.8 GB/s, USB4 Gen 4×2 is 9.6 GB/s. These values taken from: https://en.wikipedia.org/wiki/List_of_interface_bit_rates#Peripheral I would hope the device driver can detect the max capability of a channel, i.e., most usb-a to usb-c cables are only wired for usb 2.0 speeds. Can the driver detect usb 3.0 speed cables? usb 3.1 cables?, etc. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 472102] New: Crash while cropping
https://bugs.kde.org/show_bug.cgi?id=472102 Bug ID: 472102 Summary: Crash while cropping Classification: Applications Product: gwenview Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: sw...@world.std.com Target Milestone: --- Application: gwenview (22.12.3) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.3.8-100.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Ctrl-C is my shortcut for crop Ctrl-C -> set crop region -> reset -> (region vanished, so) Ctrl-C -> crash The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 0x7fbd26aafe5c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7fbd26a5fa76 in raise () from /lib64/libc.so.6 #6 0x7fbd26a497fc in abort () from /lib64/libc.so.6 #7 0x7fbd26ca2b37 in __gnu_cxx::__verbose_terminate_handler() [clone .cold] () from /lib64/libstdc++.so.6 #8 0x7fbd26cae44c in __cxxabiv1::__terminate(void (*)()) () from /lib64/libstdc++.so.6 #9 0x7fbd26cae4b7 in std::terminate() () from /lib64/libstdc++.so.6 #10 0x7fbd26caf1e5 in __cxa_pure_virtual () from /lib64/libstdc++.so.6 #11 0x7fbd2830f717 in QtPrivate::intersect_rect(QGraphicsItem const*, QRectF const&, Qt::ItemSelectionMode, QTransform const&, void const*) () from /lib64/libQt5Widgets.so.5 #12 0x7fbd283104c2 in QGraphicsSceneIndexPrivate::recursive_items_helper(QGraphicsItem*, QRectF, bool (*)(QGraphicsItem const*, QRectF const&, Qt::ItemSelectionMode, QTransform const&, void const*), QList*, QTransform const&, Qt::ItemSelectionMode, double, void const*) const () from /lib64/libQt5Widgets.so.5 #13 0x7fbd28310404 in QGraphicsSceneIndexPrivate::recursive_items_helper(QGraphicsItem*, QRectF, bool (*)(QGraphicsItem const*, QRectF const&, Qt::ItemSelectionMode, QTransform const&, void const*), QList*, QTransform const&, Qt::ItemSelectionMode, double, void const*) const () from /lib64/libQt5Widgets.so.5 #14 0x7fbd28310404 in QGraphicsSceneIndexPrivate::recursive_items_helper(QGraphicsItem*, QRectF, bool (*)(QGraphicsItem const*, QRectF const&, Qt::ItemSelectionMode, QTransform const&, void const*), QList*, QTransform const&, Qt::ItemSelectionMode, double, void const*) const () from /lib64/libQt5Widgets.so.5 #15 0x7fbd28310cdc in QGraphicsSceneIndex::items(QRectF const&, Qt::ItemSelectionMode, Qt::SortOrder, QTransform const&) const () from /lib64/libQt5Widgets.so.5 #16 0x7fbd282e7dd8 in QGraphicsScene::items(QRectF const&, Qt::ItemSelectionMode, Qt::SortOrder, QTransform const&) const () from /lib64/libQt5Widgets.so.5 #17 0x7fbd28319f6b in QGraphicsView::items(QPoint const&) const () from /lib64/libQt5Widgets.so.5 #18 0x7fbd282cd0e8 in QGraphicsItem::setCursor(QCursor const&) () from /lib64/libQt5Widgets.so.5 #19 0x7fbd282cc16c in QGraphicsItem::sceneEvent(QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7fbd282f1ff2 in QGraphicsScenePrivate::setFocusItemHelper(QGraphicsItem*, Qt::FocusReason, bool) () from /lib64/libQt5Widgets.so.5 #21 0x7fbd28300dc1 in QGraphicsScene::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7fbd27faed72 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7fbd2729d618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x7fbd282f1e2b in QGraphicsScene::setFocus(Qt::FocusReason) () from /lib64/libQt5Widgets.so.5 #25 0x7fbd282f2159 in QGraphicsScenePrivate::setActivePanelHelper(QGraphicsItem*, bool) () from /lib64/libQt5Widgets.so.5 #26 0x7fbd282d50b4 in QGraphicsItemPrivate::setParentItemHelper(QGraphicsItem*, QVariant const*, QVariant const*) () from /lib64/libQt5Widgets.so.5 #27 0x7fbd282d53a3 in QGraphicsItem::setParentItem(QGraphicsItem*) () from /lib64/libQt5Widgets.so.5 #28 0x7fbd2905fdf5 in Gwenview::RasterImageView::setCurrentTool(Gwenview::AbstractRasterImageViewTool*) () from /lib64/libgwenviewlib.so.5 #29 0x55855f1af372 in Gwenview::ImageOpsContextManagerItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.0] () #30 0x7fbd272d114f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #31 0x7fbd27fa8306 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #32 0x7fbd27faafc3 in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #33 0x7fbd27fabb9d in QAction::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #34 0x7fbd27faed72 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from
[kdeplasma-addons] [Bug 471514] New: Need a plasma widget to display progress of data transfer between devices, i.e., usb to/from hdd, etc
https://bugs.kde.org/show_bug.cgi?id=471514 Bug ID: 471514 Summary: Need a plasma widget to display progress of data transfer between devices, i.e., usb to/from hdd, etc Classification: Plasma Product: kdeplasma-addons Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: steven.e.friedr...@gmail.com Target Milestone: --- SUMMARY KDE's Dolphin will show MiB/s, but doesn't send a notification detailing max speed, min speed, avg speed. A widget displaying transfer speed, like the network speed widget would be helpful. What is the transfer speed from my usb device to my hdd/ssd? A widget that displays that info and issues a notification indicating statistics would be much appreciated. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464693] Dolphin does not open with the previous tabs when launched by an external app (via 'Show in the folder' or 'Open containing folder')
https://bugs.kde.org/show_bug.cgi?id=464693 Steven Eastland changed: What|Removed |Added CC||seastl...@gmail.com --- Comment #3 from Steven Eastland --- This is also happening to me. My observations: I have "Show on startup: Folders, tabs, add window state from last time" selected. After closing Dolphin: * Opening it again from a pinned entry in the Icons-Only Task Manager does not remember the last tabs. * Restoring it after login from a saved session does not remember the last tabs. * Opening it again using the Meta+E shortcut DOES remember the last tabs. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.2-arch1-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 469356] New: KMail crashed while configuring email account
https://bugs.kde.org/show_bug.cgi?id=469356 Bug ID: 469356 Summary: KMail crashed while configuring email account Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: free...@twc.com CC: c...@carlschwan.eu Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: FreeBSD 13.2-RELEASE amd64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: The REAL issue is mail.twc.com was sold to Charter Communications and they didn't fix their certificates. The crash can be reproduced every time. -- Backtrace: Application: Account Assistant (accountwizard), signal: Segmentation fault (lldb) process attach --pid 54118 (lldb) settings set term-width 200 (lldb) thread info (lldb) bt all Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468817] Screen energy saving causes multiple problems when waking up
https://bugs.kde.org/show_bug.cgi?id=468817 --- Comment #4 from Steven A. Falco --- Created attachment 158401 --> https://bugs.kde.org/attachment.cgi?id=158401=edit After waking monitors Note that one Desktop window has disappeared and the backround is now just plain black. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468817] Screen energy saving causes multiple problems when waking up
https://bugs.kde.org/show_bug.cgi?id=468817 --- Comment #3 from Steven A. Falco --- Created attachment 158400 --> https://bugs.kde.org/attachment.cgi?id=158400=edit windows before sleeping Two desktop windows, proper desktop background. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468817] Screen energy saving causes multiple problems when waking up
https://bugs.kde.org/show_bug.cgi?id=468817 --- Comment #2 from Steven A. Falco --- I opened the kwin debug window before letting the screens go to sleep. At that point it shows two X11 Desktop windows - one for the 2560x1600 monitor and one for the 1920x1080 monitor. I then let the screens go to sleep and then woke them back up. At that point I only have one X11 Desktop window for the 2560x1600 monitor. So it looks like the one for the 1920x1080 monitor has died. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468817] New: Screen energy saving causes multiple problems when waking up
https://bugs.kde.org/show_bug.cgi?id=468817 Bug ID: 468817 Summary: Screen energy saving causes multiple problems when waking up Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: stevenfa...@gmail.com Target Milestone: --- SUMMARY I have a two monitor desktop. I enabled "screen energy savings" but when I move the mouse to wake up the monitors, I can no longer click on anything. The task bar no longer responds, nor do any of the other panel buttons. I can drag a window around, so the mouse isn't completely dead, but the window leaves trails of partial images as I drag it around. Also, the background on the secondary monitor becomes black, rather than the picture I had set as the background. I'm not able to log out using the panel buttons, since they cannot be clicked. However, I can switch to a virtual tty and kill the session. That brings me back to the SDDM screen, and when I log in everything is back to normal. STEPS TO REPRODUCE 1. Enable screen energy saving 2. Wait until the monitors turn off 3. Move the mouse to wake the monitors OBSERVED RESULT As described above EXPECTED RESULT Normal waking of the monitors and desktop fully functional SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I'm using the X11 graphics platform. Video card is AMD Radeon Pro W6600. The primary monitor is connected via Display Port and is an HP ZR30w (2560x1600). The secondary monitor is connected via a Display Port to HDMI adapter and is an ASUS VA24E (1920x1080). I'll be happy to provide whatever additional information is needed to solve this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #45 from Steven C. Buttgereit --- (In reply to Fabian Vogt from comment #44) > I had a similar issue today in the wayland session with virtio: There was no > offset at the origin (top left), but the X and Y offset increased towards > the opposite edges, as if there was some broken scale factor involved. > > Resizing the VM window triggered a resolution change and the issue > disappeared. I tried this workaround using my setup, which is fairly different to yours, and it did not work there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 Steven C. Buttgereit changed: What|Removed |Added CC||bugs.kde@musesystems.co ||m --- Comment #43 from Steven C. Buttgereit --- I'll add another anecdote that I'm seeing this issue as well on Fedora 37 under VMWare Workstation 16 on a Windows host. Recently I got a kernel upgrade from a 6.1 version to 6.2 and I started seeing the issue with that update. If I boot the system using the previous 6.1 kernel using Grub2, then the problem goes away and everything works fine; I only see the problem using the 6.2 kernel. Not Working System Info: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.7-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × Intel® Xeon® CPU E5-2630 v4 @ 2.20GHz Memory: 62.8 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; Manufacturer: VMware, Inc. Product Name: VMware Virtual Platform System Version: None Working System Info: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × Intel® Xeon® CPU E5-2630 v4 @ 2.20GHz Memory: 62.8 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; Manufacturer: VMware, Inc. Product Name: VMware Virtual Platform System Version: None If there's any other information I can provide I'd be happy to do so. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463225] Akonadi server crashed when switching user
https://bugs.kde.org/show_bug.cgi?id=463225 --- Comment #4 from Steven Danderson --- Created attachment 156740 --> https://bugs.kde.org/attachment.cgi?id=156740=edit New crash information added by DrKonqi akonadiserver (5.22.2 (22.12.2)) using Qt 5.15.8 I was closing KPatience. The screen went totally black. The the desktop returned; first the wallpaper, then the taskbar. -- Backtrace (Reduced): #4 0x55a901bac29b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f32594c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f325949d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f32594a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f32594eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463225] Akonadi server crashed when switching user
https://bugs.kde.org/show_bug.cgi?id=463225 Steven Danderson changed: What|Removed |Added CC||danderson.ste...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #151 from Steven Robbins --- (In reply to Nate Graham from comment #146) > I suspect this has been fixed by the fix for Bug 462725. > > Anybody who can reproduce the issue and build software from source: can you > patch KWin with 1d237c29655c7e3fb15fb9b71e5f167bd207593f Very happy to report that patch (applied to 5.27.0 libkscreen as delivered in Debian sid) fixes the symptoms I've been experiencing -- namely that hot disconnect / reconnect of a monitor failed to enable it. Thank you to the KDE screen team!! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #134 from Steven Robbins --- (In reply to brian from comment #133) > I was surprised tonight that after upgrading to 5.27.0 Just upgraded my system to 5.27.0 today (Debian Sid) and sadly I have to report that the unplug/re-plug issue remains. Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-9900K CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 --- Comment #11 from Steven Robbins --- On Monday, February 6, 2023 10:36:43 A.M. CST you wrote: > https://bugs.kde.org/show_bug.cgi?id=464334 > > Nate Graham changed: > >What|Removed |Added > > Resolution|BACKTRACE |WORKSFORME > Status|NEEDSINFO |RESOLVED > > --- Comment #10 from Nate Graham --- > Then there's no way for us to investigate and fix this issue, sorry. :/ It would be good to at least document in this bug whether any developer even attempted to replicate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 --- Comment #9 from Steven Robbins --- On Saturday, February 4, 2023 10:04:50 P.M. CST you wrote: > https://bugs.kde.org/show_bug.cgi?id=464334 > > Nate Graham changed: > >What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #8 from Nate Graham --- > Thanks! Unfortunately what we need is likely in here: > > #6 0x5643da751644 in ?? () > #7 0x5643da76c4cf in ?? () > > Can you install debug symbols for Plasma and KScreen and get a new > backtrace? No, sorry. There's something goofy with the KDE neon DVD. It takes literally 30+ minutes to boot and makes my DVD drive sound like it's going to break. I'm not doing this a third time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 Steven Robbins changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Steven Robbins --- Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=140269930528384) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f932361be80 (LWP 2462))] (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=140269930528384) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=140269930528384) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140269930528384, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f932788d476 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #4 0x7f9329f4105d in KCrash::defaultCrashHandler(int) () from /lib/x86_64-linux-gnu/libKF5Crash.so.5 #5 #6 0x5643da751644 in ?? () #7 0x5643da76c4cf in ?? () #8 0x7f9327f910d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f9327f9515e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9327f869ff in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f9328c61793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f9327f5907a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f9327fb1e0b in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f9327fb2754 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f93268f5d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f932694a6c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f93268f33e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f9327fb2ad8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f9327f5799b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f9327f5ff34 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x5643da73fa8b in ?? () #22 0x7f9327874d90 in __libc_start_call_main (main=main@entry=0x5643da73eb70, argc=argc@entry=2, argv=argv@entry=0x7fff45400258) at ../sysdeps/nptl/libc_start_call_main.h:58 #23 0x7f9327874e40 in __libc_start_main_impl (main=0x5643da73eb70, argc=2, argv=0x7fff45400258, init=, fini=, rtld_fini=, stack_end=0x7fff45400248) at ../csu/libc-start.c:392 #24 0x5643da73fbb5 in ?? () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 Steven Robbins changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Steven Robbins --- As noted initially, the kde neon boot disc did not provide a backtrace. However, the steps to reproduce are trivial enough that I expect the developer is able to get the backtrace themselves. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 --- Comment #2 from Steven Robbins --- On Sunday, January 15, 2023 12:31:12 P.M. CST you wrote: > https://bugs.kde.org/show_bug.cgi?id=464334 > > Nate Graham changed: > >What|Removed |Added > > Status|REPORTED|NEEDSINFO > CC||n...@kde.org > Resolution|--- |BACKTRACE > > --- Comment #1 from Nate Graham --- > Can you attach a backtrace of the creah please? According to the crash handler, there was no usable backtrace. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #109 from Steven Robbins --- (In reply to Steven Robbins from comment #108) > (In reply to Brian Cohen from comment #105) > > > so I probably need to first install Neon Stable and verify > > that I can reproduce the problem there as a baseline. > > That sounds like a good idea. I tried last night with Neon "User Edition", > however, and failed to trigger the bug. Wondering what your experience was. Despite not being able to reproduce the problem with "user edition", I tried the experiment (disconnecting one monitor via an HDMI switch; see comment 81) using "unstable edition". I discovered a crash in plasmashell if the monitor is Primary (bug 464334). But the monitor WAS re-enabled when reconnected. It's unclear what this proves given that that I was unable to reproduce the bug in the older "user edition" KDE neon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] New: Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 Bug ID: 464334 Summary: Plasmashell crash when primary monitor disconnected Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: st...@sumost.ca Target Milestone: 1.0 SUMMARY *** Plasmashell crash when primary monitor (of a two monitor system) disconnected. Discovered this while using KDE Neon 20230115-1117 in attempt to test bug 460341. Sadly, there was no usable backtrace - but the crash handler indicated that PlasmaShell crashed with seg fault. *** STEPS TO REPRODUCE 1. Attach two monitors. 2. Boot KDE Neon 20230115-1117 live image - both monitors are enabled 3. Disconnect the primary monitor (using an HDMI switch) OBSERVED RESULT Crash handler reported that plasmashell exited with segfault. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 20230115-1117 live ISO image ADDITIONAL INFORMATION I switched the primary to the other monitor and repeated. There was no crash in the situation that the "non primary" monitor was the one disconnected. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #108 from Steven Robbins --- (In reply to Brian Cohen from comment #105) > so I probably need to first install Neon Stable and verify > that I can reproduce the problem there as a baseline. That sounds like a good idea. I tried last night with Neon "User Edition", however, and failed to trigger the bug. Wondering what your experience was. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] No folder or file icons are shown
https://bugs.kde.org/show_bug.cgi?id=462307 Steven <4spuds+...@gmail.com> changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #9 from Steven <4spuds+...@gmail.com> --- (In reply to Steven from comment #7) > I'm also having incorrect rendering behavior in krusader v2.8.0 on > debian/bookworm. > I have a 4k screen, so global scaling is set at 150% and font rendering DPI > is set at 192. > > Interestingly, the Icons are being rendered as if the line height isn't > scaled, because what is see is the bottom ½ of the icons rendered on the top > ½ of the line if that makes sense. In other words, it looks like the icon > is shifted up by 50% and the top portion gets cut off. > > I can also confirm that setting the scaling back to 100% fixes the rendering > in the file/folder frame, but then of course the action buttons across the > top get too small to see/use. > > QT_SCREEN_SCALE_FACTORS=eDP-1=1.5;DP-1=1.5;HDMI-1=1.5;DP-2=1.5;DP-3=1.5;DP- > 4=1.5;DP-5=1.5;eDP-1-2=1.5;DP-1-6=1.5;DP-1-7=1.5;HDMI-1-2=1.5;DP-1-8=1.5; > QT_AUTO_SCREEN_SCALE_FACTOR=0 > > Global Scaling 150% > Force Font DPI = 192 > > KDE Plasma v5.26.4 > KDE Framework v5.101.0 > QT v5.15.6 (In reply to Bug Janitor Service from comment #6) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! Status -> CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] No folder or file icons are shown
https://bugs.kde.org/show_bug.cgi?id=462307 --- Comment #8 from Steven <4spuds+...@gmail.com> --- Created attachment 154784 --> https://bugs.kde.org/attachment.cgi?id=154784=edit Screenshot with incorrect icon rendering Incorrect icon rendering at 150% scaling. Interestingly, the active panel renders the bottom ½ of the icon and the inactive panel renders the top ½. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] No folder or file icons are shown
https://bugs.kde.org/show_bug.cgi?id=462307 Steven <4spuds+...@gmail.com> changed: What|Removed |Added CC||4spuds+...@gmail.com --- Comment #7 from Steven <4spuds+...@gmail.com> --- I'm also having incorrect rendering behavior in krusader v2.8.0 on debian/bookworm. I have a 4k screen, so global scaling is set at 150% and font rendering DPI is set at 192. Interestingly, the Icons are being rendered as if the line height isn't scaled, because what is see is the bottom ½ of the icons rendered on the top ½ of the line if that makes sense. In other words, it looks like the icon is shifted up by 50% and the top portion gets cut off. I can also confirm that setting the scaling back to 100% fixes the rendering in the file/folder frame, but then of course the action buttons across the top get too small to see/use. QT_SCREEN_SCALE_FACTORS=eDP-1=1.5;DP-1=1.5;HDMI-1=1.5;DP-2=1.5;DP-3=1.5;DP-4=1.5;DP-5=1.5;eDP-1-2=1.5;DP-1-6=1.5;DP-1-7=1.5;HDMI-1-2=1.5;DP-1-8=1.5; QT_AUTO_SCREEN_SCALE_FACTOR=0 Global Scaling 150% Force Font DPI = 192 KDE Plasma v5.26.4 KDE Framework v5.101.0 QT v5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #95 from Steven Robbins --- (In reply to Nate Graham from comment #94) > No KDE developer has been able to reproduce this issue, so Martin was not > able to determine if that work fixes it or not. > > Any of you who are experiencing this issue, if you could test it, that would > be lovely. You'll have to be using unstable/git master packages from your > distro, or Neon Unstable, or openSUSE Krypton. Or you'll have to compile a > Plasma session from source code yourself. I'm willing to give it a go. My distro (Debian) doesn't have 5.27 packages yet so it would be me compiling them. Can you point me to a list of packages that I would need to build? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341
--- Comment #92 from Steven Robbins ---
I've made some progress on this issue -- at least for my case, which is
switching the monitor between two computers (see comment #81).
With debug logging [1] I was able to immediately see that when the monitor was
connected, it was marked as disabled in the configuration received. I made a
straightforward change to KScreenDaemon::configChanged() that simply forces all
connected outputs to be enabled. In version 5.26.4 this looks as follows; I
added the lines marked **:
void KScreenDaemon::configChanged()
{
qCDebug(KSCREEN_KDED) << "Change detected";
m_monitoredConfig->log();
qCDebug(KSCREEN_KDED) << " -- after log";
// Modes may have changed, fix-up current mode id
bool changed = false;
const auto outputs = m_monitoredConfig->data()->outputs();
for (const KScreen::OutputPtr : outputs) {
**if (output->isConnected())
**output->setEnabled(true);
I don't understand the configuration mechanism well -- specifically I don't
know what module is generating the configuration after connecting the monitor
so I would bet that the above change is not suitable in general. However, it
fixes my itch so I thought I'd share it here.
[1] https://community.kde.org/Solid/Projects/ScreenManagement
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #83 from Steven Robbins --- Created attachment 154554 --> https://bugs.kde.org/attachment.cgi?id=154554=edit Steve's kscreen-console bug output for two working monitors For completeness, here's the working output -- both monitors enabled. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #82 from Steven Robbins --- Created attachment 154553 --> https://bugs.kde.org/attachment.cgi?id=154553=edit Steve's kscreen-console bug output for one monitor connected For comparison, here is "kscreen-console bug" output for the situation where I've switched the one monitor to the second computer. In other words, this is the legitimate "one monitor connected" situation. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 Steven Robbins changed: What|Removed |Added CC||st...@sumost.ca --- Comment #81 from Steven Robbins --- Created attachment 154552 --> https://bugs.kde.org/attachment.cgi?id=154552=edit Steve's kscreen-console bug output for one monitor I think this is the same issue, but did not see my symptoms described. I use an NVIDIA card, two monitors. One of the monitors is switched between this machine and another. Have been using this setup for ages. Prior to October, when I switch the monitor to the other machine, KDE notices and automatically puts all windows on one screen; then, when I switch the monitor back KDE notices and uses both screens. Since October, KDE does notice when I switch from 1 monitor to 2: In the "Display Configuration" section of System Settings, I can see the second monitor present, but the "Enabled" button is UNchecked. I need to manually check it, then apply --> then the two-monitor configuration is restored. Happens 100% of the time when I switch the monitor. Attached is the "kscreen-console bug" output for the broken configuration: both monitors connected, but one is not enabled. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379860] Kontact inconify does not iconify, it minimizes
https://bugs.kde.org/show_bug.cgi?id=379860 Steven changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- CC||steven.che...@gmail.com --- Comment #2 from Steven --- can confirm this behaviour still persist with KDE 5.25.5 and Kontact 5.21.1 there is also a old report at https://bugs.kde.org/show_bug.cgi?id=311666 hope it will be fixed. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 461356] New: How To Borrow Money From Cash App For Managing Your Needs?
https://bugs.kde.org/show_bug.cgi?id=461356 Bug ID: 461356 Summary: How To Borrow Money From Cash App For Managing Your Needs? Classification: Applications Product: akregator Version: 5.21.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: paulilauli...@gmail.com Target Milestone: --- Are you suffering from some problems encountered during the course of taking a loan on Cash App? It may happen due to the lack of information about How To Borrow Money From Cash App. So, you have to first learn the required source of information and then implement the required steps and instructions get a loan on Cash App without any kind of trouble. In case of any hassle regarding the same, you should place a call at the helpline number that remains active all the time. https://www.emailsupport-contact.com/blog/how-to-borrow-money-from-cash-app/ -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461227] New: KDE Connect crash when click on virtual monitor button
https://bugs.kde.org/show_bug.cgi?id=461227 Bug ID: 461227 Summary: KDE Connect crash when click on virtual monitor button Classification: Applications Product: kdeconnect Version: 22.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: steven.che...@gmail.com Target Milestone: --- Application: kdeconnectd (22.08.1) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.5-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: fir time seems to work, second time sometime crash. repeated clicking is guaranteed to crash. the other side is a windows 11 pc with no vnc installed so when it work there is a pop-up ask me which app to open vnc link. The crash can be reproduced sometimes. -- Backtrace: Application: KDE Connect 守护进程 (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x0020 in ?? () #5 0x7fa52c6da063 in VirtualMonitorPlugin::stop() () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_virtualmonitor.so #6 0x7fa52c6dc520 in VirtualMonitorPlugin::requestVirtualMonitor() () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_virtualmonitor.so #7 0x7fa52c6dd930 in VirtualMonitorPlugin::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_virtualmonitor.so #8 0x7fa5413920bb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5 #9 0x7fa541395f66 in QDBusConnectionPrivate::activateCall(QObject*, int, QDBusMessage const&) [clone .part.0] () from /lib64/libQt5DBus.so.5 #10 0x7fa54139653e in QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&, QDBusMessage const&, int) () from /lib64/libQt5DBus.so.5 #11 0x7fa541398a0c in QDBusActivateObjectEvent::placeMetaCall(QObject*) () from /lib64/libQt5DBus.so.5 #12 0x7fa5408d2c44 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7fa5415aed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7fa5408a81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7fa5408ab534 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #16 0x7fa5408f9537 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #17 0x7fa53ede5faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7fa53ee3b2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #19 0x7fa53ede3940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7fa5408f902a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7fa5408a6c1a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7fa5408aece2 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #23 0x55d747022106 in main () [Inferior 1 (process 13725) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 458452] Discover crashes when browsing or checking installed apps
https://bugs.kde.org/show_bug.cgi?id=458452 --- Comment #5 from Steven --- (In reply to Nate Graham from comment #4) > I'm afraid that's not a backtrace. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. Ah my fault! Sorry still new to this, I read over carefully and I believe I have it here: (gdb) backtrace #0 0x7fffa47d1b67 in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #1 0x7fffa47db7dc in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #2 0x76223e86 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #3 0x772701a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #4 0x7620017a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #5 0x76200c79 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #6 0x76247558 in () at /usr/lib/libQt5Core.so.5 #7 0x74a9cf13 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #8 0x74af30d9 in () at /usr/lib/libglib-2.0.so.0 #9 0x74a9a485 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #10 0x7624b45a in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x761f845b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #12 0x76203ba7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #13 0x55568950 in () #14 0x75bb7b25 in __libc_start_main () at /usr/lib/libc.so.6 #15 0x5556931e in () (gdb) Quit -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 458452] Discover crashes when browsing or checking installed apps
https://bugs.kde.org/show_bug.cgi?id=458452 --- Comment #2 from Steven --- Nate,Thank you for your help, I'm at a loss but hopefully it's an easy fix! I ran it through the konsole once and the crash app automade a backtrace, hope it helps! On Tuesday, August 30, 2022 at 03:42:23 PM CDT, Nate Graham wrote: https://bugs.kde.org/show_bug.cgi?id=458452 Nate Graham changed: What |Removed |Added Resolution|--- |BACKTRACE CC| |n...@kde.org Status|REPORTED |NEEDSINFO --- Comment #1 from Nate Graham --- Hello Steven! Just to set expectations accordingly, this is a bug tracker, not a user support channel. So we can investigate the bug and fix it, but I can't guarantee that you personally will experience it being fixed soon. See https://community.kde.org/Get_Involved/Issue_Reporting#Have_realistic_expectations. That said, we'll be happy to help investigate the bug! To proceed, we need a backtrace of the crash. Can you attach one? If you're not familiar with the process for how to do so, see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 458452] New: Discover crashes when browsing or checking installed apps
https://bugs.kde.org/show_bug.cgi?id=458452 Bug ID: 458452 Summary: Discover crashes when browsing or checking installed apps Product: Discover Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: stvnw...@yahoo.com CC: aleix...@kde.org Target Milestone: --- Created attachment 151673 --> https://bugs.kde.org/attachment.cgi?id=151673=edit Backlog for the crash SUMMARY I have trouble using Discover because it constantly crashes. I get the same error message when it starts "Error updating appstream2" and it always eventually crashes. Im pretty new to Linux and cant find a solution, please help! STEPS TO REPRODUCE 1. Open Discover 2. Click 'Installed' OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Steam OS 3.3 (Steam Deck) (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 457423] New: Kgpg crash on start up
https://bugs.kde.org/show_bug.cgi?id=457423 Bug ID: 457423 Summary: Kgpg crash on start up Product: kgpg Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: steven.che...@gmail.com Target Milestone: --- Application: kgpg (22.04.1) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.13-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Kgpg crashed on a cold start. crash message appear after login and splash screen. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KGpg (kgpg), signal: Aborted [KCrash Handler] #4 0x7ff5be816c4c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7ff5be7c69c6 in raise () from /lib64/libc.so.6 #6 0x7ff5be7b07f4 in abort () from /lib64/libc.so.6 #7 0x7ff5bd7b7c92 in _dbus_abort.cold () from /lib64/libdbus-1.so.3 #8 0x7ff5bd7de810 in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3 #9 0x7ff5c00f8871 in QDBusConnectionPrivate::getNameOwnerNoCache(QString const&) () from /lib64/libQt5DBus.so.5 #10 0x7ff5c00fab3b in QDBusConnectionPrivate::addSignalHook(QString const&, QDBusConnectionPrivate::SignalHook const&) () from /lib64/libQt5DBus.so.5 #11 0x7ff5c00fbac1 in QtPrivate::QSlotObject, bool>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libQt5DBus.so.5 #12 0x7ff5beeb22c4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7ff5bee8820b in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7ff5bee8b594 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #15 0x7ff5beed9467 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #16 0x7ff5bcda6faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x7ff5bcdfc2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #18 0x7ff5bcda4940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x7ff5beed8f5a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7ff5bee86c7a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7ff5becc718a in QThread::exec() () from /lib64/libQt5Core.so.5 #22 0x7ff5c00e5b1b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #23 0x7ff5becc8487 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #24 0x7ff5be814e2d in start_thread () from /lib64/libc.so.6 #25 0x7ff5be89a1b0 in clone3 () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff5ac040640 (LWP 2315) "QXcbEventQueue"): #1 0x7ff5bd785fba in _xcb_conn_wait.part.0 () from /lib64/libxcb.so.1 #2 0x7ff5bd78794c in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7ff5ac17ce61 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7ff5becc8487 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7ff5be814e2d in start_thread () from /lib64/libc.so.6 #6 0x7ff5be89a1b0 in clone3 () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff5b9845980 (LWP 2165) "kgpg"): #1 0x7ff5becca30b in QSemaphore::acquire(int) () from /lib64/libQt5Core.so.5 #2 0x7ff5beebb9b9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #3 0x7ff5c0142897 in QDBusConnectionPrivate::signalNeedsConnecting(QString const&, QDBusConnectionPrivate::SignalHook const&) () from /lib64/libQt5DBus.so.5 #4 0x7ff5c00f006a in QDBusConnectionPrivate::connectRelay(QString const&, QString const&, QString const&, QDBusAbstractInterface*, QMetaMethod const&) () from /lib64/libQt5DBus.so.5 #5 0x7ff5beeb36b2 in QMetaObjectPrivate::connect(QObject const*, int, QMetaObject const*, QObject const*, int, QMetaObject const*, int, int*) () from /lib64/libQt5Core.so.5 #6 0x7ff5beeb7047 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /lib64/libQt5Core.so.5 #7 0x7ff5ab5af0f7 in QIBusPlatformInputContext::connectToContextSignals() () from /usr/lib64/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so #8 0x7ff5ab5b3442 in QIBusPlatformInputContext::connectToBus() () from /usr/lib64/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so #9 0x7ff5beebba4f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7ff5beebec5e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #11 0x7ff5beeb2155 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7ff5bf943d22 in
[digikam] [Bug 457347] fix crash in qtav libavfilter with FFMPEG 5
https://bugs.kde.org/show_bug.cgi?id=457347 --- Comment #1 from Steven Robbins --- Note: I followed the ffmeg example code to implement fix. See https://ffmpeg.org/doxygen/trunk/opt__common_8c_source.html#l00788 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457347] New: fix crash in qtav libavfilter with FFMPEG 5
https://bugs.kde.org/show_bug.cgi?id=457347 Bug ID: 457347 Summary: fix crash in qtav libavfilter with FFMPEG 5 Product: digikam Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Preview-Video Assignee: digikam-bugs-n...@kde.org Reporter: st...@sumost.ca Target Milestone: --- Created attachment 151031 --> https://bugs.kde.org/attachment.cgi?id=151031=edit bug fix SUMMARY When built using FFMPEG 5, the current git master/HEAD crashes while running tests/video/qtav/tests/codecslist. Stack trace: Thread 1 "qtav-codecslist" received signal SIGSEGV, Segmentation fault. 0x73b82cf9 in av_filter_iterate () from /lib/x86_64-linux-gnu/libavfilter.so.8 (gdb) bt #0 0x73b82cf9 in av_filter_iterate () at /lib/x86_64-linux-gnu/libavfilter.so.8 #1 0x776ed947 in QtAV::LibAVFilter::registeredFilters(int) (type=0) at /home/steve/Packages/digikam/upstream/core/libs/video/qtav/filter/LibAVFilter.cpp:479 #2 0x776ed0b5 in QtAV::LibAVFilter::videoFilters() () at /home/steve/Packages/digikam/upstream/core/libs/video/qtav/filter/LibAVFilter.cpp:327 #3 0x5bcc in main(int, char**) () at /home/steve/Packages/digikam/upstream/core/tests/video/qtav/tests/codecslist.cpp:64 (gdb) The bug is in how LibAVFilter::registeredFilters() calls av_filter_iterate(). Patch attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shade/shutter feature
https://bugs.kde.org/show_bug.cgi?id=450582 Steven R. changed: What|Removed |Added CC||stevenrosensh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 452313] GCompris package does NOT have audio files.
https://bugs.kde.org/show_bug.cgi?id=452313 --- Comment #1 from Steven --- The next day, voices are working. Perhaps I did something wrong. Anyway, I want to add voices for other keyboard keys, so I tried searching using find to locate the voices. Found no .ogg or .wav files associated with gcompris. Why? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 452313] New: GCompris package does NOT have audio files.
https://bugs.kde.org/show_bug.cgi?id=452313 Bug ID: 452313 Summary: GCompris package does NOT have audio files. Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: free...@twc.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org 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. Install GCompris using apt install gcompris or via Discover 2. Launch Baby keyboard. 3. type letter A OBSERVED RESULT No voice proclaiming A. There was no introductory voice either. EXPECTED RESULT Expected to heard a voice, like on my Chromebook. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon KDE (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I went to settings within GCompris, and it claims all the extra resources were downloaded.. I installed GCompris on my Chromebook, and I hear the letter A from the voice. Originally, I installed GCompris from Discover, I I uninstalled it and used apt install. Still don't have a voice proclaiming the letter A. I have installed the latest GCompris, ver 2.3 -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 452311] New: Baby keyboard activity should be enhanced with voice pronunciation of letters, numbers, and symbols.
https://bugs.kde.org/show_bug.cgi?id=452311 Bug ID: 452311 Summary: Baby keyboard activity should be enhanced with voice pronunciation of letters, numbers, and symbols. Product: gcompris Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: free...@twc.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. Open Baby keyboard activity 2. Press letter A. OBSERVED RESULT Note no sound EXPECTED RESULT A sound (voice) pronouncing the letter A. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.24.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I would be willing to record these sounds and email them to someone. It would also be very nice if an example of each letter was used in a word, such as A is for Apple, with a graphic of an apple. I have written C programs since 1983. I would be willing to submit enhancements to Got, if someone will mentor me. I have next to zero experience with git, but I setup a subversion sever on my machine to commit my own code. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450632] Date does not wrap when widget is on the desktop
https://bugs.kde.org/show_bug.cgi?id=450632 --- Comment #6 from Steven --- Created attachment 147077 --> https://bugs.kde.org/attachment.cgi?id=147077=edit Digital Clock default size with long date As you can see from this .png file, the long date is quite small if user doesn't resize the widget. I am willling to resize the widget to make long date readable on my screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450632] Date does not wrap when widget is on the desktop
https://bugs.kde.org/show_bug.cgi?id=450632 --- Comment #4 from Steven --- I'm so sorry for this bug report. I didn't realize I could simply resize the widget on the Desktop and get a larger date. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450764] New: Discover missing Libre Office help
https://bugs.kde.org/show_bug.cgi?id=450764 Bug ID: 450764 Summary: Discover missing Libre Office help Product: Discover Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: free...@twc.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover missing Libre Office help STEPS TO REPRODUCE 1. Using Discover, install Libre Office. 2. Using Discover, Install Libre Office Help. OBSERVED RESULT There is no Libre Office Help in Discover. EXPECTED RESULT Libre Office Help should be available in Discover. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.24 (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450729] New: Neither KWrite or Kate allow margins for printing.
https://bugs.kde.org/show_bug.cgi?id=450729 Bug ID: 450729 Summary: Neither KWrite or Kate allow margins for printing. Product: kate Version: 21.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: free...@twc.com Target Milestone: --- SUMMARY Neither KWrite or Kate allow margins for printing. STEPS TO REPRODUCE 1. Open any text document. 2. Try to set a half-inch left margin. OBSERVED RESULT There are no margin settings. EXPECTED RESULT I expect margin capability in any modern editor that supports printing. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Neon Plasma: 5.24 (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450632] Date does not wrap when widget is on the desktop
https://bugs.kde.org/show_bug.cgi?id=450632 --- Comment #2 from Steven --- My digital clock widget is at the top center of my screen. No wrapping is necessary. When I configure the widget for long date format, the long date is too tiny. I would like it to be the same size as the clock digits. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450633] New: Digital Clock Custom Date format documentation states you can use YYYY, but it literally displays YYYY, not the four digit year.
https://bugs.kde.org/show_bug.cgi?id=450633 Bug ID: 450633 Summary: Digital Clock Custom Date format documentation states you can use , but it literally displays , not the four digit year. Product: plasmashell Version: 5.24.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: free...@twc.com Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Add Digital Clock widget to your desktop. 2. Right click Digital clock to see pop-up menu. 3. Select Configure Digital Clock 4. On Appearance page, select Custom Date format. 5. Enter just as the format string. 6. Click OK or Apply. OBSERVED RESULT Observe the Custom date is literally , not the four digit year. EXPECTED RESULT Four digit year per documentation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450632] New: Digital Clock Date format: Long Date produces text too small to read
https://bugs.kde.org/show_bug.cgi?id=450632 Bug ID: 450632 Summary: Digital Clock Date format: Long Date produces text too small to read Product: plasmashell Version: 5.24.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: free...@twc.com Target Milestone: 1.0 SUMMARY Digital Clock Date format: Long Date produces text too small to read STEPS TO REPRODUCE 1. Add Digital Clock widget to your desktop. 2. Right click Digital clock to see pop-up menu. 3. Select Configure Digital Clock 4. On Appearance page, select Long Date Date format. 5. Click OK or Apply. Observe the long date is too small to read. Why isn't it as big as time? 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.
[Powerdevil] [Bug 447475] lowering brightness to 0 on oled irreversibly turns off screen
https://bugs.kde.org/show_bug.cgi?id=447475 Steven Noonan changed: What|Removed |Added CC||ste...@uplinklabs.net -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 448458] New: Suggestion for KMyMoney
https://bugs.kde.org/show_bug.cgi?id=448458 Bug ID: 448458 Summary: Suggestion for KMyMoney Product: kmymoney Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: m...@cyberlizard.co.uk Target Milestone: --- Re: KMyMoney this is not a bug notification, rather the wishlist/suggestion page brought me here. when adding a transaction to the ledgers, is it possible in a future revision to have the option to attach a file, namely a PDF scanned receipt for example. Also would it be possible to include a 'number' column to the transactions for systems where each transaction has a specified number, for example in our current system, every new transaction is given an incremental number. thanks Steve -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444971] New: Okular crashed when opening a markdown file
https://bugs.kde.org/show_bug.cgi?id=444971
Bug ID: 444971
Summary: Okular crashed when opening a markdown file
Product: okular
Version: 21.08.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: linjt...@outlook.com
Target Milestone: ---
Application: okular (21.08.2)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I tried opening a markdown file from dolphin, and then it crashed.
Here is the markdown file:
https://github.com/syl20bnr/spacemacs/blob/develop/README.md
The crash can be reproduced every time.
-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 0x7f1ef020c2a3 in QFragmentMapData::next
(this=, this=, n=7274595) at
../../include/QtGui/5.15.2/QtGui/private/../../../../../src/gui/text/qfragmentmap_p.h:295
#7 QFragmentMap::next (n=, this=) at
../../include/QtGui/5.15.2/QtGui/private/../../../../../src/gui/text/qfragmentmap_p.h:859
#8 QTextBlock::iterator::operator++ (this=this@entry=0x7ffc644b1150) at
text/qtextobject.cpp:1615
#9 0x7f1ee1ae1cb8 in Markdown::Converter::convertImages (this=, textDocument=0x55d751be8760, dir=..., parent=...) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/generators/markdown/converter.cpp:184
#10 Markdown::Converter::convertImages (parent=parent@entry=0x55d751c5ed10,
dir=..., textDocument=textDocument@entry=0x55d751be8760, this=0x55d751bc84e0)
at
/usr/src/debug/okular-21.08.2-1.1.x86_64/generators/markdown/converter.cpp:177
#11 0x7f1ee1ae2396 in Markdown::Converter::convertOpenFile
(this=this@entry=0x55d751bc84e0) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/generators/markdown/converter.cpp:125
#12 0x7f1ee1ae2591 in Markdown::Converter::convert (this=0x55d751bc84e0,
fileName=...) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/generators/markdown/converter.cpp:68
#13 0x7f1ee2448f3f in Okular::TextDocumentConverter::convertWithPassword
(fileName=..., this=0x55d751bc84e0) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/core/textdocumentgenerator.cpp:52
#14 Okular::TextDocumentGenerator::loadDocumentWithPassword (this=, fileName=..., pagesVector=..., password=...) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/core/textdocumentgenerator.cpp:290
#15 0x7f1ee240bc1c in Okular::DocumentPrivate::openDocumentInternal
(this=0x55d7510ce260, offer=..., isstdin=, docFile=...,
filedata=..., password=...) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/core/document.cpp:890
#16 0x7f1ee24181eb in Okular::Document::openDocument
(this=this@entry=0x55d7512fa100, docFile=..., url=..., _mime=..., password=...)
at /usr/src/debug/okular-21.08.2-1.1.x86_64/core/document.cpp:2330
#17 0x7f1ee2555d75 in Okular::Part::doOpenFile
(this=this@entry=0x55d7512fef20, mimeA=..., fileNameToOpenA=...,
isCompressedFile=isCompressedFile@entry=0x7ffc644b1917) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/part/part.cpp:1393
#18 0x7f1ee255860b in Okular::Part::openFile (this=0x55d7512fef20) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/part/part.cpp:1511
#19 0x7f1ef13aa265 in KParts::ReadOnlyPartPrivate::openLocalFile
(this=this@entry=0x55d751307620) at
/usr/src/debug/kparts-5.87.0-1.1.x86_64/src/readonlypart.cpp:180
#20 0x7f1ef13ae937 in KParts::ReadOnlyPart::openUrl
(this=this@entry=0x55d7512fef20, url=...) at
/usr/src/debug/kparts-5.87.0-1.1.x86_64/src/readonlypart.cpp:141
#21 0x7f1ee25569a3 in Okular::Part::openUrl (this=,
_url=..., swapInsteadOfOpening=) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/part/part.cpp:1743
#22 0x55d7503213bb in Shell::openUrl (this=, url=...,
serializedOptions=...) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/shell/shell.cpp:285
#23 0x55d7503265ee in Shell::openDocument (this=0x55d751302950, url=...,
serializedOptions=...) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/shell/shell.cpp:236
#24 0x55d75031da85 in Shell::openDocument (serializedOptions=..., url=...,
this=0x55d751302950) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/shell/okular_main.cpp:158
#25 Okular::main (serializedOptions=..., paths=...) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/shell/okular_main.cpp:162
#26 main (argc=, argv=0x7ffc644b1eb0) at
/usr/src/debug/okular-21.08.2-1.1.x86_64/shell/main.cpp:91
[Inferior 1 (process 11254) detached]
Possible duplicates by query: bug 443057.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 444564] OK button is grayed out
https://bugs.kde.org/show_bug.cgi?id=444564 --- Comment #8 from Steven A. Falco --- Created attachment 143008 --> https://bugs.kde.org/attachment.cgi?id=143008=edit Example of changing desktop icon properties When I try to change the properties of an icon on the desktop, it works as expected. The OK button is always clickable for desktop icon properties. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444564] OK button is grayed out
https://bugs.kde.org/show_bug.cgi?id=444564 --- Comment #7 from Steven A. Falco --- Ok, that is interesting. Icons on the desktop work as expected. The OK button is not grayed out, and works properly for desktop icons. In fact, the OK button can be clicked even without changing any of the properties - it is always allowed. However, icons on a panel show the error I reported: If I right click on an icon in a panel, and select "Properties", the OK button is grayed out, regardless of what I try to change. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444564] OK button is grayed out
https://bugs.kde.org/show_bug.cgi?id=444564 --- Comment #5 from Steven A. Falco --- I tried Fedora Rawhide, which has: KDE Plasma Version 5.23.0 KDE Frameworks Version 5.87.0 QT Version 5.15.2 I see the same behavior there - trying to change properties via the panel icons gives me the same grayed out OK button. Perhaps the bug was fixed in an even later release than 5.87.0. I'll have to dig around and see if it is practical for me to compile an even later version of KDE. But I've never tried building KDE, and it may be too big a challenge. Fedora breaks kf5 up into many packages. I don't know which package(s) I might have to rebuild, or if it is possible to mix and match versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444564] OK button is grayed out
https://bugs.kde.org/show_bug.cgi?id=444564 --- Comment #3 from Steven A. Falco --- Comment on attachment 142978 --> https://bugs.kde.org/attachment.cgi?id=142978 Screenshot showing that the OK button is grayed out The properties as shown by right-clicking the icon in the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444564] OK button is grayed out
https://bugs.kde.org/show_bug.cgi?id=444564 --- Comment #2 from Steven A. Falco --- Created attachment 142979 --> https://bugs.kde.org/attachment.cgi?id=142979=edit Screenshot showing that the OK button is clickable The properties dialog as seen via dolphin on directory ~/.local/share/plasma_icons/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444564] OK button is grayed out
https://bugs.kde.org/show_bug.cgi?id=444564 --- Comment #1 from Steven A. Falco --- Created attachment 142978 --> https://bugs.kde.org/attachment.cgi?id=142978=edit Screenshot showing that the OK button is grayed out -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444564] New: OK button is grayed out
https://bugs.kde.org/show_bug.cgi?id=444564 Bug ID: 444564 Summary: OK button is grayed out Product: plasmashell Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: stevenfa...@gmail.com Target Milestone: 1.0 SUMMARY I used to be able to right-click on a desktop icon in a panel, change properties, and hit OK to complete the change. Recently, the OK button is grayed out, and cannot be clicked. I can navigate to the corresponding desktop file (in ~/.local/share/plasma_icons) using dolphin, and I can then right-click the icon and select "properties". The OK button in the resulting properties dialog is _not_ grayed out and I can click it. I tried creating a new user, and I see the same behavior there, so it doesn't seem to be related to my account or permissions. However, that is not a good way to edit the desktop file, because changing the icon via dolphin does not update the icon in the panel. I have to remove the desktop file from the panel, then drag the modified copy from dolphin to the panel. I'll attach some screen shots, showing what this looks like when editing via the panel vs editing via dolphin. STEPS TO REPRODUCE 1. right-click an icon in a panel 2. select properties 3. notice that the OK button is grayed out OBSERVED RESULT OK button is grayed out EXPECTED RESULT OK button is clickable SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442107] Reboot fails to install updates
https://bugs.kde.org/show_bug.cgi?id=442107 --- Comment #1 from Steven --- In my "Additional Information, I referenced the wrong bug number, though the link was correct. I meant to indicated that I found bug 438809 (I mistakenly typed the 8's as 9's). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442107] New: Reboot fails to install updates
https://bugs.kde.org/show_bug.cgi?id=442107 Bug ID: 442107 Summary: Reboot fails to install updates Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: steven.c.how...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Updates do not install on reboot, and there is no option to "press 'c' to cancel" during startup. STEPS TO REPRODUCE 1. Boot machine 2. Receive pop-up notification that restart is needed to install updates 3. Restart 4a. Wait for reboot to complete 4b. Press arrow key (forget which one) to show detailed boot log 5. No option to "press 'c' to cancel updates" or anything like that come up for either the graphical boot or the detailed log view of the boot process 6. Return to step 2. OBSERVED RESULT Every time I boot the laptop, I get the same notification that I need to install updates. In addition to the above steps, I have tried running `sudo apt update && sudo apt -y -m dist-upgrade && sudo apt -y autoremove && sudo apt -y autoclean` to try to freshly install the updates with no change in the outcome. EXPECTED RESULT Updates would install and stop notifying me. SOFTWARE/OS VERSIONS Windows: none macOS: none Kernel Version: 5.11.0.27-generic (64-bit) (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Processor: 4 x Intel Core i5-6200U CPU @ 2.30 GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel HD Graphics 520 ADDITIONAL INFORMATION I found bug 439909 (https://bugs.kde.org/show_bug.cgi?id=438809) describing a similar behavior but the listed solution do not work for me. I do not get an option to press "c", I tried repeatedly pressing "c" anyway with no change. I tried rebooting the machine over a dozen times with no change (Well over the three reboots described by Paul Worrall). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage
https://bugs.kde.org/show_bug.cgi?id=425271 Steven changed: What|Removed |Added CC||steven.gaens...@advanova.de --- Comment #20 from Steven --- I'm observing the same behaviour with high cpu usage from xembedsniproxy. In my case I'm pretty sure it comes in combination with evolution-alarm-notify. I first observed the high cpu after switching from Thunderbird to Evolution. After some try and error with starting and stopping of evolution at all i found out that killing xembedsniproxy OR evolution-alarm-notify instantly stops the high cpu usage. I'm also using firefox and keepassxc, but that combination never made problems until using evolution-mail. Also running with nvidia (RTX 2060) and two monitors (Notebook build-in HD and external WQHD). Compositing was turned off so far. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-lp152.84-preempt OS Type: 64-bit NVIDIA driver: 470.57.02-lp152.43.1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 433047] New: KDE Neon, Kubuntu, and Linux Mint not finding all audio devices
https://bugs.kde.org/show_bug.cgi?id=433047 Bug ID: 433047 Summary: KDE Neon, Kubuntu, and Linux Mint not finding all audio devices Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: disposable...@twc.com Target Milestone: --- SUMMARY dmesg reports: [7.899532] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC671: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [7.899533] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.899534] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [7.899535] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [7.899535] snd_hda_codec_realtek hdaudioC0D0:inputs: [7.899536] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [7.899537] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x18 [7.899537] snd_hda_codec_realtek hdaudioC0D0: Line=0x1b [7.994357] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [7.994406] input: HDA Intel PCH Headset Mic as /devices/pci:00/:00:1f.3/sound/card0/input10 [7.994440] input: HDA Intel PCH Line as /devices/pci:00/:00:1f.3/sound/card0/input11 [7.994487] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input12 [7.994531] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1f.3/sound/card0/input13 [7.994566] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input14 [7.994607] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input15 [7.994643] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input16 [7.994678] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input17 [7.994716] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input18 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Only the HDMI audio is found by KDE. EXPECTED RESULT KDE should find all three audio devices. Realtek(which sends audio to rear and front panels) and Intel (which sends audio to HDMI). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.21 (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION System is an HP Slimline 290-p0014 Desktop PC. I am multi-booting Linux Mint 20.1 Cinnamon, KDE Neon 5.21 User Edition, and Kubutu 20.10, and FreeBSD 12.2p3. FreeBSD only recognizes the Realtek device, not the Intel HDMI device. All these Linux distros only configure the Intel device, even though the Realtek device is recognized in dmesg. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 432907] New: Elisa crashed after playing last item in playlist
https://bugs.kde.org/show_bug.cgi?id=432907
Bug ID: 432907
Summary: Elisa crashed after playing last item in playlist
Product: elisa
Version: 20.12.1
Platform: Debian stable
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: steven.dehe...@gmail.com
Target Milestone: ---
Application: elisa (20.12.1)
Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.10.0-2-amd64 x86_64
Windowing system: X11
Distribution: Debian GNU/Linux bullseye/sid
-- Information about the crash:
- What I was doing when the application crashed:
I never experienced this crash before. It occured when I was doing something
else -- not interacting with Elisa. After the last item in the playlist had
played, the program crashed.
This is perhaps an apropriate day to express my gratitude to you: thank you all
for your work on KDE! ('cause, you know, #ilovefs)
-- Backtrace:
Application: Elisa (elisa), signal: Segmentation fault
[KCrash Handler]
#4 0x7fb25d03f528 in
TrackMetadataModel::radioData(DataTypes::TrackDataType const&) () at
/usr/lib/x86_64-linux-gnu/elisa/libelisaLib.so.0
#5 0x7fb25b9d3f51 in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7fb25c9b015f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7 0x7fb25b9a7f2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x7fb25b9aa961 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x7fb25b9ffdf3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fb25969ad3b in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fb25969afe8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7fb25969b09f in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7fb25b9ff47f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fb25b9a68eb in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fb25b9aeb60 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x55758f5321e4 in ()
#17 0x7fb25b38cd0a in __libc_start_main (main=0x55758f531680, argc=1,
argv=0x7ffda45c30a8, init=, fini=,
rtld_fini=, stack_end=0x7ffda45c3098) at ../csu/libc-start.c:308
#18 0x55758f5325da in ()
[Inferior 1 (process 30226) detached]
Possible duplicates by query: bug 432633, bug 432496, bug 432456, bug 432313,
bug 432084.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 409595] Ambiguous shortcuts if the toolbar is modified
https://bugs.kde.org/show_bug.cgi?id=409595 Steven R. Gustafson changed: What|Removed |Added CC||stevengustafson4...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #165 from Steven Swart --- Good day, all! Sad to report that after a "zypper dup" and reboot yesterday, still got the same error. I couldn't report the stacktrace via the OS reporting mechanism, the message said that there was no email address associated with the component. Kind regards, Steven. On Wed, 28 Oct 2020 at 16:36, Steven Swart wrote: > > Hi All! > > I am on this thread because I reported the same bug. Since then, there > have been a lot of duplicates. > > On my side, I am running OpenSUSE Tumbleweed on my media server. It's > a rolling release, and there are frequent updates, pretty much daily, > most of the time. > > Many of these updates require a reboot. > > I was only ever getting this problem after I had run a distribution > update -"zypper dup", and then rebooted. > > For a while, I was frequently getting the same error, but not every > time. I don't recall seeing it for the past few weeks. I will report > it if I see it again. > > Tumbleweed is pretty bleeding-edge as far as the kernel and system > libraries are concerned, I think SUSE uses us a beta-testers for their > commercial platforms. > > But, this being the case, there is a possibility that the bug has > already been fixed, and just needs to roll out to the majority of > distros. > > Kind regards, > Steven. > > On Wed, 28 Oct 2020 at 16:21, Papoteur wrote: > > > > https://bugs.kde.org/show_bug.cgi?id=389848 > > > > --- Comment #162 from Papoteur --- > > On my side, I have luks encrypted home partition, too. The index file is 1Go > > heavy and is on a professional computer, thus I can't deliver it. > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 --- Comment #163 from Steven Swart --- Hi All! I am on this thread because I reported the same bug. Since then, there have been a lot of duplicates. On my side, I am running OpenSUSE Tumbleweed on my media server. It's a rolling release, and there are frequent updates, pretty much daily, most of the time. Many of these updates require a reboot. I was only ever getting this problem after I had run a distribution update -"zypper dup", and then rebooted. For a while, I was frequently getting the same error, but not every time. I don't recall seeing it for the past few weeks. I will report it if I see it again. Tumbleweed is pretty bleeding-edge as far as the kernel and system libraries are concerned, I think SUSE uses us a beta-testers for their commercial platforms. But, this being the case, there is a possibility that the bug has already been fixed, and just needs to roll out to the majority of distros. Kind regards, Steven. On Wed, 28 Oct 2020 at 16:21, Papoteur wrote: > > https://bugs.kde.org/show_bug.cgi?id=389848 > > --- Comment #162 from Papoteur --- > On my side, I have luks encrypted home partition, too. The index file is 1Go > heavy and is on a professional computer, thus I can't deliver it. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
