[keditbookmarks] [Bug 488181] New: keditbookmarks doesn't show in launcher
https://bugs.kde.org/show_bug.cgi?id=488181 Bug ID: 488181 Summary: keditbookmarks doesn't show in launcher Classification: Applications Product: keditbookmarks Version: 23.08.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: k...@kenrushia.com Target Milestone: --- SUMMARY keditbookmarks doesn't show in launchers because of NoDisplay=True in org.kde.keditbookmarks.desktop Would be nice if it showed up. SOFTWARE/OS VERSIONS Bookmark Editor Version 23.08.5 KDE Frameworks Version 5.115.0 Gentoo kde-apps/keditbookmarks-23.08.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 487303] plasma-brower-integration causes Cloudflare to lock out humans
https://bugs.kde.org/show_bug.cgi?id=487303 --- Comment #9 from Ken --- (In reply to Ken from comment #8) > Confirm the same issue using Brave browser with KDE Plasma Integration v1.9. > Turnstile works fine on the same machine using Firefox and works fine on > Brave when Plasma Integration extension is disabled. PS - Issue only started recently (this week). Have been using Brave with Plasma Integration for years without prior Turnstile issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 487303] plasma-brower-integration causes Cloudflare to lock out humans
https://bugs.kde.org/show_bug.cgi?id=487303 Ken changed: What|Removed |Added CC||k...@remotetohome.io --- Comment #8 from Ken --- Confirm the same issue using Brave browser with KDE Plasma Integration v1.9. Turnstile works fine on the same machine using Firefox and works fine on Brave when Plasma Integration extension is disabled. -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr
https://bugs.kde.org/show_bug.cgi?id=485407 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485510] System Settings crash when trying to set auto-login
https://bugs.kde.org/show_bug.cgi?id=485510 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485769] Autologin settings for SSD not read from kde_settings.conf correctly
https://bugs.kde.org/show_bug.cgi?id=485769 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 427307] Strange behavior of module 'Printers--System Settings'
https://bugs.kde.org/show_bug.cgi?id=427307 --- Comment #4 from Ken Jarstad --- I upgraded to Kubuntu 22.04 and a Canon Maxify printer. No issues. Please close the Bug report. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442160] Can not use shift+click to select a range
https://bugs.kde.org/show_bug.cgi?id=442160 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 299898] The generalized time (year, month, day, hour, etc.) displayed should have the capability of showing seconds, milliseconds, and the time zone.
https://bugs.kde.org/show_bug.cgi?id=299898 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 449687] Karbon crashes when opening a particular odg file
https://bugs.kde.org/show_bug.cgi?id=449687 Ken Rushia changed: What|Removed |Added CC||dan...@dmarcucci.it --- Comment #3 from Ken Rushia --- *** Bug 448249 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 448249] I using libreoffice-draw and crash but exit error from karbon
https://bugs.kde.org/show_bug.cgi?id=448249 Ken Rushia changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||k...@kenrushia.com --- Comment #1 from Ken Rushia --- *** This bug has been marked as a duplicate of bug 449687 *** -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 449687] Karbon crashes when opening a particular odg file
https://bugs.kde.org/show_bug.cgi?id=449687 --- Comment #2 from Ken Rushia --- Created attachment 165142 --> https://bugs.kde.org/attachment.cgi?id=165142=edit Another file that causes the crash Probably authored by Libreoffice, but can't remember. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 449687] Karbon crashes when opening a particular odg file
https://bugs.kde.org/show_bug.cgi?id=449687 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 125474] MAINTENANCE : possibility to merge digiKam databases
https://bugs.kde.org/show_bug.cgi?id=125474 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478660] New: Adding clip zone to timeline is always adding video and audio together
https://bugs.kde.org/show_bug.cgi?id=478660 Bug ID: 478660 Summary: Adding clip zone to timeline is always adding video and audio together Classification: Applications Product: kdenlive Version: 23.08.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: krovma...@gmail.com Target Milestone: --- Created attachment 164258 --> https://bugs.kde.org/attachment.cgi?id=164258=edit The icons mentioned in description. SUMMARY Adding clip zone to timeline is always adding video and audio together STEPS TO REPRODUCE 0. Ensure the imported clip has both audio and video tracks activated. 1. Set zone In Point and Out Point on an imported video clip, and click Insert Zone in Project Bin. 2. Add the zone to timeline, by clicking and dragging from the video icon or audio icon, which intends to add video or audio only. OBSERVED RESULT If dragged to an AV track, audio and video are always added together, as if drag a clip without clicking the video icon or audio icon. Zone can't be added to audio-only track or video-only track. EXPECTED RESULT Can add only audio or video, according to which icon is clicked at the beginning of operation. SOFTWARE/OS VERSIONS Kdenlive: 23.08.3 Package Type: Unknown/Default MLT: 7.21.0 Qt: 5.15.10 (built against 5.15.10 x86_64-little_endian-llp64) Frameworks: 5.111.0 System: Windows 11 Version 2009 Kernel: winnt 10.0.22621 CPU: x86_64 Windowing System: windows Movit (GPU): disabled Track Compositing: qtblend -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 476902] [Feature Request] Indicate if hardware acceleration is working
https://bugs.kde.org/show_bug.cgi?id=476902 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #242 from Ken Fallon --- To be 100% clear, the work that the teams are doing and the amount of time and effort involved is appreciated. It is also reasonable to ask for a bug like this to be fixed. If you're not going to fix it then fine. The solution of "RESOLVED UPSTREAM" is not correct when the bug in question is marked at the QT side as "Unresolved". I would suggest INTENTIONAL, or NOT A BUG would better reflect the status. As a side note Thunderbird had a similar discussion which is now resolved. https://bugzilla.mozilla.org/show_bug.cgi?id=1509096 My suggestion of a #4 rolling your own was very serious. I would appreciate someone helping me with a beginners guide to creating a custom locale for the different distros. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #239 from Ken Fallon --- I think there is a fourth option. 4. Create a ugly hack where each user generates a custom locale for themselves -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 459573] KDE Daemon crashes on startup
https://bugs.kde.org/show_bug.cgi?id=459573 --- Comment #8 from Ken Roberts --- Comment on attachment 154235 --> https://bugs.kde.org/attachment.cgi?id=154235 New crash information added by DrKonqi I no longer run Rocky Linux. Cannot verify any fixes. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 472384] Breaks copy function in Google Sheets
https://bugs.kde.org/show_bug.cgi?id=472384 Ken changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Ken --- Disregard, there's another factor at play here. I don't believe the browser extension is the root cause. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 472384] Breaks copy function in Google Sheets
https://bugs.kde.org/show_bug.cgi?id=472384 Ken changed: What|Removed |Added CC||khawkin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 472384] New: Breaks copy function in Google Sheets
https://bugs.kde.org/show_bug.cgi?id=472384 Bug ID: 472384 Summary: Breaks copy function in Google Sheets Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: khawkin...@gmail.com Target Milestone: --- SUMMARY Using the browser extension FF (115.0.2 (64-bit), Manjaro ) breaks the ability to Ctrl+C copy in Google Sheets. Copying from the Google Sheets menu entry works fine. Disabling the browser extension and reloading the Google Sheets tab allows Ctrl+C to work normally. STEPS TO REPRODUCE 1. Install the browser extension 2. Attempt to Ctrl+C in google sheets (silently fails, no browser error) 3. Ctrl-V pastes the previous clipboard value SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.3-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1130G7 @ 1.10GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469212] New: plasma shell and kded5 crashing when KDE system settings is opened.
https://bugs.kde.org/show_bug.cgi?id=469212 Bug ID: 469212 Summary: plasma shell and kded5 crashing when KDE system settings is opened. Classification: Plasma Product: plasmashell Version: 5.24.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: kct...@juno.com Target Milestone: 1.0 Created attachment 158579 --> https://bugs.kde.org/attachment.cgi?id=158579=edit Dr Konqi generated crash report with debug symbols SUMMARY *** plasma shell and kded5 crashing when KDE system settings is opened. Backtrace with symbols attached. *** STEPS TO REPRODUCE 1. Click on System Preferences located Pinned to Icons-Only Task Manager 2. Wait several seconds. Crashes only appear approximately 15% of the time. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux = 5.14.21-150400-default x86_64 / KDE Plasma = 5.24.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz Memory: 30.3 GiB of RAM Graphics Processor: Radeon RX550/550 Series kded5 also closed unexpectedly, but cannot be reported because kded5 does not provide a bug reporting address. -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 468227] New: CPU vs CPU game crash
https://bugs.kde.org/show_bug.cgi?id=468227
Bug ID: 468227
Summary: CPU vs CPU game crash
Classification: Applications
Product: knights
Version: 2.6.22123
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: alexander.se...@web.de
Reporter: k...@kenrushia.com
CC: kde-games-b...@kde.org
Target Milestone: ---
Application: knights (2.6.22123)
(Compiled from sources)
Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 5.15.16-gentoo-dist x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.26.5 [KCrashBackend]
-- Information about the crash:
Crash at some point when watching a game with Stockfish vs Stockfish...
The crash can be reproduced every time.
-- Backtrace:
Application: Knights (knights), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 std::__atomic_base::operator++ (this=0xc08e59623ff792c4) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/atomic_base.h:384
#7 QAtomicOps::ref (_q_value=) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:283
#8 QBasicAtomicInteger::ref (this=0xc08e59623ff792c4) at
/usr/include/qt5/QtCore/qbasicatomic.h:118
#9 QSharedDataPointer::QSharedDataPointer (o=...,
this=0x7ffc5b4edfb8) at /usr/include/qt5/QtCore/qshareddata.h:96
#10 Knights::Move::Move (this=this@entry=0x7ffc5b4edfb0, other=...) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/core/move.cpp:104
#11 0x558982e00303 in QtPrivate::indexOf
(from=0, u=..., list=...) at /usr/include/qt5/QtCore/qlist.h:1042
#12 QList::indexOf (from=0, t=..., this=0x7ffc5b4ee088) at
/usr/include/qt5/QtCore/qlist.h:1026
#13 QList::removeOne (_t=..., this=0x7ffc5b4ee088) at
/usr/include/qt5/QtCore/qlist.h:962
#14 Knights::ChessRules::legalMoves (this=0x55898550bf90, pos=...) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/rules/chessrules.cpp:163
#15 0x558982dfc8df in Knights::ChessRules::changeNotation (this=, move=0x7ffc5b4ee2b0, notation=, color=Knights::White) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/rules/chessrules.cpp:584
#16 0x558982e018a0 in Knights::ChessRules::checkSpecialFlags
(this=0x55898550bf90, move=0x7ffc5b4ee2b0, color=Knights::White) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/rules/chessrules.cpp:285
#17 0x558982dfc321 in Knights::ChessRules::changeNotation (this=, move=, notation=, color=) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/rules/chessrules.cpp:631
#18 0x558982e02167 in Knights::ChessRules::checkSpecialFlags
(this=0x55898550bf90, move=0x7ffc5b4ee400, color=Knights::White) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/rules/chessrules.cpp:280
#19 0x558982e14faa in Knights::Manager::processMove (this=0x558982e48580
<(anonymous namespace)::Q_QGS_instance::innerFunction()::holder>, move=...) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/gamemanager.cpp:736
#20 0x7fded3efa602 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5b4ee520,
r=0x558982e48580 <(anonymous
namespace)::Q_QGS_instance::innerFunction()::holder>, this=0x5589853bd410) at
/usr/src/debug/dev-qt/qtcore-5.15.8-r3/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x558985105020, signal_index=3,
argv=0x7ffc5b4ee520) at
/usr/src/debug/dev-qt/qtcore-5.15.8-r3/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3923
#22 0x7fded3ef44ff in QMetaObject::activate
(sender=sender@entry=0x558985105020, m=m@entry=0x558982e46020
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc5b4ee520)
at
/usr/src/debug/dev-qt/qtcore-5.15.8-r3/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3983
#23 0x558982dd8c5e in Knights::Protocol::pieceMoved
(this=this@entry=0x558985105020, _t1=...) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3_build/src/knights_autogen/I75TQUSI5N/moc_protocol.cpp:374
#24 0x558982dee121 in Knights::UciProtocol::parseLine (this=0x558985105020,
line=...) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/proto/uciprotocol.cpp:61
#25 0x558982de22f8 in Knights::TextProtocol::readFromDevice
(this=0x558985105020) at
/usr/src/debug/kde-apps/knights-22.12.3/knights-22.12.3/src/proto/textprotocol.cpp:48
#26 0x7fded3efa602 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5b4ee6c0,
r=0x558985105020, this=0x558985503bf0) at
/usr/src/debug/dev-qt/qtcore-5.15.8-r3/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#27 doActivate (sender=0x7fdec80093d0, signal_index=3,
argv=0x7ffc5b4ee6c0) at
/usr/src/debug/dev-qt/qtcore-5.15.8-r3/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3923
[yakuake] [Bug 449540] Open Tab in New Profile with Yakuake
https://bugs.kde.org/show_bug.cgi?id=449540 Ken Rushia changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@kenrushia.com Status|REPORTED|RESOLVED --- Comment #2 from Ken Rushia --- *** This bug has been marked as a duplicate of bug 313210 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 313210] Ability to open a new tab with a specific profile
https://bugs.kde.org/show_bug.cgi?id=313210 Ken Rushia changed: What|Removed |Added CC||tste...@protonmail.com --- Comment #3 from Ken Rushia --- *** Bug 449540 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 464977] Add option to start new session with specific profile in tab bar, plus keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=464977 Ken Rushia changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@kenrushia.com Resolution|--- |DUPLICATE --- Comment #1 from Ken Rushia --- *** This bug has been marked as a duplicate of bug 313210 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 313210] Ability to open a new tab with a specific profile
https://bugs.kde.org/show_bug.cgi?id=313210 Ken Rushia changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #2 from Ken Rushia --- *** Bug 464977 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448681] digikam uses abandoned library incompatible with ffmpeg 5.0
https://bugs.kde.org/show_bug.cgi?id=448681 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445058] kwin interactive console does not work
https://bugs.kde.org/show_bug.cgi?id=445058 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 467040] New: Include game seed in bug report wizard
https://bugs.kde.org/show_bug.cgi?id=467040 Bug ID: 467040 Summary: Include game seed in bug report wizard Classification: Applications Product: kpat Version: 22.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: k...@kenrushia.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY When invoking the bug report wizard; the game type, options, and seed should be automatically filled into the form. STEPS TO REPRODUCE 1. Play a game and discover a rare bug that requires the random seed to reproduce 2. Help > "Report Bug..."; "Launch Bug Report Wizard" 3. Sneeze OBSERVED RESULT 4. Realize you closed the game window in step 3, and have no idea what the game seed was 5. Instead of reporting a rare bug, proceed to report a bug about reporting bugs EXPECTED RESULT 4. Realize you closed the game window in step 3, but the crucial game info was automatically added to the Bugzilla form for you 5. Continue filling out your important bug report SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This is honestly what happened -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464496] New: Updates cannot install
https://bugs.kde.org/show_bug.cgi?id=464496 Bug ID: 464496 Summary: Updates cannot install Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: kenr...@jackson.kz CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Package download failed:E: http://no.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 libegl1-mesa amd64 22.0.5-0ubuntu0.3 is not (yet) available (404 Not Found [IP: 193.35.52.51 80]) E: http://no.archive.ubuntu.com/ubuntu jammy-updates/universe i386 libgl1-mesa-glx i386 22.0.5-0ubuntu0.3 is not (yet) available (404 Not Found [IP: 193.35.52.51 80]) E: http://no.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 libgl1-mesa-glx amd64 22.0.5-0ubuntu0.3 is not (yet) available (404 Not Found [IP: 193.35.52.51 80]) E: http://no.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 mesa-va-drivers amd64 22.0.5-0ubuntu0.3 is not (yet) available (404 Not Found [IP: 193.35.52.51 80]) E: http://no.archive.ubuntu.com/ubuntu jammy-updates/universe i386 mesa-va-drivers i386 22.0.5-0ubuntu0.3 is not (yet) available (404 Not Found [IP: 193.35.52.51 80]) -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 462647] New: When launched, kid3 produces an error dialog (see attachment) with the message "kid3 cannot be opened because of a problem."
https://bugs.kde.org/show_bug.cgi?id=462647 Bug ID: 462647 Summary: When launched, kid3 produces an error dialog (see attachment) with the message "kid3 cannot be opened because of a problem." Classification: Applications Product: kid3 Version: 3.9.x Platform: macOS (DMG) OS: Other Status: REPORTED Severity: major Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: k...@winakey.org Target Milestone: --- Created attachment 154313 --> https://bugs.kde.org/attachment.cgi?id=154313=edit Screenshot of the error dialog SUMMARY Installed kid3 v3.9.2 into MacOS High Sierra v10.13.6. When launched, kid3 produces an error dialog (see attachment) with the message "kid3 cannot be opened because of a problem." The Problem report details are: Process: kid3 [21335] Path: /Applications/kid3.app/Contents/MacOS/kid3 Identifier:org.kde.kid3 Version: 3.9.2 (???) Code Type: X86-64 (Native) Parent Process:??? [1] Responsible: kid3 [21335] User ID: 501 Date/Time: 2022-12-04 15:27:06.699 -0500 OS Version:Mac OS X 10.13.6 (17G14042) Report Version:12 Anonymous UUID:C12EE7C4-62C6-7195-35CC-5D966D1C97DA Sleep/Wake UUID: 0C85C524-913F-419B-B495-C27FA5011F9B Time Awake Since Boot: 38 seconds Time Since Wake: 1300 seconds System Integrity Protection: enabled Crashed Thread:0 Exception Type:EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Exception Note:EXC_CORPSE_NOTIFY Termination Reason:DYLD, [0x4] Symbol missing Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: Symbol not found: _NSAppearanceNameDarkAqua Referenced from: /Applications/kid3.app/Contents/MacOS/../Frameworks/QtCore.framework/Versions/A/QtCore (which was built for Mac OS X 10.14) Expected in: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit in /Applications/kid3.app/Contents/MacOS/../Frameworks/QtCore.framework/Versions/A/QtCore Binary Images: 0x108a5c000 -0x108ab0ff7 +org.kde.kid3 (3.9.2 - ???) <7CC09B5E-3EC4-39D5-8842-BCE6ACA1D033> /Applications/kid3.app/Contents/MacOS/kid3 0x108ae1000 -0x108ba9ff7 +libkid3-gui.dylib (0) <7A33C523-494F-3843-BF72-0B26DB403CE9> /Applications/kid3.app/Contents/Frameworks/libkid3-gui.dylib 0x108bec000 -0x108d6dfff +libkid3-core.dylib (0) <509C6A9C-7D63-314E-B44F-5827D368D46E> /Applications/kid3.app/Contents/Frameworks/libkid3-core.dylib 0x108da8000 -0x108dc3ffb +org.qt-project.QtXml (6.2 - 6.2.2) /Applications/kid3.app/Contents/Frameworks/QtXml.framework/Versions/A/QtXml 0x108dd8000 -0x1092bbfff +org.qt-project.QtWidgets (6.2 - 6.2.2) /Applications/kid3.app/Contents/Frameworks/QtWidgets.framework/Versions/A/QtWidgets 0x10940a000 -0x1094bdfff +org.qt-project.QtMultimedia (6.2 - 6.2.2) <289FF5CC-14B4-31F1-B312-3561698C> /Applications/kid3.app/Contents/Frameworks/QtMultimedia.framework/Versions/A/QtMultimedia 0x1094fe000 -0x109b95fff +org.qt-project.QtGui (6.2 - 6.2.2) <77D73B6C-20B6-31AA-BD30-0BDC992ABFED> /Applications/kid3.app/Contents/Frameworks/QtGui.framework/Versions/A/QtGui 0x109caf000 -0x109de2ffb +org.qt-project.QtNetwork (6.2 - 6.2.2) <308DCDE2-5B81-3729-9914-F5D0CBCEC7F7> /Applications/kid3.app/Contents/Frameworks/QtNetwork.framework/Versions/A/QtNetwork 0x109e27000 -0x10a31ebf3 +org.qt-project.QtCore (6.2 - 6.2.2) /Applications/kid3.app/Contents/Frameworks/QtCore.framework/Versions/A/QtCore 0x10a3cc000 -0x10a45bffb +org.qt-project.QtDBus (6.2 - 6.2.2) <10B9DC5A-E04E-325D-9BC8-DEA43C683375> /Applications/kid3.app/Contents/Frameworks/QtDBus.framework/Versions/A/QtDBus 0x10b04b000 -0x10b095adf dyld (551.5) /usr/lib/dyld 0x7fff3b566000 - 0x7fff3b56affb com.apple.agl (3.3.1 - AGL-3.3.1) <60370135-B4DB-3BF6-B184-61B04BD802B0> /System/Library/Frameworks/AGL.framework/Versions/A/AGL 0x7fff3b56b000 - 0x7fff3b74bff3 com.apple.avfoundation (2.0 - 1536.36) /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation 0x7fff3b74c000 - 0x7fff3b805fff com.apple.audio.AVFAudio (1.0 - ???) <716306C4-A0EA-3D81-8F33-943153538C47> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Frameworks/AVFAudio.framework/Versions/A/AVFAudio 0x7fff3b90b000 - 0x7fff3b90bfff com.apple.Accelerate (1.11 - Accelerate 1.11) <8632A9C5-19EA-3FD7-A44D-80765CC9C540> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x7fff3b923000 - 0x7fff3be21fc3 com.apple.vImage (8.1 - ???)
[kdeconnect] [Bug 459573] KDE Daemon crashes on startup
https://bugs.kde.org/show_bug.cgi?id=459573 --- Comment #1 from Ken Roberts --- Created attachment 154235 --> https://bugs.kde.org/attachment.cgi?id=154235=edit New crash information added by DrKonqi kdeconnectd (22.04.1) using Qt 5.15.3 - What I was doing when the application crashed: Fresh install Rock Linux 9 KDE Plasma >From SDDM login to any user -- Backtrace (Reduced): #4 0x7f9019a46526 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.22 #5 0x7f9019a4b247 in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib64/libkdeconnectcore.so.22 #6 0x7f9019a37280 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.22 #7 0x7f9018550e99 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f901855413e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 459573] KDE Daemon crashes on startup
https://bugs.kde.org/show_bug.cgi?id=459573 Ken Roberts changed: What|Removed |Added CC||alisonk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453875] kdeconnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=453875 --- Comment #3 from Ken Roberts --- Created attachment 154204 --> https://bugs.kde.org/attachment.cgi?id=154204=edit New crash information added by DrKonqi kdeconnectd (22.04.1) using Qt 5.15.3 - What I was doing when the application crashed: When logging in. Also happens when selecting restart app using crash assistant. Dell Optiplex 3010 Intel Core i5. -- Backtrace (Reduced): #4 0x7f1b54b26526 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.22 #5 0x7f1b54b2b247 in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib64/libkdeconnectcore.so.22 #6 0x7f1b54b17280 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.22 #7 0x7f1b53630e99 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f1b5363413e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453875] kdeconnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=453875 Ken Roberts changed: What|Removed |Added CC||alisonk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461471] 01-build-mxe Script Fails Due to Unavailable Github Repository
https://bugs.kde.org/show_bug.cgi?id=461471 --- Comment #2 from Ken Lerner --- Thank you Gilles! I will switch the Qt5-maintenance branch. Please close the issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461471] 01-build-mxe Script Fails Due to Unavailable Github Repository
https://bugs.kde.org/show_bug.cgi?id=461471 Ken Lerner changed: What|Removed |Added CC||kenler...@bellsouth.net -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461471] New: 01-build-mxe Script Fails Due to Unavailable Github Repository
https://bugs.kde.org/show_bug.cgi?id=461471 Bug ID: 461471 Summary: 01-build-mxe Script Fails Due to Unavailable Github Repository Classification: Applications Product: digikam Version: 7.8.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: kenler...@bellsouth.net Target Milestone: --- SUMMARY Attempted to cross-compile digikam 7.8.0 for 64-bit Windows. While running 01-buiild-mxe.sh, script fails because of an unavailable github repository, https://github.com/jrfonseca/libdwarf. This repository is retrieved during the build of ext_drmingw. I realize that this has nothing to do, specifically with digiKam. Rather it has something to do with building the cross-compiling environment. But, I don't know how to fix it or where else to submit an issue. Cloning into '/home/xxx/digikam/project/bundles/mxe/temp.build/ext_drmingw/ext_drmingw-prefix/src/ext_drmingw/thirdparty/libdwarf'... Username for 'https://github.com': Password for 'https://github.com': remote: Repository not found. fatal: Authentication failed for 'https://github.com/jrfonseca/libdwarf/' fatal: clone of 'https://github.com/jrfonseca/libdwarf' into submodule path '/home/xxx/digikam/project/bundles/mxe/temp.build/ext_drmingw/ext_drmingw-prefix/src/ext_drmingw/thirdparty/libdwarf' failed STEPS TO REPRODUCE 1. Run the 01-build-mxe script 2. Wait OBSERVED RESULT Build Fails EXPECTED RESULT Build Succeeds SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457394] My closed accounts use to be archived, now they all show up when in HOME. Also the drop down lists will not display. Just installed Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=457394 --- Comment #3 from Ken Clayton --- I will not be providing any more information. Please consider this matter closed. On Wed, Sep 7, 2022 at 9:36 PM Bug Janitor Service wrote: > https://bugs.kde.org/show_bug.cgi?id=457394 > > --- Comment #2 from Bug Janitor Service --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 456958] kglobalshortcutsrc does not propagate via $XDG_CONFIG_DIRS
https://bugs.kde.org/show_bug.cgi?id=456958 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]
https://bugs.kde.org/show_bug.cgi?id=453752 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Ken D'Ambrosio changed: What|Removed |Added CC||k...@jots.org --- Comment #45 from Ken D'Ambrosio --- Yeah, throw me on the list. I'm still using Compiz, but it's woo growing long in the tooth, and obviously not making the jump to lightspee... err, Wayland. If you guys get a cube that works in Wayland, I'll be on KDE for the first time since I got Compiz working back in '06. Wonder if anything's changed in the past 16 years? ;-) Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457394] New: My closed accounts use to be archived, now they all show up when in HOME. Also the drop down lists will not display. Just installed Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=457394 Bug ID: 457394 Summary: My closed accounts use to be archived, now they all show up when in HOME. Also the drop down lists will not display. Just installed Ubuntu 22.04 Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ken.clayto...@gmail.com Target Milestone: --- My closed accounts use to be archived, now they all show up when in HOME. Also the drop down lists will not display. Just installed Ubuntu 22.04 *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 451748] New: program crashes every time I attempt to enter investment transactions in the ledger & loses all entered investment data
https://bugs.kde.org/show_bug.cgi?id=451748 Bug ID: 451748 Summary: program crashes every time I attempt to enter investment transactions in the ledger & loses all entered investment data Product: kmymoney Version: 5.0.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: k...@lenzcorp.com Target Milestone: --- SUMMARY *** STEPS TO REPRODUCE 1. enter new investment "buy" data for transaction 2. click on the "Enter" button 3. CRASH! Entire program blows up every time OBSERVED RESULT Program immediately closes - no investment transaction can be saved EXPECTED RESULT I expected the investment transaction section of the program to work properly SOFTWARE/OS VERSIONS Linux MATE desktop environment 1.24.0 O/S: Linux (x86_64) release 5.4.0-104-generic kmymoney version: 5.0.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439911] Allow text input to applications that do not support text-input-v2 or v3
https://bugs.kde.org/show_bug.cgi?id=439911 Ken Bloom changed: What|Removed |Added CC||kbl...@gmail.com --- Comment #6 from Ken Bloom --- Squeekboard is a virtual keyboard that works with Gnome. Here are the protocols it uses: https://gitlab.gnome.org/World/Phosh/squeekboard/-/tree/master/protocols. It sounds like kwin would need to implement virtual_keyboard_unstable_v1 (and route the keystrokes approriately) in order for a virtual keyboard to work everywhere. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 450889] New: Ark extracts files to the wrong directory
https://bugs.kde.org/show_bug.cgi?id=450889 Bug ID: 450889 Summary: Ark extracts files to the wrong directory Product: ark Version: 21.08.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: k...@kenrushia.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY While extracting two large archives in separate panes of Dolphin with the "autodetect subfolder" service menu, Ark gets confused and mixes up the locations. STEPS TO REPRODUCE 1. Open Dolphin with split panes, each pointing to a different location containing a different large archive 2. Right-click one archive, Extract > Extract archive here, autodetect subfolder. Do the same with the other one. 3. Play around with Dolphin while each archive extracts. This may not be needed. 4. Go check on each directory OBSERVED RESULT The first time I did this, items from the first archive somehow extracted into the subfolder Ark created for the second archive. Later I saw the opposite. The extent of "confusion" varies each time, but in all cases Ark shuffles files into the wrong directories. EXPECTED RESULT Each archive is extracted into a subfolder in the location of the archive file. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 444849] Make all issues appear in the My Bugs section, independently of the bug status
https://bugs.kde.org/show_bug.cgi?id=444849 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com --- Comment #10 from Ken Rushia --- According to the docs: https://bugzilla.readthedocs.io/en/5.0/using/finding.html#pronoun-substitution Using %user% gives us the following URL that anyone logged in can click: https://bugs.kde.org/buglist.cgi?email1=%25user%25_to1=1=1=1=equals_format=advanced If someone with permissions could place this at the top of the shared searches list found here: https://bugs.kde.org/userprefs.cgi?tab=saved-searches Then at least it's there to be found. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 436538] kdeinit5: Qt: Session management error: networkIdsList argument is NULL
https://bugs.kde.org/show_bug.cgi?id=436538 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 Ken Rice changed: What|Removed |Added CC||krinp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 446557] New: File Properties symlink entry not respected
https://bugs.kde.org/show_bug.cgi?id=446557 Bug ID: 446557 Summary: File Properties symlink entry not respected Product: frameworks-kio Version: 5.88.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Properties dialog Assignee: kio-bugs-n...@kde.org Reporter: verme...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When entering a new relative destination for a symlink in the file properties window, it will either not set the symlink or change it to an absolute path. STEPS TO REPRODUCE 1. Right-click a symlink -> Properties 2. In "Points to" change it from an absolute path to a relative path (in this use-case the destination is the same, the path needed is just relative) 3. Hit OK OBSERVED RESULT Dialog closes with path unchanged EXPECTED RESULT Dialog should close with the path changed to exactly what is in the "Points to" field. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: KDE Neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION The properties dialog closes without any acknowledgement that the exact user input was not respected. If there are any validity checks being performed, or it's checking to see if the path is the "same" in some way, it should not modify user input without warning. In the event that the path is malformed at most a warning dialog should spawn stating that an invalid link was entered (with a CONTINUE/CANCEL option) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 444920] k3b calculates size incorrectly when deciding when size of media was exceeded
https://bugs.kde.org/show_bug.cgi?id=444920 --- Comment #10 from Ken Arromdee --- I found the cause of this, sort of. growisofs reserves 256M spare area for defect management (see http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/ ). You can avoid this by adding the parameter -use-the-force-luke=spare:none. If I add this parameter, the size doesn't suddenly decrease by 256M, and everything works. So the problem is a mismatch between k3b calling growisofs using default behavior that creates 256M spare, but calculating the available size in a way that doesn't take the 256M spare into account. That page doesn't mention BD-R XL, but I would be unsurprised if juef17 had this same problem for his BD-R XL. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 444920] k3b calculates size incorrectly when deciding when size of media was exceeded
https://bugs.kde.org/show_bug.cgi?id=444920 --- Comment #8 from Ken Arromdee --- I think you uploaded the wrong files. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 444920] k3b calculates size incorrectly when deciding when size of media was exceeded
https://bugs.kde.org/show_bug.cgi?id=444920 --- Comment #5 from Ken Arromdee --- (In reply to Ken Arromdee from comment #4) > The text is readable for me; the bar is thicker relative to the text so the > text is on the bar. To clarify: Burning files produces a bar at the bottom with readable text. Directly burning an ISO didn't show a bar at all (with or without text) because directly burning an ISO doesn't use that part of the GUI. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 444920] k3b calculates size incorrectly when deciding when size of media was exceeded
https://bugs.kde.org/show_bug.cgi?id=444920 --- Comment #4 from Ken Arromdee --- The text is readable for me; the bar is thicker relative to the text so the text is on the bar. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 444920] k3b calculates size incorrectly when deciding when size of media was exceeded
https://bugs.kde.org/show_bug.cgi?id=444920 --- Comment #2 from Ken Arromdee --- (In reply to Patrick Silva from comment #1) > Can you also reproduce by creating an ISO image? I created an ISO image in k3b using "Only create image". The image is size 24852099072, which is expected given the above. I then used Tools/Burn Image, with "Start multisession CD" unchecked. Burning an image doesn't give a bar at the bottom telling you whether you have exceeded capacity. Same problem however. It's out of space. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 444920] New: k3b calculates size incorrectly when deciding when size of media was exceeded
https://bugs.kde.org/show_bug.cgi?id=444920 Bug ID: 444920 Summary: k3b calculates size incorrectly when deciding when size of media was exceeded Product: k3b Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: arrom...@gmx.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Try to burn a BD-R containing files that seem to almost fill a BD-R OBSERVED RESULT The bottom bar will report "Available: ___ of 23.3 GB". The burn will fail with "mkisofs crashed" and the log shows "no space left on device". The bar will then show that the capacity is exceeded, even though it didn't think the capacity was exceeded when you started to burn. In this case it claims that I have Available: 165.6 MB, but after the burn fails, it says capacity is exceeded by 90.4 MB. EXPECTED RESULT The amount available when I start should be accurate, so that if I exceeded capacity by 90.4 MB, it says that instead of falsely claiming there is space available. SOFTWARE/OS VERSIONS Linux: Linux version 5.10.52-desktop-1.mga8 (i...@ec2x1.mageia.org) (gcc (Mageia 10.3.0-1.mga8) 10.3.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Tue Jul 20 17:00:24 UTC 2021 KDE Plasma Version: None (running just fvwm3) k3b version is 20.12.0 which is not listed above. ADDITIONAL INFORMATION I have had this problem over many versions of k3b. It is not new. I don't think it is limited to BDs . If you do have enough space for the burn, the amount available will still go down when you burn it, just not by enough to cause an error. The difference between the available space at the start and at the end is exactly 256M. On computers, the number 256 looks suspicious. Also, the difference seems too small to be a 1000/1024 mixup. The log file shows that the mkisofs result has a size of 24852099072. Cursoring to the bottom bar shows that the files total to 24851695616 which is not the same number but close. A BD-R is supposed to have 25025315816 bytes which is indeed about 165M (using powers of 2) over. cdrwtool shows track size 12219392 which multiplied by 2048 gives the expected 25025315816. The extra space may be used up by overhead, but if so, I have no idea where the overhead comes from, and k3b really should not tell you there is available space when there is not because of overhead. I have Multisession: No and don't know about other possible sources of overhead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 Ken Mankoff changed: What|Removed |Added CC|mank...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 437451] New: Adding a directory containing over 199 files adds x-199 files
https://bugs.kde.org/show_bug.cgi?id=437451 Bug ID: 437451 Summary: Adding a directory containing over 199 files adds x-199 files Product: k3b Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@kde.org Reporter: arrom...@gmx.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY Adding a directory containing over 199 files adds x-199 files STEPS TO REPRODUCE 1. Create a data project 2. "Add to Project" a folder containing 217 files OBSERVED RESULT 18 files are added. No error is produced. EXPECTED RESULT 217 files should be added. The number seems to be x-199--if I add three extra dummy files, so it contains 220 files, 21 files are now added. I tried it on another directory and the same thing happened, also adding x-199 files. SOFTWARE/OS VERSIONS Mageia Linux 8.0. K3b version 20.12.0 (which is not listed above under Version:) ADDITIONAL INFORMATION No existing bug matches this but I did find a similar bug mentioned elsewhere at https://unix.stackexchange.com/questions/630966/k3b-only-imports-part-of-data The workaround is to select all the files and add them, rather than trying to add the folder. This is a serious bug because it can silently cause data loss. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431063] Hanging Process After Closing Application in MS Windows
https://bugs.kde.org/show_bug.cgi?id=431063 --- Comment #12 from Ken Lerner --- Yes, the issue still appears. If there's any information I can gather to help identify the issue please let me know. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420755] Option to disable animated scroll transitions
https://bugs.kde.org/show_bug.cgi?id=420755 Ken Fallon changed: What|Removed |Added CC||bugs.kde@kenfallon.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431851] Automatic screen rotation should rotate all built-in pointing devices.
https://bugs.kde.org/show_bug.cgi?id=431851 --- Comment #1 from Ken Bloom --- It would also be nice if this feature could automatically rotate the feed from a built-in webcam. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 431851] New: Automatic screen rotation should rotate all built-in pointing devices.
https://bugs.kde.org/show_bug.cgi?id=431851 Bug ID: 431851 Summary: Automatic screen rotation should rotate all built-in pointing devices. Product: KScreen Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kbl...@gmail.com Target Milestone: --- SUMMARY Automatic screen rotation should rotate all built-in pointing devices, such as the touchpad. STEPS TO REPRODUCE 1. Start a Plasma Wayland Session 2. Enable Automatic screen rotation, even when not in tablet mode 3. Turn my laptop on its side, counterclockwise, so that the caps lock key is near my physical desk surface, the enter key is on top, and the screen is to the left of the keyboard. OBSERVED RESULT The screen and touch screen rotate, but the touchpad does not. Moving my finger up on the touchpad (parallel to the space bar, in the direction towards the Enter key) should moves the mouse cursor rightward on the rotated display (towards the hinge). EXPECTED RESULT Moving my finger up on the touchpad (parallel to the space bar, in the direction towards the Enter key) should moves the mouse cursor up on the display (towards the hinge). In my opinion, all built-in pointing devices should be rotated. This includes the Trackpoint if this laptop were a ThinkPad. All external pointing devices should not be rotated, for example an external mouse, my Logitech M570 wireless trackball, or an external touch pad such as this one. https://www.amazon.com/Touchpad-Jelly-Comb-Multi-Touch-Precision/dp/B08DP28F22) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Stable KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431063] Hanging Process After Closing Application in MS Windows
https://bugs.kde.org/show_bug.cgi?id=431063 --- Comment #7 from Ken Lerner --- A very short video demonstrating the issue: https://tinyurl.com/yak53k28 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431063] Hanging Process After Closing Application in MS Windows
https://bugs.kde.org/show_bug.cgi?id=431063 --- Comment #6 from Ken Lerner --- @Maik - Problem occurs with windows bundle downloaded and installed from https://files.kde.org/digikam/ In my environment some photos are stored locally but most are stored on a shared network drive. The network drive resides on a slow NAS device (connected to router and accessed via WiFi with PC). The problem occurs when a photo is transferred from an album on the local drive to an album on the shared drive. After the photo is transferred, digikam is closed. In that case, a digikam process remains running and must be terminated using task manager. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431063] Hanging Process After Closing Application in MS Windows
https://bugs.kde.org/show_bug.cgi?id=431063 --- Comment #3 from Ken Lerner --- Created attachment 134475 --> https://bugs.kde.org/attachment.cgi?id=134475=edit digikamrc file -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431063] Hanging Process After Closing Application in MS Windows
https://bugs.kde.org/show_bug.cgi?id=431063 --- Comment #1 from Ken Lerner --- Created attachment 134469 --> https://bugs.kde.org/attachment.cgi?id=134469=edit debugview log -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431063] New: Hanging Process After Closing Application in MS Windows
https://bugs.kde.org/show_bug.cgi?id=431063 Bug ID: 431063 Summary: Hanging Process After Closing Application in MS Windows Product: digikam Version: 7.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: kenler...@bellsouth.net Target Milestone: --- SUMMARY After closing application, digikam process remains running, as visible in windows task manager. Process constantly uses around 1% of cpu time and will remain running until terminated using task manager. This is with 7.2.0 beta built on ubuntu. STEPS TO REPRODUCE 1. Start digikam 2. Move photo from local drive to album on network drive 3. Close digikam and observe the digikam application in task manager. OBSERVED RESULT As noted above, digikam process continues to run. EXPECTED RESULT Digikam should close completely SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Debug log attached. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429931] New: Small Typo on web page.
https://bugs.kde.org/show_bug.cgi?id=429931 Bug ID: 429931 Summary: Small Typo on web page. Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Website Assignee: digikam-bugs-n...@kde.org Reporter: kenler...@bellsouth.net Target Milestone: --- There's a small typo on the web page: https://www.digikam.org/contribute/ "Note ... digiKam with QT_LOGGIN_RULES environment variable." should be: "Note ... digiKam with QT_LOGGING_RULES environment variable." A "G" is missing in QT_LOGGING_RULES -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429467] Alt + A on search in Find Replace is not working
https://bugs.kde.org/show_bug.cgi?id=429467 Ken Fallon changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Ken Fallon --- Apologies for the delay. I installed two other distros to check the issue I confirmed that the problem is NOT in version 19.12.1 on Fedora release 31 (Thirty One), and also NOT in version 17.12.3 on GalliumOS 3.1 (ubuntu 18.04) It is also NOT a problem on a clean install of Fedora release 32 (Thirty Two)20.08.3 The issue is still present in Version 20.08.3 Fedora release 32 (Thirty Two) I did notice that when I pressed ALT it placed an Underscore under the "A" in "Replace All". I confirmed that LXQT does not have Alt + A assigned. I did notice that when I pressed ALT it placed an Underscore under the "c" in "Replace All". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429551] Many Tags Stored in Photos are not Inserted into Digikam's tag list When Photos are Read.
https://bugs.kde.org/show_bug.cgi?id=429551 Ken Lerner changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429551] Many Tags Stored in Photos are not Inserted into Digikam's tag list When Photos are Read.
https://bugs.kde.org/show_bug.cgi?id=429551 Ken Lerner changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429551] Many Tags Stored in Photos are not Inserted into Digikam's tag list When Photos are Read.
https://bugs.kde.org/show_bug.cgi?id=429551 --- Comment #3 from Ken Lerner --- Thanks for the information Maik. I will close the defect. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429551] Many Tags Stored in Photos are not Inserted into Digikam's tag list When Photos are Read.
https://bugs.kde.org/show_bug.cgi?id=429551 --- Comment #1 from Ken Lerner --- See link below for a video example of issue: https://www.dropbox.com/s/hfftwfv6v5h9gmk/example.mp4?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429551] New: Many Tags Stored in Photos are not Inserted into Digikam's tag list When Photos are Read.
https://bugs.kde.org/show_bug.cgi?id=429551 Bug ID: 429551 Summary: Many Tags Stored in Photos are not Inserted into Digikam's tag list When Photos are Read. Product: digikam Version: 7.1.0 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: kenler...@bellsouth.net Target Milestone: --- SUMMARY Many tags stored in photos are not inserted into Digikam's tag list when photos are read. STEPS TO REPRODUCE 1. Install digikam, add directory where photos reside. In this case, photos are stored on a network drive in many different folders. 2. Allow digikam to read all photos 3. After digikam completes scan of all photos, observe tag list. OBSERVED RESULT Tag list is incomplete EXPECTED RESULT Tag list is complete SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Used Xviv to insert xmp subject tags into many photos. (For example: ./exiv2 -M "add Xmp.dc.subject 5 Star Photos: 2003 - 2005" "P:/2003/2003_01/esimg2829.jpg") Many photos are tagged with the same subject. When looking at individual photos, DigiKam shows that the tags exist (in the metadata view), but the photo does not appear under the "5 Star Photos: 2003 - 2005." tag in the tag view. I think this has to do with the filename of the photo. In many cases, the filenames of photos are similar. For example: "esimg374 3-19-2003 12-53-02 PM.JPG", "esimg374 3-19-2003 2-12-36 PM.JPG" Is it possible that there is a dependency on file name? Also tried re-reading image metadata with the same result. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429467] New: Alt + A on search in Find Replace is not working
https://bugs.kde.org/show_bug.cgi?id=429467 Bug ID: 429467 Summary: Alt + A on search in Find Replace is not working Product: kate Version: 20.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: bugs.kde@kenfallon.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Ctrl R 2. Enter something to search and something to replace 3. Press Alt + A OBSERVED RESULT The behaviour for Alt + Up (Previous Document) occurs EXPECTED RESULT Replace All SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: KDE Frameworks 5.75.0 Qt Version: Qt 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION LXQT On Fedora release 32 (Thirty Two) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427388] Machine Freeze opening application
https://bugs.kde.org/show_bug.cgi?id=427388 --- Comment #10 from Ken Smith --- I use the RPMFusion Spin of kdenlive. It is usable with Xorg. Perhaps I should log this on the RPMFusion bugzilla Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427388] Machine Freeze opening application
https://bugs.kde.org/show_bug.cgi?id=427388 --- Comment #8 from Ken Smith --- After further testing have downgraded to 20.08.01 :-( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427388] Machine Freeze opening application
https://bugs.kde.org/show_bug.cgi?id=427388 --- Comment #7 from Ken Smith --- Have installed 20.08.03 on the system that froze previously. In the meanwhile that system has been upgraded from Fedora 32 to Fedora 33.(Kernel 5.9.8-200) Sad to report that the same freeze occurs with Wayland and not with Xorg. In Xorg mode, I opened a large 1080p project on version 20.08.03 and the system became unresponsive. On investigation several threads of ffmpeg were consuming the system resources. It would be worth having kdenlive produce some user information as on the surface the system appeared frozen. After 10-15 mins the processing had completed but this version of kdenlive barely plays that project whereas 20.08.01 played OK. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395191] WebViewTest::loadSignalsChangePageTest() Compared values are not the same (qt-5.11.0)
https://bugs.kde.org/show_bug.cgi?id=395191 --- Comment #7 from Ken Moffat --- (In reply to Justin Zobel from comment #6) > Thanks for the update Ken. > > Are you happy then for me to resolve this bug report? Sure. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395191] WebViewTest::loadSignalsChangePageTest() Compared values are not the same (qt-5.11.0)
https://bugs.kde.org/show_bug.cgi?id=395191 --- Comment #5 from Ken Moffat --- I think this was fixed by December 2018, my notes show that I stopped sedding that test when I was using qt-5.12.0.(In reply to Justin Zobel from comment #3) > Ken can you please re-test with current Qt and Falkon and confirm if this is > still an issue, if not we can close this bug report, thanks. I think this was fixed by December 2018, my notes show that I stopped sedding that test when I was using qt-5.12.0. With 3.1.0 plus fixes to include headers which moved in qt, all 11 tests pass. I could not see a link at github to get a current snapshot of falkon. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408458] The window icon is changing to BELL
https://bugs.kde.org/show_bug.cgi?id=408458 Ken Fallon changed: What|Removed |Added CC||bugs.kde@kenfallon.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427388] Machine Freeze opening application
https://bugs.kde.org/show_bug.cgi?id=427388 --- Comment #5 from Ken Smith --- Just to respond to this reminder. Will test version 20.08.2 when it becomes available via RPMFusion. Can report that 20.08.1 operates as expected without Wayland, just X-Org -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 428115] k3b silently drops files whose names contain special characters when adding to project
https://bugs.kde.org/show_bug.cgi?id=428115 --- Comment #2 from Ken Arromdee --- Created attachment 132675 --> https://bugs.kde.org/attachment.cgi?id=132675=edit example Tar archive containing two identical files, one with a name containing a special character. When adding the directory in k3b, only the file without the special character is added and the other is silently dropped. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 428115] New: k3b silently drops files whose names contain special characters when adding to project
https://bugs.kde.org/show_bug.cgi?id=428115 Bug ID: 428115 Summary: k3b silently drops files whose names contain special characters when adding to project Product: k3b Version: 19.04 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: arrom...@gmx.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY k3b silently drops files whose names contain special characters when adding to project STEPS TO REPRODUCE 1. Add a directory full of files to a data project. The directory contains a file with \367 (M-q) in the filename. 2. Check and see which files k3b actually added to the project by expanding the directory in the left part of the data tab. OBSERVED RESULT The file was not added. EXPECTED RESULT The file should be added, or at least an error should be produced. At this point I have no idea how much data I have already lost because of this behavior. I only discovered that this was happening because of a fluke. If you try adding only the individual file, k3b will at least produce an error saying that it can't find the file, although it really should be able to. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) -- I am not using a full desktop environment, only fvwm2, so no About System. This bug is not related to a graphical environment anyway. May also be related to bug #282390. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427388] Machine Freeze opening application
https://bugs.kde.org/show_bug.cgi?id=427388 --- Comment #2 from Ken Smith --- This has also been reported to the RPMFusion Buzilla and a Wayland anomaly identified. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427388] Machine Freeze opening application
https://bugs.kde.org/show_bug.cgi?id=427388 --- Comment #1 from Ken Smith --- Further data point. I installed 18.12.from Fedora 30 that I had used successfully before to try to get some editing done. It froze the machine too. The reinstall brought mlt-6.22.1-1.fc32.x86_64 with it as a dependency. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427388] New: Machine Freeze opening application
https://bugs.kde.org/show_bug.cgi?id=427388 Bug ID: 427388 Summary: Machine Freeze opening application Product: kdenlive Version: 20.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: k...@kensnet.org Target Milestone: --- SUMMARY Open application. Click on GUI. Machine freezes - power off required STEPS TO REPRODUCE 1. Open Kdenlive 2. Click on the Logging, Editing, Audio, Effects, Color items in the top right 3. Wait a couple of moments OBSERVED RESULT Mouse movement ceases, keyboard unresponsive. Last resort - pull power This happens of 3 different Fedora 32 installations. One on a i7/nVidia/nouveau another Core 2 Duo/Intel VGA and another on i5/Intel VGA EXPECTED RESULT Application continues running, does not reduce the machine to inoperable state SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32 / Gnome / Wayland (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.14 (qt5-qtbase-common-5.14.2-5.fc32.noarch) ADDITIONAL INFORMATION These packages don't appear to be available for Fedora "gdb kdenlive-dbg libmit-dbg" Previously I had version 18.12 installed on one of these machines that worked fine. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 427307] New: Strange behavior of module 'Printers--System Settings'
https://bugs.kde.org/show_bug.cgi?id=427307 Bug ID: 427307 Summary: Strange behavior of module 'Printers--System Settings' Product: print-manager Version: 20.04 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: ken.jars...@gmail.com Target Milestone: --- SUMMARY Canon Pixma MX-922 worked previously over wifi on KDE Neon 5.19 (18.04). Fresh install of kubuntu results in strange printer issue. STEPS TO REPRODUCE 1. Fresh install of kubuntu with printer shut off. 2. Open Printers in System Settings, see "no printers have been configured or discovered." 3. Power up printer. Printer automatically appears in Printers dialog! (I have never seen this before!) Power off printer, select All Settings and then select again Printers - and the printer disappears! 4. When printer appears, select Maintenance - Print Test Page OBSERVED RESULT Printer front panel reports, "There is no paper in the cassette (upper). The upper cassette supports smaller, photo sized paper and was NOT selected. Again select Maintenance - Print Test Page and error message appears, "No suitable destination host found by cups-browsed." Manually adding and selecting a printer (a second instance) and sending a Test Page from the Printer dialog has the same result. The second instance CAN be removed. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 20.04.1 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Printer dialog reports: Kind: Canon MX920 series, driverless, cups-filters 1.27.4 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426297] New: Okular crashinging when opening PDF
https://bugs.kde.org/show_bug.cgi?id=426297 Bug ID: 426297 Summary: Okular crashinging when opening PDF Product: okular Version: 1.10.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kct...@juno.com Target Milestone: --- Application: okular (1.10.2) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.36-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: Opening a pdf from Thunderbird that was dounloaded using Thunderbird. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb3b1f96f80 (LWP 13223))] Thread 7 (Thread 0x7fb385218700 (LWP 13229)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fb37700 (LWP 13228)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fb385a19700 (LWP 13227)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fb38621a700 (LWP 13226)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb3979ad700 (LWP 13225)): #0 0x7fb3adb771d8 in read () from /lib64/libc.so.6 #1 0x7fb3a851d9a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb3a84d6298 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb3a84d6720 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb3a84d688c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fb3ae51119b in QEventDispatcherGlib::processEvents (this=0x7fb39b10, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fb3ae4b232a in QEventLoop::exec (this=this@entry=0x7fb3979acc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fb3ae2d810a in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7fb3ae981cd5 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7fb3ae2d98b2 in QThreadPrivate::start (arg=0x7fb3aebf9d80) at thread/qthread_unix.cpp:361 #10 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #11 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb39fff2700 (LWP 13224)): #0 0x7fb3adb7b6db in poll () from /lib64/libc.so.6 #1 0x7fb3ab3b6307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fb3ab3b7f3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb3a2de7300 in QXcbEventQueue::run (this=0x5569bd363e10) at qxcbeventqueue.cpp:228 #4 0x7fb3ae2d98b2 in QThreadPrivate::start (arg=0x5569bd363e10) at thread/qthread_unix.cpp:361 #5 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb3b1f96f80 (LWP 13223)): [KCrash Handler] #4 QScopedPointer >::operator-> (this=0x30008) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1038 #6 QScreen::d_func (this=this@entry=0x3) at kernel/qscreen.h:69 #7 QScreen::size (this=this@entry=0x3) at kernel/qscreen.cpp:215 #8 0x7fb3aed4c6dd in QScreen::physicalDotsPerInchY (this=this@entry=0x3) at kernel/qscreen.cpp:246 #9 0x7fb3af8d7ce8 in QScrollerPrivate::setDpiFromWidget (this=this@entry=0x5569bd73c840, widget=) at util/qscroller.cpp:1035 #10 0x7fb3af8db0c8 in QScrollerPrivate::prepareScrolling (this=this@entry=0x5569bd73c840, position=...) at util/qscroller.cpp:1430 #11 0x7fb3af8dc56f in
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #10 from Ken --- (In reply to Ivan Čukić from comment #8) > @Ken > > You should try from the terminal - when dolphin/krusader get blocked, test > whether you can open some file in vim or another console editor. If that > works, then you might be experiencing an issue that *is* somewhere in KDE (I > assume krusader uses the same underlying libraries as dolpgin, though I > might be mistaken) @Ivan - will do. Thanks for the suggestion. @Zvi - apologies for muddying the waters on your ticket. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #7 from Ken --- (In reply to Ivan Čukić from comment #4) > @Ken > > You can open a separate bug report on Dolphin. > > Dolphin is not to blame for "Filesystem is not responding" reported by Zvi. > There have been reports here of cryfs being blocked even in terminal. So, > nothing to do with Dolphin. Looks like you're correct about it not being Dolphin. Hang issue is still present using Krusader as well. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #3 from Ken --- Cryfs is not the issue. The issue is dolphin and any large ecrypted filesystem. I get similar behavior with veracrypt volumes mounted using zulucrypt. Dolphin has consistently takes a dive anytime a new filesystem device is suddenly mounted with hundreds of thousands of files. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Ken changed: What|Removed |Added CC||k...@macferrin.com --- Comment #1 from Ken --- Exact same issue. Kubuntu 20.04. Large cryfs (100GB+) become unresponsive for several minutes after mounting. Causes dolphin to freeze for long periods. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 421403] Text Filter Plugin not working
https://bugs.kde.org/show_bug.cgi?id=421403 Ken Fallon changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Ken Fallon --- It fixed in a Fedora update. Sorry not to be able to provide any more information or logs. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 421403] Text Filter Plugin not working
https://bugs.kde.org/show_bug.cgi?id=421403 Ken Fallon changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 421403] New: Text Filter Plugin not working
https://bugs.kde.org/show_bug.cgi?id=421403 Bug ID: 421403 Summary: Text Filter Plugin not working Product: kate Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugin-snippets Assignee: kwrite-bugs-n...@kde.org Reporter: bugs.kde@kenfallon.com Target Milestone: --- SUMMARY The Text Filter Plugin stopped working. STEPS TO REPRODUCE 1. Select text 2. Select Tools → Filter Text (Ctrl+\) 3. Enter command (wc, sort, etc...) https://docs.kde.org/stable5/en/applications/kate//kate-application-plugin-textfilter.html OBSERVED RESULT Nothing happens EXPECTED RESULT Expected sort to sort, wc to give a word count. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: KDE Frameworks 5.68.0 Qt Version: Qt 5.13.2 (built against 5.13.2) The xcb windowing system ADDITIONAL INFORMATION Distributor ID: Fedora Description:Fedora release 31 (Thirty One) Release:31 Codename: ThirtyOne -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #336 from Ken Fallon --- Hi All, I too am suffering from the multi monitor issues. However frustrating it may be, I can't but feel that the developers are not doing this on purpose. @Developers, is there anything we can do to provide you more information to identify the issues causing the problems ? Is there a check-list or some script we can run through to gather the required information ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 418926] New: Baloo crash
https://bugs.kde.org/show_bug.cgi?id=418926 Bug ID: 418926 Summary: Baloo crash Product: frameworks-baloo Version: 5.67.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: kct...@juno.com Target Milestone: --- Application: baloo_file (5.67.0) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.7-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I was watching and listening to a video. Nothing abnormal.. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fee19e3ec80 (LWP 17481))] Thread 3 (Thread 0x7fee1759d700 (LWP 18517)): [KCrash Handler] #6 0x7fee1c96eea1 in raise () from /lib64/libc.so.6 #7 0x7fee1c95853d in abort () from /lib64/libc.so.6 #8 0x7fee1b36a543 in mdb_assert_fail.constprop.0 (env=0x5637ba858320, expr_txt=expr_txt@entry=0x7fee1b36c477 "rc == 0", func=func@entry=0x7fee1b36c9b0 <__func__.7211> "mdb_page_dirty", line=line@entry=2127, file=0x7fee1b36c010 "mdb.c") at mdb.c:1542 #9 0x7fee1b368bd5 in mdb_page_dirty (mp=, txn=0x5637ba859720) at mdb.c:2114 #10 mdb_page_dirty (txn=0x5637ba859720, mp=) at mdb.c:2114 #11 0x7fee1b361d06 in mdb_page_alloc.isra.0.lto_priv.0 (num=, mp=0x7fee1759c118, mc=) at mdb.c:2308 #12 0x7fee1b3691b3 in mdb_page_touch (mc=0x7fee1759c660) at mdb.c:2495 #13 0x7fee1b360c5c in mdb_cursor_touch (mc=mc@entry=0x7fee1759c660) at mdb.c:6523 #14 0x7fee1b36367d in mdb_cursor_put (mc=mc@entry=0x7fee1759c660, key=key@entry=0x7fee1759ca40, data=data@entry=0x7fee1759ca30, flags=, flags@entry=0) at mdb.c:6657 #15 0x7fee1b3665bb in mdb_put (txn=0x5637ba859720, dbi=2, key=0x7fee1759ca40, data=0x7fee1759ca30, flags=0) at mdb.c:9022 #16 0x7fee1c721d8a in Baloo::PostingDB::put(QByteArray const&, QVector const&) () from /usr/lib64/libKF5BalooEngine.so.5 #17 0x7fee1c726381 in Baloo::WriteTransaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #18 0x7fee1c72691f in Baloo::Transaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #19 0x5637ba68194d in ?? () #20 0x7fee1c195862 in QThreadPoolThread::run (this=0x5637baa68ab0) at thread/qthreadpool.cpp:99 #21 0x7fee1c1926f8 in QThreadPrivate::start (arg=0x5637baa68ab0) at thread/qthread_unix.cpp:342 #22 0x7fee1b3c9efa in start_thread () from /lib64/libpthread.so.0 #23 0x7fee1ca323bf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fee180c0700 (LWP 17483)): #0 0x7fee1ca27acf in poll () from /lib64/libc.so.6 #1 0x7fee1ab5f2fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fee1ab5f41f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fee1c3bec6b in QEventDispatcherGlib::processEvents (this=0x7fee1b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fee1c366bfb in QEventLoop::exec (this=this@entry=0x7fee180bfd70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7fee1c19162e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7fee1c762507 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fee1c1926f8 in QThreadPrivate::start (arg=0x7fee1c7e4da0) at thread/qthread_unix.cpp:342 #8 0x7fee1b3c9efa in start_thread () from /lib64/libpthread.so.0 #9 0x7fee1ca323bf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fee19e3ec80 (LWP 17481)): #0 0x7fee1ca27acf in poll () from /lib64/libc.so.6 #1 0x7fee1ab5f2fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fee1ab5f41f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fee1c3bec4e in QEventDispatcherGlib::processEvents (this=0x5637ba8409b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7fee1c366bfb in QEventLoop::exec (this=this@entry=0x7ffdbe661800, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7fee1c36e9d2 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x5637ba66c4e6 in ?? () #7 0x7fee1c959ceb in __libc_start_main () from /lib64/libc.so.6 #8 0x5637ba66c95a in ?? () [Inferior 1 (process 17481) detached] Possible duplicates by query: bug 418744, bug 417970, bug 417717, bug 415416, bug 414397. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
