[telepathy] [Bug 368395] Error: Handler no longer available
https://bugs.kde.org/show_bug.cgi?id=368395 Mostafa changed: What|Removed |Added CC||mostafa.pakpar...@gmail.com --- Comment #4 from Mostafa --- I have the same issue with ktp-text-ui 15.12.3 running on KDE Neon and the following: KDE Frameworks 5.37.0 Qt 5.9.1 (built against 5.9.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 368395] Error: Handler no longer available
https://bugs.kde.org/show_bug.cgi?id=368395 --- Comment #5 from Mostafa --- (In reply to Mostafa from comment #4) > I have the same issue with ktp-text-ui 15.12.3 running on KDE Neon and the > following: > > KDE Frameworks 5.37.0 > Qt 5.9.1 (built against 5.9.1) > The xcb windowing system If I open the contact from KRunner the chat window opens normally. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 497404] New: crashed
https://bugs.kde.org/show_bug.cgi?id=497404 Bug ID: 497404 Summary: crashed Classification: Applications Product: Elisa Version: 22.08.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mostafa.heln...@gmail.com Target Milestone: --- Application: elisa (22.08.2) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.7-301.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.26.2 [KCrashBackend] -- Information about the crash: nothing to say try to open file and program crashedccd The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Elisa (elisa), signal: Aborted [KCrash Handler] #4 0x7fcaa54b0e7c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7fcaa5460aa6 in raise () from /lib64/libc.so.6 #6 0x7fcaa544a7fc in abort () from /lib64/libc.so.6 #7 0x7fcaa56d7eb0 in std::__glibcxx_assert_fail(char const*, int, char const*, char const*) () from /lib64/libstdc++.so.6 #8 0x7fca748941a7 in FileBrowserProxyModel::recursiveEnqueue() () from /usr/lib64/elisa/libelisaLib.so.0 #9 0x7fca7489872b in FileBrowserProxyModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/elisa/libelisaLib.so.0 #10 0x7fcaa62e9913 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () from /lib64/libQt5Qml.so.5 #11 0x7fcaa61c1a09 in CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) () from /lib64/libQt5Qml.so.5 #12 0x7fcaa61c3910 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib64/libQt5Qml.so.5 #13 0x7fcaa61e090d in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5 #14 0x7fcaa61e4077 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) () from /lib64/libQt5Qml.so.5 #15 0x7fcaa6175586 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #16 0x7fcaa6304391 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #17 0x7fcaa62b4d1f in QQmlBoundSignalExpression::evaluate(void**) () from /lib64/libQt5Qml.so.5 #18 0x7fcaa62b64a8 in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #19 0x7fcaa62e93df in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #20 0x7fcaa5cdb680 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #21 0x7fcaa6290492 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Qml.so.5 #22 0x7fcaa62e9913 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () from /lib64/libQt5Qml.so.5 #23 0x7fcaa61c1a09 in CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) () from /lib64/libQt5Qml.so.5 #24 0x7fcaa61c3910 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib64/libQt5Qml.so.5 #25 0x7fcaa61e090d in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5 #26 0x7fcaa61e4077 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) () from /lib64/libQt5Qml.so.5 #27 0x7fcaa6175586 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #28 0x7fcaa6304391 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #29 0x7fcaa62b4d1f in QQmlBoundSignalExpression::evaluate(void**) () from /lib64/libQt5Qml.so.5 #30 0x7fcaa62b64a8 in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #31 0x7fcaa62e93df in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #32 0x7fcaa5cdb680 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #33 0x7fcaa6290492 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Qml.so.5 #34 0x7fcaa62e9913 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () from /lib64/libQt5Qml.so.5 #35 0x7fcaa61c057d in CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) () from /lib64/libQt5Qml.so.5 #36 0x7fcaa61c3910 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from
[frameworks-baloo] [Bug 371878] New: After starting system baloo_file gets a memory leak.
https://bugs.kde.org/show_bug.cgi?id=371878 Bug ID: 371878 Summary: After starting system baloo_file gets a memory leak. Product: frameworks-baloo Version: 5.21.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: msh7...@gmail.com Target Milestone: --- Application: baloo_file (5.21.0) Qt Version: 5.5.1 Operating System: Linux 4.1.12-1-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8dd4610780 (LWP 1488))] Thread 2 (Thread 0x7f8c89615700 (LWP 1644)): #0 0x7ffcc47e1d33 in clock_gettime () #1 0x7f8dd2145c9d in clock_gettime () at /lib64/libc.so.6 #2 0x7f8dd2bda7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f8dd2d5a3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f8dd2d5a945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8dd2d5bb5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f8dceb714ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f8dceb71d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f8dceb71f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f8dd2d5bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f8dd2d02d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x0041531b in () #12 0x7f8dd2b26382 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f8dd2b2932f in () at /usr/lib64/libQt5Core.so.5 #14 0x7f8dd116d0a4 in start_thread () at /lib64/libpthread.so.0 #15 0x7f8dd213904d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f8dd4610780 (LWP 1488)): [KCrash Handler] #6 0x7f8dcfe5d25c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so #7 0x7f8dd33f74cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x7f8dd33f4dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x7f8dd3406949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x0041d453 in () #11 0x0041de02 in () #12 0x7f8dd2d3473f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #13 0x0041e75a in () #14 0x004228f9 in () #15 0x7f8dd2d3473f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x7f8dd2db68ee in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #17 0x7f8dd2d41a89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7f8dd2d0518d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x7f8dd2d04e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7f8dd2d5cca5 in () at /usr/lib64/libQt5Core.so.5 #21 0x7f8dceb71c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x7f8dceb71ed8 in () at /usr/lib64/libglib-2.0.so.0 #23 0x7f8dceb71f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x7f8dd2d5bd6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #25 0x7f8dd2d02d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #26 0x7f8dd2d0a8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #27 0x0040a832 in () #28 0x7f8dd2075b05 in __libc_start_main () at /lib64/libc.so.6 #29 0x0040a9a8 in _start () Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 372177] New: could not save and overwirte current opened file
https://bugs.kde.org/show_bug.cgi?id=372177 Bug ID: 372177 Summary: could not save and overwirte current opened file Product: kwordquiz Version: 0.9.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: pe...@peterandlinda.com Reporter: msh7...@gmail.com Target Milestone: --- when i want to save the current new file again i see this message: The file is locked by another process. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425502] New: File extensions overflow and stick for a while in Icon View Mode if "Maximum lines" is set to 1 or 2.
https://bugs.kde.org/show_bug.cgi?id=425502 Bug ID: 425502 Summary: File extensions overflow and stick for a while in Icon View Mode if "Maximum lines" is set to 1 or 2. Product: dolphin Version: 20.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: mostafazaman...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 130968 --> https://bugs.kde.org/attachment.cgi?id=130968&action=edit The attachment is a video (screen recording) of the issue SUMMARY When "Maximum lines" is set to 1 or 2 in View Modes in Dolphin preferences, some filenames don't respect the line limitation. Their file extensions exceed the specified lines and when another folder is accessed, the overflowing file extensions stick there until something's clicked. I noticed this mostly with PDF files. STEPS TO REPRODUCE 1. Set "Maximum lines" to 1 or 2 in View Modes in Dolphin preferences 2. Go to a folder containing folders & files (preferably PDF) with relatively long names in Icon View Mode 3. Open another folder in the current folder OBSERVED RESULT At step 2, you should be noticing that some file extensions didn't stay in the specified lines. At step 3, after opening a folder those overflowing extensions should be sticking in place until something's clicked. EXPECTED RESULT File extensions should be contained in specified lines and they should not be sticking there after opening a folder. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (KDE Plasma) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I noticed the same issue in KDE neon user edition. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425502] File extensions overflow and stick there until something's clicked in Icon View Mode if "Maximum lines" is set to 1 or 2.
https://bugs.kde.org/show_bug.cgi?id=425502 Mostafa Zaman changed: What|Removed |Added Summary|File extensions overflow|File extensions overflow |and stick for a while in|and stick there until |Icon View Mode if "Maximum |something's clicked in Icon |lines" is set to 1 or 2.|View Mode if "Maximum ||lines" is set to 1 or 2. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425502] File extensions overflow and stick there until clicked in Icon View Mode if "Maximum lines" is set to 1 or 2.
https://bugs.kde.org/show_bug.cgi?id=425502 Mostafa Zaman changed: What|Removed |Added Summary|File extensions overflow|File extensions overflow |and stick there until |and stick there until |something's clicked in Icon |clicked in Icon View Mode |View Mode if "Maximum |if "Maximum lines" is set |lines" is set to 1 or 2.|to 1 or 2. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412265] New: Conflicting file association between Office files and Zip archives
https://bugs.kde.org/show_bug.cgi?id=412265 Bug ID: 412265 Summary: Conflicting file association between Office files and Zip archives Product: systemsettings Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_filetypes Assignee: fa...@kde.org Reporter: mostafazaman...@gmail.com Target Milestone: --- Microsoft Office files (DOC, DOCX, XLS, XLSX, PPT, PPTX) are recognized as compressed Zip archive on KDE neon. Whenever I double click those files, Ark will open them. Then I changed file association of those files in Settings and set my Office program (WPS Office) as the default. Now, whenever I double click an actual Zip archive, my office program tries to open it. To get what I want, I have to right-click and individually choose the program I want to open Office files and Compressed Zip files with from the context menu. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412265] Conflicting file association between Office files and Zip archives
https://bugs.kde.org/show_bug.cgi?id=412265 --- Comment #1 from Mostafa Zaman --- One thing I forgot to mention, those Office files' icons changed to a Zip icon too.. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 502476] New: An eject button is not showing to eject my removable Android phone
https://bugs.kde.org/show_bug.cgi?id=502476 Bug ID: 502476 Summary: An eject button is not showing to eject my removable Android phone Classification: Applications Product: dolphin Version: 24.12.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mostafa2018...@gmail.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 Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. Connect an Android phone (mine is Xiaomi Redmi Note 8 Pro) 2. Search everywhere for an unmount button 3. You will not find one, even with the search functionality of Dolphin! OBSERVED RESULT No "unmount" button showing EXPECTED RESULT Some "unmount" button to be able to safely unmount my device instead of removing it and hoping that no data gets corrupted! KINFO libEGL warning: egl: failed to create dri2 screen Operating System: Arch Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.13.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-12650H Memory: 15.2 GiB of RAM Graphics Processor 1: Mesa Intel® Graphics Graphics Processor 2: zink Vulkan 1.4 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 502477] New: An eject button is not showing to eject my removable Android phone
https://bugs.kde.org/show_bug.cgi?id=502477 Bug ID: 502477 Summary: An eject button is not showing to eject my removable Android phone Classification: Applications Product: dolphin Version: 24.12.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mostafa2018...@gmail.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 Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. Connect an Android phone (mine is Xiaomi Redmi Note 8 Pro) 2. Search everywhere for an unmount button 3. You will not find one, even with the search functionality of Dolphin! OBSERVED RESULT No "unmount" button showing EXPECTED RESULT Some "unmount" button to be able to safely unmount my device instead of removing it and hoping that no data gets corrupted! KINFO libEGL warning: egl: failed to create dri2 screen Operating System: Arch Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.13.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-12650H Memory: 15.2 GiB of RAM Graphics Processor 1: Mesa Intel® Graphics Graphics Processor 2: zink Vulkan 1.4 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 502477] An eject button is not showing to eject my removable Android phone
https://bugs.kde.org/show_bug.cgi?id=502477 Mostafa Beder changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Mostafa Beder --- *** This bug has been marked as a duplicate of bug 502476 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 502476] An eject button is not showing to eject my removable Android phone
https://bugs.kde.org/show_bug.cgi?id=502476 --- Comment #1 from Mostafa Beder --- *** Bug 502477 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
