[plasmashell] [Bug 447870] plasmashell crashes in HistoryItem::create() when selecting an item in plasma-pass
https://bugs.kde.org/show_bug.cgi?id=447870 --- Comment #3 from Isaac Salgueiro --- No worries, thanks for the update on this. I just installed plasma-pass 1.2.0-2 and it works for me. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: X11 Processors: 12 × 13th Gen Intel® Core™ i7-1355U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 478744] Currency quote update fails on no date
https://bugs.kde.org/show_bug.cgi?id=478744 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467000] Can't load app.mavenlink.com/timesheets
https://bugs.kde.org/show_bug.cgi?id=467000 Isaac Salgueiro changed: What|Removed |Added Version|22.12.2 |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467000] New: Can't load app.mavenlink.com/timesheets
https://bugs.kde.org/show_bug.cgi?id=467000 Bug ID: 467000 Summary: Can't load app.mavenlink.com/timesheets Classification: Applications Product: Falkon Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: isalgue...@gmail.com Target Milestone: --- SUMMARY *** When you open app.mavenlink.com/timesheets webpage loads a spinner and never loads content. *** STEPS TO REPRODUCE 1. Open app.mavenlink.com/timesheets (registered account needed) OBSERVED RESULT Infinite spinner. Following errors in console: - Uncaught TypeError: u.at is not a function - Uncaught DOMException: Blocked a frame with origin "https://service.force.com; from accessing a cross-origin frame. EXPECTED RESULT Page loads SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 Isaac Wismer changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Isaac Wismer --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 459186] akondi crash
https://bugs.kde.org/show_bug.cgi?id=459186 --- Comment #1 from Isaac --- Created attachment 152447 --> https://bugs.kde.org/attachment.cgi?id=152447=edit New crash information added by DrKonqi akonadiserver (5.20.1 (22.04.1)) using Qt 5.15.5 Thanks dear volunteer reading this. The crash occured when I booted up my computer and disconnected the bluetooth from an audio device it automatically linked with on boot. -- Backtrace (Reduced): #4 0x55efa20091eb in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f0f08a212b4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f0f089f71fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f0f089fa584 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f0f08a48457 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 459186] akondi crash
https://bugs.kde.org/show_bug.cgi?id=459186 Isaac changed: What|Removed |Added CC||isaacji...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455440] New: Crash when selecting connections and a wifi I have never used before
https://bugs.kde.org/show_bug.cgi?id=455440 Bug ID: 455440 Summary: Crash when selecting connections and a wifi I have never used before Product: systemsettings Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fakespam...@gmail.com Target Milestone: --- Application: systemsettings (5.24.5) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.14-300.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I opened the system settings and went to network, then connections. I am already connected to a network but when I clicked the second one that I have never used before it crashed. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f906dc4506a in QGestureManager::getState(QObject*, QGestureRecognizer*, Qt::GestureType) () from /lib64/libQt5Widgets.so.5 #5 0x7f906dc47ab5 in QGestureManager::filterEventThroughContexts(QMultiMap const&, QEvent*) () from /lib64/libQt5Widgets.so.5 #6 0x7f906dc4aaf8 in QGestureManager::filterEvent(QWidget*, QEvent*) () from /lib64/libQt5Widgets.so.5 #7 0x7f906dbfd7e6 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7f906d01e658 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f906dbfc402 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #10 0x7f906dc51aec in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7f906dc54eb0 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7f906dbf5c82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7f906d01e658 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f906d579115 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #15 0x7f906d558f5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #16 0x7f906a3636e4 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #17 0x7f906ac21faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f906ac772c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #19 0x7f906ac1f940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f906d06f2fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7f906d01d0ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7f906d025162 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #23 0x55632a8cc185 in main () [Inferior 1 (process 5533) detached] Possible duplicates by query: bug 453966, bug 440925, bug 434216, bug 428036, bug 422963. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 454688] If a zip contains multiple files with the same name, Ark will only show one of them
https://bugs.kde.org/show_bug.cgi?id=454688 --- Comment #1 from Isaac Cohen --- Created attachment 149369 --> https://bugs.kde.org/attachment.cgi?id=149369=edit My test zip I'm uploading my test zip so it can save people time -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 454688] New: If a zip contains multiple files with the same name, Ark will only show one of them
https://bugs.kde.org/show_bug.cgi?id=454688 Bug ID: 454688 Summary: If a zip contains multiple files with the same name, Ark will only show one of them Product: ark Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: icohen2...@zoho.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- Recently I was working with a zip file that had strange behavior (when extracting it asked whether I wanted to replace the files I already extracted). It turned out the zip contained multiple files with the same name at the same directory level. I tried to reproduce such a zip, but only succeeded by the method outlined here: https://stackoverflow.com/questions/17606573/how-to-add-two-files-with-the-same-file-name-into-a-single-zip-archive-file I found that other archiving tools such as Engrampa will show the individual files with the same name whereas Ark only shows one file in their place. I thought it would be nice to add a feature to Ark that does this too. STEPS TO REPRODUCE 1. First create three files like this: echo "Test1" >> file1 echo "Test2" >> file2 echo "Test3" >> file3 Note: It's important that the filenames should be the same length. This makes step 3 easier. 2. Archive them into a zip: zip test.zip file1 file2 file3 3. Open a hex editor and change the names of two of the files to match the third. For instance, change all occurrences of "file2" and "file3" to "file1". There will be two occurrences of the name for each file in the zip. If the names are different lengths there will probably be other fields to change as well. 4. View the files in the zip with: unzip -l test.zip You should see multiple files with the same name. 5. Open the zip with Ark OBSERVED RESULT There is only one file. EXPECTED RESULT There should be multiple files with the same name as in the output of unzip -l SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-051705-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453857] malloc() aborts during save
https://bugs.kde.org/show_bug.cgi?id=453857 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca --- Comment #11 from Isaac Wismer --- I'm no longer seeing the crash after updating gnutls 3.7.5-1 to 3.7.5-2 on Arch. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Bluetooth Headphones (fine otherwise)
https://bugs.kde.org/show_bug.cgi?id=443184 --- Comment #10 from Isaac Milarsky --- Went back and reproduced this bug again in version 22.04.1. Same situation was observed. Using Bluetooth headphones causes Elisa to stutter and pause a half second into track start and also just delays track start in general. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453642] Multiple monitors reset configuration and mirror screens after sleep
https://bugs.kde.org/show_bug.cgi?id=453642 --- Comment #1 from Isaac --- I think an additional point that might be causing this bug is that both monitors are identified as "DP_FREESYNC 1" in the Display Configuration settings tab. They are identically named, and I think this is breaking the configuration upon waking. An additional point: The bug is not present when the system goes to sleep, only when the monitors are turned off for power savings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453642] New: Multiple monitors reset configuration and mirror screens after sleep
https://bugs.kde.org/show_bug.cgi?id=453642 Bug ID: 453642 Summary: Multiple monitors reset configuration and mirror screens after sleep Product: kwin Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: isaaccurt...@gmail.com Target Milestone: --- Created attachment 148721 --> https://bugs.kde.org/attachment.cgi?id=148721=edit qdbus org.kde.KWin /KWin supportInformation SUMMARY When having multiple monitors connected under a wayland session, after the screens time out, the monitor configuration resets. Both monitors will be mirrored instead of extended, and the framerate will be set to 60Hz instead of 144Hz. STEPS TO REPRODUCE 1. Setup two 1440p monitors at 144Hz, connected via displayport. Have one directly to the right of the other. 2. Enable Screen Energy Savings under Power Management and allow screens to go blank. 3. Wake up computer by touching the keyboard or mouse. 4. Observe that monitors are now mirrored instead of extended and that the frame rate is now set to 60Hz. OBSERVED RESULT Monitors are now mirrors of each other with reduced framerate of 60Hz. EXPECTED RESULT After waking up, the monitors should retain the configuration setup previously. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 1700X Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION KDE support information attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] Digital clock/whole panel sometimes stops updating until there is user interaction with Plasma
https://bugs.kde.org/show_bug.cgi?id=429211 --- Comment #19 from Isaac Milarsky --- (In reply to Nate Graham from comment #18) > *** Bug 449021 has been marked as a duplicate of this bug. *** For whatever reason, my version of this bug doesn't react to right clicking and the only workaround is to restart plasma. Right click menus work but otherwise all of the panel widgets are frozen and don't react to left clicks except for the Application Menu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449084] Issue with idling on lock-screen when auto-sleep mode is disabled on wayland KDE. Freeze on return
https://bugs.kde.org/show_bug.cgi?id=449084 --- Comment #4 from Isaac Milarsky --- (In reply to Vlad Zahorodnii from comment #1) > Can you get the backtrace of kwin when the screen is frozen? You would need > to ssh from another computer and attach a debugger to kwin_wayland process, > e.g. "gdb -p `pidof kwin_wayland`" then type "bt" in gdb Just lmk if I should provide anything else -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449084] Issue with idling on lock-screen when auto-sleep mode is disabled on wayland KDE. Freeze on return
https://bugs.kde.org/show_bug.cgi?id=449084 --- Comment #3 from Isaac Milarsky --- Created attachment 145958 --> https://bugs.kde.org/attachment.cgi?id=145958=edit GDB traceback as asked for Here is the traceback for kwin when it freezes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 --- Comment #8 from Isaac Milarsky --- Packages (32) cmake-3.22.2-1 dialog-1:1.3_20220117-1 dune-2.9.2-1 electron-16.0.7-2 ethtool-1:5.16-1 faudio-22.01-1 gdb-11.2-1 gdb-common-11.2-1 git-2.35.0-1 js78-78.15.0-3 lib32-faudio-22.01-1 lib32-libldap-2.6.1-1 lib32-util-linux-2.37.3-1 lib32-zstd-1.5.2-1 libbsd-0.11.5-1 libldap-2.6.1-1 libplacebo-4.192.0-1 python-3.10.2-1 python-dnspython-1:2.2.0-1 python-lxml-4.7.1-1 python-tomli-2.0.0-1 python-urllib3-1.26.8-1 python-zipp-3.7.0-1 quazip-1.2-1 [removal] quazip-qt5-1.2-2 svt-av1-0.9.0-1 util-linux-2.37.3-1 util-linux-libs-2.37.3-1 vlc-3.0.16-7 wpa_supplicant-2:2.10-1 xf86-input-libinput-1.2.1-1 zstd-1.5.2-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 --- Comment #7 from Isaac Milarsky --- (In reply to Isaac Milarsky from comment #6) > The bug happened again today on my other arch machine that I haven't updated > in about 2 days. Right clicking doesn't fix the issue but context menus work > and I can right click things like normal. It seems only the panel is > affected. Right clicking doesn't cause it to unfreeze. However, I haven't > been able to replicate the bug on my laptop for a while now and that might > be due to it being more up to date. These were the arch packages that were out of date when the bug last occurred on my desktop machine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 --- Comment #6 from Isaac Milarsky --- The bug happened again today on my other arch machine that I haven't updated in about 2 days. Right clicking doesn't fix the issue but context menus work and I can right click things like normal. It seems only the panel is affected. Right clicking doesn't cause it to unfreeze. However, I haven't been able to replicate the bug on my laptop for a while now and that might be due to it being more up to date. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449084] Issue with idling on lock-screen when auto-sleep mode is disabled on wayland KDE. Freeze on return
https://bugs.kde.org/show_bug.cgi?id=449084 Isaac Milarsky changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 --- Comment #5 from Isaac Milarsky --- I haven't been able to replicate this bug lately but will update this page if/when it pops up again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 --- Comment #4 from Isaac Milarsky --- (In reply to Nate Graham from comment #3) > So right-clicking doesn't make them unfreeze? No. Admittedly, it hasn't happened today though and I've been updating my arch setup daily. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 Isaac Milarsky changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449084] New: Issue with idling on lock-screen when auto-sleep mode is disabled on wayland KDE. Freeze on return
https://bugs.kde.org/show_bug.cgi?id=449084 Bug ID: 449084 Summary: Issue with idling on lock-screen when auto-sleep mode is disabled on wayland KDE. Freeze on return Product: plasmashell Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: imilar...@gmail.com Target Milestone: 1.0 SUMMARY There is a minor issue with KDE where when auto-sleep mode is disabled and the computer is left idling. The screen auto locks as intended but if left alone will freeze upon unlocking the session and a couple seconds of mouse movement. When the session freezes all input is ignored including the standard Ctrl+Alt+F5 to try to get to a login shell. Sometimes it breaks out of the freeze on its own but other times the only cure is to hard restart the computer. I have found turning auto-sleep mode back on avoids this issue thankfully. STEPS TO REPRODUCE 1. Start a wayland KDE session from sddm 2. Set the power save mode to only lock the screen upon idle instead of going to sleep mode 3. Wait until the screen locks itself from idling or a little longer 4. Unlock the screen and attempt to use the computer OBSERVED RESULT Screen is frozen and all inputs are ignored. Either it unfreezes on its own or a hard reboot is needed. If it decides to unfreeze the results of the previously ignored inputs are then shown. Audio seems to work when it is frozen as it still plays youtube videos in the background when it is frozen like this. EXPECTED RESULT Successful unlocking of the KDE session followed by standard use of the desktop environment. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem tem
https://bugs.kde.org/show_bug.cgi?id=449021 --- Comment #2 from Isaac Milarsky --- (In reply to Nate Graham from comment #1) > Just the panel? When it's frozen, can you right-click on the desktop and get > a context menu? If that works, do you also get a context menu when you > right-click on the frozen panel? Yes Right clicking seems to work. However stuff like appmenu buttons are unresponsive and other widgets like the clock are frozen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449021] New: After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the proble
https://bugs.kde.org/show_bug.cgi?id=449021 Bug ID: 449021 Summary: After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem temporarily Product: plasmashell Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: imilar...@gmail.com Target Milestone: 1.0 Created attachment 145808 --> https://bugs.kde.org/attachment.cgi?id=145808=edit Some of the messages from Journalctl from around the time of a recent freeze SUMMARY After a period of working as intended, the KDE Panel freezes and is unresponsive. The clock freezes at the time of the crash. Restarting kde in Konsole fixes the problem temporarily with "kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell." This is with Arch Linux using a wayland session started using sddm. STEPS TO REPRODUCE 1. Boot Arch Linux to SDDM 2. Login to a Wayland session and do standard browsing on firefox, write code, etc 3. Wait for the panel clock to freeze and not match the current time OBSERVED RESULT The Panel is unresponsive for all widgets except the application menu. Otherwise KDE seems to be functioning as intended. KDE needs to be restarted in order for the panel to start working again. EXPECTED RESULT Panel ideally should be responsive as intended and not freeze quietly. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447870] New: plasmashell crashes when selecting an item in plasma-pass
https://bugs.kde.org/show_bug.cgi?id=447870 Bug ID: 447870 Summary: plasmashell crashes when selecting an item in plasma-pass Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: isalgue...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.4) Qt Version: 5.15.3 Frameworks Version: 5.89.0 Operating System: Linux 5.11.0-43-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Select an item in plasma-pass - Unusual behavior I noticed: Plasma shell crashed and restarted itself. Nothing was copied to clipboard. `pass -c` command worked fine. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1680] [New LWP 1701] [New LWP 1749] [New LWP 1750] [New LWP 1751] [New LWP 1752] [New LWP 1753] [New LWP 1754] [New LWP 1755] [New LWP 1778] [New LWP 1807] [New LWP 1808] [New LWP 1815] [New LWP 1816] [New LWP 1817] [New LWP 1828] [New LWP 1836] [New LWP 1837] [New LWP 1922] [New LWP 1923] [New LWP 2633] [New LWP 2634] [New LWP 2641] [New LWP 2642] [New LWP 2643] [New LWP 2644] [New LWP 2645] [New LWP 2646] [New LWP 2647] [New LWP 2648] [New LWP 2649] [New LWP 2650] [New LWP 2651] [New LWP 2652] [New LWP 2653] [New LWP 2654] [New LWP 2655] [New LWP 2656] [New LWP 2657] [New LWP 2658] [New LWP 3237] [New LWP 3238] [New LWP 3256] [New LWP 3257] [New LWP 3344] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f50f1bf9aff in poll () from /lib/x86_64-linux-gnu/libc.so.6 __preamble__ [Current thread is 1 (Thread 0x7f50edd3d9c0 (LWP 1672))] Thread 46 (Thread 0x7f50057fa700 (LWP 3344)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50e59549bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f50e595472b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 45 (Thread 0x7f4fe37fe700 (LWP 3257)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50f1f8e5cb in QWaitConditionPrivate::wait (deadline=..., this=0x563e3ebf81c0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x563e3e438800, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f50f3bf8c24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f50f3bf9099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f50f1f8845c in QThreadPrivate::start (arg=0x563e3e438760) at thread/qthread_unix.cpp:329 #6 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 44 (Thread 0x7f4fe3fff700 (LWP 3256)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50e59549bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f50e595472b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 43 (Thread 0x7f4fedc99700 (LWP 3238)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50f1f8e5cb in QWaitConditionPrivate::wait (deadline=..., this=0x563e3e49f800) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x563e3e5473c0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f50f3bf8c24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f50f3bf9099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f50f1f8845c in QThreadPrivate::start (arg=0x563e3e547320) at thread/qthread_unix.cpp:329 #6 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 42 (Thread 0x7f4fee49a700 (LWP 3237)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50e59549bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f50e595472b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f50f0ec3609 in start_thread ()
[krunner] [Bug 445153] krunner causes error messages in my system log because kconfig reads each line of an .ods file I open
https://bugs.kde.org/show_bug.cgi?id=445153 --- Comment #4 from Isaac Cohen --- Interestingly this only happens (for me) when I try to open the document using the application launcher. It doesn't happen for krunner. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 445153] krunner causes error messages in my system log because kconfig reads each line of an .ods file I open
https://bugs.kde.org/show_bug.cgi?id=445153 Isaac Cohen changed: What|Removed |Added CC||icohen2...@zoho.com --- Comment #3 from Isaac Cohen --- I can replicate this. Here are the steps: 1. Open a PDF file the ordinary way, by double clicking it in Dolphin. 2. Click the application launcher and enter the name of the PDF in the search box 3. The launcher will find the PDF (as a recently opened document) 4. Select the document from the list and click to open it 5. The document will open after a short delay (depending on the size of the document - for my Calculus textbook it's about 4-5 seconds) 6. Looking in .xsession-errors you will see a bunch of lines that look like this: kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846558: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846559: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846560: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846561: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846562: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846563: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846564: " Invalid entry (missing ']') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846565: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846566: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846567: " Invalid entry (missing '=') kf.config.core: "KConfigIni: In file /home/isaac/James Stewart - Calculus_ Early Transcendentals 8th Edition. 8.pdf, line 846568: " Invalid entry (missing '=') Specs: Operating System: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.15.1-051501-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-4160 CPU @ 3.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Bluetooth Headphones (fine otherwise)
https://bugs.kde.org/show_bug.cgi?id=443184 Isaac Milarsky changed: What|Removed |Added Summary|Elisa Music Player Stutters |Elisa Music Player Stutters |on Each Track Start with|on Each Track Start with |Pipewire|Bluetooth Headphones (fine ||otherwise) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 444639] New: Prompt for PIN when using systemd-homed FIDO login
https://bugs.kde.org/show_bug.cgi?id=444639 Bug ID: 444639 Summary: Prompt for PIN when using systemd-homed FIDO login Product: kscreenlocker Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcheckpass Assignee: plasma-b...@kde.org Reporter: isaaccurt...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Support systemd-homed users when a FIDO U2F device is used with a PIN. Devices without a PIN work as expected in both sddm and kscreenlocker. When the user presses enter on a blank password dialog, the FIDO device prompts for presence and unlocks the computer. Once a PIN is registered, this process breaks. Sddm works if pin is entered as password dialog before enter. However, kscreenlocker no longer is capable of accepting the FIDO device to unlock the computer. STEPS TO REPRODUCE 1. Plug in FIDO device such as Solo or Yubikey, setup FIDO2 device with PIN. 2. Create systemd-homed user `homectl create foo --fido2-device=auto` 3. Follow prompts to enter PIN and register FIDO device with homed. Reboot. 4. Login with sddm by entering PIN in password dialog and activating device. 5. Lock screen. Attempt to unlock by pressing enter with blank password dialogue. OBSERVED RESULT Login failed. Password prompt unlocks. The FIDO device is not polled. EXPECTED RESULT kscreenlocker polls FIDO device and prompts for PIN entry (or allows PIN entry instead of password like SDDM). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.15.15-zen1-1-zen KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Related tickets: 430828, 396703 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440496] "Show in all activities" no longer works
https://bugs.kde.org/show_bug.cgi?id=440496 Isaac Zylstra changed: What|Removed |Added CC||cavetrol...@gmail.com --- Comment #3 from Isaac Zylstra --- I have this issue in Kubuntu 21.10 and Plasma 5.23 (using backports). Using the system title bar context menu to set "All Activities" does work properly, and accurately displays the state of the window. (e.g. only one activity is still ticked after using the task manager context menu to set "All Activities") -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Pipewire
https://bugs.kde.org/show_bug.cgi?id=443184 --- Comment #7 from Isaac Milarsky --- Update: So the stuttering is only happening when I listen through bluetooth headphones. Everything works perfectly when I use my speakers plugged into my computer. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Pipewire
https://bugs.kde.org/show_bug.cgi?id=443184 --- Comment #6 from Isaac Milarsky --- Okay so it persists on reboot now as well. This is extremely strange to me. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Pipewire
https://bugs.kde.org/show_bug.cgi?id=443184 --- Comment #5 from Isaac Milarsky --- So the stutters came back after I used my computer to do other things for a while. Same issue returns after a while. Here is the journalctl output from around when the stutters happened: Oct 13 21:11:59 cinnamon kernel: audit: type=1131 audit(1634177519.152:208): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=> Oct 13 21:13:39 cinnamon plasmashell[880]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:27:1: QML Panel: Binding loop detected for property "state" Oct 13 21:13:39 cinnamon plasmashell[880]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:27:1: QML Panel: Binding loop detected for property "state" Oct 13 21:13:41 cinnamon elisa[3381]: libpng warning: iCCP: known incorrect sRGB profile Oct 13 21:13:52 cinnamon plasmashell[880]: kde.dataengine.mpris: "org.mpris.MediaPlayer2.elisa" has an invalid URL for the xesam:url entry of the "Metadata" property Oct 13 21:13:59 cinnamon plasmashell[880]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:233: TypeError: Cannot read property 'visible' of null Oct 13 21:14:05 cinnamon elisa[3381]: kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling. Oct 13 21:14:05 cinnamon elisa[3381]: kf.kirigami: Previous message repeats 2 times. Oct 13 21:14:09 cinnamon xdg-desktop-portal-kde[6904]: xdp-kde-background: GetAppState called: no parameters Oct 13 21:14:17 cinnamon elisa[3381]: kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling. Oct 13 21:14:17 cinnamon elisa[3381]: kf.kirigami: Previous message repeats 2 times. Oct 13 21:14:39 cinnamon plasmashell[880]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:27:1: QML Panel: Binding loop detected for property "state" Oct 13 21:14:39 cinnamon plasmashell[880]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:27:1: QML Panel: Binding loop detected for property "state" Oct 13 21:14:39 cinnamon xdg-desktop-portal-kde[6904]: xdp-kde-background: GetAppState called: no parameters Oct 13 21:14:44 cinnamon plasmawindowed[8852]: :1: TypeError: Cannot read property 'Layout' of null Oct 13 21:14:44 cinnamon plasmawindowed[8852]: QObject::disconnect: Unexpected nullptr parameter Oct 13 21:14:54 cinnamon plasmashell[880]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog(0x560382238610) Oct 13 21:14:54 cinnamon plasmashell[880]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog(0x560382238610) Oct 13 21:14:54 cinnamon plasmashell[880]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog(0x560382238610) Oct 13 21:14:55 cinnamon plasmashell[880]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:233: TypeError: Cannot read property 'visible' of null Oct 13 21:15:04 cinnamon plasmashell[880]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog(0x560382238610) Oct 13 21:15:04 cinnamon plasmashell[880]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog(0x560382238610) Oct 13 21:15:04 cinnamon plasmashell[880]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog(0x560382238610) Oct 13 21:15:07 cinnamon plasmashell[880]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:233: TypeError: Cannot read property 'visible' of null Oct 13 21:15:09 cinnamon xdg-desktop-portal-kde[6904]: xdp-kde-background: GetAppState called: no parameters Oct 13 21:15:12 cinnamon plasmashell[880]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:27:1: QML Panel: Binding loop detected for property "state" Oct 13 21:15:12 cinnamon plasmashell[880]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:27:1: QML Panel: Binding loop detected for property "state" Oct 13 21:15:19 cinnamon elisa[3381]: libpng warning: iCCP: known incorrect sRGB profile Oct 13 21:15:23 cinnamon elisa[3381]: kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling. Oct 13 21:15:23 cinnamon elisa[3381]: kf.kirigami: Previous message repeats 2 times. Oct 13 21:15:25 cinnamon plasmashell[880]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:233: TypeError: Cannot read property 'visible' of null Oct 13 21:15:25 cinnamon plasmashell[880]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:233: TypeError: Cannot read property 'visible' of null Oct 13 21:15:34 cinnamon systemd[713]: Started Konsole - Terminal. Oct 13 21:15:34 cinn
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Pipewire
https://bugs.kde.org/show_bug.cgi?id=443184 --- Comment #4 from Isaac Milarsky --- Hmm.. It seems to also be working within an x session too now. I wonder if an upstream change fixed it or something. I am running elisa 21.08.2 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Pipewire
https://bugs.kde.org/show_bug.cgi?id=443184 --- Comment #3 from Isaac Milarsky --- Okay I tried Elisa again recently on a KDE wayland session and it worked just fine. No stutters at all. I am still on pipewire so it is working with pipewire without stuttering using a wayland session. I will try with an x session again to see if the stutters return. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #28 from Isaac Wismer --- I'll definitely send a note off to my bank about their malformed OFX export, but knowing Canadian banks, it'll just be ignored... Thanks for all your hard work on this application, it's great to use! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Pipewire
https://bugs.kde.org/show_bug.cgi?id=443184 --- Comment #2 from Isaac Milarsky --- (In reply to Nate Graham from comment #1) > Hmm, I'm using PipeWire and I don't experience this. I remember Elisa working just fine back when I was using PulseAudio and then the problem suddenly starting after an update or two and after switching to PipeWire. It might not be PipeWire I just thought that was the most likely culprit. Let me know if there is anything that I can try or provide to make squashing this bug easier. I can give systemd journals if that helps. I looked into a similar error that was raised on here a while ago that blamed VLC audio libraries during compilation or something? I don't think that would affect me since I didn't compile Elisa from source. Is there anything else unusual that might cause something like this? Thanks for answering I really like Elisa and most kde stuff otherwise. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #22 from Isaac Wismer --- I have libOFX 0.9.15 I will email the outputs of ofxdump. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #20 from Isaac Wismer --- Is there anything else you need from me to try and reproduce it? Or anything I can do to reset the account number? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443184] New: Elisa Music Player Stutters on Each Track Start with Pipewire
https://bugs.kde.org/show_bug.cgi?id=443184 Bug ID: 443184 Summary: Elisa Music Player Stutters on Each Track Start with Pipewire Product: Elisa Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: imilar...@gmail.com Target Milestone: --- SUMMARY Using kde plasma on archlinux with pipewire makes Elisa stutter when starting every track that it tries to play. Works fine otherwise. STEPS TO REPRODUCE 1. Use KDE plasma with pipewire as a replacement for pulseaudio 2. Install elisa music player with pacman 3. Play any track OBSERVED RESULT Elisa plays the first half-second of the track before pausing and stuttering. After a short pause it plays the rest of the track as expected. This happens for the start of every song that plays whether it is started manually or via a playlist. EXPECTED RESULT Elisa should ideally not stutter at the start of each track playing. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.8-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon Pro W5500 ADDITIONAL INFORMATION Pipewire Version: Compiled with libpipewire 0.3.38 Linked with libpipewire 0.3.38 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #18 from Isaac Wismer --- I didn't edit the files, so yeah, definitely weird output. Maybe the problem is in the OFX library? Or maybe my bank is giving me malformed OFX files? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #16 from Isaac Wismer --- When importing the OFX file it doesn't create an ofxlog.txt (yes, I checked to make sure my log path was correct and that I had checked "Log OFX transactions"). But I think I can get the same information by just opening up the OFX file I downloaded from my bank. from kmm-statement: from the actual OFX file: CAD4525501001994321CREDITLINE I have not used the other credit card in the past few days, so I unfortunately can't really import anything right now. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #14 from Isaac Wismer --- (In reply to Isaac Wismer from comment #13) > The correct credit card account has a StatementKey, the account it goes into > has a StatementKey, but it's just 2 spaces. Actually, I'm sorry, the account that the import should go into does not have a statement key, the account that it does go into (but shouldn't) has a statementkey of just 2 spaces. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #13 from Isaac Wismer --- The correct credit card account has a StatementKey, the account it goes into has a StatementKey, but it's just 2 spaces. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #10 from Isaac Wismer --- What is the file type/encoding of the .kmy file? I can't seem to figure out out to inspect it. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #8 from Isaac Wismer --- The credit cards are from different banks. All the details in the account info seems correct. Unfortunately neither bank offers direct connect, so that's not an option to test. I will try setting up a new card in KMyMoney and see what happens. The really weird thing is that I manually select for it to be imported into the correct account, but it still ends up importing into the wrong account. I guess it doesn't respect the manual selection. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #6 from Isaac Wismer --- As a workaround, I just download the transactions as a CSV and import it that way, which doesn't have any issues, it just takes a little more work. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #5 from Isaac Wismer --- Also, for a little more info: Credit card account #1 imports fine. It gives me a dialog, which defaults to importing into card #1, and then I hit OK and it imports into account #1. Credit card account #2 doesn't import correctly. It gives me a dialog which defaults to card #1, so I change it to card #2, but then when I hit OK, the status dialog shows that it was imported into account #1 (so I think maybe it just always imports into the default account?). Unfortunately I only have 2 credit cards that offer OFX export, so I can't test with anything else. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 --- Comment #4 from Isaac Wismer --- Yes, this still occurs in 5.1.2. Both accounts are credit cards. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 423760] The "Hide titlebar for maximized windows" option is not remembered across restarts
https://bugs.kde.org/show_bug.cgi?id=423760 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca --- Comment #2 from Isaac Wismer --- I also have this problem, but it just started when I updated: frameworks 5.84 to 5.85 gear 21.04 to 21.08 plasma 5.22.3 to 5.22.4 Unfortunately I didn't test these separately as I was away and they all updated at once. On the older version it works, on the newer version it doesn't. This is reproducible on 2 of my machines both running KDE on Arch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441536] Trying to start a wayland session from SDDM crashes KDE on start. The desktop background is black and no widgets or panels are present. After a while the crash report dialog
https://bugs.kde.org/show_bug.cgi?id=441536 --- Comment #1 from Isaac Milarsky --- (In reply to Isaac Milarsky from comment #0) > Created attachment 141039 [details] > This is what the crash reporter gave me. > > SUMMARY > > > STEPS TO REPRODUCE > 1. Boot computer with OpenSUSE Tumbleweed using KDE plasma to SDDM login > screen. > 2. Select the session as KDE with Wayland > 3. Login like normal with SDDM > > OBSERVED RESULT > > Desktop is shown briefly before going to a black screen. No panels or > widgets are present at any point but I do see desktop shortcuts before it > goes black. After a few seconds the crash reporter launches. > > > EXPECTED RESULT > Successful Launch of a KDE Wayland session. > > SOFTWARE/OS VERSIONS > Linux Version: 5.13.12-1-default(64-bit) > (available in About System) > KDE Plasma Version: 5.22.4 > KDE Frameworks Version: 5.85.0 > Qt Version: 5.15.2 > > ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441536] New: Trying to start a wayland session from SDDM crashes KDE on start. The desktop background is black and no widgets or panels are present. After a while the crash report d
https://bugs.kde.org/show_bug.cgi?id=441536 Bug ID: 441536 Summary: Trying to start a wayland session from SDDM crashes KDE on start. The desktop background is black and no widgets or panels are present. After a while the crash report dialogue pops up. I can still use Konsole with Ctrl+shift+T but no plasma. Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: imilar...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 141039 --> https://bugs.kde.org/attachment.cgi?id=141039=edit This is what the crash reporter gave me. SUMMARY STEPS TO REPRODUCE 1. Boot computer with OpenSUSE Tumbleweed using KDE plasma to SDDM login screen. 2. Select the session as KDE with Wayland 3. Login like normal with SDDM OBSERVED RESULT Desktop is shown briefly before going to a black screen. No panels or widgets are present at any point but I do see desktop shortcuts before it goes black. After a few seconds the crash reporter launches. 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.
[konsole] [Bug 431827] Konsole crashes if issuing CTLR+d if input is copied to other tabs
https://bugs.kde.org/show_bug.cgi?id=431827 Isaac Salgueiro changed: What|Removed |Added CC|isalgue...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 --- Comment #26 from Isaac Cohen --- Also, I should point out that for me this issue only began when I upgraded to Plasma 5.21. When I used 5.19 it never happened and after I upgraded it happened every time. When filing my big report I actually saw this one but noticed it was from several years ago and so figured it must be a different issue (since mine just started with 5.21). So I filed a separate bug report but it was marked a duplicate of this one. I guess it is the same issue. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 --- Comment #25 from Isaac Cohen --- (In reply to David Edmundson from comment #20) > I have a theory to rule out: > > If someone can reproduce this reliably, could they run "kcmshell5 > qtquicksettings" and set their backend to software and see if the screen > locker issue perists or goes away I could reproduce reliably. I tried what you said and now it works every time. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436751] New: Screen shows before lockscreen on resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=436751 Bug ID: 436751 Summary: Screen shows before lockscreen on resuming from sleep Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: icohen2...@zoho.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On resuming from suspend, the screen shows for a moment before the lock screen comes on. This might be a concern for some people, especially if they don't want others to be able to view their session before they enter the password. STEPS TO REPRODUCE 1. Put computer on Sleep. 2. Resume from Sleep. OBSERVED RESULT You see the screen for a moment with the things you had open when you put your computer on sleep. Then, a moment later, the lockscreen appears. EXPECTED RESULT You see the lockscreen right away. SOFTWARE/OS VERSIONS Linux: 5.11.16-generic KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kubuntu: 21.04 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 --- Comment #11 from Isaac Salgueiro --- Sorry, is Qt 5.15.2. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 Isaac Salgueiro changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from Isaac Salgueiro --- Hi All This is fixed for me in konsole 21.04.0 and Qt 5.12.2 Regards, Isaac -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379874] Crash opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379874 --- Comment #7 from Isaac Salgueiro --- Hi Pierre Sorry, I don't remember with what document calligrawords crashed and rn I can't find a document that makes it crash. BR, Isaac -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433445] Autostarted applications show incorrect application name
https://bugs.kde.org/show_bug.cgi?id=433445 --- Comment #2 from Isaac Wismer --- I have 247.3, so it looks like that commit should fix it in 248. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433446] New: Application name displays as "0" when a column is a line graph (other than CPU)
https://bugs.kde.org/show_bug.cgi?id=433446 Bug ID: 433446 Summary: Application name displays as "0" when a column is a line graph (other than CPU) Product: plasma-systemmonitor Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: kdeb...@iwismer.ca CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136060 --> https://bugs.kde.org/attachment.cgi?id=136060=edit system monitor showing 0 as the application names SUMMARY When I set the memory column in the applications tab of the system monitor to a line graph, the names of all the applications get set to "0". It also seems to happen to all the other columns too. If I close and reopen the system monitor, it resets the columns to text only, and the applications are normal again, so there also seems to be a bug with persisting the column configuration. STEPS TO REPRODUCE 1. Open system monitor 2. Configure columns by right clicking in the top bar 3. Set memory to line graph OBSERVED RESULT The application names are all replaced with 0 EXPECTED RESULT The application names remain correct SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433445] New: Autostarted applications show incorrect application name
https://bugs.kde.org/show_bug.cgi?id=433445 Bug ID: 433445 Summary: Autostarted applications show incorrect application name Product: plasma-systemmonitor Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: kdeb...@iwismer.ca CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136059 --> https://bugs.kde.org/attachment.cgi?id=136059=edit System monitor showing the incorrect application name SUMMARY I wasn't sure if this is the correct product to list the bug under so feel free to move it if it belongs with other systemd boot related bugs I just upgraded to 5.21 and enabled the new systemd boot option. I have a few applications that start on login (desktop files that get converted to systemd units). In the system monitor, the don't have the correct application name. See the attached screenshot. STEPS TO REPRODUCE 1. Enable systemd boot 2. Add auto start applications 3. Reboot 4. Open system monitor to the "Applications" tab OBSERVED RESULT All the autostarted application names are "autostart" EXPECTED RESULT The name of the application should be the application's name SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 431468] Unable to copy and paste tasks
https://bugs.kde.org/show_bug.cgi?id=431468 --- Comment #12 from Isaac Wismer --- I have 5 calendars: Nextcloud - Personal Nextcloud - Class Nextcloud - Assignments Nextcloud - Contacts Birthdays (Read Only) ICal - Holidays (Read Only, and for some reason also gives me an extra calendar "akonadi_ical_resource_11", which seems to be an empty calendar) I think the birthday calendar is set to my default (not sure why). If I set the default to my personal calendar, then change the save settings back to add to default calendar, the bug is gone. So it looks like the bug was related to it not asking for an alternate calendar when the original calendar is not writeable. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 431468] Unable to copy and paste tasks
https://bugs.kde.org/show_bug.cgi?id=431468 --- Comment #10 from Isaac Wismer --- It was set to "Be added to the standard calendar", and when I switched it to "Be asked which calendar to use" it was fixed! It now prompts me with what calendar I want to add it to. I guess there was an issue with the default calendar, and it didn't know what calendar to add it to. Thank you very much for your help! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 431468] Unable to copy and paste tasks
https://bugs.kde.org/show_bug.cgi?id=431468 --- Comment #7 from Isaac Wismer --- (In reply to gjditchfield from comment #6) > Copy/paste works for me. I hate it when that happens. :( darn, definitely makes it hard to diagnose. > I suspect that your Akonadi database is damaged. This might help: > - close Kontact, KOrganizer, and the rest of the PIM suite. > - on the command line, run "akonadictl stop; akonadictl fsck; akonadictl > vacuum" I tried stopping akonadi first, but then it said it wouldn't run fsck or vacuum, so then I restarted it, and it ran both. Didn't fix the bug though. > Removing and re-adding the Nextcloud calendar might also work around the > problem. Did this, and still can't copy/paste. Same behaviour as before. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 431468] Unable to copy and paste tasks
https://bugs.kde.org/show_bug.cgi?id=431468 --- Comment #3 from Isaac Wismer --- (In reply to gjditchfield from comment #1) > Which view or views did you try this in? I also tried copying events in the month and agenda (week) views > > When you paste, does a dialog appear that gives you a choice of calendars to > paste into? > > Do you get errors if you copy events? > > If you run korganizer from the command line and reproduce the error, does it > print any messages? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 431468] Unable to copy and paste tasks
https://bugs.kde.org/show_bug.cgi?id=431468 --- Comment #2 from Isaac Wismer --- (In reply to gjditchfield from comment #1) > Which view or views did you try this in? The ToDo list view > > When you paste, does a dialog appear that gives you a choice of calendars to > paste into? No > > Do you get errors if you copy events? Yes, the same error > > If you run korganizer from the command line and reproduce the error, does it > print any messages? "Invalid parent collection" org.kde.pim.korganizer: Incidence not added, job reported error: "Invalid parent collection" -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 431468] New: Unable to copy and paste tasks
https://bugs.kde.org/show_bug.cgi?id=431468 Bug ID: 431468 Summary: Unable to copy and paste tasks Product: korganizer Version: 5.16.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: todoview Assignee: kdepim-b...@kde.org Reporter: kdeb...@iwismer.ca Target Milestone: --- SUMMARY I have some tasks that are repetitive, and so I want to be able to copy and paste them, but when I try to paste them, I get the error: "Error while trying to create calendar item. Error was: Invalid parent collection" STEPS TO REPRODUCE 1. Create task 2. Copy Task 3. Paste task OBSERVED RESULT An error message pops up and the task is not copied EXPECTED RESULT A duplicate task is created. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have a nextcloud calendar synced, with 3 different calendars, plus a couple read only ICal calendars. The task is in one of the nextcloud calendars. The same error also occurs when I use the "Copy To" command in the context menu, -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 431333] Doesn't handle timezones well
https://bugs.kde.org/show_bug.cgi?id=431333 --- Comment #2 from Isaac Wismer --- Ah, I didn't realize that the EXIF data doesn't contain the timezone. I guess that would explain why I had a hard time finding that data when making this bug report. I will send you an email with test data. If we can't automatically detect what timezone the photos are in, would it be possible to add a dropdown for selecting the timezone the photo was taken in (or at least an offset), so that I don't need to convert 6 hours into seconds manually? -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 431333] New: Doesn't handle timezones well
https://bugs.kde.org/show_bug.cgi?id=431333 Bug ID: 431333 Summary: Doesn't handle timezones well Product: kgeotag Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: tobias.leup...@gmx.de Reporter: kdeb...@iwismer.ca Target Milestone: --- SUMMARY I took some photos on my camera while on a hike in Switzerland, and now when I try to tag them with a location from my GPS watch, I need to set the time offset by 6 hours to get the times to match up (I'm in a time zone 6 hours away now). I know I had my camera set to the correct time, as in dolphin it shows the time as being UTC+1, but in KGeoTag it shows the time as UTC-5. STEPS TO REPRODUCE 1. Take photos + record GPX with timezone other than your current 2. Try to tag the photos OBSERVED RESULT you need to set an offset of the time difference between the timezones EXPECTED RESULT The timezone difference should be handled automatically SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It seems that KGeoTag just assumes that the photo timestamps are in your local timezone, but does the conversion for the GPX track. I could be wrong though as I haven't looked into the code. Overall though, this is a really cool project and I'm now going through my photo library adding locations! -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379874] Crash opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379874 Isaac Salgueiro changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Isaac Salgueiro --- Sorry, forgot to update the status on my previous comment. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379874] Crash opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379874 --- Comment #3 from Isaac Salgueiro --- Created attachment 134149 --> https://bugs.kde.org/attachment.cgi?id=134149=edit kcrash dump Well, I don't even remember with what document this segfaulted three years ago, but it just crashed on the second document I tried to open. calligrawords 1:3.2.0-0xneon+20.04+focal+build8 Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-58-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428479] Choosing SWITCH USER option causing system freeze on post-login desktop session
https://bugs.kde.org/show_bug.cgi?id=428479 Isaac Cohen changed: What|Removed |Added Ever confirmed|0 |1 CC||icohen2...@zoho.com Status|REPORTED|CONFIRMED --- Comment #2 from Isaac Cohen --- I was about to report a similar issue but then I saw this bug and figured it's related. So first I successfully reproduced this one and am now marking it as confirmed. Now, the issue I was about to report is that if you push Ctrl + Alt + L or + L and then "Switch User" (I sometimes do this in order to get the "Sleep" button on the lockscreen) it will hang when you enter your password and try to log back in. Steps to Reproduce: 1. Push Ctrl + Alt + L to get lockscreen 2. Click "Switch User" 3. Enter your password and attempt to log in -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 420280] Can't add Google account: authentication stucks
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #33 from Isaac Salgueiro --- (In reply to Nicolas Fella from comment #29) > @Isaac your issue is described in https://bugs.kde.org/show_bug.cgi?id=426034 > > It's fixed upstream but that fix hasn't arrived in Neon yet You're right Nicolas, thanks for the link, I already put my vote on the upstream issue. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 420280] Can't add Google account: authentication stucks
https://bugs.kde.org/show_bug.cgi?id=420280 Isaac Salgueiro changed: What|Removed |Added CC||isalgue...@gmail.com --- Comment #28 from Isaac Salgueiro --- I have a similar issue when trying to log in my google account. For me, clicking in 'Google' in the 'Add new account' dialog opens no window and it shows the following error message: "Message recipient disconnected from message bus without responding". I think these are the relevant logs: nov 25 09:59:17 myhostname signond[6067]: Cannot use KWindowSystem without a QGuiApplication nov 25 09:59:17 myhostname kernel: signond[6067]: segfault at 8 ip 7ff745b657ae sp 7ffca98bc090 error 4 in libQt5Core.so.5.15.1[7ff7459c6000+3080> Versions I'm running: kaccounts-providers/focal,now 4:20.08.3-0xneon+20.04+focal+build13 amd64 [installed,automatic] KDE providers for accounts sign-on Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.4.0-54-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Please, let me know if there's some other test or log that you may need to get your way around this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411493] kwrite memory usage when opening a rather big file
https://bugs.kde.org/show_bug.cgi?id=411493 --- Comment #5 from Isaac Salgueiro --- Just tried again (20.08.02) and this time CPU only spiked when scrolling through the file. IMO memory usage is still huge as you can see in the attached screenshot: that ~4GB step was the memory used by kwrite. Overall responsiveness is way better than when I opened this issue, but still system felt a bit laggy until I closed kwrite. I'm currently using: Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-52-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411493] kwrite memory usage when opening a rather big file
https://bugs.kde.org/show_bug.cgi?id=411493 --- Comment #4 from Isaac Salgueiro --- Created attachment 132904 --> https://bugs.kde.org/attachment.cgi?id=132904=edit kwrite 20.08.2 CPU and memory usage -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428156] New: OFX import goes to the wrong account
https://bugs.kde.org/show_bug.cgi?id=428156 Bug ID: 428156 Summary: OFX import goes to the wrong account Product: kmymoney Version: 5.1.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: kdeb...@iwismer.ca Target Milestone: --- Created attachment 132669 --> https://bugs.kde.org/attachment.cgi?id=132669=edit The import selection and result screen SUMMARY When I use the OFX import wizard from an OFX file downloaded from the internet, it asks me which account to import it into, but then imports it into a different account. This only seems to happen with my credit cards, not with my bank accounts. STEPS TO REPRODUCE 1. Have multiple credit card accounts 2. Import OFX for one of them 3. In the account selection wizard, select the one you want 4. Click OK OBSERVED RESULT The transactions are imported into the wrong account EXPECTED RESULT The transactions are imported into the correct account. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION This may be similar to: https://bugs.kde.org/show_bug.cgi?id=405206 except in this case it allows me to choose the target, but then seemingly ignores my choice. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427530] Shutdown and restart buttons are missing from fullscreen application dashboard.
https://bugs.kde.org/show_bug.cgi?id=427530 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca --- Comment #4 from Isaac Wismer --- I have the same issue, and moving them from the power/session section worked for a while (just reset every reboot) I upgraded to 5.20 today, and now they're gone from the power/session section too. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 423376] New: Terminal programs started in Dolphin continue running after Dolphin exits, writing to .xsession-errors
https://bugs.kde.org/show_bug.cgi?id=423376 Bug ID: 423376 Summary: Terminal programs started in Dolphin continue running after Dolphin exits, writing to .xsession-errors Product: dolphin Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 8switchsoftw...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When you start a Terminal program from Dolphin, it continues running in the background even after you close Dolphin. It receives zeroes as input and its output is directed to .xsession-errors. This continues until the disk is full (unless the user notices and stops it). STEPS TO REPRODUCE 1. Write a short program that reads input and writes the same thing back as output. E.g. something like this: BEGIN: cin >> var; cout << var; goto BEGIN; 2. Compile it (I used: g++ test.cpp) 3. Go to the a.out file in Dolphin and double click on it. 4. Click on "Execute". The program will now run in the background but won't do anything (since it's not getting any input). You can see the program listed as a child process of Dolphin in KSysGuard. 5. Close Dolphin. OBSERVED RESULT The child process will continue running in the background (after Dolphin exits). You can see it will start taking up a whole CPU thread in KSysGuard (or "top" in Terminal). .xsession-errors will begin filling up with zeroes. It seems like after dolphin exits, the process starts being fed a steady stream of zeroes and its output is being redirected to .xsession-errors. EXPECTED RESULT I don't know what would be a good way to fix this. Would there be a way to make all child processes of Dolphin close when Dolphin closes? This might not be good though as other GUI applications are often started in Dolphin and they ought to continue running. Perhaps a feature can be added to prevent Dolphin from starting these sorts of programs to begin with? Or maybe when Dolphin runs a program like this it should open the Terminal along with it (much like Windows does when you start a Terminal program from Explorer). SOFTWARE/OS VERSIONS Linux: 5.7.0-050700-generic KDE Plasma: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION I'm using Kubuntu 20.04. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Isaac Salgueiro changed: What|Removed |Added CC||isalgue...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 416466] GoPro footage thumbnails are just noise in Dolphin
https://bugs.kde.org/show_bug.cgi?id=416466 --- Comment #5 from Isaac A. --- Sorry, just now checked up on this issue. I'll upload a file shortly -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 417958] New: Keyframable clip speed in Kdenlive
https://bugs.kde.org/show_bug.cgi?id=417958 Bug ID: 417958 Summary: Keyframable clip speed in Kdenlive Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: is...@isaacs.site Target Milestone: --- It'd be nice to have a way to keyframe the clip speed in kdenlive, similar to how it's done with premeire: https://motionarray.com/learn/premiere-pro/premiere-pro-speed-ramping-tutorial/ As far as I'm aware a smooth way to adjust clip speed over time isn't possible yet. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 417650] New: Add booking to calendar
https://bugs.kde.org/show_bug.cgi?id=417650 Bug ID: 417650 Summary: Add booking to calendar Product: KDE Itinerary Version: unspecified Platform: Android OS: unspecified Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: kdeb...@iwismer.ca Target Milestone: --- Since it is possible to add bookings to KDE Itinerary directly from PDFs for pkpass files, it would be nice to be able to add those bookings to your calendar, just like the KMail plugin does. This is an option in PassAndroid that would be nice to have in KDE Itinerary. -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 416466] GoPro footage thumbnails are just noise in Dolphin
https://bugs.kde.org/show_bug.cgi?id=416466 --- Comment #2 from Isaac A. --- (In reply to Christoph Feck from comment #1) > Please try this command in Konsole (try with different time-stamps): > > ffmpeg -ss 00:00:10 -i GXxx.MP4 -vframes 1 testoutput.jpg When running this command with any timestamp on any of the footage that's corrupted I get a valid thumbnail from ffmpeg: https://i.imgur.com/LvAULtw.png -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416768] Colors aren't as vivid on videos imported into Kdenlive w/ hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=416768 --- Comment #2 from Isaac A. --- Ahh I see. I think for now I'll leave it enabled and then render without it as it's basically impossible to edit without gpu acceleration for me. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389335] Audio randomly "disconnects" from pulseaudio server
https://bugs.kde.org/show_bug.cgi?id=389335 Isaac A. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Isaac A. --- Have not seen this at all recently -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416768] Colors aren't as vivid on videos imported into Kdenlive w/ hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=416768 Isaac A. changed: What|Removed |Added Summary|Colors aren't as vivid on |Colors aren't as vivid on |videos imported into|videos imported into |Kdenlive|Kdenlive w/ hardware ||acceleration -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416768] New: Colors aren't as vivid on videos imported into Kdenlive
https://bugs.kde.org/show_bug.cgi?id=416768 Bug ID: 416768 Summary: Colors aren't as vivid on videos imported into Kdenlive Product: kdenlive Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: is...@isaacs.site Target Milestone: --- Created attachment 125418 --> https://bugs.kde.org/attachment.cgi?id=125418=edit A comparison between a view of Kdenlive and VLC media player SUMMARY When importing videos into Kdenlive, color is noticeably not as vivid and seems to have a white "tint" over it almost. It renders it like this as well. Seems to be visible more in videos taken at sunset. It does *not* behave like this using the 19.12.1 AppImage and looks exactly the same as VLC does, I think it may be related to hardware acceleration somehow as the AppImage does not support it. I'm not sure. STEPS TO REPRODUCE 1. Import footage into Kdenlive 2. Open said footage in VLC 3. Look at side-by-side with the preview window OBSERVED RESULT Footage has a weird white tint look to it compared to the VLC view EXPECTED RESULT Footage should look mostly the same as VLC SOFTWARE/OS VERSIONS Linux: 5.4.12 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413470] kdenlive crashes when editing a text clip
https://bugs.kde.org/show_bug.cgi?id=413470 Isaac A. changed: What|Removed |Added CC||is...@isaacs.site --- Comment #3 from Isaac A. --- I'm seeing this crash as well, I think it could possibly be related to some sort've hardware acceleration as it does not happen in the AppImage, which doesn't support hardware acceleration as far as I can tell. I'm using an AMD RX 580 on Fedora 31 with Kdenlive 19.12.0.. The AppImage is 19.12.1 so I guess I'll have to wait until the repo updates to test if it's been fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 416466] New: GoPro footage thumbnails are just noise in Dolphin
https://bugs.kde.org/show_bug.cgi?id=416466 Bug ID: 416466 Summary: GoPro footage thumbnails are just noise in Dolphin Product: kdemultimedia Version: 19.12 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ffmpegthumbs Assignee: kde-multime...@kde.org Reporter: is...@isaacs.site Target Milestone: --- Whenever viewing footage from my GoPro Hero 8 with ffmpegthumbs enabled in Dolphin the thumbnails are just noise most of the time, may be related to #406981.. Occasionally some of the footage has a thumbnail, I'm not sure what causes it, but it's consistent on what footage does and does not. I can upload said footage if needed once I'm near a fast connection. It could also be related to file size somehow as I'm unable to find any files over around 150 MB that display thumbnails.. Picture of the issue: https://i.imgur.com/1wm2ITp.png -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 416466] GoPro footage thumbnails are just noise in Dolphin
https://bugs.kde.org/show_bug.cgi?id=416466 Isaac A. changed: What|Removed |Added CC||is...@isaacs.site -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 126153] Camera stores both jpeg and raw (nef), handle both as one
https://bugs.kde.org/show_bug.cgi?id=126153 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 410167] Cannot change or enter time for calendar entry
https://bugs.kde.org/show_bug.cgi?id=410167 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca --- Comment #5 from Isaac Wismer --- *** Bug 411820 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 411820] Problems setting event start and end time
https://bugs.kde.org/show_bug.cgi?id=411820 Isaac Wismer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Isaac Wismer --- *** This bug has been marked as a duplicate of bug 410167 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca -- You are receiving this mail because: You are watching all bug changes.
