[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #95 from Nikunj Bhatt --- (In reply to Nikunj Bhatt from comment #90) > (In reply to Nikunj Bhatt from comment #89) > > On opening the KDE Connect SMS through the icon of KDE Connect, I am seeing > > the window as per this attached screenshot > > https://bugs.kde.org/attachment.cgi?id=132304. The loader animation is > > animating forever. > > > > Then I closed the window and opened it through terminal using > > "kdeconnect-sms" command. The following messages appeared in the terminal: > > > > qrc:/qml/ChatMessage.qml:63:29: Invalid property assignment: string expected > > - Assigning null to incompatible properties in QML is deprecated. This will > > become a compile error in future versions of Qt. > > qrc:/qml/main.qml:36: ReferenceError: _initialMessage is not defined > > QGridLayoutEngine::addItem: Cell (0, 0) already taken > > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > QGridLayoutEngine::addItem: Cell (0, 0) already taken > > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > QGridLayoutEngine::addItem: Cell (0, 0) already taken > > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > > > I tried settings Microsoft SMS Organizer as default SMS app and also Google > > Messages app in the Android phone, but same problem occurred with both. > > > > The phone is Moto X Play, having Android 7.1.1. > > > > The laptop's info is: > > Operating System: Fedora 32 > > KDE Plasma Version: 5.18.5 > > KDE Frameworks Version: 5.73.0 > > Qt Version: 5.14.2 > > Kernel Version: 5.8.8-200.fc32.x86_64 > > OS Type: 64-bit > > Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz > > Memory: 7.2 GiB of RAM > > I forgot to mention that the KDE Connect SMS is unable to load messages but > I can reply to messages from the reply button and the window appears for > replying. With last update of either KDE Connect App desktop app or the SMS Organizer app it started working on the Moto X Play. BTW, I have now stopped using Moto phone and now using Nokia 5.3 with Android 10, and all functions are working fine with it. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 364578] Download Services
https://bugs.kde.org/show_bug.cgi?id=364578 --- Comment #4 from Nikunj Bhatt --- (In reply to Justin Zobel from comment #3) > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as resolved. > > I have set the bug status to "needsinfo" pending your response, please > change back to "reported" or "resolved/worksforme" when you respond, thank > you. Presently I am not experiencing this bug. Konqueror's current version on my system is 20.08.3. Here is more info of my current system: Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 Kernel Version: 5.9.11-100.fc32.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz Memory: 7.2 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #90 from Nikunj Bhatt --- (In reply to Nikunj Bhatt from comment #89) > On opening the KDE Connect SMS through the icon of KDE Connect, I am seeing > the window as per this attached screenshot > https://bugs.kde.org/attachment.cgi?id=132304. The loader animation is > animating forever. > > Then I closed the window and opened it through terminal using > "kdeconnect-sms" command. The following messages appeared in the terminal: > > qrc:/qml/ChatMessage.qml:63:29: Invalid property assignment: string expected > - Assigning null to incompatible properties in QML is deprecated. This will > become a compile error in future versions of Qt. > qrc:/qml/main.qml:36: ReferenceError: _initialMessage is not defined > QGridLayoutEngine::addItem: Cell (0, 0) already taken > QGridLayoutEngine::addItem: Cell (0, 1) already taken > QGridLayoutEngine::addItem: Cell (0, 0) already taken > QGridLayoutEngine::addItem: Cell (0, 1) already taken > QGridLayoutEngine::addItem: Cell (0, 0) already taken > QGridLayoutEngine::addItem: Cell (0, 1) already taken > > I tried settings Microsoft SMS Organizer as default SMS app and also Google > Messages app in the Android phone, but same problem occurred with both. > > The phone is Moto X Play, having Android 7.1.1. > > The laptop's info is: > Operating System: Fedora 32 > KDE Plasma Version: 5.18.5 > KDE Frameworks Version: 5.73.0 > Qt Version: 5.14.2 > Kernel Version: 5.8.8-200.fc32.x86_64 > OS Type: 64-bit > Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz > Memory: 7.2 GiB of RAM I forgot to mention that the KDE Connect SMS is unable to load messages but I can reply to messages from the reply button and the window appears for replying. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #89 from Nikunj Bhatt --- On opening the KDE Connect SMS through the icon of KDE Connect, I am seeing the window as per this attached screenshot https://bugs.kde.org/attachment.cgi?id=132304. The loader animation is animating forever. Then I closed the window and opened it through terminal using "kdeconnect-sms" command. The following messages appeared in the terminal: qrc:/qml/ChatMessage.qml:63:29: Invalid property assignment: string expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. qrc:/qml/main.qml:36: ReferenceError: _initialMessage is not defined QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken I tried settings Microsoft SMS Organizer as default SMS app and also Google Messages app in the Android phone, but same problem occurred with both. The phone is Moto X Play, having Android 7.1.1. The laptop's info is: Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 Kernel Version: 5.8.8-200.fc32.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz Memory: 7.2 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Nikunj Bhatt changed: What|Removed |Added CC||nikunjbhat...@gmail.com --- Comment #88 from Nikunj Bhatt --- Created attachment 132304 --> https://bugs.kde.org/attachment.cgi?id=132304=edit KDE Connect SMS Window -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 383527] KDE shows the desktop for some seconds after system wake-up.
https://bugs.kde.org/show_bug.cgi?id=383527 Nikunj Bhatt changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||nikunjbhat...@gmail.com --- Comment #2 from Nikunj Bhatt --- I have seen this happening just a day before. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424915] Q: When view setting is sort by modified, It affected by '.directory' file change. Is that intended?
https://bugs.kde.org/show_bug.cgi?id=424915 --- Comment #5 from Nikunj Bhatt --- As can be seen in the attached image, the sorting order of the directories is right but it is not helpful when we want to see the directories sorted by modified date of the files inside them. Mostly main purpose of sorting is this rather than what is currently implemented and correct. I think an option should be given to sort directories according to the files' order. However, problem deepens when deeper directories are opened in the details view which could result in resorting of the whole tree. This feature/suggestion require brainstorming to think about various possibilities and options. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424915] Q: When view setting is sort by modified, It affected by '.directory' file change. Is that intended?
https://bugs.kde.org/show_bug.cgi?id=424915 Nikunj Bhatt changed: What|Removed |Added CC||nikunjbhat...@gmail.com --- Comment #4 from Nikunj Bhatt --- Created attachment 132121 --> https://bugs.kde.org/attachment.cgi?id=132121=edit Directory and File sorting according to modified date in Details view The sorting order of directory is right but it is not helpful when we want to see the directories sorted by modified date of the files inside them. Mostly main purpose of sorting is this rather than what is currently implemented and correct. I think an option should be given to sort directories according to the files' order. However problem deepens when deeper directories are opened in the details view which could result in resorting of the whole tree. This feature/suggestion require brainstorming to think about various possibilities and options. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 426495] New: Kate is showing project only if .kateproject file is opened in Kate
https://bugs.kde.org/show_bug.cgi?id=426495 Bug ID: 426495 Summary: Kate is showing project only if .kateproject file is opened in Kate Product: kate Version: 20.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: nikunjbhat...@gmail.com Target Milestone: --- SUMMARY Kate is not auto-detecting .kateproject file I am browsing in Filesystem Browser sidebar panel. If there is .kateproject file in a folder and that folder is already open in Filesystem Browser then Kate should auto-detect the .kateproject file and add the current folder as a project in the Projects panel. STEPS TO REPRODUCE 1. Open a folder/directory in Filesystem Browser 2. Create/save a .kateproject file in that folder 3. Close and reopen Kate 4. Navigate to the same folder in Filesystem Browser (if not already open) where the .kateproject file was created/saved. Now the folder should get added to the Projects panel as a project but it is not getting added. 5. Open the .kateproject file. Now the folder is added as a project in Projects panel. OBSERVED RESULT The folder is only detected as a project after its .kateproject file is opened in Kate. Is it happening because I haven't added .kateproject file in the folder's Git repo? I haven't, and I think it should not matter, Kate should show the folder in Projects panel regardless of whether the .kateproject file is added to Git repo or not. EXPECTED RESULT Kate should auto-detect .kateproject file from curretly opened folder in Filesystem Browser and add that folder as a project in the Projects panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Suggestion: Instead of creating .kateproject file in the folders of the projects, these should be maintained somewhere in ~/.config folder of currently logged in user. (There are lots of such configuration files being created by different software or requirements in project folders which are not main parts of the projects.) Or provide options to the user to save and load .kateproject file from (1) a ~/.config/ folder, and (2) project/repository folder. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 383346] New: Konqueror crashed when tried to search in config dialog > plugins
https://bugs.kde.org/show_bug.cgi?id=383346 Bug ID: 383346 Summary: Konqueror crashed when tried to search in config dialog > plugins Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: nikunjbhat...@gmail.com Target Milestone: --- Application: konqueror (4.14.25) KDE Platform Version: 4.14.25 Qt Version: 4.8.6 Operating System: Linux 4.4.74-18.20-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I wanted to search for 'zip' extension and it crashed when I typed just 'z' in the search textbox. Was the problem occurred because there wasn't any other plugin? - Custom settings of the application: Searching and finding in plugin/extension. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8d445ed780 (LWP 13689))] Thread 5 (Thread 0x7f8d16be8700 (LWP 13749)): #0 0x7f8d41bb120d in poll () at /lib64/libc.so.6 #1 0x7f8d3ecbe314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8d3ecbe42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8d43288fce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f8d4325ad3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f8d4325b035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f8d4315849f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f8d4315ab7f in () at /usr/lib64/libQtCore.so.4 #8 0x7f8d42ec4744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8d41bb9aad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f8d177fe700 (LWP 13748)): #0 0x7f8d42ec90bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8d37a7ccb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f8d37a7cce9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f8d42ec4744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f8d41bb9aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f8d17fff700 (LWP 13747)): #0 0x7f8d41bb120d in poll () at /lib64/libc.so.6 #1 0x7f8d3ecbe314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8d3ecbe42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8d43288fce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f8d4325ad3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f8d4325b035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f8d4315849f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f8d4323c643 in () at /usr/lib64/libQtCore.so.4 #8 0x7f8d4315ab7f in () at /usr/lib64/libQtCore.so.4 #9 0x7f8d42ec4744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8d41bb9aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f8d1ef9d700 (LWP 13697)): #0 0x7f8d41bb120d in poll () at /lib64/libc.so.6 #1 0x7f8d3ecbe314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8d3ecbe42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8d43288fce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f8d4325ad3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f8d4325b035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f8d4315849f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f8d4315ab7f in () at /usr/lib64/libQtCore.so.4 #8 0x7f8d42ec4744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8d41bb9aad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f8d445ed780 (LWP 13689)): [KCrash Handler] #6 0x7f8d34ccc0c0 in () at /usr/lib64/libknewstuff3.so.4 #7 0x7f8d34cd3db4 in () at /usr/lib64/libknewstuff3.so.4 #8 0x7f8d34cc4fae in () at /usr/lib64/libknewstuff3.so.4 #9 0x7f8d34cc6de9 in () at /usr/lib64/libknewstuff3.so.4 #10 0x7f8d432700ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #11 0x7f8d427d4392 in QLineEdit::textChanged(QString const&) () at /usr/lib64/libQtGui.so.4 #12 0x7f8d427d4769 in () at /usr/lib64/libQtGui.so.4 #13 0x7f8d432700ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #14 0x7f8d42a25205 in QLineControl::textChanged(QString const&) () at /usr/lib64/libQtGui.so.4 #15 0x7f8d427d9dad in QLineControl::finishChange(int, bool, bool) () at /usr/lib64/libQtGui.so.4 #16 0x7f8d427dbab0 in
[krita] [Bug 381909] New: Krita crashed when setting position of tools from sidebar to toolbar from settings dialog
https://bugs.kde.org/show_bug.cgi?id=381909 Bug ID: 381909 Summary: Krita crashed when setting position of tools from sidebar to toolbar from settings dialog Product: krita Version: 2.9.11 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: nikunjbhat...@gmail.com Target Milestone: --- Application: krita (2.9.11) KDE Platform Version: 4.14.25 Qt Version: 4.8.6 Operating System: Linux 4.4.72-18.12-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: - Custom settings of the application: Krita crashed when setting position of tools from sidebar to toolbar from its settings window. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efe2376e8c0 (LWP 16372))] Thread 6 (Thread 0x7efdfaab8700 (LWP 27115)): #0 0x7efe20c2b873 in select () at /lib64/libc.so.6 #1 0x7efe21639ae7 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) () at /usr/lib64/libQtCore.so.4 #2 0x7efe2163f6e8 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timeval*) () at /usr/lib64/libQtCore.so.4 #3 0x7efe2163fb5a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7efe2160dd3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7efe2160e035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7efe2150b49f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7efe215ef643 in () at /usr/lib64/libQtCore.so.4 #8 0x7efe2150db7f in () at /usr/lib64/libQtCore.so.4 #9 0x7efe1bc65744 in start_thread () at /lib64/libpthread.so.0 #10 0x7efe20c32aad in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7efe05852700 (LWP 16415)): #0 0x7efe20c2b873 in select () at /lib64/libc.so.6 #1 0x7efe21639ae7 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) () at /usr/lib64/libQtCore.so.4 #2 0x7efe2163f6e8 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timeval*) () at /usr/lib64/libQtCore.so.4 #3 0x7efe2163fb5a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7efe2160dd3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7efe2160e035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7efe2150b49f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7efe215ef643 in () at /usr/lib64/libQtCore.so.4 #8 0x7efe2150db7f in () at /usr/lib64/libQtCore.so.4 #9 0x7efe1bc65744 in start_thread () at /lib64/libpthread.so.0 #10 0x7efe20c32aad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7efdf9ab6700 (LWP 16414)): #0 0x7efe1bc6a0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe2150e066 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7efe224f2116 in () at /usr/lib64/libQtGui.so.4 #3 0x7efe2150db7f in () at /usr/lib64/libQtCore.so.4 #4 0x7efe1bc65744 in start_thread () at /lib64/libpthread.so.0 #5 0x7efe20c32aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7efdf92b5700 (LWP 16409)): #0 0x7efe1bc6a0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe2150e066 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7efe2150a593 in QSemaphore::tryAcquire(int, int) () at /usr/lib64/libQtCore.so.4 #3 0x7efe1e3ec57a in KisTileDataSwapper::run() () at /usr/lib64/libkritaimage.so.14 #4 0x7efe2150db7f in () at /usr/lib64/libQtCore.so.4 #5 0x7efe1bc65744 in start_thread () at /lib64/libpthread.so.0 #6 0x7efe20c32aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7efdfa2b7700 (LWP 16408)): #0 0x7efe1bc6a0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe2150e066 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7efe2150a18b in QSemaphore::acquire(int) () at /usr/lib64/libQtCore.so.4 #3 0x7efe1e3cf1de in () at /usr/lib64/libkritaimage.so.14 #4 0x7efe1e3cf5fd in () at /usr/lib64/libkritaimage.so.14 #5 0x7efe2150db7f in () at /usr/lib64/libQtCore.so.4 #6 0x7efe1bc65744 in start_thread () at /lib64/libpthread.so.0 #7 0x7efe20c32aad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7efe2376e8c0 (LWP 16372)): [KCrash Handler] #6 0x7efe223c69c9 in QAbstractButton::setIcon(QIcon const&) () at /usr/lib64/libQtGui.so.4 #7 0x7efe22ed1de2 in KisPaintopBox::slotUpdateSelectionIcon() () at /usr/lib64/libkritaui.so.14 #8 0x7efe22da3cdd in () at
