[plasma-systemmonitor] [Bug 472522] Plasma System monitor falsely shows 100% CPU usage on one core
https://bugs.kde.org/show_bug.cgi?id=472522 --- Comment #7 from Martin Schnitkemper --- (In reply to Jesus from comment #6) > The same on arch linux, one core at 100% but htop shows all cores at 0% In 'htop' press 'F2', then check in the "Display Options" the option "Detailed CPU time", and after that you see the IO-Wait for the core in the meters panel. The problem is, that in opposite to other tools like 'htop' the KDE system monitor reports IO-Waits as CPU usage; and that should be fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 472522] Plasma System monitor falsely shows 100% CPU usage on one core
https://bugs.kde.org/show_bug.cgi?id=472522 --- Comment #5 from Martin Schnitkemper --- (In reply to Matej Mrenica from comment #4) > Yes, mariadb is indeed the cause of this, so this might not be a kde issue > afterall? How can we determine what uses mariadb? It looks like a kernel regression. I just downgraded to version 6.1.38-1-lts and the problem is gone. Since I am afraid of any negative site effects of downgraded components, I prefer to stay at the current kernel and decided to live with the problem. It seems that it is more a kind of cosmetic problem, because the system is not rather slow or does heat up. And it's also not shown in other applications like "top", or at the process table. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 472522] Plasma System monitor falsely shows 100% CPU usage on one core
https://bugs.kde.org/show_bug.cgi?id=472522 --- Comment #3 from Martin Schnitkemper --- It seems that it belongs to MariaDB: if I stop also the mariadb.service, CPU load for all cores are gone. That explains why after stopping the akonadi server, only one core has the 100% load, since akonadi also uses MariaDB; if I run mariadb and akonadi, I get the load on two cores, if I stop both, the CPU usage is back to normal. That happens with kernel v6.4.4 as well as with LTS v6.1.39. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 472522] Plasma System monitor falsely shows 100% CPU usage on one core
https://bugs.kde.org/show_bug.cgi?id=472522 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #2 from Martin Schnitkemper --- Same here after latest update. Got 100% CPU usage on two cores after sign in as user, but can't find neither in the processtable nor top (or htop) such the process that triggers the load. Interesting observation: If I stop akonadi it goes down to one CPU, if I start the akonadi server again, it raises again up to two CPUs. System Information: | Operating System: Arch Linux | KDE Plasma Version: 5.27.6 | KDE Frameworks Version: 5.108.0 | Qt Version: 5.15.10 | Kernel Version: 6.4.4-arch1-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390806] kmail sleeping after opening an attachment
https://bugs.kde.org/show_bug.cgi?id=390806 Martin Schnitkemper changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Martin Schnitkemper --- The problem has now been fixed and no longer occurs. [kmail2 5.22.3 (22.12.3) | KDE Plasma version: 5.27.2 | KDE Framework Version: 5.103.0 | Qt version: 5.15.8] -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467397] New: Thumbnails disappeared
https://bugs.kde.org/show_bug.cgi?id=467397 Bug ID: 467397 Summary: Thumbnails disappeared Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: martin.schnitkem...@nexgo.de Target Milestone: --- SUMMARY Since version 22.12.3 the thumbnails in the timeline have disappeared. I set the "In/Out Frames" option, but only a placeholder with no image appears. STEPS TO REPRODUCE 1. Open a project 2. Set one of the frame preview options (I used "In/Out Frames") OBSERVED RESULT Placeholder instead of the thumbnail EXPECTED RESULT A thumbnail of the first/last frame in full zoom step (21/21) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Furthermore, there is a process running in the background that permanently loads the system and continues to run after kdenlive is closed and has to be shut down manually. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463732] Print Dialog should remember PDF Options
https://bugs.kde.org/show_bug.cgi?id=463732 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463732] Print Dialog should remember PDF Options
https://bugs.kde.org/show_bug.cgi?id=463732 --- Comment #6 from Martin Schnitkemper --- (In reply to Nate Graham from comment #4) > This would work for the scaling option, since it's added by Okular. But it > would not work for any other options that come from the basic dialog itself. > So if we did this, we'd go from "nothing is remembered" to "random options > are remembered, but most aren't". You have a point with that. Perhaps one possibility would be to let the user specify in the application's configuration dialog which option he would like to start the dialog with. Then it is clear that it is not the last selected option that becomes the default, but explicitly the option specified by the user. For me, the scaling option is not that important, we just had a discussion in a German newsgroup about how to change the behavior, and I didn't see an option there. For anyone who suffers from the current behavior, I can provide a patch that defaults to the third item in the list instead of the first. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463732] Print Dialog should remember PDF Options
https://bugs.kde.org/show_bug.cgi?id=463732
--- Comment #3 from Martin Schnitkemper ---
Sorry, it seems to be decided in the function "PDFOptionsPage" of
"generators/poppler/generator_pdf.cpp":
| m_scaleMode = new QComboBox;
| m_scaleMode->insertItem(FitToPrintableArea, i18n("Fit to printable area"),
FitToPrintableArea);
| m_scaleMode->insertItem(FitToPage, i18n("Fit to full page"), FitToPage);
| m_scaleMode->insertItem(None, i18n("None; print original size"), None);
| m_scaleMode->setToolTip(i18n("Scaling mode for the printed pages"));
| printBackendLayout->addRow(i18n("Scale mode:"), m_scaleMode);
So the return value of "m_scaleMode" should be saved and reloaded as default.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 463732] Print Dialog should remember PDF Options
https://bugs.kde.org/show_bug.cgi?id=463732
Martin Schnitkemper changed:
What|Removed |Added
CC||martin.schnitkemper@nexgo.d
||e
--- Comment #2 from Martin Schnitkemper ---
I'm not the expert, but the decision is made in core/printoptionswidget.cpp:
| {
| setWindowTitle(i18n("Print Options"));
| QFormLayout *layout = new QFormLayout(this);
| m_ignorePrintMargins = new QComboBox;
| // value indicates whether full page is enabled (i.e. print margins
ignored)
| m_ignorePrintMargins->insertItem(0, i18n("Fit to printable area"),
false);
| m_ignorePrintMargins->insertItem(1, i18n("Fit to full page"), true);
| layout->addRow(i18n("Scale mode:"), m_ignorePrintMargins);
| }
Then it should be possible to store the return value ("true" or "false") as a
status in ~/.config/okularrc and when opening the dialog again,
read the value and set it as default.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 428384] Dolphin displays duplicate files and then crashes in KFileItemModel::refreshDirectory() when refreshing sftp-folder
https://bugs.kde.org/show_bug.cgi?id=428384 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405284] baloo_file_extractor crashes in Baloo::DocumentDB::del() / mdb_cursor_del()
https://bugs.kde.org/show_bug.cgi?id=405284 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 454948] Akonadi server will not start on fresh install; yields "unknown error"
https://bugs.kde.org/show_bug.cgi?id=454948 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #97 from Martin Schnitkemper --- I don't know how & why, but since I upgraded today to KDE Plasma Version 5.25.0 and KDE Frameworks Version 5.95.0 the startup sound is back again on all systems after months of absence. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405284] baloo_file_extractor crashes in Baloo::DocumentDB::del() / mdb_cursor_del()
https://bugs.kde.org/show_bug.cgi?id=405284 --- Comment #15 from Martin Schnitkemper --- (In reply to scripptor from comment #14) > Possibly a regression, in framework version 5.94.0. We are meanwhile on KDE Frameworks Version 5.95.0. I was for weeks on version 5.94 and I cannot confirm any issues with baloo. Since today I am on KDE Plasma Version 5.25.0 and KDE Frameworks Version 5.95.0 on two systems and it still works without problems: Create and delete file & folders or purge and recreate the database runs without any crashes. Operating System is Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 454948] Akonadi server will not start on fresh install; yields "unknown error"
https://bugs.kde.org/show_bug.cgi?id=454948 --- Comment #16 from Martin Schnitkemper --- I have now run the update on two systems and in both cases akonadi no longer starts. I didn't get the "unknown error" error, but the file "ib_logfile0" was missing after the first login. A "touch $HOME/.local/share/akonadi/db_data/ib_logfile0" as suggested here several times was not a solution because after the second logon I had 3200+ entries in mysql.err like | [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 1447482201 is in the future! Current system log sequence number 1378510903. | [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery. A "recovery" was not an option for me because it seems complicated to me, is only insufficiently described in the MariaDB knowledgebase and I am not sure if it solves the problem at all. I had already completed the update to mariadb 10.8.3 last week and also updated the structures with "mariadb-upgrade --socket=/run/user/$(id -u)/akonadi/mysql.socket", it came therefore only the "KDE Gear 22.04.2" update with akonadi and its accompanying components. Based on the experience of the first system, I copied now the "ib_logfile0" file to a safe place before updating the second system. After the file was missing again after the update and the first logon, the easiest solution for me was to copy the file back after the update and restart akonadi. It also survived a reboot. My recommendation is therefore to back up the file before an update or restore it from a current backup. If it has already happened then it also helps to delete (or rename) the "db_data" folder and start new with a "mariadb-install-db --datadir=$HOME/.local/share/akonadi/db_data --basedir= /usr". The question remains (and here I see the real problem) why akonadi or one of its components removes the "ib_logfile0" file on the first logon after the update. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 454948] Akonadi server will not start on fresh install; yields "unknown error"
https://bugs.kde.org/show_bug.cgi?id=454948 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451790] System Monitor Sensor breaks WeatherWidget-2 from the KDE store on KDE Framework 5.92
https://bugs.kde.org/show_bug.cgi?id=451790 --- Comment #7 from Martin Schnitkemper --- I rebuilt the package while applying the provided patches, and it seems that it works. After I placed a widget (disk usage) on the desktop and signed off-/on, the connection of the weather widget to Met.No was still operational. To verify the behavior I reverted back to the package of the provider, and the connection was again broken. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 --- Comment #17 from Martin Schnitkemper --- (In reply to Nate Graham from comment #16) > Did you mean 5.24.5? 5.25.5 is a long ways away! :D Yes... you are right... my fault... can't edit the comment, but it is 5.24.5: | 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-arch1-1 (64-bit) | Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 --- Comment #15 from Martin Schnitkemper --- (In reply to nicdex from comment #14) > kwin_x11 (5.24.4) using Qt 5.15.3 Try update to the latest plasma 5.25.5. Even if not stated in the changelog, since I upgrade to plasma 5.25.5 I had no more crashes since three days; before three or more times a day. It seems that it has been fixed in kwin or some of the depent components. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451790] System Monitor Sensor breaks WeatherWidget-2 from the KDE store on KDE Framework 5.92
https://bugs.kde.org/show_bug.cgi?id=451790 --- Comment #3 from Martin Schnitkemper --- Problem still persist in the latest update of KDE Framework 5.93.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #7 from Martin Schnitkemper --- Got the same error for several times already: | Application: KWin (kwin_x11), signal: Aborted | | [KCrash Handler] | #4 0x7f2bbd65834c in __pthread_kill_implementation () at /usr/lib/libc.so.6 | #5 0x7f2bbd60b4b8 in raise () at /usr/lib/libc.so.6 | #6 0x7f2bbd5f5534 in abort () at /usr/lib/libc.so.6 | #7 0x7f2bb5cd059b in () at /usr/lib/dri/iris_dri.so | #8 0x7f2bb690823f in () at /usr/lib/dri/iris_dri.so | #9 0x7f2bb5f51ea7 in () at /usr/lib/dri/iris_dri.so | #10 0x7f2bc008e84f in KWin::WindowThumbnailItem::updateOffscreenTexture() (this=0x556e2d05e810) at /usr/src/debug/kwin-5.24.4/src/scripting/thumbnailitem.cpp:432 | #11 0x7f2bbe70c463 in () at /usr/lib/libQt5Core.so.5 | #12 0x7f2bc0062a4e in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) (this=0x556e2c377920, damage=..., repaint=..., updateRegion=0x7ffe51a306e0, validRegion=0x7ffe51a306d8, renderLoop=, projection=...) at /usr/src/debug/kwin-5.24.4/src/scene.cpp:282 | #13 0x7f2bc013045c in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) (this=0x556e2c377920, output=0x0, damage=..., toplevels=, renderLoop=0x556e2c099f10) at /usr/src/debug/kwin-5.24.4/src/scenes/opengl/scene_opengl.cpp:259 | #14 0x7f2bbffc6507 in KWin::Compositor::composite(KWin::RenderLoop*) (this=0x556e2c0b11d0, renderLoop=0x556e2c099f10) at /usr/src/debug/kwin-5.24.4/src/composite.cpp:633 | #15 0x7f2bbffc6b91 in KWin::X11Compositor::composite(KWin::RenderLoop*) (this=0x556e2c0b11d0, renderLoop=) at /usr/src/debug/kwin-5.24.4/src/composite.cpp:844 | #16 0x7f2bbe70c463 in () at /usr/lib/libQt5Core.so.5 | #17 0x7f2bbff800d7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) (this=, _t1=) at /usr/src/debug/build/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206 | #18 0x7f2bc00546d8 in KWin::RenderLoopPrivate::dispatch() (this=0x556e2c099f30) at /usr/src/debug/kwin-5.24.4/src/renderloop.cpp:150 | #19 0x7f2bbe70c463 in () at /usr/lib/libQt5Core.so.5 | #20 0x7f2bbe70e69f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 | #21 0x7f2bbe6ff766 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 | #22 0x7f2bbdd091c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 | #23 0x7f2bbe6db5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 | #24 0x7f2bbe726dd5 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 | #25 0x7f2bbe727272 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 | #26 0x7f2bb857af83 in () at /usr/lib/libQt5XcbQpa.so.5 | #27 0x7f2bbe6d388b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 | #28 0x7f2bbe6defd7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 | #29 0x556e2a030a25 in main(int, char**) (argc=, argv=0x7ffe51a31108) at /usr/src/debug/kwin-5.24.4/src/main_x11.cpp:482 | [Inferior 1 (process 135328) detached] I compiled the package with debug options but konqi reported that the collected crash information maybe useless for the developers. So if you need a backtrace from any other application belonging to this problem, let me know. My System-Information: = Operating System: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.17.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-9400 CPU @ 2.90GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451790] System Monitor Sensor breaks WeatherWidget-2 from the KDE store on KDE Framework 5.92
https://bugs.kde.org/show_bug.cgi?id=451790 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449828] Startup sound doesn't play
https://bugs.kde.org/show_bug.cgi?id=449828 --- Comment #13 from Martin Schnitkemper --- (In reply to KazuhiroShigeru from comment #12) > other sounds work fine, like the logoff one. You are also able to check it on a notebook while you disconnect/connect the power cord? Thats where I discovered the problem first after upgrade to plasma 5.24.0, so it's not only the logon sound. And other sound events have also a strange behaviour, like the bell on konsole. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 449828] Login notification doesn't play the sound queue on login since the system was updated to KDE Plasma 5.24
https://bugs.kde.org/show_bug.cgi?id=449828 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #4 from Martin Schnitkemper --- I can confirm this bug on system | Operating System: Arch Linux | KDE Plasma Version: 5.24.0 | KDE Frameworks Version: 5.90.0 | Qt Version: 5.15.2 | Kernel Version: 5.16.8-arch1-1 (64-bit) | Graphics Platform: X11 | Processors: 2 × Intel® Core™2 Duo CPU P8600 @ 2.40GHz | Memory: 7,7 GiB of RAM | Graphics Processor: Mesa DRI Mobile Intel® GM45 Express Chipset It seems that it is a regression of bug 422948, which was never really fixed, only solved by a workaround. As I already stated in the other report, the problem is that events are not handlded correctly on sign on. You can easily verify that if you check another option in the settings like writing a logfile on logon-/logoff-event. Then you realize that log entries are written on logoff but never on logon. Other events are meanwhile also affected since the release of Plasma-5.2.4 like notification of connect/disconnect the powercord on notebooks. Usualy you will get a notification sound but since Plasma-5.2.4 its muted. Other actions like writing a logfile fails the same as display a message, so it seems that the notification is completely unhandled. Other site effects after release of Plasma-5.2.4 are that the sound i.e. in konsole for notifications like "bell in focused session" is rather not hearable on the first occurence, next occurence is loud as configured, but a few seconds later its silent again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439799] Mails with attachment not stored after sent
https://bugs.kde.org/show_bug.cgi?id=439799 Martin Schnitkemper changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Martin Schnitkemper --- Reason was a malformed filter that moved some of the sent mails to a special folder. After correction of the filter criteria sent mails are stored now as expected. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439799] New: Mails with attachment not stored after sent
https://bugs.kde.org/show_bug.cgi?id=439799 Bug ID: 439799 Summary: Mails with attachment not stored after sent Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: martin.schnitkem...@nexgo.de Target Milestone: --- SUMMARY Mails with an attachment are not stored & lost after sending. Sent mail without attachments are stored for later review. STEPS TO REPRODUCE 1. Send a mail with an attachment; the mail is not stored after sending 2. Send a mail without an attachment; the mail is stored after sending OBSERVED RESULT Lost mail copy after sending EXPECTED RESULT Stored a copy of mail for later review SOFTWARE/OS VERSIONS kmail2 5.17.3 (21.04.3) Operating System: Arch Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-arch1-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413368] upgraded to 5.17.x, krunner alt-f2 shortcut stopped working
https://bugs.kde.org/show_bug.cgi?id=413368 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413368] upgraded to 5.17.x, krunner alt-f2 shortcut stopped working
https://bugs.kde.org/show_bug.cgi?id=413368 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] [Regression] Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 --- Comment #26 from Martin Schnitkemper --- (In reply to Giorgio from comment #25) > I'm logging in to a remote server, I can't unmount it and perform a check. > Or are you talking about my local system? I assumed that it was a system like a NAS where you signed on. If you have no physical access to the server, you should ask your service provider for assistance. He can probably also explain the facts behind the error message. I think that the problem is not related to the reported bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] [Regression] Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 --- Comment #24 from Martin Schnitkemper --- (In reply to Giorgio from comment #23) > But when I create a new folder I get the notification > > "Examination (Failed)" The filesystem is probably not clean. Try to unmount the volume and perform a fileysystem check. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] [Regression] Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 --- Comment #22 from Martin Schnitkemper --- (In reply to Germano Massullo from comment #20) > Well the bugs is still here. Using a FTP I created a new folder, then I > could not paste files inside it Can it be permission problem that you have no write access on the folder? I just tried it, I can create a new folder and a textfile in the new folder, and can also drag & drop a file from the local filesystem to the remote filesystem. For me it works as designed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] [Regression] Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 --- Comment #21 from Martin Schnitkemper --- I can confirm, that the problem has been solved in both distributions, "Arch" and "KDE neon", since both are on Frameworks 5.81. But I still discovered another strange behaviour: if you create a new folder, then a name "New Folder" is offered, and if you try to create another folder, it is automaticly named as "New Folder (1)". Not so on a file: first offer is i. e. for a textfile "Text file.txt" and if you try to create another one, "Text file.txt" is offered again and you get the "already exist" warning and has to correct the filename to continue. That happen only on a ftp share, not on a local device; there you get an offer like "Text file (1).txt". That does not really annyoing me, just want to mention it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428384] Dolphin displays duplicate files and then crashes in KFileItemModel::refreshDirectory() when refreshing sftp-folder
https://bugs.kde.org/show_bug.cgi?id=428384 --- Comment #6 from Martin Schnitkemper --- Seems that the problem has been solved with the release of version 21.04.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428384] Dolphin displays duplicate files and then crashes in KFileItemModel::refreshDirectory() when refreshing sftp-folder
https://bugs.kde.org/show_bug.cgi?id=428384 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #5 from Martin Schnitkemper --- I can confirm that behaviour, it happen to me also on a local folder. When I am scrolling up an down a folder with a larger amount of files or subfolders, suddenly some entries appear double. After refesh, Dolphin crashes. Systeminformation: = Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.12-arch1-1 OS Type: 64-bit Graphics Platform: X11 Application: === dolphin 20.12.3 Backtrace: = #0 0x7f575284def5 in raise () from /usr/lib/libc.so.6 #1 0x7f5752166189 in KCrash::defaultCrashHandler(int) () from /usr/lib/libKF5Crash.so.5 #2 #3 0x7f575284def5 in raise () from /usr/lib/libc.so.6 #4 0x7f5752837862 in abort () from /usr/lib/libc.so.6 #5 0x7f575288ff38 in __libc_message () from /usr/lib/libc.so.6 #6 0x7f5752897bea in malloc_printerr () from /usr/lib/libc.so.6 #7 0x7f5752898fcc in _int_free () from /usr/lib/libc.so.6 #8 0x7f575289cca8 in free () from /usr/lib/libc.so.6 #9 0x7f57506d6018 in QHashData::free_helper(void (*)(QHashData::Node*)) () from /usr/lib/libQt5Core.so.5 #10 0x7f575274a2f6 in KFileItemModel::ItemData::~ItemData (this=0x559567c31120, __in_chrg=) at /usr/src/debug/dolphin-20.12.3/src/kitemviews/kfileitemmodel.h:285 #11 qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt/QtCore/qalgorithms.h:320 #12 qDeleteAll > (c=...) at /usr/include/qt/QtCore/qalgorithms.h:328 #13 KFileItemModel::slotClear (this=0x559566e79de0) at /usr/src/debug/dolphin-20.12.3/src/kitemviews/kfileitemmodel.cpp:1147 #14 0x7f57508ba9d6 in ?? () from /usr/lib/libQt5Core.so.5 #15 0x7f575226326b in ?? () from /usr/lib/libKF5KIOCore.so.5 #16 0x7f5752263a72 in ?? () from /usr/lib/libKF5KIOCore.so.5 #17 0x7f5752755a53 in KFileItemModel::refreshDirectory (this=0x559566e79de0, url=...) at /usr/src/debug/dolphin-20.12.3/src/kitemviews/kfileitemmodel.cpp:123 #18 0x7f57527b2022 in DolphinView::reload (this=0x559566c239d0) at /usr/src/debug/dolphin-20.12.3/src/views/dolphinview.cpp:453 #19 0x7f5752a3f65e in DolphinViewContainer::reload (this=0x559566e97ef0) at /usr/src/debug/dolphin-20.12.3/src/dolphinviewcontainer.cpp:448 #20 0x7f5752a29021 in DolphinMainWindow::reloadView (this=0x559566a92070) at /usr/src/debug/dolphin-20.12.3/src/dolphinmainwindow.cpp:830 #21 0x7f57508ba9d6 in ?? () from /usr/lib/libQt5Core.so.5 #22 0x7f5751346f73 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #23 0x7f5751349855 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #24 0x7f5751441232 in ?? () from /usr/lib/libQt5Widgets.so.5 #25 0x7f5751441353 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #26 0x7f575153637b in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #27 0x7f575138ebde in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #28 0x7f575134d762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #29 0x7f575135488b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #30 0x7f575088362a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #31 0x7f575135388e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #32 0x7f57513a7319 in ?? () from /usr/lib/libQt5Widgets.so.5 #33 0x7f57513aa70f in ?? () from /usr/lib/libQt5Widgets.so.5 #34 0x7f575134d762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #35 0x7f575088362a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #36 0x7f5750c5e724 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #37 0x7f5750c33bc5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #38 0x7f574b0a519c in ?? () from /usr/lib/libQt5XcbQpa.so.5 #39 0x7f574e6bc02c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #40 0x7f574e70fb59 in ?? () from /usr/lib/libglib-2.0.so.0 #41 0x7f574e6b9781 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #42 0x7f57508dc1a1 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #43 0x7f5750881f8c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Cor
[plasmashell] [Bug 428929] File and folder dialogs stop accepting mouse input in Virtualbox on Plasma 5.20 and newer
https://bugs.kde.org/show_bug.cgi?id=428929 --- Comment #10 from Martin Schnitkemper --- I found after some searches a related bug report now on the Oracle bug tracker: https://www.virtualbox.org/ticket/20222 There is also attached a "vbox-fix-file-picker.patch", but it seems only to be a workaround and not a real fix: https://bugs.mageia.org/show_bug.cgi?id=27433#c11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428929] VirtualBox selection windows freezes on Plasma 5.20 and newer
https://bugs.kde.org/show_bug.cgi?id=428929 --- Comment #8 from Martin Schnitkemper --- Created attachment 136977 --> https://bugs.kde.org/attachment.cgi?id=136977=edit file chooser dialog Sorry for the delay, here is the screenshot as requested. The mouse wheel for scrolling in the left bar (Places/Remote/Recent) does also not work, only the close button in the title bar react upon a mouse action. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428929] VirtualBox selection windows freezes on Plasma 5.20 and newer
https://bugs.kde.org/show_bug.cgi?id=428929 --- Comment #6 from Martin Schnitkemper --- (In reply to Nate Graham from comment #5) > Probably a VirtualBox bug. But just to be sure, I'd like to reproduce. The > existing instructions are too unclear for my puny brain. Can someone write > very clear, simple, Nate-friendly instructions? Thanks! For example, open an existing VM, then call "Settings", and there the "Advanced" tab in the "General"section. In this tab, open the item "Snapshot Folder"and clock to "other" to change the folder. >From now, you can't select any folder or any button with the mouse; just the keyboard still works. The same happen if you try to attach or change a ISO in the "Storage" section. After you clicked on the blue button for "Choose a a disk file..." you cannot select the ISO, or change to another folder, or select any item if the tool bar, or one of the buttons to open the file or cancel the dialog. If you still can't reproduce the behaviour, feel free to ask. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405284] baloo_file_extractor crashes in Baloo::DocumentDB::del() / mdb_cursor_del()
https://bugs.kde.org/show_bug.cgi?id=405284 --- Comment #13 from Martin Schnitkemper --- It seems to work now after the latest upgrade to KDE Frameworks 5.79.0; it does no more crash after creating or deleting a folder. On one system it was necessary to purge the database and create the index again, since it crashed always on startup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #75 from Martin Schnitkemper --- (In reply to Colin J Thomson from comment #74) > This issue seems to have reappeared again in 5.21.0 I can't confirm this behaviour, it still works for me Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428929] VirtualBox selection windows freezes on Plasma 5.20 and newer
https://bugs.kde.org/show_bug.cgi?id=428929 Martin Schnitkemper changed: What|Removed |Added Status|RESOLVED|REOPENED CC||martin.schnitkemper@nexgo.d ||e Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #4 from Martin Schnitkemper --- The issue still exist, but it is NOT a freeze as reported, since the application is still operational. The problem occurs in some file dialogs, such as attaching a optical media to a VM, or change the target directory for snapshots. In these dialogs, mouse actions are not handled, that leads to the impression that the application hangs. In these circumstances, the focus has been set to the name field of the form and it is possible to type. The mouse pointer is visible and moving, but does not respond on any click. As a workaround, it is possible to change the focus using the TAB key, or the cursor/arrow keys to select an item. I am not sure, if it is a KDE issue, but I could not find any related report at the VirtualBox bugtracker. System-Information: == Operating System: Arch Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.6-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405284] baloo_file_extractor crashes in Baloo::DocumentDB::del() / mdb_cursor_del()
https://bugs.kde.org/show_bug.cgi?id=405284 --- Comment #12 from Martin Schnitkemper --- Same issue here, it happen reproducable after creating or deleting a directory. Application: baloo_file (baloo_file), signal: Aborted [KCrash Handler] #4 0x7fdc0efdb615 in raise () from /usr/lib/libc.so.6 #5 0x7fdc0efc4862 in abort () from /usr/lib/libc.so.6 #6 0x7fdc0f51a9ac in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #7 0x7fdc0f519d59 in qt_assert(char const*, char const*, int) () from /usr/lib/libQt5Core.so.5 #8 0x56117dc047d5 in Baloo::FileWatch::slotFileDeleted (this=0x7ffce4fa9440, urlString=..., isDir=) at /usr/src/debug/baloo-5.78.0/src/file/filewatch.cpp:100 #9 0x7fdc0f776dd6 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x56117dc229a2 in KInotify::deleted (_t2=true, _t1=..., this=0x56117e473980) at /usr/src/debug/build/src/file/baloofilecommon_autogen/include/moc_kinotify.cpp:334 #11 KInotify::slotEvent (this=0x56117e473980, socket=) at /usr/src/debug/baloo-5.78.0/src/file/kinotify.cpp:395 #12 0x7fdc0f776dd6 in ?? () from /usr/lib/libQt5Core.so.5 #13 0x7fdc0f77a340 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #14 0x7fdc0f77ab4d in QSocketNotifier::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #15 0x7fdc0f73fa50 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7fdc0f7992f6 in ?? () from /usr/lib/libQt5Core.so.5 #17 0x7fdc0dcdaa84 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #18 0x7fdc0dd2e9b1 in ?? () from /usr/lib/libglib-2.0.so.0 #19 0x7fdc0dcd92b1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0x7fdc0f7986e1 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #21 0x7fdc0f73e3fc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #22 0x7fdc0f746894 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #23 0x56117dc04e8d in main (argc=, argv=0x7ffce4fa93b0) at /usr/src/debug/baloo-5.78.0/src/file/main.cpp:78 [Inferior 1 (process 8573) detached] Operating System: Arch Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.6-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405284] baloo_file_extractor crashes in Baloo::DocumentDB::del() / mdb_cursor_del()
https://bugs.kde.org/show_bug.cgi?id=405284 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 Martin Schnitkemper changed: What|Removed |Added Platform|Neon Packages |Archlinux Packages --- Comment #6 from Martin Schnitkemper --- Why has the platform of the report been changed from "Archlinux Packages" to "Neon Packages"? I as the reporter of the bug have to set the platform where the bug has been observed, and that was "Archlinux Packages" and not "Neon Packages". Even if it also exist on other platforms, I can only confirm that it exist on that platform where I observed it, and the value should be kept on the value the reporter has been set while creating the report. Reverted to the original value. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 --- Comment #4 from Martin Schnitkemper --- (In reply to Giorgio from comment #3) > Happy it was helpful for you. Unfortunately ftp is essential for me. And > downgrading kio nor kio-extras does not work for me. You tried kio-5.75.0? That did it for me, but since I am not sure of site effects, if I mix outdated with current software, I am staying on the latest release (now 5.77.0). Bugreport is open since a month and still in status REPORTED, so I don't believe in a fast solution from the devs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 --- Comment #2 from Martin Schnitkemper --- (In reply to Giorgio from comment #1) > It doesn't happen with fish/ssh protocol, I can't try with samba. Thanks for your comment; after I changed the protocol from ftp to sftp and the port from 21 to 22, I was again able to create files & folders on the network drive. I can live for the moment with this workaround. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 429541] New: Can't create folders or files on ftp shares
https://bugs.kde.org/show_bug.cgi?id=429541 Bug ID: 429541 Summary: Can't create folders or files on ftp shares Product: frameworks-kio Version: 5.76.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: FTP Assignee: kio-bugs-n...@kde.org Reporter: martin.schnitkem...@nexgo.de CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 133584 --> https://bugs.kde.org/attachment.cgi?id=133584=edit Error on create a folder SUMMARY If I try to create a folder on a ftp share I got the error, that the folder already exist, even if it didn't. Same happen with files STEPS TO REPRODUCE 1. inside dolphin connect to a network share, change into any folder and try to create a folder using the context menu or F10. It results into an error, that the folder already exist. Copy files or folders with i.e. drag works, so it's not a permission issue. 2. After downgraded kio (5.76.0-1 -> 5.75.0-2) it works again, so it seems to be a problem with the current version of kio. OBSERVED RESULT Error message EXPECTED RESULT Create the folder SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.9.9-arch1-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #71 from Martin Schnitkemper --- (In reply to Michał Dybczak from comment #70) > The weird thing is, I didn't see any KDE packages in the update. The only > related packages may be pulseaudio packages (6 of them). On native Arch, the version 5.20.2-1 of package plasma-workspace did the thing. There should be something similar in Manjaro -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #68 from Martin Schnitkemper --- I can not say, since when the notification-problem exist. I just discovered it since the "play a sound"-event is configured in the same systemsettings panel than the other events, but I didn't used them so far. After I discovered the startup sound problem, I configured in addition the "log to a file"-event to verify, if it is just a sound problem or a general problem with the notifications. And I can confirm now, that the problem affects every event, that should be triggered on startup. I configured the same events on logout, and on every logout I got an entry in the logfile, written by KNotify, but never on login. Same happen with the "show a message in a popup". If that leads into a racing condition, than this concept is unusable for any other event too, since it doesn't work. If it works on logout, why not on logon? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #64 from Martin Schnitkemper --- I tried the patch and startup sound is back for me now. But other events like notifications or logfile entries on startup still does not work, therefore I still think that the main problem is elsewhere, than just to fix the startup sound problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #60 from Martin Schnitkemper --- As I told already months before, it has nothing to do with the sound, the problem is that events are not handldes correctly on sign on. You can easily verify that if you configure a another action like writing a logfile on logon-/logoff-event, and you realize that log entries are written on logoff but not on logon. Developers should watch in that direction, than always and only to a missing sound. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #48 from Martin Schnitkemper --- As I already commented in https://bugs.kde.org/show_bug.cgi?id=422948#c41, the problem seems that it does not trigger the notifications for the "Login" event. The "ffplay"-command in konsole plays the sound, but not, if it has been set as a command for notifications. I still use th "Log to a file" option for the "Login" and "Logout" events, but only logouts are written, and never a logon. To place a "ffplay"-command on autostart may be a workaround for a missing startup-sound, but is not a solution that the logon-events are not handled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #41 from Martin Schnitkemper --- It seems, that it does not trigger the notifications for the "Login" event. To see what happen, I set beside the sound in the notification configuration now also a "Log to a file" option for the "Login" and "Logout" events. On every logout an entry has been written, but not after a login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #38 from Martin Schnitkemper --- Problem was, that the maintainer tried to copy a file on and not into a directory. Seems that the PKBUILD was broken, but they fixed it yesterday: https://aur.archlinux.org/cgit/aur.git/commit/?h=oxygen-sounds=da68b016e2525439be94614b1cc67b24f88ed443 So build your package against the latest sources. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] startup sound cut off
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #12 from Martin Schnitkemper --- Applied both patches and created packages for Arch, but no changes; I still get no startup sound. Sorry to tell you that this issue is not solved for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 422948] startup sound cut off
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #2 from Martin Schnitkemper --- (In reply to Martin Schnitkemper from comment #1) > ...and I still can't find the settings in the configuration panel where to > check or change the sound. Ok... found it now... it's good hidden in the (new?) configuration panel, set to "Oxygen-Sys-Log-In-Short.ogg", and it is playable. Even on logon it's quiet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 422948] startup sound cut off
https://bugs.kde.org/show_bug.cgi?id=422948 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #1 from Martin Schnitkemper --- It's completely gone here. After update to Plasma-5.19 and during the first logon I also heard a cut-off-sound as reported, but until then the logon procedure ist muted. ...and I still can't find the settings in the configuration panel where to check or change the sound. OS is Arch. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415242] BlackOnRandomLight colorscheme always gives black background
https://bugs.kde.org/show_bug.cgi?id=415242 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Switching profile does not execute the custom command
https://bugs.kde.org/show_bug.cgi?id=408217 Martin Schnitkemper changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Switching profile does not execute the custom command
https://bugs.kde.org/show_bug.cgi?id=408217 --- Comment #18 from Martin Schnitkemper --- (In reply to Wolfgang Bauer from comment #14) > Maybe a problem with the color scheme? > Might be bug#415242... Yes, it is as you described. After I changed the background to a fixed color, all is visible for me. Hence, it is not a connection problem, it was just the black on black that confused me. For a workaround I will keep these settings, or try to re-compile using the given patch. Sorry for the noise, and thanks for your advice. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Switching profile does not execute the custom command
https://bugs.kde.org/show_bug.cgi?id=408217 --- Comment #13 from Martin Schnitkemper --- I am not sure if it is the same problem: since version 19.12.0 I am no longer able to connect to a remote host, using another profile. For example: I have a profile and in the settings I set a commend "ssh root@host". Until version 19.08.3 I got then a new tab and connection to the host, i. e. after hitting File --> New Tab --> . Now in version 19.12.0 I get only a blank, black screen, neither a prompt or a flasing cursor; nothing. If I downgrade to version 19.08.3 it works again. Other commands like "su -" for a root-session are working, and also if I issue a "ssh root@host" on a prompt of a existing session, but can't connect to the host while switching to another profile. Platform are the Archlinux packages. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Switching profile does not execute the custom command
https://bugs.kde.org/show_bug.cgi?id=408217 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390781] KMail is blank!
https://bugs.kde.org/show_bug.cgi?id=390781 --- Comment #2 from Martin Schnitkemper --- Why has the state changed to "RESOLVED"? It's still not resolved, it happen to me every few days that kmail starts with a blank screen and no contents. After closing, there still remains a process named "kmail" and I have to kill it, before I can start starting a next kmail-session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405548] Dark breeze: invalid tooltip/widget colors with compositing enabled
https://bugs.kde.org/show_bug.cgi?id=405548 --- Comment #13 from Martin Schnitkemper --- Package has been rebuilt on Arch as plasma-framework-5.56.1-4 with the lastest patches included, and it seems that the tootips working for me now with dark background and compositing enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405548] Dark breeze: invalid tooltip/widget colors with compositing enabled
https://bugs.kde.org/show_bug.cgi?id=405548 Martin Schnitkemper changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #7 from Martin Schnitkemper --- Almost fixed on Arch with latest package plasma-framework release 5.56.1-3, but tooltips have still a light gray background while the compositor is actve; with a disabled compositor it has a dark background as expected. Can be easy verfied by switching the compositor on and off using Alt+Shift+F12. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394208] color clips and project monitor color
https://bugs.kde.org/show_bug.cgi?id=394208 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #2 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- I discovered the same problem today. Since I use this function frequently I am sure that it is new in version 18.04.1. The workaround to set the quality to "None" is not a real solution, because after rendering there remains still a white frame at the beginning, resulting in a visible short white flash in the movie. The function is currently unusable. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390811] Settings on folder pane columns are not preserved
https://bugs.kde.org/show_bug.cgi?id=390811 --- Comment #2 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- Yes: Qt 5.10.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) on "xcb" Interesting behaviour: if I widen the columns until none of the unwanted columns are visible and I unchecked the three boxes, then on next (and overnext) start the status kept unchecked. I can check and uncheck every box, and they keep their state. Once I narrow the foldername column until the horizontal scrollbar disappears, it's still OK, if I check one box again, like "unread", then on next start all three boxes are checked again and the columns are visible. For a first workaround it should be a solution for me to widen the filename column until the other columns are no longer visible, then it seems to keep the state after switch off the unwanted columns. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390811] New: Settings on folder pane columns are not preserved
https://bugs.kde.org/show_bug.cgi?id=390811 Bug ID: 390811 Summary: Settings on folder pane columns are not preserved Product: kmail2 Version: 5.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: martin.schnitkem...@nexgo.de Target Milestone: --- After latest update, the settings of the folder pane are no longer preserved; all values of visible columns are always set. If I uncheck these boxes it is only valid for thge current and next session. Then, all boxes are checked and all columns are visible again. It seems that is belong to a setting in kmail2rc: if I delete the value "HeaderState" in section "[CollectionFolderView]" (or even the whole section), the columns are not visible on the next start, but at the overnext start shows again all unwanted columns (unread, summary and size). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390781] KMail is blank!
https://bugs.kde.org/show_bug.cgi?id=390781 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #1 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- I can confirm this bad behaviour, it happen time by time but could not find out yet the reason, or how to reproduce it. The only workaround so far I know is to restart the akonadi-server in those cases (issue a "akonadictl restart" on console), but it is annoying anyways. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390806] New: kmail sleeping after opening an attachment
https://bugs.kde.org/show_bug.cgi?id=390806
Bug ID: 390806
Summary: kmail sleeping after opening an attachment
Product: kmail2
Version: 5.7.2
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: martin.schnitkem...@nexgo.de
Target Milestone: ---
After opening an attachment, kmail does not remove its process on exit. It is
not possible to launch kmail again, unless I kill the previous process. In
fact, a second process is starting but kmail does not appear.
If launching kmail on console I get these messages after opening a PDF:
| command= "okular %U" args= ("okular %U",
"file:///tmp/messageviewer_attachment_JpSXKU/RE1258538069258.pdf")
| EXEC "/usr/bin/okular
/tmp/messageviewer_attachment_JpSXKU/RE1258538069258.pdf"
| EXEC done
| sleeping...
This happen with every kind of attachment.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 387073] Cannot create New Folder
https://bugs.kde.org/show_bug.cgi?id=387073 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC|martin.schnitkemper@nexgo.d | |e | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 --- Comment #24 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- (In reply to Christoph Feck from comment #22) > Martin, please report your issue as a new ticket, ideally providing the SMTP > conversation log showing the error. Of course, if someone can guide me how to get a SMTP log out of kmail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #21 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- This problem is not limited to the SSL or TLS encryption, it still does not work with outgoing mails and attachments, regardless if encryption is active or not. Latest ksmtp is installed, but does not solve the problem. I still get a server error, and no progress bar while sending, but the mail will be send in a background process and delivered to the receipient, but remains in the outgoing mail folder of kmail as unsent due to an error. OS is Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 387073] Cannot create New Folder
https://bugs.kde.org/show_bug.cgi?id=387073 --- Comment #11 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- Creating a new folder on the desktop is now possible afer applying the patch, but I still run into the same malformed URL message if I try to create a new file, or a link on the desktop. Should I file a new bug report for this issue, or you prefer to re-open this one? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 387073] Cannot create New Folder
https://bugs.kde.org/show_bug.cgi?id=387073 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #5 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- It's not really fixed, since I have the same problem while trying to create any item (not limited on folders) on the KDE-Desktop, such as a new file, folder or link. Actions are refused with the comment of invalid url. In Dolphin it works after applying the latest patch, but not on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 --- Comment #25 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- After latest system update it works for me again, I can scroll in both panels with normal speed. I don't know which of the components exactly solved the problem since I got a whole bunch of updates of KDE Plasma 5.8.5 and the KDE Applications 16.12. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 373918] Mispelled folders after "Import File Listing"
https://bugs.kde.org/show_bug.cgi?id=373918 --- Comment #2 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- Hi Robby, thanks for your fast response. After applying the patch and rebuild the package, the import works for me, all folders are displayed again correct now. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 373918] New: Mispelled folders after "Import File Listing"
https://bugs.kde.org/show_bug.cgi?id=373918
Bug ID: 373918
Summary: Mispelled folders after "Import File Listing"
Product: tellico
Version: 3.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: ro...@periapsis.org
Reporter: martin.schnitkem...@nexgo.de
Target Milestone: ---
After upgrading from version 2.3.11 to 3.0 the name of folders are truncating
by the first two digits using the "Import File Listing". The root of a volume
is now representing by a single dot (".") instead of an empty entry as before.
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 373915] New: Notification Icon no longer visible
https://bugs.kde.org/show_bug.cgi?id=373915 Bug ID: 373915 Summary: Notification Icon no longer visible Product: kmail2 Version: 5.3.44 pre (QtWebEngine) Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: martin.schnitkem...@nexgo.de Target Milestone: --- After the latest update to 16.12.0 (KMail reports version 5.4.0) the notification icon is no longer visible in the notification area. There is an empty gap and if I hover over it with the mouse, the letter symbol fades in, and after leaving the mouse the symbol fades off. If the symbol is visible, there is also no longer a counter with the number of unread mails. That is rather annoying since you get no visible information of new and unread mails, if you were absent from your desk for a moment. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #21 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- It's not solved for me. I have also not installed xf86-input-libinput on my desktop system but scrolling in the left folder- or places panel in dolphin is still unusable slow, in the main windows its OK. It seems new to me after upgrading to 16.08. Distribution is Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356862] KMail crashes on exit
https://bugs.kde.org/show_bug.cgi?id=356862 --- Comment #6 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- Has already been patched & fixed for Arch users. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356862] KMail crashes on exit
https://bugs.kde.org/show_bug.cgi?id=356862 Martin Schnitkemper <martin.schnitkem...@nexgo.de> changed: What|Removed |Added CC||martin.schnitkemper@nexgo.d ||e --- Comment #4 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- KMail crashed here on exit, too. After I applied the patches from https://quickgit.kde.org/?p=kdepimlibs.git=commit=c6bf33a9018587e96a350bfd0b2bffde1859db27 and re-compiled the kdepimlibs I could exit KMail without a crash. Seems that it works for me (Arch Linux) -- You are receiving this mail because: You are watching all bug changes.
