[kwin] [Bug 372015] kwin_x11 crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=372015 --- Comment #9 from Wayne --- I have been experiencing a similar, but somewhat sporadic "crash" on boot-up, since an upgrade ~3-4+(?) months ago. It happens ~50-75% of the time, closer to 100% the last week. This crash happens, but then the machine apparently recovers and restarts kwin and then works without kwin re-crashing. System: Debian "testing" net install late last year (new HD but I5/MB built about 5 yr ago), upgraded regularly. While it has extra software (video/audio/office/Myth/radio) and now debug files installed, it has not really been modified other than for auto login on boot. I am a neophyte on backtraces, but these backtraces/problems are not consistent. This was the first today of two consecutive crashes on a single boot. The second, is similar. I can provide that trace if wished. Earlier crash reports were much more extensive, along the lines of the original report reported here, but were incomplete and the kcrash handler reported them as needing additional debug files for: /usr/bin/kwin_x11 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 Other reported similar bugs seem to require user input/or are related to other programs which I have not provided to the operating system/do not seem to be in these traces. But, I leave windows/programs open to expedite startup and those restart with the boot. General Symptoms (may not be related to this kwin crash, but have been around since that upgrade). -alt tab keyboard shortcut between programs no longer works. -very slow window responsiveness to changing among running programs-mainly libreoffice/iceweasel/icedove (lately several seconds or more). That seems to be fixed by a memory transplant last week (to 16Gb from 8Gb). Other erratic symptoms which may or may not be related: -after this crash kate's title bar was mostly above the top screen edge, that operating program behaviour does not happen all the time. After moving the window and a change in focus to another program and back, it went back up mostly above the screen a couple of times. Reducing the size of the kate window apparently stopped that behavior, even after re-maximizing the window. -sometimes the widgets (? in the task bar ? not sure those are the right names) for running programs do not show up and one has to close or kill the top program to see/switch to the window underneath. -A second boot (occasionally a third) will clear problems up. Other: systemd gives messages on shutdown, maybe ~15-20% of the time, about failure to unmount swap (4x) and a couple of times I have noted an extra similar message for the rpc file system. Again this swap thing started up about the same time as the upgrade. Changes to the originally installed fstab (by the net install disk which used /dev/sdx rather than the uuid for the swap) seemed to have fixed that swap issue a few weeks ago, but that restarted recently. Current software is Linux debian 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64 GNU/Linux Package: qt5-default Source: qtbase-opensource-src (5.6.1+dfsg-3) Package: breeze Version: 4:5.8.2-1 Package: kde-full Source: meta-kde Version: 5:91 Package: kwin-x11 Source: kwin Version: 4:5.8.2-1 I installed breeze from Jessie a month or so ago, that did not seem to help so have changed apt back to point to Stretch. Wayne Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa59bbfae00 (LWP 2238))] Thread 3 (Thread 0x7fa57298c700 (LWP 2261)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:73 #1 0x7fa5b31702a5 in select () at ../sysdeps/unix/syscall-template.S:84 #2 0x7fa5b0fd5d3f in qt_safe_select (nfds=16, fdread=fdread@entry=0x7fa56c000a78, fdwrite=fdwrite@entry=0x7fa56c000d08, fdexcept=fdexcept@entry=0x7fa56c000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #3 0x7fa5b0fd77e4 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fa56c000f98, writefds=0x7fa56c000d08, readfds=0x7fa56c000a78, nfds=, this=0x7fa56c0008c0) at kernel/qeventdispatcher_unix.cpp:320 #4 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa56c0008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #5 0x7fa5b0fd7cfa in QEventDispatcherUNIX::processEvents (this=0x7fa56c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #6 0x7fa5b0f8219a in QEventLoop::exec (this=this@entry=0x7fa57298bc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7fa5b0da7e53 in QThread::exec (this=this@entry=0x22e8130) at thread/qthread.cpp:500 #8 0x7fa5abf88a55 in QQmlThreadPrivate::run (this=0x22e8130) at qml/ftw/qqmlthrea
[systemsettings] [Bug 445914] New: When I was about to download the Global Theme, my system Settings crashed, as it does every time, requesting resolution.
https://bugs.kde.org/show_bug.cgi?id=445914 Bug ID: 445914 Summary: When I was about to download the Global Theme, my system Settings crashed, as it does every time, requesting resolution. Product: systemsettings Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: 2095234...@qq.com Target Milestone: --- Created attachment 143829 --> https://bugs.kde.org/attachment.cgi?id=143829&action=edit This is a crash log, but does not seem to have reference value, hope it can be resolved, I did my best. 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 the system setup program 2. Open the appearance -> Global theme -> Get a new global theme -> Install a random global theme -> Enter the password to authenticate the identity extract 3. Boom! The system Settings crashed and I was in despair <3 OBSERVED RESULT System Settings crash EXPECTED RESULT The theme was successfully installed and used SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION What's going on? I have not encountered any problems before, so I cannot repair him. Please hurry up and repair him. Thank you! Hard work! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445914] When I was about to download the Global Theme, my system Settings crashed, as it does every time, requesting resolution.
https://bugs.kde.org/show_bug.cgi?id=445914 Wayne <2095234...@qq.com> changed: What|Removed |Added Alias||System, Settings, ->, ||global, theme, Download, a, ||random, crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 Wayne <2095234...@qq.com> changed: What|Removed |Added CC||2095234...@qq.com --- Comment #24 from Wayne <2095234...@qq.com> --- Me, too. I don't know how to fix it -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445768] System Settings crash upon installing any new theme
https://bugs.kde.org/show_bug.cgi?id=445768 Wayne <2095234...@qq.com> changed: What|Removed |Added CC||2095234...@qq.com --- Comment #1 from Wayne <2095234...@qq.com> --- Same thing. Same thing with me. I'm looking for a solution -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476354] New: The app will not connect my laptop to my phone a second time. It only works the first time
https://bugs.kde.org/show_bug.cgi?id=476354 Bug ID: 476354 Summary: The app will not connect my laptop to my phone a second time. It only works the first time Classification: Applications Product: kdeconnect Version: 23.08.2 Platform: Android OS: Android 13.x Status: REPORTED Severity: crash Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: wkipkurui5...@gmail.com CC: andrew.g.r.hol...@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. Pair phone with pc on the same network. 2. Disconnect both devices from the network 3. Reconnect both devices to same network 4. Try to connect KDE Application OBSERVED RESULT The two devices will not reconnect EXPECTED RESULT The two devices reconnect automatically. SOFTWARE/OS VERSIONS Windows: windows 10 pro 22H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This happens when the PC disconnects, and everything it happens I have to reinstall the app on my phone for it to work -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446799] System Settings crash when downloading global themes
https://bugs.kde.org/show_bug.cgi?id=446799 Wayne <2095234...@qq.com> changed: What|Removed |Added CC||2095234...@qq.com --- Comment #1 from Wayne <2095234...@qq.com> --- Yes, I also have the same problem, which has not been solved, but it is shown in 439797 that the state has been solved, but it is still not solved, at least yesterday, I still have this problem, looking forward to solving it, in addition, my report is 445914. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 357396] Tried to open KDE Wallet Manager Handbook. Window flag in task bar opens and then closes. F1 does nothing.
https://bugs.kde.org/show_bug.cgi?id=357396 Wayne changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419379] New: Issues with screen dissapering when i load a new canvas.
https://bugs.kde.org/show_bug.cgi?id=419379 Bug ID: 419379 Summary: Issues with screen dissapering when i load a new canvas. Product: krita Version: 4.2.9 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: wolf-eye...@hotmail.com Target Milestone: --- Created attachment 127087 --> https://bugs.kde.org/attachment.cgi?id=127087&action=edit An image clearly showing the issue SUMMARY When selecting a canvas to use for painting, the screen area disappears where the canvas is meant to show. The rest of the screen is ok except that part of the screen. STEPS TO REPRODUCE 1. Open Krita 2. Select a canvas from the options provided. 3. Wait for the canvas to show on the screen. OBSERVED RESULT The section on of screen where the canvas is meant to be disappears EXPECTED RESULT To see the canvas ready to pain on with the dark background. SOFTWARE/OS VERSIONS Windows: 7 32bit ADDITIONAL INFORMATION Under Component, i'm just guessing i selected the correct one in this bug report! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.
https://bugs.kde.org/show_bug.cgi?id=419379 --- Comment #3 from Wayne --- I gave that a try and also the filtering options and got it to work. It does, however, cause some slight lagging so I've decided sadly to revert back to the older version. Thank you anyway for your help and time. Wayne. From: Boudewijn Rempt Sent: 29 March 2020 14:21 To: wolf-eye...@hotmail.com Subject: [krita] [Bug 419379] Issues with screen dissapering when i load a new canvas. https://bugs.kde.org/show_bug.cgi?id=419379 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- That might not be possible on 32 bits Windows 7 -- I'm not sure whether there's the right version of directx for Windows 7 to make Angle work. Btw, note that we no longer support Windows 7, the minimum we support in Windows 8.1 (and even that gets trickier all the time). -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.
https://bugs.kde.org/show_bug.cgi?id=419379 --- Comment #5 from Wayne --- Version 4.2.8 which I believe is the version before this current release? Get Outlook for Android<https://aka.ms/ghei36> From: Boudewijn Rempt Sent: Sunday, March 29, 2020 3:02:46 PM To: wolf-eye...@hotmail.com Subject: [krita] [Bug 419379] Issues with screen dissapering when i load a new canvas. https://bugs.kde.org/show_bug.cgi?id=419379 --- Comment #4 from Boudewijn Rempt --- Which version did you use before? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.
https://bugs.kde.org/show_bug.cgi?id=419379 --- Comment #7 from Wayne --- It does seem odd. Get Outlook for Android<https://aka.ms/ghei36> From: Boudewijn Rempt Sent: Sunday, March 29, 2020 3:56:55 PM To: wolf-eye...@hotmail.com Subject: [krita] [Bug 419379] Issues with screen dissapering when i load a new canvas. https://bugs.kde.org/show_bug.cgi?id=419379 --- Comment #6 from Boudewijn Rempt --- That's curious, because there were no changes to the opengl canvas that I know of between 4.2.8 and 4.2.9... -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.
https://bugs.kde.org/show_bug.cgi?id=419379 --- Comment #9 from Wayne --- I will do so in future, I just need to learn the correct way to do so. Thank you for your help and time. Get Outlook for Android<https://aka.ms/ghei36> From: Bug Janitor Service Sent: Monday, March 30, 2020 5:33:12 AM To: wolf-eye...@hotmail.com Subject: [krita] [Bug 419379] Issues with screen dissapering when i load a new canvas. https://bugs.kde.org/show_bug.cgi?id=419379 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383700] New: Opening a new document
https://bugs.kde.org/show_bug.cgi?id=383700 Bug ID: 383700 Summary: Opening a new document Product: krita Version: 3.2.0-beta.1 Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: wolf-eye...@hotmail.com Target Milestone: --- When i select New and open a document ( A4 300pi for example ) the program then crashes. I have uninstalled all other versions of Krita which have all worked very well before but having downloaded and installed Krita 3.2.0.6, it seems to have this problem? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] New: vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 Bug ID: 372188 Summary: vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2 Product: valgrind Version: 3.12 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: wayne.arn...@autodesk.com Target Milestone: --- appears to be another instance of pcmpistrm that is not being recognized. 1477b0: 66 0f 3a 62 48 10 10pcmpistrm $0x10,0x10(%rax),%xmm1 1477b7: 48 83 c0 10 add$0x10,%rax 1477bb: 66 0f 7e c1 movd %xmm0,%ecx 1477bf: 85 c9 test %ecx,%ecx this is in a 3rd party library, rapidjson compiled with support for SSE4.2 enabled I don't have the source available vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F3A vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==9471== valgrind: Unrecognised instruction at address 0x8c4115a0. ==9471==at 0x8C4115A0: void rapidjson_sse42::GenericReader, rapidjson_sse42::UTF8, rapidjson_sse42::CrtAllocator>::ParseObject<1u, rapidjson_sse42: :GenericInsituStringStream >, rapidjson_sse42::GenericDocument, rapidjson_sse42::MemoryPoolAllocator, rapidjson_sse42::CrtAllocator> >(rapidjson_sse42::GenericInsituStringStream >&, rapidjson_sse42::GenericDocument, rapidjson_s se42::MemoryPoolAllocator, rapidjson_sse42::CrtAllocator>&) (reader.h:299) ==9471==by 0x8C4107ED: rapidjson_sse42::ParseResult rapidjson_sse42::GenericReader, rapidjson_sse42::UTF8, rapidjson_sse42::CrtAllocator>::Parse<1u , rapidjson_sse42::GenericInsituStringStream >, rapidjson_sse42::GenericDocument, rapidjson_sse42::MemoryPoolAllocator, rapidjson_sse42::CrtAllocator> >(rapidjson_sse42::GenericInsituStringStream >&, rapidjson_sse42::GenericDocument, rapidjson_sse42::MemoryPoolAllocator, rapidjson_sse42::CrtAllocator>&) (reader.h:498) ==9471==by 0x8C410686: rapidjson_sse42::GenericDocument, rapidjson_sse42::MemoryPoolAllocator, rapidjson_sse42::CrtAllocator>& rapidjson_sse42::GenericDocument, rapidjson_sse42::MemoryPoolAllocator, rapidjson_sse42::CrtAllocator>::ParseStream<1u, rapidjson_sse42::UTF8, rapidjson_sse42::GenericInsituStringStream > >(rapidjson_sse42::GenericInsituStringStream >&) (document.h:2150) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #1 from Wayne Arnold --- sorry, real instance, there are a number when disassembled 1485a0: 66 0f 3a 62 4a 10 10pcmpistrm $0x10,0x10(%rdx),%xmm1 1485a7: 48 83 c2 10 add$0x10,%rdx 1485ab: 66 0f 7e c0 movd %xmm0,%eax -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #2 from Wayne Arnold --- 148a20: 66 0f 3a 62 49 10 10pcmpistrm $0x10,0x10(%rcx),%xmm1 148a27: 48 83 c1 10 add$0x10,%rcx 148a2b: 66 0f 7e c0 movd %xmm0,%eax 148a2f: 85 c0 test %eax,%eax -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 466860] New: Time Zone isn't consistent in all parts of APP
https://bugs.kde.org/show_bug.cgi?id=466860 Bug ID: 466860 Summary: Time Zone isn't consistent in all parts of APP Classification: Applications Product: korganizer Version: 5.19.1 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: waynelloydsm...@gmail.com Target Milestone: --- SUMMARY *** I live in Saskatoon. Our time zone is UTC-6 or same as America/Guatemala I can set it to America/Regina or America/Swift-current and they seem to work I want to set it to UTC-6 but there is no selection for that on the main set date/time /timezone. UTC-6 does appear on the event timezone selection but not on the main clock/timezone set up. Its just simpler to remember UTC-6 than the name of some city in Saskatchewan. There is more than one. *** STEPS TO REPRODUCE 1. try to configure - System Settings for KOrganizer - Date/Time 2. UTC-6 is not in the list of available timezone settings 3. Create an event . UTC-6 is available on the event timezone selection OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Slackware 15 (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.
[systemsettings] [Bug 459005] New: There is no save button for an OpenVPN password entered - it keeps asking for password everytime i reconnect
https://bugs.kde.org/show_bug.cgi?id=459005
Bug ID: 459005
Summary: There is no save button for an OpenVPN password
entered - it keeps asking for password everytime i
reconnect
Product: systemsettings
Version: 5.25.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_networkmanagement
Assignee: jgrul...@redhat.com
Reporter: lawayn...@linksnb.com
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
There is no save button for an OpenVPN password entered.
STEPS TO REPRODUCE
1. Go to https://www.freeopenvpn.org
2. Click 'Get access' on any online country
3. Once on the download page, click UDP or TCP (don't leave the web page)
4. Go to KDE System Settings > Connections
5. And new connection ("+" button)
6. Scroll down until you see "Import VPN connection" and double-click it
7. Locate and open the .ovpn file you downloaded
8. Apply
9. Click the Networks system try/panel icon
10. Click the "Connect" button of the new *freeopenvpn* that you added and
enter the Password/PIN from the Download page of the freeopenvpn
11. Wait for it to connect. You can check your new IP address if you want.
12. Click the Networks system try/panel icon
13. Click the "Disconnect" button of the new *freeopenvpn*
14. Click the "Connect" button of the new *freeopenvpn* again
15. Notice that it keeps asking for the password/PIN because there's no way to
save it. That's a problem.
ADDITIONAL INFORMATION
It also sometimes disconnects on its own, which is a problem I'm not able to
reproduce. Therefore it would be nice to add a few VPN connections, save
PIN/Password, and set a rule to fallback to any of the added VPNs in case one
VPN connection fails unexpectedly.
--
You are receiving this mail because:
You are watching all bug changes.
[bugs.kde.org] [Bug 459007] New: NixOS is not listed as Platform
https://bugs.kde.org/show_bug.cgi?id=459007 Bug ID: 459007 Summary: NixOS is not listed as Platform Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: templates Assignee: sysad...@kde.org Reporter: lawayn...@linksnb.com CC: she...@kde.org Target Milestone: --- SUMMARY When filing a bug and selecting the linux Platform, nixos isn't listed. It should be there since it's more popular than some of the listed ones. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 459095] New: Breeze Dark theme should have this kind of window shadows (see attachment)
https://bugs.kde.org/show_bug.cgi?id=459095 Bug ID: 459095 Summary: Breeze Dark theme should have this kind of window shadows (see attachment) Product: Breeze Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: lawayn...@linksnb.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 152048 --> https://bugs.kde.org/attachment.cgi?id=152048&action=edit old oxygen dark theme has light and even shadows on all corners of a window SUMMARY The old Oxygen dark theme makes more sense because it has a light-colored and even shadowing on all corners unlike the Breeze dark theme that has stronger or thicker shadow at the bottom of the window. Breeze light maybe doesn't need this but breeze dark doesn't look great. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 459096] New: Paid service for KDE Connect cloud storage/sync
https://bugs.kde.org/show_bug.cgi?id=459096 Bug ID: 459096 Summary: Paid service for KDE Connect cloud storage/sync Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: lawayn...@linksnb.com Target Milestone: --- SUMMARY Since it costs money to spawn a server to offer/host a KDEConnect online service for users on networks who cannot use KDE Connect locally, why not offer that as a PAID service instead? Communist users will disagree about the commercialization so you'll have to justify the decision. There's nothing wrong about asking for money for offering a service anyway. Plus it could potentially become a revenue source for the project or KDE as a whole - who knows. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 459096] Paid service for KDE Connect cloud storage/sync
https://bugs.kde.org/show_bug.cgi?id=459096 don wayne changed: What|Removed |Added Assignee|albertv...@gmail.com|lucas.w...@tuta.io Component|android-application |ios-application -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458701] New: Kate cannot edit a system file on nixos
https://bugs.kde.org/show_bug.cgi?id=458701 Bug ID: 458701 Summary: Kate cannot edit a system file on nixos Product: kate Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwrite-bugs-n...@kde.org Reporter: lawayn...@linksnb.com Target Milestone: --- SUMMARY Kate cannot edit a system file and won't even ask for the sudo password. Error: The document could not be saved, as it was not possible to write to /etc/nixos/configuration.nix. Check that you have write access to this file or that enough disk space is available. The original file may be lost or damaged. Don't quit the application until the file is successfully written. STEPS TO REPRODUCE 1. on nixos (unstable channel), open /etc/nixos/configuration.nix with kate. 2. edit configuration.nix 3. click save. 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.
[systemsettings] [Bug 458739] New: I can't find the control for kuserfeedback in kde sysmtem settings
https://bugs.kde.org/show_bug.cgi?id=458739 Bug ID: 458739 Summary: I can't find the control for kuserfeedback in kde sysmtem settings Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_feedback Assignee: aleix...@kde.org Reporter: lawayn...@linksnb.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. install nixos kde unstable channel 2. find user feedback in system settings, you can't 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.
[digikam] [Bug 457086] New: A request to add our own tag icons
https://bugs.kde.org/show_bug.cgi?id=457086 Bug ID: 457086 Summary: A request to add our own tag icons Product: digikam Version: unspecified Platform: unspecified OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tags-Manager Assignee: digikam-bugs-n...@kde.org Reporter: mr.waynewilli...@gmail.com Target Milestone: --- The icons available in Tag Properties are great, but I would like to use my own. Could you add a way for users to add their own icons? If this function is already available, please let me know where I can find it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457086] A request to add our own tag icons
https://bugs.kde.org/show_bug.cgi?id=457086 --- Comment #2 from Wayne Williams --- (In reply to Maik Qualmann from comment #1) > You can drag and drop an image onto a tag in the main view and set it as the > tag thumbnail. > > Maik I tried but I must be doing something wrong. What is the main view? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457086] A request to add our own tag icons
https://bugs.kde.org/show_bug.cgi?id=457086 --- Comment #4 from Wayne Williams --- Created attachment 150883 --> https://bugs.kde.org/attachment.cgi?id=150883&action=edit Tag List with Icons I'm sorry, but I cannot get it to work. I attached a screenshot to show what I am trying to do. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457086] A request to add our own tag icons
https://bugs.kde.org/show_bug.cgi?id=457086 --- Comment #6 from Wayne Williams --- (In reply to Maik Qualmann from comment #5) > You cannot drop an external image. It must be an image of your collection > from the central view. > > Maik Is there a way to put my icons into the collection? Is the central view the one I get when I click on the icon in Tag Manager? If so, that didn't work for me also. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 120055] ALBUMTHUMBS : Allow to use any image managed by digiKam as Tags album thumbnail
https://bugs.kde.org/show_bug.cgi?id=120055 --- Comment #9 from Wayne Williams --- Yes it works! -Thank you Sent from my iPhone > On Jul 25, 2022, at 1:57 AM, Maik Qualmann wrote: > > https://bugs.kde.org/show_bug.cgi?id=120055 > > --- Comment #8 from Maik Qualmann --- > Icons or images from the collection can be assigned to an album as thumbnail > using drag and drop. In order to set an icon to a tag as a thumbnail, the tag > must also be assigned to the icon. > > Maik > > -- > 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.
[kmymoney] [Bug 439819] New: Issue with changing credit card limits
https://bugs.kde.org/show_bug.cgi?id=439819 Bug ID: 439819 Summary: Issue with changing credit card limits Product: kmymoney Version: 5.1.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: posah2...@gmail.com Target Milestone: --- SUMMARY Change to account limits breaks report "To Minimum Balance/Maximum Credit" My credit card limit was increased recently and I attempted to change the Maximum Credit under Edit Account. STEPS TO REPRODUCE 1. Opened Account and selected edit account. The account limits for warning and maximum are showing blank. 2. Entered new maximum credit limit and selected OK. 3. Returned to home page and scrolled to Preferred Accounts. 4. New "To Minimum Balance/Maximum Credit" showing a negative number which equals current account balance and new account limit added together. 5. My other credit accounts are displaying the limits correctly on the "Preferred Account" report. These other credit accounts also have blank displays in their limits tabs. So as long as the limits are not changed, the report displays correctly. OBSERVED RESULT Extremely large negative number in the "Maximum Credit" column. EXPECTED RESULT A positive number reflecting new credit limit minus current account balance SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: Version 5.1.2-64335bc5d KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439819] Issue with changing credit card limits
https://bugs.kde.org/show_bug.cgi?id=439819 --- Comment #2 from Wayne Howard --- (In reply to Thomas Baumgart from comment #1) > I tried to duplicate this behavior without success. Differences: I was using > 5.1.2-070754227 on Linux. Can you double check the account type? Is it > really a credit-card account? Yes, under the General tab, this account shows "Credit Card" grayed out. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439819] Issue with changing credit card limits
https://bugs.kde.org/show_bug.cgi?id=439819 --- Comment #8 from Wayne Howard --- I agree with you. W10 bug rectified. On Fri, Jul 23, 2021, 08:16 Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=439819 > > Thomas Baumgart changed: > >What|Removed |Added > > >Version Fixed In||5.1.3 > Status|CONFIRMED |RESOLVED > Latest Commit|| > https://invent.kde.org/offi >| > |ce/kmymoney/commit/b3ffeec2 >| > |1438efb18326159cd75530aee29 >||ca133 > Resolution|--- |FIXED > > --- Comment #7 from Thomas Baumgart --- > Git commit b3ffeec21438efb18326159cd75530aee29ca133 by Thomas Baumgart. > Committed on 23/07/2021 at 13:15. > Pushed by tbaumgart into branch '5.1'. > > Allow parens around an amount to be a valid when locale uses it > > A locale can request numbers to be presented with parens around the > value. This change allows them to be entered in this format in the > amount fields. > FIXED-IN: 5.1.3 > > M +1-0kmymoney/widgets/CMakeLists.txt > M +46 -0kmymoney/widgets/amountvalidator.cpp > M +2-0kmymoney/widgets/amountvalidator.h > M +1-0kmymoney/widgets/tests/CMakeLists.txt > > > https://invent.kde.org/office/kmymoney/commit/b3ffeec21438efb18326159cd75530aee29ca133 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 440238] New: Korganizer Crashing
https://bugs.kde.org/show_bug.cgi?id=440238 Bug ID: 440238 Summary: Korganizer Crashing Product: korganizer Version: 5.17.80 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: waynelloydsm...@gmail.com Target Milestone: --- Linux (x86_64)release 5.13.4 korganizer 5.17.3(21.04.3) SUMMARY edit a todo item in the past like jan 15 2021 note:the start date in the todo edit screen is different than the start date shown in the list (this is not the way it used to work) press Apply STEPS TO REPRODUCE 1. edit a todo item in the past like jan 15 2021 2. press Apply 3. crash OBSERVED RESULT I started it in a terminal so I could get some information about the crash org.kde.pim.akonadicore: Invalid mimetype requested: "" terminate called after throwing an instance of 'Akonadi::PayloadException' what(): Akonadi::PayloadException: Wrong payload type (requested: sp(0); present: sp(2)) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = korganizer path = /usr/bin pid = 16250 KCrash: Arguments: /usr/bin/korganizer KCrash: Attempting to start /usr/lib64/drkonqi EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFO i'm running on Slackware current with 5.13.4 kernel also known as Slackware 15 -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 440242] New: cannot display Cron lof files
https://bugs.kde.org/show_bug.cgi?id=440242 Bug ID: 440242 Summary: cannot display Cron lof files Product: KSystemLog Version: 21.04.3 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.ternis...@gmail.com Reporter: waynelloydsm...@gmail.com Target Milestone: --- SUMMARY the /var/log/cron log file looks empty but its not any system that runs logrotate will have four files cron , cron.1 , cron.2 , cron.3 and cron.4 you should be able to select which one you want to look at too STEPS TO REPRODUCE 1. click on the "Cron Log" button 2. at the bottom of the screen it says 18:20:23 Log successfully loaded OBSERVED RESULT 3. you are looking at a blank screen now EXPECTED RESULT you should see the data in the cron log file SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION 4. as root on a terminal cd /var/log 5. cat cron 6. you will get a screen full of information also I could find no way to add other log files that are in my system I'am running Slackware 15 log files in my sytem are debug , maillog , messages, faillog , lastlog ,secure, spooler, syslog. most of these use logrotate so there are four versions of them -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 440242] cannot display Cron log files
https://bugs.kde.org/show_bug.cgi?id=440242 Wayne Smith changed: What|Removed |Added Summary|cannot display Cron lof |cannot display Cron log |files |files -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 440238] Korganizer Crashing
https://bugs.kde.org/show_bug.cgi?id=440238 --- Comment #1 from Wayne Smith --- crashes frequently just select an event by double clicking on it then don't change anything and press "OK" or "APPLY" bash-5.1$ korganizer .. started the program from a terminal org.kde.pim.incidenceeditor: free slot calculation: invalid range. range( 0 ) / mSlotResolutionSeconds( 900 ) = 0 org.kde.pim.incidenceeditor: free slot calculation: invalid range. range( 0 ) / mSlotResolutionSeconds( 900 ) = 0 org.kde.pim.akonadicore: Invalid mimetype requested: "" terminate called after throwing an instance of 'Akonadi::PayloadException' what(): Akonadi::PayloadException: Wrong payload type (requested: sp(0); present: sp(2)) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = korganizer path = /usr/bin pid = 4739 KCrash: Arguments: /usr/bin/korganizer KCrash: Attempting to start /usr/lib64/drkonqi [1]+ Stopped korganizer -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2 (PCMPxSTRx $0x10)
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #9 from Wayne Arnold --- thank you. I was able to run this updated version on our code. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #4 from Wayne Arnold --- SSE 4.2 adds four string text processing instructions PCMPISTRI, PCMPISTRM, PCMPESTRI and PCMPESTRM. These instructions take three parameters, arg1 an xmm register, arg2 an xmm or a 128-bit memory location and IMM8 an 8-bit immediate control byte the current valgrind code implements the 1st case xmm register for both arg1 and arg2 is it possible to add the 2nd case of arg2 being being a memory location -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #3 from Wayne Arnold --- Created attachment 104388 --> https://bugs.kde.org/attachment.cgi?id=104388&action=edit unit test from rapidjson that uses sse4.2 unit test from rapidjson that fails with illegal instruction for pcmpistri when using MEM for arg2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 Wayne Arnold changed: What|Removed |Added Version|3.12 SVN|3.13 SVN -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #5 from Wayne Arnold --- the unit test is from: https://github.com/miloyip/rapidjson -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372188] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x62 0x4A 0x10 0x10 0x48 0x83 0xC2
https://bugs.kde.org/show_bug.cgi?id=372188 --- Comment #6 from Wayne Arnold --- any suggestions on how to add in the MEM option. are there other instructions that can be used as a guide ? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 499043] New: How to remove a user given permission to a Flatpak Application
https://bugs.kde.org/show_bug.cgi?id=499043 Bug ID: 499043 Summary: How to remove a user given permission to a Flatpak Application Classification: I don't know Product: kde Version: unspecified Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rmalla...@gmail.com Target Milestone: --- Created attachment 177610 --> https://bugs.kde.org/attachment.cgi?id=177610&action=edit removing permission in flatseal comapred to settings SUMMARY How does one remove a given permission to flatpak application without removing/resetting the another given permission . Say for example i give Brave Flatpak permission to have access to my A,B,C folder situated in my home to do so i go to system settings - application permission - flatpak permission - Brave - File System Access there i select the plus Add New icon and then select the file system path and select A folder and then under permission(probably) i select read write and last press ok. I do this for all 3 of them A, B, and C. Now suppose i want to remove permission for folder B there is no option for removing the permission instead i have to remove all of the add folder access permission by pressing the default button at the bottom. Compared to flatseal there is a cross next to user file access added permission which can be pressed to remove only that permission without affecting the remaining other given permission STEPS TO REPRODUCE 1. go to system settings 2. application permission 3. flatpak permission 4. select Brave 5. go to File System Access and press add new and add access to a folder OBSERVED RESULT after adding multiple permission there is no cross to remove only a selected permission EXPECTED RESULT a cross next to the added permission to remove it instead of a check mark toggle SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.9-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i3-1220P Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop X1502ZA_X1502ZA System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 499043] How to remove a user given permission to a Flatpak Application
https://bugs.kde.org/show_bug.cgi?id=499043 Bruce Wayne changed: What|Removed |Added CC||joshiesuha...@gmail.com Product|kde |systemsettings Component|general |kcm_flatpak Version|unspecified |6.2.5 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 499043] How to remove a user given permission to a Flatpak Application
https://bugs.kde.org/show_bug.cgi?id=499043 Bruce Wayne changed: What|Removed |Added Version|6.2.5 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 499043] How to remove a user given permission to a Flatpak Application
https://bugs.kde.org/show_bug.cgi?id=499043 --- Comment #2 from Bruce Wayne --- (In reply to David Edmundson from comment #1) > Untick apply, leave the page and it will be gone. > > It's the same thing just presented differently. oh sorry i didn't know , that how it is done. Thanks for the info -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500304] New: Glitchy Application Launcher
https://bugs.kde.org/show_bug.cgi?id=500304 Bug ID: 500304 Summary: Glitchy Application Launcher Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rmalla...@gmail.com Target Milestone: --- Created attachment 178509 --> https://bugs.kde.org/attachment.cgi?id=178509&action=edit recording of application launcher SUMMARY when Colour Accuracy under Settings-Display & Monitors is set to "Prefer Colour Accuracy" and the application launcher is opened and closed quickly either by mouse left click or windows key from the keyboard the application launcher is showing some rainbowy/black pixel artifact but if the Colour Accuracy is set to "Prefer Efficiency " Opening/Closing the application launcher is normal. STEPS TO REPRODUCE 1. Go to Application Launcher 2. Search Setting or Scroll to System 3. Go to System Settings 4. Display & Monitors 5. Select Colour Accuracy 6. From the drop down select Prefer Colour Accuracy 7. Hit Apply 8. Open and close the application launcher quickly OBSERVED RESULT rainbow and black pixel artifact when opening the Application Launcher EXPECTED RESULT Normal Application Launcher SOFTWARE/OS VERSIONS Operating System: CachyOS Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Intel® UHD Graphics 620 Manufacturer: HP Product Name: HP Laptop 15-bs1xx System Version: Type1ProductConfigId ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500860] New: Interating with a notification in the notification tray icon and open the related application
https://bugs.kde.org/show_bug.cgi?id=500860 Bug ID: 500860 Summary: Interating with a notification in the notification tray icon and open the related application Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rmalla...@gmail.com Target Milestone: --- Created attachment 178969 --> https://bugs.kde.org/attachment.cgi?id=178969&action=edit Notification Tray SUMMARY is there any way to interact with a notification like say opening the app when the notification tray is opened as in case for telegram when we get a notification clicking on the tray notification bell and open that chat/channel/group from the notification STEPS TO REPRODUCE 1. Get a notification on any messaging/chat application 2. let the notification bubble to timeout 3. click the bell notification tray 4. click on the notification (which was on step 1) OBSERVED RESULT clicking the notification does nothing, the bell tray icon only just show and notify us that there was a notification EXPECTED RESULT clicking the notification on the bell tray icon after the timeout open up the related app SOFTWARE/OS VERSIONS Operating System: CachyOS Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Intel® UHD Graphics 620 Manufacturer: HP Product Name: HP Laptop 15-bs1xx System Version: Type1ProductConfigId ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500860] Interating with a notification in the notification tray icon and open the related application
https://bugs.kde.org/show_bug.cgi?id=500860 --- Comment #1 from Bruce Wayne --- Created attachment 178970 --> https://bugs.kde.org/attachment.cgi?id=178970&action=edit when clicked on the notification opens telegram -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500860] Interating with a notification in the notification tray icon and open the related application
https://bugs.kde.org/show_bug.cgi?id=500860 --- Comment #2 from Bruce Wayne --- Created attachment 178971 --> https://bugs.kde.org/attachment.cgi?id=178971&action=edit clicking on the telegram notification from the bell does nothing -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 502358] New: Folder Properties window does a jumping animation
https://bugs.kde.org/show_bug.cgi?id=502358 Bug ID: 502358 Summary: Folder Properties window does a jumping animation Classification: Applications Product: dolphin Version: 24.12.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: rmalla...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 179962 --> https://bugs.kde.org/attachment.cgi?id=179962&action=edit jumping animation window effect SUMMARY when kdenetwork-filesharing is installed and property for a folder is opened the Dolphin does a jump animation window effect just once and thereafter doing the same dolphin show property window normally STEPS TO REPRODUCE 1. Install kdenetwork-filesharing 2. restart pc 3. open Dolphin 4. right click a folder and go to properties OBSERVED RESULT properties window does a jumping animation window effect EXPECTED RESULT normal property window without any effect SOFTWARE/OS VERSIONS Operating System: CachyOS Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.14.0-4-cachyos (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Intel® UHD Graphics 620 Manufacturer: HP Product Name: HP Laptop 15-bs1xx System Version: Type1ProductConfigId ADDITIONAL INFORMATION if kdenetwork-filesharing is not installed then opening property does no animation of opening the property window normally -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464245] Toggle for Mac-Randomization
https://bugs.kde.org/show_bug.cgi?id=464245 Bruce Wayne changed: What|Removed |Added CC||rmalla...@gmail.com --- Comment #6 from Bruce Wayne --- a gui similar to gnome would be appreciated where a user can toggle wifi mac randomization. Since in fedora 40+ for example they have set to wifi mac randomization. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 373082] New: Krunner Crash While System Is Idle
https://bugs.kde.org/show_bug.cgi?id=373082 Bug ID: 373082 Summary: Krunner Crash While System Is Idle Product: krunner Version: 5.7.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: altbins...@yahoo.com Target Milestone: --- Application: krunner (5.7.5) Qt Version: 5.6.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.8-200.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: System had been running 3 days, hardly used, unattended when crash occurred. Two open instances of Dolphin, One paused SMPlayer, one Firefox 50 from Fedora repo, one instance Konsole. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1c349f0940 (LWP 1997))] Thread 17 (Thread 0x7f1bdbfff700 (LWP 21322)): [KCrash Handler] #6 0x7f1c455d1765 in raise () at /lib64/libc.so.6 #7 0x7f1c455d336a in abort () at /lib64/libc.so.6 #8 0x7f1c45612710 in __libc_message () at /lib64/libc.so.6 #9 0x7f1c4561aeaa in _int_free () at /lib64/libc.so.6 #10 0x7f1c4561d6d0 in _int_realloc () at /lib64/libc.so.6 #11 0x7f1c4561e714 in realloc () at /lib64/libc.so.6 #12 0x7f1c46302dbb in QListData::realloc_grow(int) () at /lib64/libQt5Core.so.5 #13 0x7f1c46302f4a in QListData::prepend() () at /lib64/libQt5Core.so.5 #14 0x7f1c4647cc7f in QObjectCleanupHandler::add(QObject*) () at /lib64/libQt5Core.so.5 #15 0x7f1c46bc49ae in KPluginFactory::KPluginFactory() () at /lib64/libKF5CoreAddons.so.5 #16 0x7f1c00073d0d in factory::factory() () at /usr/lib64/qt5/plugins/kpackage/packagestructure/plasmoid_packagestructure.so #17 0x7f1c00073e0d in qt_plugin_instance () at /usr/lib64/qt5/plugins/kpackage/packagestructure/plasmoid_packagestructure.so #18 0x7f1c464360e3 in QPluginLoader::instance() () at /lib64/libQt5Core.so.5 #19 0x7f1c46bc89ac in KPluginLoader::factory() () at /lib64/libKF5CoreAddons.so.5 #20 0x7f1c480f6a08 in KPackage::PackageLoader::loadPackageStructure(QString const&) () at /lib64/libKF5Package.so.5 #21 0x7f1c480f7d48 in KPackage::PackageLoader::listPackages(QString const&, QString const&) () at /lib64/libKF5Package.so.5 #22 0x7f1c480f807d in KPackage::PackageLoader::findPackages(QString const&, QString const&, std::function) () at /lib64/libKF5Package.so.5 #23 0x7f1c48f4e5cd in Plasma::PluginLoader::listAppletInfo(QString const&, QString const&) () at /lib64/libKF5Plasma.so.5 #24 0x7f1c0bfd11c6 in WindowedWidgetsRunner::match(Plasma::RunnerContext&) () at /usr/lib64/qt5/plugins/krunner_windowedwidgets.so #25 0x7f1c195326f8 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /lib64/libKF5Runner.so.5 #26 0x7f1c193121f8 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5 #27 0x7f1c19310d40 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5 #28 0x7f1c19310850 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #29 0x7f1c462ac99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #30 0x7f1c41dda5ca in start_thread () at /lib64/libpthread.so.0 #31 0x7f1c456a00ed in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f1c00ff9700 (LWP 21321)): #0 0x7f1c41ddfbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1c462ad01a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f1c1930e8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f1c19312a78 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f1c1930da3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f1c19310909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f1c462ac99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f1c41dda5ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f1c456a00ed in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f1c017fa700 (LWP 21320)): #0 0x7f1c41ddfbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1c462ad01a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f1c1930e8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f1c19
[kwin] [Bug 482207] New: i915 Kwin and plasmashell crashes on hp530 notebook
https://bugs.kde.org/show_bug.cgi?id=482207 Bug ID: 482207 Summary: i915 Kwin and plasmashell crashes on hp530 notebook Classification: Plasma Product: kwin Version: 5.27.10 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: altbins...@yahoo.com Target Milestone: --- Application: kwin_x11 (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.6-200.fc39.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 39 (Thirty Nine)" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: At boot, during desktop load, Kwin will always crash and recover. It then runs for an unpredictable period, minutes or hours or nearly a day. Using 'kwin_x11 --replace' followed by 'plasmashell --no-respawn' restores function but the next crash may be seconds or hours away. It doesn't matter whether the system is being actively used or just sitting there displaying a slideshow or idling. Probably the system has finally met the software too evolved for it to run; it is an interesting experiment and in fact is perfectly usable as a daily driver for business-type use. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7fe89e5c80fc in i915_drm_batchbuffer_validate_buffers () at /usr/lib64/dri/i915_dri.so #5 0x7fe89e5c2724 in i915_emit_hardware_state () at /usr/lib64/dri/i915_dri.so #6 0x7fe89e5bebde in setup_tri () at /usr/lib64/dri/i915_dri.so #7 0x7fe89e08fdbc in pipe_run_linear () at /usr/lib64/dri/i915_dri.so #8 0x7fe89e090d93 in draw_pipeline_run_linear () at /usr/lib64/dri/i915_dri.so #9 0x7fe89e108527 in llvm_pipeline_generic.constprop.0.isra () at /usr/lib64/dri/i915_dri.so #10 0x7fe89e108899 in llvm_middle_end_linear_run () at /usr/lib64/dri/i915_dri.so #11 0x7fe89e09eb62 in vsplit_run_linear () at /usr/lib64/dri/i915_dri.so #12 0x7fe89e097922 in draw_pt_arrays.isra () at /usr/lib64/dri/i915_dri.so #13 0x7fe89e097cf0 in draw_instances () at /usr/lib64/dri/i915_dri.so #14 0x7fe89e0981ad in draw_vbo () at /usr/lib64/dri/i915_dri.so #15 0x7fe89e5b8926 in i915_draw_vbo () at /usr/lib64/dri/i915_dri.so #16 0x7fe89dd64289 in _mesa_draw_arrays.part.0 () at /usr/lib64/dri/i915_dri.so #17 0x7fe8bacae697 in KWin::ItemRendererOpenGL::renderItem(KWin::Item*, int, QRegion const&, KWin::WindowPaintData const&) () at /lib64/libkwin.so.5 #18 0x7fe8bacb2fb7 in KWin::WorkspaceScene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #19 0x7fe8bac3488b in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #20 0x7fe8bacb7b81 in KWin::WorkspaceScene::paintWindow(KWin::WindowItem*, int, QRegion const&) () at /lib64/libkwin.so.5 #21 0x7fe8bacb7e5e in KWin::WorkspaceScene::paintSimpleScreen(int, QRegion const&) () at /lib64/libkwin.so.5 #22 0x7fe8bac347d9 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /lib64/libkwin.so.5 #23 0x7fe8bacb7a9a in KWin::WorkspaceScene::paint(KWin::RenderTarget*, QRegion const&) () at /lib64/libkwin.so.5 #24 0x7fe8baca9751 in KWin::SceneDelegate::paint(KWin::RenderTarget*, QRegion const&) () at /lib64/libkwin.so.5 #25 0x7fe8babf28b8 in KWin::Compositor::paintPass(KWin::RenderLayer*, KWin::RenderTarget*, QRegion const&) () at /lib64/libkwin.so.5 #26 0x7fe8babf73c3 in KWin::Compositor::composite(KWin::RenderLoop*) () at /lib64/libkwin.so.5 #27 0x7fe8babf772d in KWin::X11Compositor::composite(KWin::RenderLoop*) () at /lib64/libkwin.so.5 #28 0x7fe8b92e9151 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #29 0x7fe8baba6c24 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /lib64/libkwin.so.5 #30 0x7fe8babfd48f in KWin::RenderLoopPrivate::dispatch() () at /lib64/libkwin.so.5 #31 0x7fe8b92e9151 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #32 0x7fe8b92ec6cd in QTimer::timeout(QTimer::QPrivateSignal) () at /lib64/libQt5Core.so.5 #33 0x7fe8b92df97b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #34 0x7fe8b87aeb95 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #35 0x7fe8b92b4e78 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #36 0x7fe8b930670b in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #37 0x7fe8b9307009 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #38 0x7fe8b6b11e5c in g_main_context_dispatch_unlocked.lto_pr
[plasmashell] [Bug 488316] New: Plasmashell Crash During grsync
https://bugs.kde.org/show_bug.cgi?id=488316
Bug ID: 488316
Summary: Plasmashell Crash During grsync
Classification: Plasma
Product: plasmashell
Version: 6.0.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: altbins...@yahoo.com
Target Milestone: 1.0
Application: plasmashell (6.0.5)
Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.8.11-300.fc40.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.0.5 [CoredumpBackend]
-- Information about the crash:
~15 windows open on one of three desktop monitors, running rsync on ~6GB
fileset over 1G ethernet. Brave browser (only one open) with ~100 tabs. One
video in pop-out window playing. Plasmashell suddenly died and disappeared, as
it has once before with this setup, two days ago, then came back. Video, IRC
etc. continued without loss. Something made plasma switch to software
rendering, which sucked until I logged out and back in.
Desktop effects: Translucency (custom settings), focus follows mouse (mouse
precedence), four desktops, three monitors, two GPUs (onboard RS880, RX 570) .
It's a Frankensystem with Asus AGM78-LE and Phenom II X4 955, 8GB DDR2-800
running at 533 because BIOS. Not production system.
There is an X11 use issue that may be related, as I am holding off dnf updates
( --exclude=plasma* ) until updated plasma-workspace-x11 is updated to match.
I cannot use Wayland unless and until they allow a corner of the titlebar to
raise focus on hover; I 'reverse cascade' windows to the left and down, use
translucency to see what is going on up to four windows deep, and focus each
window on hover without having to click. Wayland cannot do this. Phonecentric
bias?
The reporter is unsure if this crash is reproducible.
-- Backtrace (Reduced):
#5 0x7f8ad36b08a7 in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x555c34131f00) at
/usr/src/debug/plasma-workspace-6.0.5.1-1.fc40.x86_64/applets/kicker/plugin/kastatsfavoritesmodel.cpp:196
#6 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7
QtPrivate::FunctorCallable::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#8
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x555c34131ef0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#9 0x7f8b0e5ebdeb in QObject::event (this=0x555c340f9e90,
e=0x555c38206550) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:1452
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 488316] Plasmashell Crash During grsync
https://bugs.kde.org/show_bug.cgi?id=488316 --- Comment #1 from Wayne E. Nail --- Created attachment 170353 --> https://bugs.kde.org/attachment.cgi?id=170353&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446040] New: Plasmashell crashes after some time when system idling except for Frost-Next slow downloads
https://bugs.kde.org/show_bug.cgi?id=446040 Bug ID: 446040 Summary: Plasmashell crashes after some time when system idling except for Frost-Next slow downloads Product: plasmashell Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: altbins...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.5) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.18-200.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: Fedora 34 (MATE-Compiz) -- Information about the crash: - What I was doing when the application crashed: Nothing. Windows are open but the only activity is a Freenet node and the Frost-Next (java) application slowly downloading and refreshing groups (like a newsreader) - Unusual behavior I noticed: After some time -- minutes or hours -- I return to the system to discover that plasmashell has crashed and Frost-Next has closed. Krunner used to send command: 'kquitapp5 plasmashell && kstart5 plasmashell' has no visible effect. Must start plasmashell from a terminal instance with: 'kstart5 plasmashell' It then runs until it crashes again at some unpredictable point within a handful of hours The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f2b2b77d2a2 in raise () at /lib64/libc.so.6 #5 0x7f2b2b7668a4 in abort () at /lib64/libc.so.6 #6 0x7f2b2b766789 in _nl_load_domain.cold () at /lib64/libc.so.6 #7 0x7f2b2b775a16 in () at /lib64/libc.so.6 #8 0x7f2b185f5057 in () at /lib64/libdrm_nouveau.so.2 #9 0x7f2b185f4fb7 in nouveau_pushbuf_data () at /lib64/libdrm_nouveau.so.2 #10 0x7f2b185f50d2 in pushbuf_submit () at /lib64/libdrm_nouveau.so.2 #11 0x7f2b185f5337 in pushbuf_flush.isra () at /lib64/libdrm_nouveau.so.2 #12 0x7f2b185f607d in pushbuf_validate () at /lib64/libdrm_nouveau.so.2 #13 0x7f2b131151a6 in nve4_p2mf_push_linear () at /usr/lib64/dri/nouveau_dri.so #14 0x7f2b1311a9a1 in nouveau_transfer_write () at /usr/lib64/dri/nouveau_dri.so #15 0x7f2b1311ab78 in nouveau_buffer_transfer_unmap () at /usr/lib64/dri/nouveau_dri.so #16 0x7f2b1333b957 in u_default_buffer_subdata () at /usr/lib64/dri/nouveau_dri.so #17 0x7f2b128a6937 in st_bufferobj_data () at /usr/lib64/dri/nouveau_dri.so #18 0x7f2b1290ec67 in buffer_data_error () at /usr/lib64/dri/nouveau_dri.so #19 0x7f2b12912395 in _mesa_BufferData () at /usr/lib64/dri/nouveau_dri.so #20 0x7f2b2d6f740d in QSGBatchRenderer::Renderer::unmap(QSGBatchRenderer::Buffer*, bool) () at /lib64/libQt5Quick.so.5 #21 0x7f2b2d70078e in QSGBatchRenderer::Renderer::uploadBatch(QSGBatchRenderer::Batch*) () at /lib64/libQt5Quick.so.5 #22 0x7f2b2d706dcb in QSGBatchRenderer::Renderer::render() () at /lib64/libQt5Quick.so.5 #23 0x7f2b2d6f37c4 in QSGRenderer::renderScene(QSGBindable const&) () at /lib64/libQt5Quick.so.5 #24 0x7f2b2d6f3c63 in QSGRenderer::renderScene(unsigned int) () at /lib64/libQt5Quick.so.5 #25 0x7f2b2d74c825 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /lib64/libQt5Quick.so.5 #26 0x7f2b2d7a72e9 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /lib64/libQt5Quick.so.5 #27 0x7f2b2d73f712 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #28 0x7f2b2d7b1acc in QQuickWindow::event(QEvent*) () at /lib64/libQt5Quick.so.5 #29 0x7f2b2ca9e443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #30 0x7f2b2bdd67b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #31 0x7f2b2c21b094 in QPlatformWindow::windowEvent(QEvent*) () at /lib64/libQt5Gui.so.5 #32 0x7f2b2caa565a in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #33 0x7f2b2bdd67b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #34 0x7f2b2be26e83 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #35 0x7f2b2be277d4 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #36 0x7f2b2a1d54cf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #37 0x7f2b2a2294f8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #38 0x7f2b2a1d2c03 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #39 0x7f2b2be27b98 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #40 0x7f2b2bdd51c2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #41 0x7f2b2bddd704 in QCoreApplication::exec() () at /lib64/l
[kdepim] [Bug 492365] New: kjots fails to start after dnf update: undefined symbol
https://bugs.kde.org/show_bug.cgi?id=492365 Bug ID: 492365 Summary: kjots fails to start after dnf update: undefined symbol Classification: Applications Product: kdepim Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: waynen...@bellsouth.net Target Milestone: --- SUMMARY kjots fails to start after dnf update 26 or 27 August 2024 with: $ kjots: symbol lookup error: kjots: undefined symbol: _ZN5KMime7Content4sizeEv [1]+ Exit 127kjots STEPS TO REPRODUCE 1. Notice launching kjots from application launcher does animation and disappears 2. Enter 'kjots &' in konsole 3. Weep in despair as kjots completely fails to load OBSERVED RESULT kjots does not load. I can use KFind to search for contents of each note (every record is a separate file) in ~/.local/share/notes/ and display that file in KMail Viewer but this is unacceptable. EXPECTED RESULT kjots loads normally and displays my laboriously constructed over decades notes. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora Linux 40 (Workstation) KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION All I want is a simple, unambitious note storage application. No fancy features, no integration with anything, completely portable, free-form without predefined fields, and *STABLE*. I have used and lost too many notes applications to count or remember, starting with the TSR Sidekick because I am *OLD*. Devs likely hate this concept because it is probably boring for them. Thus applications are serially abandoned in favor of the newest whiz kid's enthusiastic exploration of tools-du-jour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
https://bugs.kde.org/show_bug.cgi?id=488187 Wayne E. Nail changed: What|Removed |Added CC||altbins...@yahoo.com --- Comment #22 from Wayne E. Nail --- Plasma 6.1.1, plasma-workspace-x11-6.1.1-1.fc40.x86_64, kernel 6.9.7-200.fc40.x86_64, AMD Phenom II X4 955, AMD RX570. Neither the Log Out, Reboot, or Power buttons on Application Menu have any effect at all. I use 'systemctl reboot' in a root terminal tab. -- You are receiving this mail because: You are watching all bug changes.
[kjots] [Bug 324285] Kjots not migrating data since the upgrade to Ubuntu 13.04
https://bugs.kde.org/show_bug.cgi?id=324285 Wayne E. Nail changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Wayne E. Nail --- At risk of violating some rule, I am pasting an IRC conversation snippet showing how I finally resolved the kjots .book file import problem, years later, on 20 February 2018. This was to migrate a version of the .book file stored on a Fedora 21 system to a Fedora 27 system. I don't remember how I managed to migrate from Fedora 15 to (eventually) Fedora 21. The trick to migrate from F21 to F27 was to install akonadiconsole, which is not an easy package to find, and which eluded all my attempts to search for anything related to kjots. So, apparently, the import issue has been solved. It *may* be necessary to copy the old-version-to-be-imported subtree to the new system in order to be able to navigate to it using the akonadiconsole GUI (with 'show hidden files' enabled). maybe so.. dnf install akonadiconsole Okay, I do now. Nice of them to let me know what the name is ;-) I mean, I searched that Good grief. It's under 'Development' category oh you're using a gui tool of some kind? This is probably what I needed. It even has kjots and Notes categories Well, yeah, the akonadiconsole, now well, maybe you can use it directly dunno because i don't know what i'm doing i'm just having you repeat what i did :) argonel: Marry me! ;-) It *worked* lol cool! I have been trying to get this done for... geez. Years! what did you do in akonadiconsole to actually get it to load the data? I literally ( and I use that term in its most literal sense ) cannot thank you enough Navigated to the copy of the directory containing the F21 book that I had pasted into ~/.local/share/notes/.aPAZXfDvf4c.directory/ and the console said it was a valid maildir, so I clicked go and it did it Acrophosist: navigated how? Specifically, in akonadiconsole, selected Agents/kjots, Configure, Configure Natively, Maildir, (navigated to ~/.local dir abovementioned), clicked OK, done There's a browse button at the end of the location bar You have to right-click to select 'show hidden folders' and then drill down again \o/ ^ whs you have a kjots agent? It's listed in the akonadiconsole gui Both kjots and Notes ... which helps clear up some conflation from previous versions ok weird, i don't have kjots When you find the directory containing valid data .. I still don't know if it will read .book files but I will check tomorrow and report back .. it will tell you 'The selected path contains valid Maildir folders.' You might need to install kjots separately, or depending upon distro, some package that contains kjots in the PIM packages this sort of thing is where akonadi gets its reputation. i *have* kjots, and with data in it :) # dnf list | grep -i kjots ... kjots.x86_64 5.0.2-7.fc27 @updates -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421360] New: Plasma crash during period of inactivity
https://bugs.kde.org/show_bug.cgi?id=421360 Bug ID: 421360 Summary: Plasma crash during period of inactivity Product: plasmashell Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: altbins...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.6.7-200.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: Nothing. The system had been running for days and suddenly plasma crashed, leaving only media frame widget on a blank screen. After about a minute plasma recovered. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efc64027800 (LWP 2507))] Thread 28 (Thread 0x7efbe64ed700 (LWP 145163)): #0 0x7efc67200d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efc67d4c943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7efc67d4c9d1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7efc699924e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #4 0x7efc6999278d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #5 0x7efc67d46e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7efc671fa4e2 in start_thread () at /lib64/libpthread.so.0 #7 0x7efc679c36a3 in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7efbf51f2700 (LWP 145162)): #0 0x7efc67200d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efc550cb11b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7efc550cad2b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7efc671fa4e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7efc679c36a3 in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7efc0590d700 (LWP 6013)): #0 0x7efc67200d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efc550cb11b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7efc550cad2b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7efc671fa4e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7efc679c36a3 in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7efc17fff700 (LWP 4420)): #0 0x7efc67200d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efc67d4c943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7efc67d4c9d1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7efc699924e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #4 0x7efc6999278d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #5 0x7efc67d46e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7efc671fa4e2 in start_thread () at /lib64/libpthread.so.0 #7 0x7efc679c36a3 in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7efbf49f0700 (LWP 4419)): #0 0x7efc67200d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efc550cb11b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7efc550cad2b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7efc671fa4e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7efc679c36a3 in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7efbe7eff700 (LWP 4163)): #0 0x7efc67200d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efc67d4c943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7efc67d4c9d1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7efc699924e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #4 0x7efc6999278d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #5 0x7efc67d46e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7efc671fa4e2 in start_thread () at /lib64/libpthread.so.0 #7 0x7efc679c36a3 in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7efbe76fe700 (LWP 4162)): #0 0x7efc67200d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efc550cb11b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7efc550cad2b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7efc671fa4e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7efc679c36a3 in clo
[plasmashell] [Bug 387032] Desktop freeze and reload
https://bugs.kde.org/show_bug.cgi?id=387032 Wayne E. Nail changed: What|Removed |Added CC||altbins...@yahoo.com --- Comment #3 from Wayne E. Nail --- Okay, sure. Glad to. But... where? To Whom? How? Maybe a url? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387700] New: Fedora 26 Plasmashell crashes, reloads every few minutes even when console is idle
https://bugs.kde.org/show_bug.cgi?id=387700 Bug ID: 387700 Summary: Fedora 26 Plasmashell crashes, reloads every few minutes even when console is idle Product: plasmashell Version: 5.10.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: altbins...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.13.16-202.fc26.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: In the following alleged duplicate, Christoph Feck advised: _ https://bugs.kde.org/show_bug.cgi?id=387032 Christoph Feck 2017-11-29 22:08:54 UTC Crash is in radeon drivers. Please report this issue directly to radeon developers. _ That's *sort of* useful, provided one is cognizant of quite a number of assumptions implied. Where are the radeon devs? A URL perhaps? An IRC #channel? How many bugzilla variant sites am I already a member of, even if they keep pretending they never heard of me because of some silly pretension of password rotation necessity? Some us may have been *using* linux very happily for 15 years, but we might not all be coders, right? So now you get this new filing of a (possible) duplicate. Note that I have functioned quite well as an experimental laboratory animal for projects including Transmission, Freenet, GPRename, and a few others. So I am happy to help as I can. Primary display: Ancor Communications Inc ASUS VN248 (DVI-0) Secondary display: Distributed Managment Task Force, Inc. (DMTF) CHHWJT* (HDMI-0) <<--Changhong LED50YC2000UA 50-inch TV Both 1920x1080p with refresh set to 'Auto' but almost certainly 60Hz on both # lspci | grep -i vga 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] Wayland pukes and nearly dies while splattering applicatiuons across both monitors in wrong resolutions and apparently at random. So, using Kwin with X11 # lspci | grep -i radeon 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] journalctl --dmesg is flooded with hundreds of red 'va above limit' lines in red, repeating with tiny increments in addresses: kernel: radeon :05:00.0: va above limit (0x00200E97 # uname -a Linux callgirl.cos.lan 4.13.16-202.fc26.x86_64 #1 SMP Thu Nov 30 15:39:32 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Both monitors are set to Wallpaper Layout: Desktop Wallpaper Type: Slideshow Positioning: Scaled, Keep Proportions Change every 0h 1m 1s on primary; 0h 1m 0s on secondary On primary monitor only: Plasmoid Media Frame, Change picture every 9.8s for 1st instance, 14.8s for 2nd, 3rd, and 4th instances. All are Fill mode: Preserve aspect fit, Pause on mouseover, Left click image opens in external viewer, half a dozen paths to stored localhost photos selected This never happened with F25, and from what I have read it appears to be a regression because someone forgot to backport some fixes to the Radeon HD 7750/8740 / R7 250E. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff7d8e564c0 (LWP 9708))] Thread 18 (Thread 0x7ff71f15a700 (LWP 10671)): #0 0x7ff7e499942d in read () at /lib64/libc.so.6 #1 0x7ff7dd8bb150 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7ff7dd877088 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7ff7dd877520 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7ff7dd87768c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7ff7e57c549b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7ff7e577322a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7ff7e55c499a in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7ff6eab43497 in KCupsConnection::run() () at /lib64/libkcupslib.so #9 0x7ff7e55c8c72 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7ff7e3ce636d in start_thread () at /lib64/libpthread.so.0 #11 0x7ff7e49a9e1f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7ff6fd117700 (LWP 10640)): #0 0x7ff7dd876ac4 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #1 0x7ff7dd8774ab in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7ff7dd87768c in g_main_context_iteration () at /lib64/l
[Discover] [Bug 394566] New: Discover Crashes When Clicking "Installed"
https://bugs.kde.org/show_bug.cgi?id=394566 Bug ID: 394566 Summary: Discover Crashes When Clicking "Installed" Product: Discover Version: 5.12.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: shwayb...@gmail.com Target Milestone: --- Application: plasma-discover (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.16.8-300.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: I opened Discover, and at the bottom left corner clicked "Installed" and the program crashed. The bug is repeatable on my system. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4514999e00 (LWP 17055))] Thread 13 (Thread 0x7f44d54c1700 (LWP 17987)): #0 0x7f451e354929 in poll () at /lib64/libc.so.6 #1 0x7f4517dc5b06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f4517dc5c30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f451f220c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f451f1cf12b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f451f01d9c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f451f02211d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f451c6cc564 in start_thread () at /lib64/libpthread.so.0 #8 0x7f451e35f31f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f44bcd13700 (LWP 17082)): #0 0x7f451e354929 in poll () at /lib64/libc.so.6 #1 0x7f4517dc5b06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f4517dc5c30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f451f220c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f451f1cf12b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f451f01d9c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f451f02211d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f451c6cc564 in start_thread () at /lib64/libpthread.so.0 #8 0x7f451e35f31f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f44bd9a3700 (LWP 17080)): #0 0x7f451e354929 in poll () at /lib64/libc.so.6 #1 0x7f4517dc5b06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f4517dc5ec2 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #3 0x7f44d42d060a in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #4 0x7f4517dedcea in g_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7f451c6cc564 in start_thread () at /lib64/libpthread.so.0 #6 0x7f451e35f31f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f44be1a4700 (LWP 17079)): #0 0x7f451e350374 in read () at /lib64/libc.so.6 #1 0x7f4517e0add0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f4517dc55fb in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f4517dc5ab0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f4517dc5c30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f4517dc5c81 in glib_worker_main () at /lib64/libglib-2.0.so.0 #6 0x7f4517dedcea in g_thread_proxy () at /lib64/libglib-2.0.so.0 #7 0x7f451c6cc564 in start_thread () at /lib64/libpthread.so.0 #8 0x7f451e35f31f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f44d6adf700 (LWP 17075)): #0 0x7f451f21ef31 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #1 0x7f451f22083f in timerSourceCheckHelper(GTimerSource*) () at /lib64/libQt5Core.so.5 #2 0x7f4517dc5521 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f4517dc5ab0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f4517dc5c30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f451f220c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f451f1cf12b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f451f01d9c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f451f02211d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f451c6cc564 in start_thread () at /lib64/libpthread.so.0 #10 0x7f451e35f31f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f44d72e0700 (LWP 17074)): #0 0x7f451e354929 in poll () at /lib64/libc.so.6 #1 0x7f4517dc5b06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f4517dc5c30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f451f220c2b in QEventDispatcherG
[kleopatra] [Bug 346136] while starting kleopatra, the selftest detects a problem with the libkleopatrarc file
https://bugs.kde.org/show_bug.cgi?id=346136 Wayne changed: What|Removed |Added CC||k...@photographic.org --- Comment #3 from Wayne --- Did you ever find a solution for this error? I am seeing the exact same thing. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 357396] New: Tried to open KDE Wallet Manager Handbook. Window flag in task bar opens and then closes. F1 does nothing.
https://bugs.kde.org/show_bug.cgi?id=357396 Bug ID: 357396 Summary: Tried to open KDE Wallet Manager Handbook. Window flag in task bar opens and then closes. F1 does nothing. Product: kwalletmanager Version: 2.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: waynesbox...@gmail.com While trying to set KDE Wallet up I tried to open the handbook for the program. There was a new window flag that appeared in the task bar like it was going to show the handbook, but then it just disappeared. Pressing F1 to open the handbook does absolutely nothing. Also I'm not sure I fully understand what this program is for. Is there a detailed source explaining in full detail the why as well as the how? Thanks. Reproducible: Always Steps to Reproduce: 1. Open Kwallet 2. Click on "Help" 3. Click on "KDE Wallet Manager Handbook" or press F1. Actual Results: There was a new window flag that appeared in the task bar like it was going to show the handbook, but then it just disappeared. Expected Results: Open the handbook. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358037] New: Filling a selection with bucket tool.
https://bugs.kde.org/show_bug.cgi?id=358037 Bug ID: 358037 Summary: Filling a selection with bucket tool. Product: krita Version: 2.9.6 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: wolf-eye...@hotmail.com When i create a selection and then try to fill it with the bucket tool, it fills the whole image. When however i use the gradient tool, it fills the selection just fine? Reproducible: Always Steps to Reproduce: 1.Make a selection with any selection tool. 2.select bucket fill 3.fill selection Actual Results: It filled the whole image rather than just the selection, Expected Results: It should have filled only the area that i created a selection. I do find that Krita also seems to have crashing problems too. It sometimes also takes a little while to start up or even after selecting a canvas size, takes a little while to get going. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362522] Cursor becomes "hand grab cursor" stuck after using "Set horizontal mirror mode"
https://bugs.kde.org/show_bug.cgi?id=362522 Wayne Parker changed: What|Removed |Added CC||artmess...@live.com --- Comment #2 from Wayne Parker --- Can confirm, it happens to me as well. Windows 10 Nvidia Geforce -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362522] Cursor becomes "hand grab cursor" stuck after using "Set horizontal mirror mode"
https://bugs.kde.org/show_bug.cgi?id=362522 --- Comment #4 from Wayne Parker --- Thank you Dmitry :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362764] New: Toolbox Icons Resize problem
https://bugs.kde.org/show_bug.cgi?id=362764 Bug ID: 362764 Summary: Toolbox Icons Resize problem Product: krita Version: 3.0 Beta Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: artmess...@live.com When right clicking and changing the toolbox icon sizes, the image icons remain normal (small) scaled, but the tile/box around the icons increase. The icon of the tool itself is unchanged. The feature worked previously as I used to increase the toolbox icons to use with my surface pro. The feature now seems to be broken. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 Wayne Parker changed: What|Removed |Added CC||artmess...@live.com --- Comment #2 from Wayne Parker --- I can confirm this is definitely a problem. I can't save shortcuts, or brush preset changes. Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361593] Hotkeys are not saved in krita-2.99.89
https://bugs.kde.org/show_bug.cgi?id=361593 --- Comment #3 from Wayne Parker --- I can confirm this is definitely a problem. I can't save shortcuts, or brush preset changes. Windows 10 -- You are receiving this mail because: You are watching all bug changes.
