[kde] [Bug 486349] .svg file causes huge memory leak if preview and SVG thumbnailer are activated in Dolphin
https://bugs.kde.org/show_bug.cgi?id=486349 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net --- Comment #4 from Till Seifert --- I have a similar, maybe same issue with current neon: * when opening in image in a folder with many simple but largish (dimensionwise; 5000x5000px viewbox) SVG files. * Gwenview will display the image and start loading previews of the other images in the folder in bar at the bottom * kioworker process appears and consumes memory of ~2GB/second. * it gets killed by oomkiller when it hits ~50GB * some thumbnails appear in gwenview, but not all i can provide a test folder if needed to repro -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 Till Seifert changed: What|Removed |Added Attachment #169401|0 |1 is obsolete|| --- Comment #56 from Till Seifert --- Created attachment 169445 --> https://bugs.kde.org/attachment.cgi?id=169445=edit gdb bt full Dolphin 24.02.2 KF 6.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #55 from Till Seifert --- > You should be able to use `coredumpctl -1 info dolphin` to get the trace > without having to reproduce the issue again. i'm not familiar enough with gdb to convert those into symbolized traces. and for some reason the crash handler now stopped outputting the gdb output to the terminal, it just stop after the crash:/ i ran dolphin with gdb manually, and this way also the auto-download of symbols works\o/. it logged a 'bt full' and will attach it -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 Till Seifert changed: What|Removed |Added Attachment #169397|0 |1 is obsolete|| --- Comment #53 from Till Seifert --- Created attachment 169401 --> https://bugs.kde.org/attachment.cgi?id=169401=edit Terminal output Dolphin 24.02.2 KF 6.1 with kf6-kio-dbgsym and dolphin-dgbsym -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #52 from Till Seifert --- > Please enabled `Debuginfod` so that the logs/and or crashes trace can help. > You might be using TW that does not support debuginfod unfortunately. > The current logs are not informative. I actually have it activates in .gdbinit, it seem to be ignored. maybe related: https://bugs.kde.org/show_bug.cgi?id=484974 With Neon 22.04, can i install the need dbgsym packages manually? I installed dolphin-dbgsym and kf6-kio-dbgsym , but the trace looks not much different when i repro, but it will attach it -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #50 from Till Seifert --- Created attachment 169397 --> https://bugs.kde.org/attachment.cgi?id=169397=edit Terminal output Dolphin 24.02.2 KF 6.1 Still happens with: Dolphin: 24.02.2 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.5-060605-generic (64-bit) Graphics Platform: X11 Log attached -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485731] Auto-Convert Windows SMB paths to smb:// format
https://bugs.kde.org/show_bug.cgi?id=485731 Till Seifert changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Till Seifert --- You're right, it works like that now. I must have missed it, or Frameworks 6.1 was needed. Thanks:) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net --- Comment #32 from Till Seifert --- also affected with 6.0.4. i can fix it by adjusting the height of my panel by 1px. then current *and* future notification appear at the correct place. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485914] New: Dolphin crash on session restore
https://bugs.kde.org/show_bug.cgi?id=485914 Bug ID: 485914 Summary: Dolphin crash on session restore Classification: Applications Product: dolphin Version: 24.02.2 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: till.seif...@spamfence.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (24.02.2) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.4.3-x64v3-xanmod1 x86_64 Windowing System: X11 Distribution: KDE neon 6.0 DrKonqi: 6.0.4 [KCrashBackend] -- Information about the crash: On every login, one Dolphin window crashes and is not restored. the others are fine, including all tabs. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139644127947456) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139644127947456) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139644127947456, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f0173842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f01738287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f01744fdb6e in qAbort () at ./src/corelib/global/qglobal.cpp:161 #10 0x7f01744f820a in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2025 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7ffc92bee020) at ./src/corelib/global/qlogging.cpp:374 #12 0x7f01744fe511 in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:889 #13 0x7f01744c2ac2 in qt_assert (assertion=assertion@entry=0x7f0176499660 "it != dirItem->lstItems.end()", file=file@entry=0x7f0176499642 "./src/core/kcoredirlister_p.h", line=line@entry=326) at ./src/corelib/global/qassert.cpp:68 #14 0x7f017637522a in KCoreDirListerCache::reinsert (this=, item=..., oldUrl=...) at ./src/core/kcoredirlister_p.h:320 #15 KCoreDirListerCache::reinsert (this=, item=..., oldUrl=...) at ./src/core/kcoredirlister_p.h:320 #16 0x7f01764276eb in KCoreDirListerCache::processPendingUpdates (this=0x55ede96734d0) at ./src/core/kcoredirlister.cpp:2011 #17 0x7f017642c40a in KCoreDirListerCache::slotResult (this=0x55ede96734d0, j=) at ./src/core/kcoredirlister.cpp:1322 #18 0x7f017446355e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:469 #19 doActivate (sender=0x55ede99fef00, signal_index=6, argv=0x7ffc92bee4b0) at ./src/corelib/kernel/qobject.cpp:4078 #20 0x7f0175e0ea80 in KJob::result (this=this@entry=0x55ede99fef00, _t1=, _t1@entry=0x55ede99fef00, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF6CoreAddons_autogen/include/moc_kjob.cpp:622 #21 0x7f0175e1285b in KJob::finishJob (this=0x55ede99fef00, emitResult=) at ./src/lib/jobs/kjob.cpp:98 #22 0x7f017446355e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:469 #23 doActivate (sender=0x55edea8516e0, signal_index=7, argv=0x7ffc92bee578) at ./src/corelib/kernel/qobject.cpp:4078 #24 0x7f017644b63d in KIO::WorkerInterface::finished (this=0x55edea8516e0) at ./obj-x86_64-linux-gnu/src/core/KF6KIOCore_autogen/include/moc_workerinterface_p.cpp:525 #25 KIO::WorkerInterface::dispatch (this=0x55edea8516e0, _cmd=, rawdata=...) at ./src/core/workerinterface.cpp:129 #26 0x7f01764445e3 in KIO::WorkerInterface::dispatch (this=0x55edea8516e0) at ./src/core/workerinterface.cpp:60 #27 0x7f017644114a in KIO::Worker::gotInput (this=0x55edea8516e0) at ./src/core/worker.cpp:263 #28 0x7f017446355e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:469 #29 doActivate (sender=0x55ede9ba9d20, signal_index=3, argv=0x7ffc92bee8f8) at ./src/corelib/kernel/qobject.cpp:4078 #30 0x7f01743fa272 in QObject::event (this=0x55ede9ba9d20, e=0x55edeac782e0) at ./src/corelib/kernel/qobject.cpp:1446 #31 0x7f017560992b in QApplicationPrivate::notify_helper (this=, receiver=0x55ede9ba9d20, e=0x55edeac782e0) at ./src/widgets/kernel/qapplication.cpp:3287 #32 0x7f01744a1c38 in QCoreApplication::notifyInternal2 (receiver=0x55ede9ba9d20, event=event@entry=0x55edeac782e0) at ./src/corelib/kernel/qcoreapplication.cpp:1134 #33 0x7f01744a1c7d in QCoreApplication::sendEvent (receiver=, event=event@entry=0x55edeac782e0) at ./src/corelib/kernel/qcoreapplication.cpp:1575 #34 0x7f01744a23e0 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55ede95cd5d0) at
[dolphin] [Bug 485731] New: Auto-Convert Windows SMB paths to smb:// format
https://bugs.kde.org/show_bug.cgi?id=485731 Bug ID: 485731 Summary: Auto-Convert Windows SMB paths to smb:// format Classification: Applications Product: dolphin Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: till.seif...@spamfence.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Enhance Dolphin to automatically convert Windows SMB paths to smb:// format when pasted into the address bar. STEPS TO REPRODUCE 1. Copy a Windows SMB path (e.g., \\Server\Share\Path\to\file). 2. Open Dolphin and paste the copied path into the address bar. 3. Press Enter. OBSERVED RESULT Dolphin does not recognize the pasted Windows SMB path format and fails to navigate to the desired directory or file. EXPECTED RESULT Dolphin should automatically detect and convert the Windows SMB path format to the appropriate smb:// format (e.g., smb://Server/Share/Path/to/file) and navigate to the directory or file. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION This feature would significantly enhance the interoperability between Windows and Linux environments, particularly in mixed-OS settings where paths are often shared between users on different systems. It would streamline workflows and reduce the manual conversion steps currently required. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #31 from Till Seifert --- (In reply to Akseli Lahtinen from comment #30) > I unfortunately can't reproduce the issue on Plasma 6. I tried in a Neon Unstable VM right now and i works without crash. The redirect to the smb-URL with `username@` also does not happen, it just uses the saved or entered username/password without changing the URL it seems -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #29 from Till Seifert --- It does _not_ crash if i enter smb://n...@fritz.box/FRITZ.NAS/ indeed. (FRITZ.NAS is the only share on the server) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #26 from Till Seifert --- > So it would be: smb://n...@fritz.box Yes when i give the username in the URL in the location bar or CLI parameter it open correctly. The samba share is the default share from my Fritz!Box 6660 Router, so i can not configure it or even see its config. It's a pretty common device in Germany. But i will try to repro with a samba installation. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #23 from Till Seifert --- Created attachment 163659 --> https://bugs.kde.org/attachment.cgi?id=163659=edit Terminal output if i directly put the smb-url as command line param Also happens if i directly put the smb-url as command line param -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #22 from Till Seifert --- Created attachment 163658 --> https://bugs.kde.org/attachment.cgi?id=163658=edit Terminal output when running dolphn and then opening smb://-url -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #18 from Till Seifert --- Created attachment 163654 --> https://bugs.kde.org/attachment.cgi?id=163654=edit Screen recording -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #17 from Till Seifert --- Created attachment 163653 --> https://bugs.kde.org/attachment.cgi?id=163653=edit Crash report from screen recording -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #16 from Till Seifert --- I can till repro it in Dolphin 23.08.3 KDE Frameworks Version 5.111.0 without opening any properties dialogs. I attached a screen recording and trace from the same event -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470588] Dolphin crash after login
https://bugs.kde.org/show_bug.cgi?id=470588 Till Seifert changed: What|Removed |Added Version|23.04.2 |23.08.3 --- Comment #4 from Till Seifert --- Still happens with Dolphin 23.08.3 and Frameworks 5.111.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 --- Comment #27 from Till Seifert --- (In reply to alberto.rinaudo from comment #26) > (In reply to Nate Graham from comment #7) > 100% agree with Nate, I don't think this needs new configurable settings. > The split position should reset to 50% once all windows have been closed or > "un-splitted". That would be intuitive for one desktop. If you use many it will still be very annoying. So it should then be a state per desktop, or there should be a way to turn it off. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470588] Dolphin crash after login
https://bugs.kde.org/show_bug.cgi?id=470588 Till Seifert changed: What|Removed |Added Version|23.04.1 |23.04.2 --- Comment #3 from Till Seifert --- Still happens after Frameworks updated to 5.107.0 Are there any debug symbols i can install, to make the trace more useful? I have dolphin-dbg and but i'm not sure in which (Neon) package the frameworks debug symbols are. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #8 from Till Seifert --- Still happening with 23.04.2 Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140487881624000) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140487881624000) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140487881624000, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fc5e6c42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fc5e6c287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fc5e937768b in KCoreDirListerCache::printDebug (this=) at ./src/core/kcoredirlister.cpp:2095 #10 0x7fc5e945483a in KCoreDirListerCache::slotUpdateResult (this=0x7fc5e94d7700 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, j=) at ./src/core/kcoredirlister.cpp:1734 #11 0x7fc5e76f4854 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb56c5250, r=0x7fc5e94d7700 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, this=0x55e5edbc1be0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55e5eea16140, signal_index=6, argv=0x7ffcb56c5250) at kernel/qobject.cpp:3925 #13 0x7fc5e76ed927 in QMetaObject::activate (sender=sender@entry=0x55e5eea16140, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffcb56c5250) at kernel/qobject.cpp:3985 #14 0x7fc5e8bca130 in KJob::result (this=this@entry=0x55e5eea16140, _t1=, _t1@entry=0x55e5eea16140, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #15 0x7fc5e8bcfe3b in KJob::finishJob (this=0x55e5eea16140, emitResult=) at ./src/lib/jobs/kjob.cpp:98 #16 0x7fc5e76f4854 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb56c5320, r=0x55e5eea16140, this=0x55e5ee911f00) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate (sender=0x55e5ee2a3930, signal_index=7, argv=0x7ffcb56c5320) at kernel/qobject.cpp:3925 #18 0x7fc5e76ed927 in QMetaObject::activate (sender=sender@entry=0x55e5ee2a3930, m=m@entry=0x7fc5e94d1980 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3985 #19 0x7fc5e93decd7 in KIO::SlaveInterface::finished (this=this@entry=0x55e5ee2a3930) at ./obj-x86_64-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:464 #20 0x7fc5e93e0fb3 in KIO::SlaveInterface::dispatch (this=0x55e5ee2a3930, _cmd=, rawdata=...) at ./src/core/slaveinterface.cpp:149 #21 0x7fc5e93df57d in KIO::SlaveInterface::dispatch (this=0x55e5ee2a3930) at ./src/core/slaveinterface.cpp:78 #22 0x7fc5e93e39b2 in KIO::Slave::gotInput (this=0x55e5ee2a3930) at ./src/core/slave.cpp:354 #23 0x7fc5e76f4854 in QtPrivate::QSlotObjectBase::call (a=0x7ffcb56c5570, r=0x55e5ee2a3930, this=0x55e5ed120750) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #24 doActivate (sender=0x55e5ee5b1790, signal_index=3, argv=0x7ffcb56c5570) at kernel/qobject.cpp:3925 #25 0x7fc5e76ea2fe in QObject::event (this=0x55e5ee5b1790, e=0x55e5ed1598c0) at kernel/qobject.cpp:1347 #26 0x7fc5e836c763 in QApplicationPrivate::notify_helper (this=, receiver=0x55e5ee5b1790, e=0x55e5ed1598c0) at kernel/qapplication.cpp:3640 #27 0x7fc5e76bcdda in QCoreApplication::notifyInternal2 (receiver=0x55e5ee5b1790, event=0x55e5ed1598c0) at kernel/qcoreapplication.cpp:1064 #28 0x7fc5e76bfec7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55e5ecd80ec0) at kernel/qcoreapplication.cpp:1821 #29 0x7fc5e7716c07 in postEventSourceDispatch (s=0x55e5ece7bb00) at kernel/qeventdispatcher_glib.cpp:277 #30 0x7fc5e5451d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fc5e54a7258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7fc5e544f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7fc5e7716258 in QEventDispatcherGlib::processEvents (this=0x55e5ece7c520, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #34 0x7fc5e76bb6fb in QEventLoop::exec (this=this@entry=0x7ffcb56c5980, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #35 0x7fc5e76c3c94 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #36 0x7fc5e7b36d50 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870 #37 0x7fc5e836c6d9 in QApplication::exec () at kernel/qapplication.cpp:2832 #38 0x55e5ec03db35 in main (argc=, argv=) at ./src/main.cpp:249 [Inferior 1 (process 6960) detached] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470588] Dolphin crash after login
https://bugs.kde.org/show_bug.cgi?id=470588 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470588] Dolphin crash after login
https://bugs.kde.org/show_bug.cgi?id=470588 --- Comment #1 from Till Seifert --- After a few reboots i can say it happens every time, no matter what folders i have open on logout -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470588] Dolphin crash after login
https://bugs.kde.org/show_bug.cgi?id=470588 Till Seifert changed: What|Removed |Added Summary|Dolhin crash in login |Dolphin crash after login -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470588] New: Dolhin crash in login
https://bugs.kde.org/show_bug.cgi?id=470588 Bug ID: 470588 Summary: Dolhin crash in login Classification: Applications Product: dolphin Version: 23.04.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: till.seif...@spamfence.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.1) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.0.3-x64v2-xanmod1 x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Dolphin crashed on session restore after login. I always just jet a couple of windows with my start folder, but alle folder-tab and some windows are not restored. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 QSharedDataPointer::~QSharedDataPointer (this=0x55dde33fb940, __in_chrg=) at /usr/include/c++/11/bits/atomic_base.h:385 #5 KFileItem::~KFileItem (this=0x55dde33fb940, __in_chrg=) at ./src/core/kfileitem.cpp:605 #6 0x7f01795d77d1 in QList::node_destruct (n=0x55dde33fb940, this=0x55dde2e70ed0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:479 #7 QList::erase (it=..., this=0x55dde2e70ed0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:566 #8 KCoreDirListerCache::reinsert (this=this@entry=0x7f0179656700 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, item=..., oldUrl=...) at ./src/core/kcoredirlister_p.h:289 #9 0x7f01795c715e in KCoreDirListerCache::processPendingUpdates (this=this@entry=0x7f0179656700 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>) at ./src/core/kcoredirlister.cpp:2022 #10 0x7f01795c8170 in KCoreDirListerCache::slotResult (this=0x7f0179656700 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, j=) at ./src/core/kcoredirlister.cpp:1342 #11 0x7f01778f41e4 in QtPrivate::QSlotObjectBase::call (a=0x7fff2f7891c0, r=0x7f0179656700 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, this=0x55dde2960040) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55dde297a120, signal_index=6, argv=0x7fff2f7891c0) at kernel/qobject.cpp:3923 #13 0x7f01778ed287 in QMetaObject::activate (sender=sender@entry=0x55dde297a120, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff2f7891c0) at kernel/qobject.cpp:3983 #14 0x7f0178d49150 in KJob::result (this=this@entry=0x55dde297a120, _t1=, _t1@entry=0x55dde297a120, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #15 0x7f0178d4ee3b in KJob::finishJob (this=0x55dde297a120, emitResult=) at ./src/lib/jobs/kjob.cpp:98 #16 0x7f01778f41e4 in QtPrivate::QSlotObjectBase::call (a=0x7fff2f789290, r=0x55dde297a120, this=0x55dde33dcaf0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate (sender=0x55dde2619310, signal_index=7, argv=0x7fff2f789290) at kernel/qobject.cpp:3923 #18 0x7f01778ed287 in QMetaObject::activate (sender=sender@entry=0x55dde2619310, m=m@entry=0x7f0179650980 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3983 #19 0x7f017955dcd7 in KIO::SlaveInterface::finished (this=this@entry=0x55dde2619310) at ./obj-x86_64-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:464 #20 0x7f017955ffb3 in KIO::SlaveInterface::dispatch (this=0x55dde2619310, _cmd=, rawdata=...) at ./src/core/slaveinterface.cpp:149 #21 0x7f017955e57d in KIO::SlaveInterface::dispatch (this=0x55dde2619310) at ./src/core/slaveinterface.cpp:78 #22 0x7f01795629b2 in KIO::Slave::gotInput (this=0x55dde2619310) at ./src/core/slave.cpp:354 #23 0x7f01778f41e4 in QtPrivate::QSlotObjectBase::call (a=0x7fff2f7894e0, r=0x55dde2619310, this=0x55dde33dc3c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #24 doActivate (sender=0x55dde260e520, signal_index=3, argv=0x7fff2f7894e0) at kernel/qobject.cpp:3923 #25 0x7f01778e9bee in QObject::event (this=0x55dde260e520, e=0x55dde29df0c0) at kernel/qobject.cpp:1347 #26 0x7f017856c793 in QApplicationPrivate::notify_helper (this=, receiver=0x55dde260e520, e=0x55dde29df0c0) at kernel/qapplication.cpp:3640 #27 0x7f01778bc18a in QCoreApplication::notifyInternal2 (receiver=0x55dde260e520, event=0x55dde29df0c0) at kernel/qcoreapplication.cpp:1064 #28 0x7f01778bf277 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55dde25e8ec0) at kernel/qcoreapplication.cpp:1821 #29 0x7f0177916597 in postEventSourceDispatch (s=0x55dde26e3a40) at kernel/qeventdispatcher_glib.cpp:277 #30
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 --- Comment #14 from Till Seifert --- > if you open the > tiling interface (Meta+T) and delete all the tiles, all of the > quick-snapping features behave like they used to in pre-5.27. Not for me ( kwin 5.27.5 ). There were actuyll no tiles in the Meta-T view in the first place after updating to 5.27. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Resizing quick tiled windows affects quick tiling behavior
https://bugs.kde.org/show_bug.cgi?id=465937 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net --- Comment #5 from Till Seifert --- Is there any way to disable this. Like not making the window a 'tiled' window' and retain the ability to position windows to the left and right half of the screen? -- 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 #8 from Till Seifert --- for me it doesn't happen anymore with 22.08.3. I'm not sure with which version it was fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417828] Spawned Child processes get grouped with parent
https://bugs.kde.org/show_bug.cgi?id=417828 --- Comment #5 from Till Seifert --- I now switched from the Snap-version of IDEA to one installed in /opt. The does *not* appear now. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418993] Dolphin crahes when i open sync folder from MEGASync Client
https://bugs.kde.org/show_bug.cgi?id=418993 --- Comment #4 from Till Seifert --- (In reply to Justin Zobel from comment #3) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? I just tried it with 22.08.1 and the current MEGA client and it did not crash! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442645] Plasma freezes on receiving call from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=442645 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net Version|unspecified |22.04.2 --- Comment #8 from Till Seifert --- Current version still affected. The workaround is good, but the call→pause music combo is like the main thing of these plugins, and it works great (the music get's paused, just plasma too:)) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409259] Icons-only Task Manager hangs when switch desktops with pinned apps
https://bugs.kde.org/show_bug.cgi?id=409259 --- Comment #6 from Till Seifert --- > Please try with a newer version(plasma 5.23.5) and if this is not an issue > any more let us know. There is still lag and quite a CPU spike of the plasmashell-process, but even with some pinned Apps it maybe 100ms. So it is not really annoying any more. But i have since switched to a faster CPU (2012 Athlon → 2020 Ryzen), so that skews it maybe. So from a user perspective it would be ok to close the bug. But if devs want more info what might cause that, i would like to contribute to that. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 371278] Dolphin crashed in QList::detach() when opening smb location
https://bugs.kde.org/show_bug.cgi?id=371278 --- Comment #29 from Till Seifert --- Created attachment 145394 --> https://bugs.kde.org/attachment.cgi?id=145394=edit Output of ' `KDE_FORK_SLAVES=1 QT_LOGGING_RULES="kf5.kio.*=true;kio_smb=true" dolphin --new-window 'smb://'` > Are you quite certain that nothing else crashed at the same time? Yes only Dolphin. No other programs disappear, no other crash-notifictions appear. > What's also weird is that your debug output talks about expecting > n...@fritz.box but we never inject user names, smb://fritz.box would get > authenticated completely behind the scenes, so the front-end code shouldn't > even know about it being nas@. > > The various outputs I asked for in > https://bugs.kde.org/show_bug.cgi?id=371278#c24 still would be useful as > well. `kwriteconfig5 --file kioslaverc --group SMB --key DebugLevel 10` outputs nothing. The output of ' `KDE_FORK_SLAVES=1 QT_LOGGING_RULES="kf5.kio.*=true;kio_smb=true" dolphin --new-window 'smb://'`' is attached -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] Pointer speed resets after restart
https://bugs.kde.org/show_bug.cgi?id=435113 --- Comment #8 from Till Seifert --- Also affected for me: Betriebssystem: KDE neon 5.23 KDE-Plasma-Version: 5.23.3 KDE-Frameworks-Version: 5.88.0 Qt-Version: 5.15.3 Kernel-Version: 5.10.0-051000-generic (64-bit) Grafik-Plattform: X11 It started some days ago, but it might be some versions back because do not reboot regularly. I'm on Neon User edition and apply any updates immediately. For me the mouse pointer is much slower than needed, and i also just touch the settings (max speed) and it's ok again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] Pointer speed resets after restart
https://bugs.kde.org/show_bug.cgi?id=435113 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 371278] Dolphin crashed in QList::detach() when opening smb location
https://bugs.kde.org/show_bug.cgi?id=371278
Till Seifert changed:
What|Removed |Added
CC||till.seif...@spamfence.net
--- Comment #27 from Till Seifert ---
I can repro this bug with current KF and can provide infos.
If can open 'smb://fritz.box/FRITZ/' while a user ('nas') and PW is stored in
KWallet for this URL, Dolphin crashes and prints:
kf.kio.core: Internal error: itemsInUse did not contain
QUrl("smb://n...@fritz.box/")
kf.kio.core: Fatal Error: HUH? Lister KFileItemModelDirLister(0x555d856033c0)
is supposed to be listing, but has no job!
If is open 'smb://n...@fritz.box/' it does not crash and works.
The crash is _not_ reproducible, if Dolphin already listed the share
successfully in the current session. As is if I open smb://n...@fritz.box and
_then_ smb://fritz.box, it works. And i mean same KDE session, not same Dolphin
session.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 444619] New: Dolphin crash when opening SMB-Url from Fritzbox
https://bugs.kde.org/show_bug.cgi?id=444619 Bug ID: 444619 Summary: Dolphin crash when opening SMB-Url from Fritzbox Product: dolphin Version: 21.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: till.seif...@spamfence.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.08.2) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.10.0-051000-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: when i open smb://fritz.box, which maps to the network share of a FritzBox with FRITZ!OS: 07.20, Dolphin very briefly shows the login-dialog for the share a then crashes. This was working up until ~4 weeks ago. A normal CIFS-mount works, but snice a recent yupdate of the FrirtzOS SMB1.0 no longer works, where previosly *only* SMB1.0 worked (an Dolphin could no open the share at all). So the Fritzbox seems to have moved from SMB1.0 to a newer version recently. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [New LWP 145975] [New LWP 145976] [New LWP 145977] [New LWP 145978] [New LWP 145979] [New LWP 145980] [New LWP 145981] [New LWP 145982] [New LWP 145983] [New LWP 145984] [New LWP 145985] [New LWP 145986] [New LWP 145987] [New LWP 145988] [New LWP 145989] [New LWP 145990] [New LWP 145991] [New LWP 145992] [New LWP 145993] [New LWP 145994] [New LWP 145995] [New LWP 146000] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f6f9fa67aff in __GI___poll (fds=0x7ffe1c51f9f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f6f9b0239c0 (LWP 145974))] Thread 23 (Thread 0x7f6f2effd700 (LWP 146000)): #0 0x7f6f9fa67aff in __GI___poll (fds=0x7f6f10005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6f9dafa36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6f9dafa4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6fa003561b in QEventDispatcherGlib::processEvents (this=0x7f6f1b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f6f9ffd98ab in QEventLoop::exec (this=this@entry=0x7f6f2effcbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f6f9fdf32c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f6f9fdf445c in QThreadPrivate::start (arg=0x558e59d51730) at thread/qthread_unix.cpp:329 #7 0x7f6f9e578609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f6f9fa74293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f6f4d7fa700 (LWP 145995)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x558e5a1ff890) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e5a1ff840, cond=0x558e5a1ff868) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e5a1ff868, mutex=0x558e5a1ff840) at pthread_cond_wait.c:638 #3 0x7f6f913dc77b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f6f913dc37b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f6f9e578609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6f9fa74293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f6f4dffb700 (LWP 145994)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x558e5a1ff890) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e5a1ff840, cond=0x558e5a1ff868) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e5a1ff868, mutex=0x558e5a1ff840) at pthread_cond_wait.c:638 #3 0x7f6f913dc77b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f6f913dc37b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f6f9e578609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6f9fa74293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f6f4e7fc700 (LWP 145993)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x558e5a1ff890) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e5a1ff840, cond=0x558e5a1ff868) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e5a1ff868, mutex=0x558e5a1ff840) at pthread_cond_wait.c:638 #3 0x7f6f913dc77b in ?? () from
[dolphin] [Bug 428384] Dolphin displays duplicate files and then crashes when refreshing sftp-folder
https://bugs.kde.org/show_bug.cgi?id=428384 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428384] New: Dolphin displays duplicate files and then crashes when refreshing sftp-folder
https://bugs.kde.org/show_bug.cgi?id=428384 Bug ID: 428384 Summary: Dolphin displays duplicate files and then crashes when refreshing sftp-folder Product: dolphin Version: 20.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: till.seif...@spamfence.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.2) Qt Version: 5.15.0 Frameworks Version: 5.75.0 Operating System: Linux 5.4.22-050422-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: is was refreshing (F5) a folder (tree-view) with some folders expanded and some (not many) files in subfolders visible. The folder refreshed and displayed some files in the expanded subfolders twice. About 1s later dolphin crashed. - Unusual behavior I noticed: this only happened with sftp so far, never with local folders. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [New LWP 1968456] [New LWP 1968482] [New LWP 1968574] [New LWP 1968576] [New LWP 1968577] [New LWP 1968578] [New LWP 1968579] [New LWP 1968580] [New LWP 1968581] [New LWP 1968582] [New LWP 1968583] [New LWP 1968584] [New LWP 1968585] [New LWP 1968586] [New LWP 1968587] [New LWP 1968588] [New LWP 1968589] [New LWP 1968590] [New LWP 1968591] [New LWP 1968592] [New LWP 1968593] [New LWP 1968594] [New LWP 1968595] [New LWP 1968596] [New LWP 1968724] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f0e5ea80aff in __GI___poll (fds=0x7ffc752175e8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f0e57f32800 (LWP 1968423))] Thread 26 (Thread 0x7f0dd335d700 (LWP 1968724)): #0 0x7f0e5ea80aff in __GI___poll (fds=0x7f0dc0004a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0e5a5831ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e5a5832e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e5c7f4eab in QEventDispatcherGlib::processEvents (this=0x7f0dcb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0e5c7991bb in QEventLoop::exec (this=this@entry=0x7f0dd335cda0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f0e5c5b7082 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f0e5c5b820c in QThreadPrivate::start (arg=0x556e6c702320) at thread/qthread_unix.cpp:342 #7 0x7f0e5af42609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f0e5ea8d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f0e22ffd700 (LWP 1968596)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556e6c4a4f68) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556e6c4a4f18, cond=0x556e6c4a4f40) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556e6c4a4f40, mutex=0x556e6c4a4f18) at pthread_cond_wait.c:638 #3 0x7f0e4ed4d8db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f0e4ed4d4db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f0e5af42609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0e5ea8d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f0e237fe700 (LWP 1968595)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556e6c4a4f68) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556e6c4a4f18, cond=0x556e6c4a4f40) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556e6c4a4f40, mutex=0x556e6c4a4f18) at pthread_cond_wait.c:638 #3 0x7f0e4ed4d8db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f0e4ed4d4db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f0e5af42609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0e5ea8d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f0e23fff700 (LWP 1968594)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556e6c4a4f68) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556e6c4a4f18, cond=0x556e6c4a4f40) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556e6c4a4f40, mutex=0x556e6c4a4f18) at pthread_cond_wait.c:638 #3 0x7f0e4ed4d8db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f0e4ed4d4db in ?? () from
[plasmashell] [Bug 417828] Spawned Child processes get grouped with parent
https://bugs.kde.org/show_bug.cgi?id=417828 Till Seifert changed: What|Removed |Added Version|5.18.0 |5.18.4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418993] Dolphin crahes when i open sync folder from MEGASync Client
https://bugs.kde.org/show_bug.cgi?id=418993 --- Comment #2 from Till Seifert --- > Since you can reproduce the crash, please provide a valgrind log as > described here: https://community.kde.org/Dolphin/FAQ/Crashes i prepared that, but since MEGA is starting Dolphin I can not manually start it with Valgrind. Is there a way i can "capture" the exact command line that MEGA is using to start dolphin? So i can reproduce from Konsole. Note: my running Dolphin windows are not affected. It seems to start a new instance which immediately crashes. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418993] New: Dolphin crahes when i open sync folder from MEGASync Client
https://bugs.kde.org/show_bug.cgi?id=418993 Bug ID: 418993 Summary: Dolphin crahes when i open sync folder from MEGASync Client Product: dolphin Version: 19.12.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: till.seif...@spamfence.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (19.12.3) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.4.22-050422-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: * I open system tray menu of the MEGA Sync client for Linux * I select -> "Syncs" -> "MEGA" * Dialog appears that Dolphin just crashed 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 0x7f3191b0f800 (LWP 10381))] Thread 3 (Thread 0x7f3170fd3700 (LWP 10385)): #0 0x7f319137c0b4 in __GI___libc_read (fd=11, buf=0x7f3170fd2b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f31830712d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f318302c0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f318302c570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f318302c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f318af380db in QEventDispatcherGlib::processEvents (this=0x7f316c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f318aed763a in QEventLoop::exec (this=this@entry=0x7f3170fd2d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f318ace8317 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f318b3c4555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f318ace97ec in QThreadPrivate::start (arg=0x7f318b63cda0) at thread/qthread_unix.cpp:342 #10 0x7f31858416db in start_thread (arg=0x7f3170fd3700) at pthread_create.c:463 #11 0x7f319138d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f317b6b7700 (LWP 10384)): #0 0x7f3191380bf9 in __GI___poll (fds=0x7f317b6b6ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3185405747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f318540736a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f3191a1e440 in ?? () from /opt/mega/plugins/platforms/../../lib/libQt5XcbQpa.so.5 #4 0x7f318ace97ec in QThreadPrivate::start (arg=0x56041024f2a0) at thread/qthread_unix.cpp:342 #5 0x7f31858416db in start_thread (arg=0x7f317b6b7700) at pthread_create.c:463 #6 0x7f319138d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f3191b0f800 (LWP 10381)): [KCrash Handler] #6 QScopedPointer >::operator-> (this=0x72006f007b) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #7 qGetPtrHelper > const> (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1133 #8 QPlatformScreen::d_func (this=0x72006f0073) at kernel/qplatformscreen.h:80 #9 QPlatformScreen::screen (this=0x72006f0073) at kernel/qplatformscreen.cpp:153 #10 0x7f318b9c986e in QScreen::virtualSiblings (this=) at kernel/qscreen.cpp:421 #11 0x7f318c2e6731 in QDesktopWidgetPrivate::screenNumber (w=w@entry=0x560410486910) at kernel/qdesktopwidget.cpp:327 #12 0x7f318c2e6b1a in QDesktopWidgetPrivate::screenNumber (w=w@entry=0x560410486910) at kernel/qdesktopwidget.cpp:318 #13 0x7f318c2c2cb5 in QWidgetPrivate::create (this=this@entry=0x560410423ce0) at kernel/qwidget.cpp:1294 #14 0x7f318c2c2de2 in QWidget::create (this=0x560410486910, window=window@entry=0, initializeWindow=initializeWindow@entry=true, destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1187 #15 0x7f318c2c32ce in QWidgetPrivate::createWinId (this=) at kernel/qwidget.cpp:2391 #16 0x7f318c2c3379 in QWidget::winId (this=this@entry=0x560410486910) at kernel/qwidget.cpp:2359 #17 0x7f318e91ae90 in KMainWindowPrivate::polish (this=0x56041042cf50, q=q@entry=0x560410486910) at ./src/kmainwindow.cpp:343 #18 0x7f318e91dde6 in KMainWindow::event (this=this@entry=0x560410486910, ev=ev@entry=0x7ffc8568cf50) at ./src/kmainwindow.cpp:820 #19 0x7f318e95f197 in KXmlGuiWindow::event (this=0x560410486910, ev=0x7ffc8568cf50) at ./src/kxmlguiwindow.cpp:121 #20 0x7f318c28f8bc in QApplicationPrivate::notify_helper (this=this@entry=0x560410249fb0, receiver=receiver@entry=0x560410486910, e=e@entry=0x7ffc8568cf50) at
[plasmashell] [Bug 417828] Spawned Child processes get grouped with parent
https://bugs.kde.org/show_bug.cgi?id=417828 --- Comment #4 from Till Seifert --- Additional info: this also happens with *non-java" apps that I launch from Intellij, (such as gitk). They even keep the IntelliJ-icon in the Task bar after i close Intellij completely! The Alt-Tab switcher is not affected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417828] Spawned Child processes get grouped with parent
https://bugs.kde.org/show_bug.cgi?id=417828 --- Comment #2 from Till Seifert --- I forgot to mention: If i launch the same command line (java -jar[…]) from Konsole while IntellJ is running, it gets its own Task Manager entry exactly like in Plasma 5.17. So it only seems to happen if the java app is a *subprocess* of IntelliJ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417828] Spawned Child processes get grouped with parent
https://bugs.kde.org/show_bug.cgi?id=417828 --- Comment #1 from Till Seifert --- Created attachment 126129 --> https://bugs.kde.org/attachment.cgi?id=126129=edit The Task manager if app is laucnched the same way on Palasma 5.17 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417828] New: Spawned Child processes get grouped with parent
https://bugs.kde.org/show_bug.cgi?id=417828 Bug ID: 417828 Summary: Spawned Child processes get grouped with parent Product: plasmashell Version: 5.18.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: till.seif...@spamfence.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 126128 --> https://bugs.kde.org/attachment.cgi?id=126128=edit Task manager with java as subprocess of intellij This happens to me when i launch a Java app i am developing with IntellJ IDEA (second line is IntelliJ, third line is the launched custom app): The process tree looks like this: └─ /bin/sh /snap/intellij-idea-ultimate/204/bin/idea.sh └─ /snap/intellij-idea-ultimate/204/jbr/bin/java -classpath /snap/intellij-idea-ultimate……… │ ├─ /home/till/jdk1.8.0_191/bin/java The task manager (normal and icon-only) display the IntelliJ icon for for the launched java-app, and group it with IntelliJ. This happens only since Plasma 5.18. STEPS TO REPRODUCE 1. Launch IntelliJ 2. Launch a Java app that creates a window from intelliJ 3. Observe Task Manager OBSERVED RESULT The Task Manager groups the launched app with IntelliJ and assigns the same icon EXPECTED RESULT The launched app is displayed as an independend entry in the Task Manager and has it's icon SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 Kernel Version: 4.18.17-041817-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 23,4 GiB ADDITIONAL INFORMATION before 5.18. this worked as expected. see two attached screenshots, icon1.png is Plasma 5.18, and icon2.png is Plasma 5.17. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409259] Icons-only Task Manager hangs when switch desktops with pinned apps
https://bugs.kde.org/show_bug.cgi?id=409259 Till Seifert changed: What|Removed |Added Version|5.16.2 |5.18.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409259] Icons-only Task Manager hangs when switch desktops with pinned apps
https://bugs.kde.org/show_bug.cgi?id=409259 Till Seifert changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Till Seifert --- Still happens the same way in 5.18.0, still lots of CPU usage and then the taskbar updates. I tried to recreate it with pinned apps and without any pinned apps: * With all apps pinned (about 7) the lag was about 0.75s (this is a fresh session, it gets longer the longer i work) * i *unpinned* all but one app: the lag was about 1.25s * i unpinned the last app: the lag is now about 0.1s -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410844] Okular segfault
https://bugs.kde.org/show_bug.cgi?id=410844 Till Seifert changed: What|Removed |Added CC||till.seif...@spamfence.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409259] Icons-only Task Manager hangs when switch desktops with pinned apps
https://bugs.kde.org/show_bug.cgi?id=409259 --- Comment #1 from Till Seifert --- Created attachment 121218 --> https://bugs.kde.org/attachment.cgi?id=121218=edit Screen recording of workspace switching Here is a screen recording. Even thou i did "unpin" all icons today i did not manage to get it back to completely snappy. But the increase in lag, after i pinned some apps, is visible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409259] New: Icons-only Task Manager hangs when switch desktops with pinned apps
https://bugs.kde.org/show_bug.cgi?id=409259 Bug ID: 409259 Summary: Icons-only Task Manager hangs when switch desktops with pinned apps Product: plasmashell Version: 5.16.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: till.seif...@spamfence.net CC: plasma-b...@kde.org Target Milestone: 1.0 I'm running KDE NEON with Plasma 5.16.2, but this bug has been present unchanged in my setup since at least 5.15. When i switch workspaces the plasmashell (desktop and all panels) freeze for about 1s–60s and use 100% of one CPU-core in that time. After that they become responsive again. I see this only if a have (at the same time): a) the icon-only task-manager enabled b) some Apps-icons pinned -> the more apps I pin, the longer the lang becomes. If i pin IntelliJ, if jumps especially, but every app increases it. Grouping of icons or not doesd not affect it. Enabling "only icons from current workspace" does not affect it. STEPS TO REPRODUCE 1. active one Icon-only Taskmanager plasmoid 2. configure it to only show icons from current workspace (this is to better see the lag) 3. open Firefox/Krwite/Konsole/Chrome each on one workspace and pin their icons in the Taskmanager 4. switch to workspaces 5. observe the icons. they update some time after the workspace was switched 6. Pin more Apps (open or not) to increase the delay EXPECTED RESULT The panel and taskmanager should update instantly after switching workspaces, which they do, if i pin no apps, even if many apps are open. SOFTWARE/OS VERSIONS Betriebssystem: KDE neon 5.16 KDE-Plasma-Version: 5.16.2 KDE-Frameworks-Version: 5.59.0 Qt-Version: 5.12.3 Kernel-Version: 5.0.5-050005-generic Art des Betriebssystems: 64-bit Prozessoren: 4 × AMD A8-6600K APU with Radeon(tm) HD Graphics Speicher: 23,5 GiB Arbeitsspeicher -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 146239] not greedy regular expression
https://bugs.kde.org/show_bug.cgi?id=146239 Till Seifert <till.seif...@spamfence.net> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #16 from Till Seifert <till.seif...@spamfence.net> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
