[dolphin] [Bug 488188] New: Dolphin Forgets SMB Network Shared Files
https://bugs.kde.org/show_bug.cgi?id=488188 Bug ID: 488188 Summary: Dolphin Forgets SMB Network Shared Files Classification: Applications Product: dolphin Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: myccl...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Files on network SMB shares "disappear" when displayed in dolphin. Files are present and can be seen on the network machine. A refresh of the dolphin tab shows the files again. Sometimes they "disappear" again and require another refresh. So far I have only seen this with SMB shares and only with media files. STEPS TO REPRODUCE 1. Open SMB Share containing media files. 2. Play the media file on the remote server or interact with it in anyway. 3. File "disappears" from dolphin, a refresh of the tab makes the file visible again. OBSERVED RESULT Files "disappear" and a refresh is required. EXPECTED RESULT The files do not disappear. Dolphin used to not have this issue. SOFTWARE/OS VERSIONS Windows: W10 22H2 macOS: N/A Linux/KDE Plasma: Fedora 40 KDE KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This issue started happening on the upgrade to Fedora 40. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 468418] Workspace Activities Not Working without First Restarting plasmashell
https://bugs.kde.org/show_bug.cgi?id=468418 --- Comment #3 from Myc --- There is nothing special or specific about the configuration. The two desktop activities and three displays. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 468418] Workspace Activities Not Working without First Restarting plasmashell
https://bugs.kde.org/show_bug.cgi?id=468418 Myc changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Myc --- The workaround is no longer working, is this going to even get addressed? Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.12-100.fc37.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 468418] New: Workspace Activities Not Working without First Restarting plasmashell
https://bugs.kde.org/show_bug.cgi?id=468418 Bug ID: 468418 Summary: Workspace Activities Not Working without First Restarting plasmashell Classification: Plasma Product: kactivitymanagerd Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: myccl...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I have two activities I use. One is for all my main computing, the other reduces power usage for night time idle. Blank black background, monitors are turned off after one minute, etc... I have to use this workaround if I want activities to work as they are supposed to. Every time I boot I wait until the machine has finished booting, HDD access light is not blinking anymore. Then I run from a terminal; killall plasmashell wait a couple seconds then nohup kstart5 plasmashell >/dev/null 2>&1 & Once I see my taskbar has popped back up I scroll on my desktop to ensure activities rolls between the two activities I have configured. After completing this I can then use my computer like normal and when I'm going to bed, I just switch activities via meta+tab. My displays shut off as configured in the second activity and all is good. If I vary in this workaround at all, I have to reboot, killing plasmashell will not fix it. I have tried deleting and remaking the activities, from both this user profile and new ones and the result is always the same. It works properly once and then after that I have to use my workaround. STEPS TO REPRODUCE 1. Boot PC 2. Don't kill plasmashell 3. Activities don't work. OBSERVED RESULT Activities do not work, you see the switcher bar appear but nothing happens. No activity settings are applied. The desktop is not changed. All windows remain where they are. EXPECTED RESULT Activities should work as expected without having to first kill plasmashell, then start it again, then roll through the activities. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500T CPU @ 2.50GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: LENOVO Product Name: 10FM001UUS System Version: ThinkCentre M900 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #16 from Myc --- This has required the workaround 15 times today. It's been over three years, is a fix ever going to be implemented? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466428] Power Settings Not Applied/Enforced
https://bugs.kde.org/show_bug.cgi?id=466428 --- Comment #2 from Myc --- The problem has been intermittent to about one in ten boots power setting work as intended. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466428] Power Settings Not Applied/Enforced
https://bugs.kde.org/show_bug.cgi?id=466428 --- Comment #1 from Myc --- Updated to 5.27.1 and problem still exists. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.13-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500T CPU @ 2.50GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: LENOVO Product Name: 10FM001UUS System Version: ThinkCentre M900 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466428] Power Settings Not Applied/Enforced
https://bugs.kde.org/show_bug.cgi?id=466428 Myc changed: What|Removed |Added Version|5.27.0 |5.27.1 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466428] New: Power Settings Not Applied/Enforced
https://bugs.kde.org/show_bug.cgi?id=466428 Bug ID: 466428 Summary: Power Settings Not Applied/Enforced Classification: Plasma Product: Powerdevil Version: 5.27.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: myccl...@outlook.com CC: m...@ratijas.tk Target Milestone: --- SUMMARY *** Power settings are not applied. This is both the general power settings as well as activity specific settings. Screens do not timeout, machine will never go to sleep, ect... *** STEPS TO REPRODUCE 1. Create user and apply their power settings. 2. Log out and back in. 3. Settings are no longer working. OBSERVED RESULT The settings only work for the first session for a user, after that they do not work. EXPECTED RESULT Power settings always work as expected. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.13-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500T CPU @ 2.50GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: LENOVO Product Name: 10FM001UUS System Version: ThinkCentre M900 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #15 from Myc --- (In reply to Andrey Babkin from comment #13) > UPD: For my situation I think I've found the root cause of the issue - most > likely this was happening due to plasma integration plugin installed in > chrome > (https://chrome.google.com/webstore/detail/plasma-integration/ > cimiefiiaegbelhefglklhhakcgmhkai). After I removed this plugin, the > play/pause button on my keyboard started to work. Then in some time I > reinstalled this plugin and as it was suggested in one of the comments on > chrome marketplace, I disabled chrome's hardware media handling > (chrome://flags/#hardware-media-key-handling). After this done I have never > encountered any issues with media controls . I hope this helps. That is interesting that it could be induced by that as well. I've found it happens most when I have a video playing on my HTPC and I play a quick video on my fedora machine. I guess it gets confused and then just stops working. I use Firefox and do not have the plasma integration installed. It was causing a host of other problems so I removed it a while ago. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #12 from Myc --- This is happening multiple times a day. It is highly annoying to have to stop what I'm doing to do the work around every couple hours. I'm on 37 now and it's still a problem. Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-200.fc37.x86_64 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 Myc changed: What|Removed |Added CC||myccl...@outlook.com --- Comment #6 from Myc --- I have also encountered this issue on KDE Fedora . I use a dedicated media keys keyboard and wondered if something was wrong with it until I tried the workaround of disabling the applet and enabling it again. I use KDEConnect and control media playing on a HTPC from my kde desktop as well as strawberry to play music, lastly with the occasional video on the local machine. Operating System: Fedora Linux 35 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454133] New: Crash on Copy Local Files to SMB1 Share
https://bugs.kde.org/show_bug.cgi?id=454133 Bug ID: 454133 Summary: Crash on Copy Local Files to SMB1 Share Product: dolphin Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: myccl...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.12.2) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.17.8-200.fc35.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: 1. Selected about 100 local images and copy them to the clipboard. 2. Navigated to the SMB1 share and paste files into share. 3. Files start copying. 4. Dolphin crashes. I then reopen Dolphin and copy the files again to the same share, this time overwriting duplicates and Dolphin does not crash. Other instances I can copy the files without Dolphin crashing. This behavior has further cemented that one should never move files but copy then delete the original once a succesful copy completes. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f421ddff52b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #5 0x7f421e99f432 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #6 0x7f421ddff7d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f421e9e32db in QWidget::setParent(QWidget*, QFlags) () from /lib64/libQt5Widgets.so.5 #8 0x7f421e9e377e in QWidgetPrivate::init(QWidget*, QFlags) () from /lib64/libQt5Widgets.so.5 #9 0x7f421ebae993 in QDialog::QDialog(QWidget*, QFlags) () from /lib64/libQt5Widgets.so.5 #10 0x7f421f9ddfa1 in KIO::RenameDialog::RenameDialog(QWidget*, QString const&, QUrl const&, QUrl const&, QFlags, unsigned long long, unsigned long long, QDateTime const&, QDateTime const&, QDateTime const&, QDateTime const&) () from /lib64/libKF5KIOWidgets.so.5 #11 0x7f421f9f0e6f in KIO::WidgetsAskUserActionHandler::askUserRename(KJob*, QString const&, QUrl const&, QUrl const&, QFlags, unsigned long long, unsigned long long, QDateTime const&, QDateTime const&, QDateTime const&, QDateTime const&) () from /lib64/libKF5KIOWidgets.so.5 #12 0x7f421f76ae4c in KIO::CopyJobPrivate::slotResultErrorCopyingFiles(KJob*) () from /lib64/libKF5KIOCore.so.5 #13 0x7f421de333e9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #14 0x7f421efcae10 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #15 0x7f421efcf19b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #16 0x7f421de333e9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #17 0x7f421f78b05d in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #18 0x7f421f7841ed in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #19 0x7f421f787c92 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #20 0x7f421de333e9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #21 0x7f421de29f49 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7f421e99f443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7f421ddff7d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x7f421de02d46 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #25 0x7f421de51117 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #26 0x7f421bb730af in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x7f421bbc8308 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #28 0x7f421bb708a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x7f421de50bb8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #30 0x7f421ddfe1e2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #31 0x7f421de06724 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #32 0x55d0b23247c9 in main () [Inferior 1 (process 34425) detached] Possible duplicates by query: bug 453858, bug 453774, bug 453582, bug 453174, bug 452686. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398646] New: Moving files from Fat32 to NTFS partition, permission error crash.
https://bugs.kde.org/show_bug.cgi?id=398646 Bug ID: 398646 Summary: Moving files from Fat32 to NTFS partition, permission error crash. Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: myccl...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: Moving files from a FAT32 formated USB to an internal NTFS drive. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d73caa6c0 (LWP 20315))] Thread 4 (Thread 0x7f2d4a923700 (LWP 20319)): #0 0x7f2d664c6cf9 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2d66480b81 in g_main_context_query () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2d664813b7 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2d6648154c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2d6d73e90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2d6d6e39ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2d6d50222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2d6d50716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2d685f26db in start_thread (arg=0x7f2d4a923700) at pthread_create.c:463 #9 0x7f2d7353788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2d562cd700 (LWP 20318)): #0 0x7f2d735260b4 in __GI___libc_read (fd=7, buf=0x7f2d562ccb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f2d664c5980 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2d66480f27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2d664813e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2d6648154c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2d6d73e90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2d6d6e39ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2d6d50222a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2d6dbbbd45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f2d6d50716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2d685f26db in start_thread (arg=0x7f2d562cd700) at pthread_create.c:463 #11 0x7f2d7353788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2d5cb6d700 (LWP 20317)): #0 0x7f2d7352abf9 in __GI___poll (fds=0x7f2d5cb6cca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2d65dc2747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2d65dc436a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2d5f91a2a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f2d6d50716d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2d685f26db in start_thread (arg=0x7f2d5cb6d700) at pthread_create.c:463 #6 0x7f2d7353788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2d73caa6c0 (LWP 20315)): [KCrash Handler] #6 0x7f2d6d6e8d41 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2d71a842f9 in KIO::FileCopyJob::slotResult(KJob*) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #8 0x7f2d6d7146cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2d6f096fdc in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #10 0x7f2d6f097b11 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7f2d71a93628 in KIO::SimpleJob::slotFinished() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x7f2d71a919db in KIO::SimpleJob::slotError(int, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7f2d6d7146cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2d71a69186 in KIO::SlaveInterface::error(int, QString const&) () fr
