[akregator] [Bug 486816] New: Text in the feed window and internal browser appear jagged and not antialiased
https://bugs.kde.org/show_bug.cgi?id=486816 Bug ID: 486816 Summary: Text in the feed window and internal browser appear jagged and not antialiased Classification: Applications Product: akregator Version: 6.0.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- Created attachment 169345 --> https://bugs.kde.org/attachment.cgi?id=169345=edit Screenshot of feed content pane Please see the attached image. I'm on Fedora 40. KDE Plasma is on Wayland. Text appearance is OK on all applications. I see the problem only with the content pane and browser of Akregator. Plasma v6.0.4 KDE Frameworks Version 6.1.0 Qt Version 6.7.0 (built against 6.7.0) AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478633] Enabling split view seems to change window size slightly
https://bugs.kde.org/show_bug.cgi?id=478633 --- Comment #4 from Syam --- (In reply to Akseli Lahtinen from comment #2) > Can't reproduce on Fedora 39. > > Are you using screen scaling? Custom window decorations? I'm using screen scaling of 150%. > > If it's at all possible, can you try updating your OS to Fedora 39 and see > if the bug still happens? I upgraded to Fedora 39 and still have the issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478633] Enabling split view seems to change window size slightly
https://bugs.kde.org/show_bug.cgi?id=478633 Syam changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Syam --- (In reply to Akseli Lahtinen from comment #2) > Are you using screen scaling? Custom window decorations? Yes! I am using screen scaling of 150%. If I change it to 100%, then I no longer have the problem. My screen resolution is 3840x2160. But I think I see the same problem on my work PC, where I'm not using scaling. I'll check and report back soon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478633] Enabling split view seems to change window size slightly
https://bugs.kde.org/show_bug.cgi?id=478633 --- Comment #1 from Syam --- This problem is annoying because attempts to close the window by moving the mouse to top right corner and clicking, causes some other window to close. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478633] New: Enabling split view seems to change window size slightly
https://bugs.kde.org/show_bug.cgi?id=478633 Bug ID: 478633 Summary: Enabling split view seems to change window size slightly Classification: Applications Product: dolphin Version: 23.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: get.so...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open Dolphin and maximize window 2. Move mouse to the extreme top-right corner and notice that the window close button is highlighted. You may move the mouse away now. 3. Press F3 to open split view 4. Now move mouse to top right corner and see that the close button no longer has highlight. A Left-clicking now will go the window behind this Dolphin window and may close that window. SOFTWARE/OS VERSIONS OS: Fedora 38 KDE Plasma Version: 5.27.9 KDE Frameworks Version: Version 5.111.0 Qt Version: Version 5.15.11 (built against 5.15.11) ADDITIONAL INFORMATION When I press F3, I can notice that the titlebar buttons move slightly to the left. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 375681] Not correctly handle binary numbers
https://bugs.kde.org/show_bug.cgi?id=375681 --- Comment #10 from Syam --- There's definitely a bug here. Test case: In 'numeral system mode', select 'Bin' for binary. Try pasting a string like "5". It fails with 'nan'. This indicates that the pasted number is expected to be in binary. In that case, why is a number like "011" interpreted in octal? If that was the logic, then "5" too should've been interpreted as decimal and converted to binary. In short, in binary mode, the pasted string is expected to be a binary number (since "5" is not accepted). So treating "011" as octal is definitely a bug. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 465043] Several old articles (mostly from KDAB) reappear occasionally on fetch of Planet Qt
https://bugs.kde.org/show_bug.cgi?id=465043 Syam changed: What|Removed |Added Summary|Several old articles|Several old articles |(mostly from KDAB) reappear |(mostly from KDAB) reappear |on every fetch of Planet Qt |occasionally on fetch of ||Planet Qt -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 465043] New: Several old articles (mostly from KDAB) reappear on every fetch of Planet Qt
https://bugs.kde.org/show_bug.cgi?id=465043 Bug ID: 465043 Summary: Several old articles (mostly from KDAB) reappear on every fetch of Planet Qt Classification: Applications Product: akregator Version: 5.22.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- I have PlanetQt feed (https://planet.qt.io/rss20.xml) in Akregator. Whenever I fetch new articles, I get several old ones (mostly from KDAB, www.pythonguis.com and www.ics.com) in the feed. If I delete them, they'll come back the next day or so, when I fetch the feed again. But they don't come back if I do a fetch immediately after I delete, or if I just quit and re-open Akregator. I'm not able to find the any specific interval value for the articles to be fetched again. The dates of the articles seem to be correct - some are from 2022, some are from earlier this month etc. So the dates indeed indicate that they are old articles. STEPS TO REPRODUCE 1. Add PlanetQt feed (https://planet.qt.io/rss20.xml) 2. Do 'Fetch all feeds' 3. Notice that several old articles are re-fetched, even after you've seen them before and deleted them I have this problem only with this particular feed (PlanetQt). Everything else is well-behaved. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 --- Comment #36 from Syam --- (In reply to Colin J Thomson from comment #35) I too haven't been seeing this bug for the past few days, on a fully updated Fedora 37. Akregator v5.21.3 (22.08.3), KDE Frameworks v5.101.0 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 349884] Spectrum analyser stops updating if Amarok window is shown in all virtual desktops
https://bugs.kde.org/show_bug.cgi?id=349884 Syam changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #2 from Syam --- The bug remains with Amarok 2.9.0, KDE Platform Version 4.14.38 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460201] New: Dolphin displays an overly prominent 'user canceled action' error message when a file drag and drop menu is closed
https://bugs.kde.org/show_bug.cgi?id=460201 Bug ID: 460201 Summary: Dolphin displays an overly prominent 'user canceled action' error message when a file drag and drop menu is closed Classification: Applications Product: dolphin Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: get.so...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Drag and drop a file within dolphin window, and the user is given a pop-up menu to move/copy/link. If the user decides to ignore the menu and close it, Dolphin displays a very prominent error message that slides down from the top saying "user canceled action". Is that really necessary? In my opinion, that message is invasive, does not offer much value, does not close with escape key and is an inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458965] Articles duplicated under wrong feeds after 'fetch all feeds'
https://bugs.kde.org/show_bug.cgi?id=458965 Syam changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Syam --- The problem seems to have rectified after several rounds of OS package updates. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458965] New: Articles duplicated under wrong feeds after 'fetch all feeds'
https://bugs.kde.org/show_bug.cgi?id=458965 Bug ID: 458965 Summary: Articles duplicated under wrong feeds after 'fetch all feeds' Product: akregator Version: 5.20.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- Occasionally (quite frequently), when fetching all feeds, articles from one feed will appear (duplicated) as unread articles under some other feed. And these are not new articles fetched in this cycle. Old articles under some feeds suddenly appear duplicated as unread articles under some other feed. This is happening since the last couple of days. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 438904] New: Crash when trying to open file open dialog from Chrome browser for uploading file
https://bugs.kde.org/show_bug.cgi?id=438904 Bug ID: 438904 Summary: Crash when trying to open file open dialog from Chrome browser for uploading file Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- Application: kdialog (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.10-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: I had chrome browser and I clicked on upload option on Google account. That should being up the file open dialog and I got this crash. I have seen the same crash with some other applications also, but I'm not able to remember which ones right now. Open/Save from Kate, Firefox and Gimp work fine. The crash can be reproduced every time. -- Backtrace: Application: KDialog (kdialog), signal: Segmentation fault [KCrash Handler] #4 0x7f71518158d6 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #5 0x7f715232525f in QImage::copy(QRect const&) const () from /lib64/libQt5Gui.so.5 #6 0x7f713fa2060d in KIO::PreviewJobPrivate::slotThumbData(KIO::Job*, QByteArray const&) () from /lib64/libKF5KIOWidgets.so.5 #7 0x7f7151d4f4b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f7153156c38 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #9 0x7f7151d4f4b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f7153138926 in KIO::SlaveInterface::data(QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #11 0x7f715313833a in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #12 0x7f715313060d in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #13 0x7f7153139c62 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #14 0x7f7151d4f4b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f7151d46257 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f7152935e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f7151d1ef48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f7151d21c76 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #19 0x7f7151d6bc57 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7f71505434cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7f71505974e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #22 0x7f7150540c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7f7151d6b6f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f7151d1d9b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7f7152b34c87 in QDialog::exec() () from /lib64/libQt5Widgets.so.5 #26 0x7f7152b34bc7 in QDialog::exec() () from /lib64/libQt5Widgets.so.5 #27 0x55a111a7aa37 in main () [Inferior 1 (process 5811) detached] Possible duplicates by query: bug 437773, bug 436863, bug 435427, bug 432084, bug 431077. Reported using DrKonqi This report was filed against 'kde' because the product 'kdelibs' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 176414] Needed provision for export and import (archiving) of articles
https://bugs.kde.org/show_bug.cgi?id=176414 --- Comment #3 from Syam --- It's a wishlist item and is still relevant. Every time I reinstall my OS, I take a backup of ~/.local/share/akregator so that I can restore it after installation. -- You are receiving this mail because: You are watching all bug changes.
[calligrastage] [Bug 389370] Calligra Stage crash when opening .ppt document.
https://bugs.kde.org/show_bug.cgi?id=389370 --- Comment #8 from Syam --- (In reply to Justin Zobel from comment #7) > 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. > The PPT file from comment #6 works fine for me (mine was a duplicate of this report). No crash. www.unm.edu/~unmvclib/powerpoint/pptexamples.ppt Calligra Stage v3.1.0 KDE Frameworks 5.75.0 Qt 5.14.2 (built against 5.14.2) May be OP can respond. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 424633] Clicking on a link to open in external browser makes the article scroll to top in Akregator
https://bugs.kde.org/show_bug.cgi?id=424633 Syam changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 426643] New: Provide option for system tray icon to show normal status on machines that are not expected to have internet access
https://bugs.kde.org/show_bug.cgi?id=426643 Bug ID: 426643 Summary: Provide option for system tray icon to show normal status on machines that are not expected to have internet access Product: plasma-nm Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: get.so...@gmail.com Target Milestone: --- On machines that are connected to private LANs without internet access, the plasma network systray icon shows an exclamation mark. This indicates something is wrong even though the machine is not expected to have access to Internet. On Windows, there are means to disable the internet access check and prevent such status icons. But I can't find any straightforward way on Plasms, other than meddling with the icon files. I feel this is a genuine requirement as having a network connection does not mean it has to have internet access. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389059] Deleting articles in Akregator causes graphics reset
https://bugs.kde.org/show_bug.cgi?id=389059 --- Comment #4 from Syam --- No. I can no longer reproduce this. I still have NVidia proprietary drivers but I no longer have this issue. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 424634] New: Middle clicking on links in feed articles do not work
https://bugs.kde.org/show_bug.cgi?id=424634 Bug ID: 424634 Summary: Middle clicking on links in feed articles do not work Product: akregator Version: 5.13.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- I have both left click and middle click configured to open in external browser (Firefox). But only left click works. Clicking on links with middle button has no visible effect. I tried changing middle click behaviour to 'open in tab' and 'open in background tab' also. But there's no difference in behaviour. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 424633] New: Clicking on a link to open in external browser makes the article scroll to top in Akregator
https://bugs.kde.org/show_bug.cgi?id=424633 Bug ID: 424633 Summary: Clicking on a link to open in external browser makes the article scroll to top in Akregator Product: akregator Version: 5.13.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open any sufficiently long feed article to view in the inline viewer 2. Scroll down in the viewer 3. *Left* click on any link to open in external browser OBSERVED RESULT Article scrolls to top in the inline viewer. EXPECTED RESULT Article's scroll position is unchanged. VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Akregator browser settings: Left mouse click: Open in external browser Middle mouse click: Open in external browser External browsing: Use default web browser KDE browser settings: Open http and https URLs: in the following application: Firefox PS: Apparently, middle clicking on a link has no effect! Only left click works. But that's for another bug report, I guess. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412967] Terminal does not sync to document path the first time when document is opened from File > Open or File > Open recent
https://bugs.kde.org/show_bug.cgi?id=412967 --- Comment #1 from Syam --- It seems the problem is only with the very first document opened after starting Kate. To reproduce: 1. Start Kate 2. Open any document by File > Open or File > Open recent 3. Notice that terminal does not change working directory -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412967] Terminal does not sync to document path the first time when document is opened from File > Open or File > Open recent
https://bugs.kde.org/show_bug.cgi?id=412967 Syam changed: What|Removed |Added Version|19.04.2 |20.04.1 Summary|Terminal does not sync to |Terminal does not sync to |document path when document |document path the first |is opened from File > Open |time when document is |recent |opened from File > Open or ||File > Open recent -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] System settings crashes on selecting Account Details from side bar search results
https://bugs.kde.org/show_bug.cgi?id=423638 Syam changed: What|Removed |Added Summary|System settings crashes on |System settings crashes on |selecting Account Details |selecting Account Details |from built-in search|from side bar search |results |results -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] System settings crashes on selecting Account Details from built-in search results
https://bugs.kde.org/show_bug.cgi?id=423638 Syam changed: What|Removed |Added Summary|System settings crashes on |System settings crashes on |selecting Account Details |selecting Account Details ||from built-in search ||results -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] System settings crashes on selecting Account Details
https://bugs.kde.org/show_bug.cgi?id=423638 --- Comment #1 from Syam --- The crash occurs only when selecting Account Details from the search results list. If I open System Settings, and then directly open the Account Details item (under Personalization), it DOES NOT crash. Account Details item opens fine and I have two sub-items - KDE wallet and User Manager. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] New: System settings crashes on selecting Account Details
https://bugs.kde.org/show_bug.cgi?id=423638 Bug ID: 423638 Summary: System settings crashes on selecting Account Details Product: systemsettings Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.19-200.fc31.x86_64 x86_64 Distribution: Fedora 31 (KDE Plasma) -- Information about the crash: 1. Open System Settings 2. Search for 'accounts' to get two results - Account Details and Online Accounts 3. Select Account Details 4. System Settings crashes The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efe1c832800 (LWP 18196))] Thread 5 (Thread 0x7efdfbfff700 (LWP 18202)): #0 0x7efe209dea3f in poll () from /lib64/libc.so.6 #1 0x7efe1ec4986e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7efe1ec499a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7efe20f6f8a3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7efe20f1923b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7efe20d69cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7efe20013399 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7efe20d6ae26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7efe064d3700 (LWP 18201)): #0 0x7efe209dea3f in poll () from /lib64/libc.so.6 #1 0x7efe1ec4986e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7efe1ec499a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7efe20f6f8a3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7efe20f1923b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7efe20d69cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7efe20013399 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7efe20d6ae26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7efe076b9700 (LWP 18199)): #0 0x7efe1f5a5d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7efe0c5fc19b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7efe0c5fbdab in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7efe0e584700 (LWP 18198)): #0 0x7efe1ec479f8 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7efe1ec491cf in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7efe1ec49812 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7efe1ec499a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7efe20f6f8a3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7efe20f1923b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7efe20d69cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7efe211f5f6a in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7efe20d6ae26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #10 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7efe1c832800 (LWP 18196)): [KCrash Handler] #4 0x7efe20924625 in raise () from /lib64/libc.so.6 #5 0x7efe2090d8d9 in abort () from /lib64/libc.so.6 #6 0x7efe20d34b25 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #7 0x7efe220723a7 in KPluginInfo::service() const [clone .cold] () from /lib64/libKF5Service.so.5 #8 0x7efe224fa1e9 in KCModuleInfo::service() const () from /lib64/libKF5KCMUtils.so.5 #9 0x7efe2254aede in ModuleView::addModule(KCModuleInfo*) () from /lib64/libsystemsettingsview.so.3 #10 0x7efe2254b60d in ModuleView::loadModule(QModelIndex const&) () from /lib64/libsystemsettingsview.so.3 #11 0x7efe065a1bbf in SidebarMode::changeModule(QModelIndex const&) () from /usr/lib64/qt5/plugins/systemsettings_sidebar_mode.so #12 0x7efe065a1cb1 in SidebarMode::setActiveCategory(int) ()
[krunner] [Bug 421292] PDF files when opened from KRunner's Document result section open in Gnome evince instead of Okular
https://bugs.kde.org/show_bug.cgi?id=421292 Syam changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Syam --- Today, I tested it again and it is working like expected. PDF files are getting opened in Okular, as expected. I have no idea how this got fixed. I had installed several updates from Fedora over these days. So no idea what fixed this. Closing the report for now. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 179530] 'Find Events' can have 'Any date' search option
https://bugs.kde.org/show_bug.cgi?id=179530 Syam changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Syam --- The search dialog now allows to ignore date when searching. Although the UI is a bit confusing as the date entry boxes are always enabled and the option for whether or not to use them is in the next line. Anyway, the "search irrespective of date" functionality is there. So I'm closing this bug. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 176454] Article search should begin only after a delay when the search text changes
https://bugs.kde.org/show_bug.cgi?id=176454 Syam changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Syam --- The search behaviour is OK now. So closing. Thanks -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 222638] The 'Current Projects' banner above the project pane wastes screen area
https://bugs.kde.org/show_bug.cgi?id=222638 Syam changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Syam --- The banner in current versions seem to be fine. So I'm closing this report. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 421292] New: PDF files when opened from KRunner's Document result section open in Gnome evince instead of Okular
https://bugs.kde.org/show_bug.cgi?id=421292 Bug ID: 421292 Summary: PDF files when opened from KRunner's Document result section open in Gnome evince instead of Okular Product: krunner Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: get.so...@gmail.com Target Milestone: --- I have Fedora 31 KDE spin (Gnome desktop is not installed). Okular is the default application set for PDF files. STEPS TO REPRODUCE 1. Open KRunner by Alt+F2 and type "pdf" in the box 2. Click on any PDF file from the search result in "Document" category 3. The file is opened in Gnome evince The problem is only with KRunner results belonging to "Document" section. PDF files in "Recent Documents" section open in Okular. When opened from Dolphin or by xdg-open, PDF files are opened in Okular, as expected. In File Associations in System Settings, Okular is the first handler for application/pdf and evince is second. This is possibly related to a particular KRunner plugin. I couldn't correctly guess it (file search or places, probably). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 416332] Add option to suppress notification message on start
https://bugs.kde.org/show_bug.cgi?id=416332 Syam changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Syam --- (In reply to Antonio Rojas from comment #1) Wow! That is true. Thanks a ton. I never figured I could do this from notifications configuration. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 416332] New: Add option to suppress notification message on start
https://bugs.kde.org/show_bug.cgi?id=416332 Bug ID: 416332 Summary: Add option to suppress notification message on start Product: yakuake Version: 3.0.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- I have Yakuake on KDE autostart. When Yakuake starts, it gives a notification message along the lines of "yakuake has been started and press F12 to get the terminal". This ends up in KDE's notification list and causes the notification icon to come up on the systray. It would be nice to have a command-line argument (eg. --quiet) for yakuake to suppress generation of this notification message so that it doesn't unnecessarily come up for people who have it in autostart. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Syam changed: What|Removed |Added CC||get.so...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 415095] New: albums with tracks from different artists are shown separately in album view
https://bugs.kde.org/show_bug.cgi?id=415095 Bug ID: 415095 Summary: albums with tracks from different artists are shown separately in album view Product: elisa Version: 0.4.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: get.so...@gmail.com Target Milestone: --- Consider an album containing 5 tracks. Each track is by a different artist. i.e. all tracks have the same entry for Album tag and different entries for artist tag. Elisa displays these 5 as separate entries in the album view. Why can't tracks be simply grouped based on album tag? Why unnecessarily involve the artist tag for this? PS: The 'album artist' tag is not a solution as that might not make sense in all cases. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414720] 'Minimize windows' widget does not remember active window on restore
https://bugs.kde.org/show_bug.cgi?id=414720 --- Comment #1 from Syam --- Just found this: bug 368867. Does that fix 'minimize windows' widget behaviour as well? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414720] New: 'Minimize windows' widget does not remember active window on restore
https://bugs.kde.org/show_bug.cgi?id=414720 Bug ID: 414720 Summary: 'Minimize windows' widget does not remember active window on restore Product: plasmashell Version: 5.15.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: get.so...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Add minimize windows widget to the task bar 2. Open a few windows (Dolphin, Firefox, Okular) 3. Make any window other than the last one in task manager as active window (bring to foreground) 2. Click on minimize windows widget (added to the taskbar) to minimize all windows 3. Click on minimize windows widget again to restore windows 4. Notice that the windows are restored in the order they appear in the task manager and not in the order they were before minimizing When you are working on a window and temporarily minimize all to check something on the desktop (or for some other reason) and then restore, one expects to get back to the earlier active window. But in this case, some other window will come to front. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412967] New: Terminal does not sync to document path when document is opened from File > Open recent
https://bugs.kde.org/show_bug.cgi?id=412967 Bug ID: 412967 Summary: Terminal does not sync to document path when document is opened from File > Open recent Product: kate Version: 19.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Start Kate 2. Open a recently opened document from File > Open recent 3. Notice that terminal does not change working directory -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408355] Selection context menu missing find in this document
https://bugs.kde.org/show_bug.cgi?id=408355 Syam changed: What|Removed |Added CC||get.so...@gmail.com --- Comment #4 from Syam --- (In reply to Albert Astals Cid from comment #3) Isn't "search for ... in this document" better than "search for ... in open document"? The first time I saw the screenshot in 'this week in KDE' report, it took me a few seconds to understand that "open document" does not refer to ODF. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412326] Colours of desktop wallpaper is different from same image in Gwenview
https://bugs.kde.org/show_bug.cgi?id=412326 --- Comment #2 from Syam --- I just realised that Firefox also renders the image with similar colour saturation as plasma wallpaper. So, I guess Gwenview is the culprit and not plasma. If someone can concur with this inference, we will move the report against gwenview. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412326] Colours of desktop wallpaper is different from same image in Gwenview
https://bugs.kde.org/show_bug.cgi?id=412326 --- Comment #1 from Syam --- This is the image I used as wallpaper. https://pasteboard.co/Iz3B9KX.jpg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412326] New: Colours of desktop wallpaper is different from same image in Gwenview
https://bugs.kde.org/show_bug.cgi?id=412326 Bug ID: 412326 Summary: Colours of desktop wallpaper is different from same image in Gwenview Product: plasmashell Version: 5.15.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: get.so...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 122864 --> https://bugs.kde.org/attachment.cgi?id=122864=edit screenshot of the wallpaper and image opened in gwenview I have set an image as desktop wallpaper. The same image is opened in Gwenview. The colours appear more vibrant in gwenview and duller in the wallpaper. Versions: Plasma: 5.15.5 Gwenview: 18.12.2 KDE frameworks: 5.59.0 Qt: 5.12.4 Desktop settings: Layout: Folderview Wallpaper type: Slideshow Positioning: scaled and cropped PS: I am not sure if the wallpaper is correct or gwenview is :-| -- You are receiving this mail because: You are watching all bug changes.
[HIG] [Bug 106807] 'Full Screen' option should really be in the 'View' menu
https://bugs.kde.org/show_bug.cgi?id=106807 --- Comment #22 from Syam --- Can this please be fixed? It's very unintuitive for Okular, at least (bug 163493). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409359] /usr/share/applications/kde-mimeapps.list contains "kde4-" prefix for all .desktop file entries, which causes problems
https://bugs.kde.org/show_bug.cgi?id=409359 Syam changed: What|Removed |Added Summary|/usr/share/applications/kde |/usr/share/applications/kde |-mimeapps.list contains |-mimeapps.list contains |"kde4-" prefix for .desktop |"kde4-" prefix for all |file entries causing|.desktop file entries, |problems|which causes problems -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409359] New: /usr/share/applications/kde-mimeapps.list contains "kde4-" prefix for .desktop file entries causing problems
https://bugs.kde.org/show_bug.cgi?id=409359 Bug ID: 409359 Summary: /usr/share/applications/kde-mimeapps.list contains "kde4-" prefix for .desktop file entries causing problems Product: systemsettings Version: 5.15.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_filetypes Assignee: fa...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- Created attachment 121253 --> https://bugs.kde.org/attachment.cgi?id=121253=edit /usr/share/applications/kde-mimeapps.list after fixing PDF entry The entries in /usr/share/applications/kde-mimeapps.list have "kde4-" prefix for all .desktop filenames. Observed Problem - PDF files when opened from the downloads list of Firefox, starts up Gimp instead of Okular which is the associated application set in KDE. On this machine, only KDE is installed (no other DE). Similar behaviour is seen when opening PDF files from Zotero. xdg-open foo.pdf works as expected and brings up Okular. This problem was fixed by editing /usr/share/applications/kde-mimeapps.list and deleting "kde4-" prefix for the .desktop filename for application/pdf entry. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 407009] New: Wrong binary number value pasted from clipboard if number begins with 0
https://bugs.kde.org/show_bug.cgi?id=407009 Bug ID: 407009 Summary: Wrong binary number value pasted from clipboard if number begins with 0 Product: kcalc Version: 18.12 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: get.so...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Copy some binary number string that starts with 0, such as "011" (without the quotes) to clipboard 2. Open KCalc 3. Select Numeral System Mode 4. Press Ctrl+C to paste 5. Find that the pasted value is not as expected (eg. 1001 instead of 011) The pasted value will be correct if the original number starts with 1 instead. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 --- Comment #42 from Syam --- (In reply to Chris Holland from comment #39) I am affected by this bug and can reproduce it at will. At every login, I find Kate in favourites list. I delete it, logout and log back in. I find that Kate is back in the favourites list. I have attached the two files that you mentioned. These files do not change at all when Kate is removed from favourites, nor after a re-login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 --- Comment #41 from Syam --- Created attachment 118873 --> https://bugs.kde.org/attachment.cgi?id=118873=edit kactivitymanagerd-statsrc from ~/.config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 --- Comment #40 from Syam --- Created attachment 118872 --> https://bugs.kde.org/attachment.cgi?id=118872=edit kactivitymanagerdrc from ~/.config -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 334847] When reaching the last image and trying to view next, an unergonomic menu is shown
https://bugs.kde.org/show_bug.cgi?id=334847 --- Comment #13 from Syam --- This problem is still there with Gwenview v18.04.3. KDE Frameworks 5.54.0 Qt 5.11.3 (built against 5.11.3) -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 403291] New: KSysguard crashes on exit
https://bugs.kde.org/show_bug.cgi?id=403291 Bug ID: 403291 Summary: KSysguard crashes on exit Product: ksysguard Version: 5.14.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- Application: ksysguard (5.14.4) Qt Version: 5.11.3 Frameworks Version: 5.53.0 Operating System: Linux 4.19.13-300.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: Just opened Ksysguard, closed it after a few seconds and it crashed. Tried again and crashed again. But subsequent trials went fine without crash. The crash can be reproduced sometimes. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd19dfcb940 (LWP 7353))] Thread 5 (Thread 0x7fd187fff700 (LWP 7358)): #0 0x7fd1a21f673c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd18cedf4e3 in () at /usr/lib64/dri/i965_dri.so #2 0x7fd18cedf23b in () at /usr/lib64/dri/i965_dri.so #3 0x7fd1a21f058e in start_thread () at /lib64/libpthread.so.0 #4 0x7fd1a54146a3 in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fd18f599700 (LWP 7356)): #0 0x7fd1a5404f84 in read () at /lib64/libc.so.6 #1 0x7fd19fabce90 in () at /lib64/libglib-2.0.so.0 #2 0x7fd19fa75e9b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fd19fa76350 in () at /lib64/libglib-2.0.so.0 #4 0x7fd19fa764d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fd1a5ab85ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fd1a5a66e0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fd1a58cee86 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fd1a696af89 in () at /lib64/libQt5DBus.so.5 #9 0x7fd1a58d82fb in () at /lib64/libQt5Core.so.5 #10 0x7fd1a21f058e in start_thread () at /lib64/libpthread.so.0 #11 0x7fd1a54146a3 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fd190327700 (LWP 7355)): #0 0x7fd1a5409421 in poll () at /lib64/libc.so.6 #1 0x7fd1a1c4339f in () at /lib64/libxcb.so.1 #2 0x7fd1a1c4501a in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fd19d66bbf9 in () at /lib64/libQt5XcbQpa.so.5 #4 0x7fd1a58d82fb in () at /lib64/libQt5Core.so.5 #5 0x7fd1a21f058e in start_thread () at /lib64/libpthread.so.0 #6 0x7fd1a54146a3 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fd19dfc7700 (LWP 7354)): #0 0x7fd1a21f673c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd1a573b690 in std::condition_variable::wait(std::unique_lock&) () at /lib64/libstdc++.so.6 #2 0x7fd1a460497a in () at /lib64/libQt5WebKit.so.5 #3 0x7fd1a4604aaf in () at /lib64/libQt5WebKit.so.5 #4 0x7fd1a5741943 in () at /lib64/libstdc++.so.6 #5 0x7fd1a21f058e in start_thread () at /lib64/libpthread.so.0 #6 0x7fd1a54146a3 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fd19dfcb940 (LWP 7353)): [KCrash Handler] #6 0x7fd1a64840c0 in () at /lib64/libQt5Widgets.so.5 #7 0x7fd1a6484c24 in QLabel::setText(QString const&) () at /lib64/libQt5Widgets.so.5 #8 0x7fd1a7827374 in () at /lib64/libkdeinit5_ksysguard.so #9 0x7fd1a6f86709 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /lib64/libksgrd.so.7 #10 0x7fd1a6f8dbb2 in () at /lib64/libksgrd.so.7 #11 0x7fd1a5a901c3 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #12 0x7fd1a5a0925e in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /lib64/libQt5Core.so.5 #13 0x7fd1a5a0e0d1 in () at /lib64/libQt5Core.so.5 #14 0x7fd1a5a0e4d0 in () at /lib64/libQt5Core.so.5 #15 0x7fd1a5a9009e in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #16 0x7fd1a5a9b95c in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /lib64/libQt5Core.so.5 #17 0x7fd1a5a9bcc1 in QSocketNotifier::event(QEvent*) () at /lib64/libQt5Core.so.5 #18 0x7fd1a6357285 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #19 0x7fd1a635e9a0 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #20 0x7fd1a5a67ec6 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #21 0x7fd1a5ab8f4c in () at /lib64/libQt5Core.so.5 #22 0x7fd19fa7606d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #23 0x7fd19fa76438 in () at /lib64/libglib-2.0.so.0 #24 0x7fd19fa764d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #25 0x7fd1a5ab8593 in
[kate] [Bug 402706] New: Show number of selected lines in the status bar
https://bugs.kde.org/show_bug.cgi?id=402706 Bug ID: 402706 Summary: Show number of selected lines in the status bar Product: kate Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- While editing text files (tabular text, for example), it is often useful to see how many lines are selected. Similar is the use case for showing how many characters in a line are selected. The latter is already available by enabling 'show word count' in configure > appearance. However, no such option exists to see how many lines are selected. The only way to determine that is to enable line numbers in the border, note down the starting and ending line number of the selection and calculate manually. It will be useful if Kate/KWrite can display the selected line count in the status bar. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389059] Deleting articles in Akregator causes graphics reset
https://bugs.kde.org/show_bug.cgi?id=389059 Syam <get.so...@gmail.com> changed: What|Removed |Added Summary|Deleting articles causes|Deleting articles in |graphics reset |Akregator causes graphics ||reset -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389059] Deleting articles causes graphics reset
https://bugs.kde.org/show_bug.cgi?id=389059 Syam <get.so...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Syam <get.so...@gmail.com> --- Additional information: I can reproduce the problem at will: 1. View any article from Slashdot feed. 2. View any article that has a video embedded (Youtube video, for example). The video does not play in the Akrgeator view area though. After step 1 or step 2, all subsequent delete operations (of articles from any feed) become very slow and cause graphics reset if too many articles are deleted together -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Kate icon removed from the favorites list is back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Syam <get.so...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||get.so...@gmail.com --- Comment #21 from Syam <get.so...@gmail.com> --- I can confirm this bug on: Fedora 28, x86-64 plasma 5.12.5 Kate 17.12.2 Frameworks 5.44.0 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383310] Import torrent operation fails with cannot copy torrent file error
https://bugs.kde.org/show_bug.cgi?id=383310 Syam <get.so...@gmail.com> changed: What|Removed |Added Summary|Unable to import torrent|Import torrent operation ||fails with cannot copy ||torrent file error -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383310] Import torrent operation fails with unable to copy torrent file error
https://bugs.kde.org/show_bug.cgi?id=383310 Syam <get.so...@gmail.com> changed: What|Removed |Added Summary|Import torrent operation|Import torrent operation |fails with cannot copy |fails with unable to copy |torrent file error |torrent file error -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383311] "Import torrent" files filter does not allow user to see & select .torrent files
https://bugs.kde.org/show_bug.cgi?id=383311 Syam <get.so...@gmail.com> changed: What|Removed |Added Summary|"Import torrent" files |"Import torrent" files |filter unables user to see |filter does not allow user |.torrent files |to see & select .torrent ||files -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383310] Unable to import torrent
https://bugs.kde.org/show_bug.cgi?id=383310 Syam <get.so...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||get.so...@gmail.com --- Comment #1 from Syam <get.so...@gmail.com> --- I can confirm this bug on Fedora 28. KTorrent v5.1.0. x86-64 The torrent file is valid and actually was exported from KTorrent itself. KTorrent is able to open the same torrent file as a fresh file (using Open Torrent action), just not by "Import torrent". -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383311] "Import torrent" files filter unables user to see .torrent files
https://bugs.kde.org/show_bug.cgi?id=383311 Syam <get.so...@gmail.com> changed: What|Removed |Added CC||get.so...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Syam <get.so...@gmail.com> --- I can confirm this problem on Fedora 28. KTorrent v5.1.0. x86-64 And the language is just US English. The file filter is shown as: Torrents (*.torrent);;All files (*) (Torrents (*.torrent);;All files Changing the filter to * makes the files visible and selectable. But import still fails with a cannot copy error for the selected torrent file (bug #383310). -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389059] Deleting articles causes graphics reset
https://bugs.kde.org/show_bug.cgi?id=389059 --- Comment #1 from Syam <get.so...@gmail.com> --- I made an observation regarding the problem. I have almost 40 feeds. But the problem is only with Slashdot feed. Deleting an article from Slashdot is slow. If I select 10 articles from Slashdot feed and press delete, it takes couple of seconds for deletion. And once I delete one or more articles from Slashdot feed, then deleting articles of other feeds also start having the same delay problem. Restarting Akregator is the only way to solve this. In my experience, this 'lag' in deleting articles is related to the graphics reset issue. As long as I don't delete any articles from Slashdot, Akregator is very well behaved. Akregator 5.7.2 Fedora 27 x86-64 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389059] New: Deleting articles causes graphics reset
https://bugs.kde.org/show_bug.cgi?id=389059 Bug ID: 389059 Summary: Deleting articles causes graphics reset Product: akregator Version: 5.7.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- I use Nvidia graphics card with proprietary drivers (from RPMFusion). Earlier with Fedora 26, when deleting multiple articles on Akregator, I often (but not always) used to get the message "desktop effects were restarted due to a graphics reset" from plasma. But plasma used to come back up and apart from the irritation, it wasn't doing major harm. Now with Fedora 27, I have the similar problem, but then plasma does not come beck up. It just hangs. I can switch to another VT and if I switch back, I see the mouse pointer on a black background. I can move the pointer around and it changes (to pointy-hand, cursor etc) based on where I keep it, indicating that underneath the black background, the applications are still active. So far, the only recovery I've been able to find is doing "init 3" followed by "init 5" to get back the login screen. I can reproduce this at will by simply deleting a few articles on Akregator. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 352511] 5.0.xx feeds.opml gets corrupted after each crash
https://bugs.kde.org/show_bug.cgi?id=352511 Syam <get.so...@gmail.com> changed: What|Removed |Added CC||get.so...@gmail.com --- Comment #2 from Syam <get.so...@gmail.com> --- I too observe feeds.opml being reported corrupted. Happened to me again just now when I booted my computer today. I don't remember Akregator crashing yesterday when I logged out yesterday. But it is possible that I didn't close Akregator before shutting down from KDE. But I am unable to reproduce this problem by forcefully terminating Akrgator with "kill -9". Using Akregator v5.5.1, KDE Frameworks 5.36.0, Qt 5.7.1 (built against 5.7.1), Fedora 26, x86_64 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 373688] Akregator crashes at startup if more than one instance of Qt Creator is running
https://bugs.kde.org/show_bug.cgi?id=373688 Syam <get.so...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Syam <get.so...@gmail.com> --- Seems to work OK now. Fedora 25, x86_64 Akregator 5.4.3 KDE Frameworks 5.34.0 Qt 5.7.1 (built against 5.7.1) Qt Creator 4.1.0 Based on Qt 5.7.1 (GCC 6.3.1 20161221 (Red Hat 6.3.1-1), 64 bit) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 365276] Selecting/deleting an article does not work if 'search article' box has focus
https://bugs.kde.org/show_bug.cgi?id=365276 Syam <get.so...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Syam <get.so...@gmail.com> --- Seems to work fine with Akregator 5.4.3, KDE Frameworks 5.34.0, Qt 5.7.1, Fedora 25. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 337882] Search misbehaves when searching for titles containing single quotes
https://bugs.kde.org/show_bug.cgi?id=337882 Syam <get.so...@gmail.com> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Syam <get.so...@gmail.com> --- Seems to work fine with Akregator 5.4.3, KDE Frameworks 5.34.0, Qt 5.7.1, Fedora 25. Searching for single-quote and words with single-quote (what's, customer's etc.) seem to work fine. Searching for double-quotes has some incomprehensible behaviour though. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 328964] Konversation crashed when Ctrl+W was pressed
https://bugs.kde.org/show_bug.cgi?id=328964 Syam <get.so...@gmail.com> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Syam <get.so...@gmail.com> --- This is an old report. I can no longer reproduce with the current version. So closing. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 373688] New: Akregator crashes at startup if more than one instance of Qt Creator is running
https://bugs.kde.org/show_bug.cgi?id=373688 Bug ID: 373688 Summary: Akregator crashes at startup if more than one instance of Qt Creator is running Product: akregator Version: 5.3.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- If I have two Qt Creator windows open and then try to start Akregator, it crashes on startup. If I close one Qt Creator window, Akregator starts OK. Similarly, if I have Akregator already running, I can start only one instance of Qt Creator. If I try to get a second instance of Qt creator running, its window doesn't come up. The second process just takes up 25% CPU, without having any window shown. Fedora 25, x86_64 Akregator v5.3.0 (QtWebEngine) KDE Frameworks 5.27.0 Qt 5.7.0 (built against 5.7.0) Qt Creator v4.1.0 Based on Qt 5.7.0 (GCC 6.2.1 20160916 (Red Hat 6.2.1-2), 64 bit) All packages installed from Fedora repos. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 337882] Search misbehaves when searching for titles containing single quotes
https://bugs.kde.org/show_bug.cgi?id=337882 Syam <get.so...@gmail.com> changed: What|Removed |Added Version|4.12.5 |5.3.0 --- Comment #5 from Syam <get.so...@gmail.com> --- This bug exists with Akregator Version 5.3.0 (QtWebEngine). I can't be sure about the behaviour when searching for "" for this version. Titles with words with single quotes (Error'd, What's etc.) are not listed when searching for that word. It's very easy to reproduce. Just add the Daily WTF's feed and you can see for yourself: http://syndication.thedailywtf.com/TheDailyWtf I have changed the version of the application to 5.3.0 for the report. Fedora 24 KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 175870] "feed" tab in message board vanishes sometimes
https://bugs.kde.org/show_bug.cgi?id=175870 --- Comment #6 from Syam <get.so...@gmail.com> --- I can no longer recreate the bug with Akregator Version 5.3.0. Fedora 24 KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 365825] Show desktop applet shortcut broken
https://bugs.kde.org/show_bug.cgi?id=365825 Syam <get.so...@gmail.com> changed: What|Removed |Added CC||get.so...@gmail.com --- Comment #1 from Syam <get.so...@gmail.com> --- I can confirm this bug with Plasma 5.7.1 on Fedora 24. Setting a keyboard shortcut for "Show Desktop" widget on the panel has no effect. However, if I go to System Settings > Shortcuts > Global Keyboard Shortcuts > KWin and assign the shortcut to "Show Desktop" item, it works. PS: I think it might be wrong to assign the bug against "kdeplasma-addons". Somebody please change to the right product. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 365276] New: Selecting/deleting an article does not work if 'search article' box has focus
https://bugs.kde.org/show_bug.cgi?id=365276 Bug ID: 365276 Summary: Selecting/deleting an article does not work if 'search article' box has focus Product: akregator Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Pressing Delete to delete an article while the 'search articles' text box has focus does not work. In general, I think there's some bigger problem with the way the article list widget and the feeds list widget gets focus. The colour of the selected item in both of these widgets is duller than the usual colour used for selected items. If you doubleclick an item in the feeds list, the feed's name becomes editable and then the item's background colour resembles that of a properly selected item. Reproducible: Always Steps to Reproduce: 1. Select any feed to display the list of articles 2. Select any article to read it in the preview pane 3. Click on the 'search articles' text box 4. Select some other article 5. Notice that the focus is still on the search text box 6. Try to delete the selected article by pressing delete key 7. Nothing happens because the search text box still has the focus 8. The only way to get out is to click somewhere in the preview pane to shift focus out of the search text box and then press Delete key Akregator version: 5.2.2 Using: KDE Frameworks 5.23.0 Qt 5.6.0 (built against 5.6.0) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 352644] FTP shares exported by eShare app on Android are inaccessible from Dolphin with "Could not enter folder ." error message
https://bugs.kde.org/show_bug.cgi?id=352644
--- Comment #5 from Syam <get.so...@gmail.com> ---
I followed the instructions, and this is what comes up in ~/.xsession-errors:
kf5.kinit.klauncher: KLauncher: launching new slave
"/usr/lib64/qt5/plugins/kf5/kio/ftp.so" with protocol= "ftp" args= ("ftp",
"local:/run/user/1000/klauncherXM4514.1.slave-socket",
"local:/run/user/1000/dolphinBC5940.4.slave-socket")
kf5.kinit.klauncher: "/usr/lib64/qt5/plugins/kf5/kio/ftp.so" (pid 5961) up and
running.
error() called twice! Please fix the KIO slave.
Can't open for listing
error() called twice! Please fix the KIO slave.
kf5.kservice.sycoca: checking file timestamps
org.kde.kurifilter-shorturi: "ftp://192.168.0.3:6262;
org.kde.kurifilter-shorturi: path = "" isLocalFullPath= false exists= false
url= QUrl("ftp://192.168.0.3:6262;)
org.kde.kurifilter-ikws: "ftp://192.168.0.3:6262; :
QUrl("ftp://192.168.0.3:6262;) , type = 0
kf5.kinit.klauncher: KLauncher: launching new slave
"/usr/lib64/qt5/plugins/kf5/kio/ftp.so" with protocol= "ftp" args= ("ftp",
"local:/run/user/1000/klauncherXM4514.1.slave-socket",
"local:/run/user/1000/dolphinHf5940.5.slave-socket")
kf5.kinit.klauncher: "/usr/lib64/qt5/plugins/kf5/kio/ftp.so" (pid 5966) up and
running.
error() called twice! Please fix the KIO slave.
Can't open for listing
error() called twice! Please fix the KIO slave.
--
You are receiving this mail because:
You are watching all bug changes.
[kio] [Bug 352644] FTP shares exported by eShare app on Android are inaccessible from Dolphin with "Could not enter folder ." error message
https://bugs.kde.org/show_bug.cgi?id=352644 --- Comment #3 from Syam <get.so...@gmail.com> --- Can somebody please take a look at this. If I need to do something to provide more debug info, do let me know. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353195] Copy error for folders with mixed files & folders in Split View
https://bugs.kde.org/show_bug.cgi?id=353195 --- Comment #17 from Syam <get.so...@gmail.com> --- (In reply to Kai Dombrowe from comment #16) I can reproduce this at will on Fedora too. Fedora 23, x86-64 Dolphin 15.12.1 KDE Frameworks 5.19.0 Qt 5.5.1 (built against 5.5.1) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 36065] dragging from a window should not raise it
https://bugs.kde.org/show_bug.cgi?id=36065 --- Comment #49 from Syam <get.so...@gmail.com> --- (In reply to Syam from comment #48) > (In reply to Martin Gräßlin from comment #47) > > (In reply to Syam from comment #46) > > > > Changing the action to be performed on release instead of press would be > > rather weird. The window would not activate till you release. That's not > > what a user (and applications) expects. > > Is it really weird? I wonder how it is done on Windows? Does the background > window raise at mouse-down itself or only on 'click', i.e. after mouse-up? I > have to boot in to a Windows machine before confirming. Just checked on Windows. You are right. The raise happens on mouse down itself, unless its a drag. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 36065] dragging from a window should not raise it
https://bugs.kde.org/show_bug.cgi?id=36065 --- Comment #48 from Syam <get.so...@gmail.com> --- (In reply to Martin Gräßlin from comment #47) > (In reply to Syam from comment #46) > > The problem is that this raise happens not on 'click' but on mouse-down > > itself. > > This is correct, the raise happens on press if that's the action you > configured for what happens on click on inactive window. This is > configurable. If you don't like the default of "Activate, Raise & Pass > Click" change it to "Activate & Pass Click". This has been suggested earlier. But it doesn't really work, because the setting is really for mouse-down and not a 'click' (which is completed at mouse-up). With "Activate and Pass click", the window won't be raised after one click. The user needs to click on it again to raise it. And that is indeed weird, I agree. > > Changing the action to be performed on release instead of press would be > rather weird. The window would not activate till you release. That's not > what a user (and applications) expects. Is it really weird? I wonder how it is done on Windows? Does the background window raise at mouse-down itself or only on 'click', i.e. after mouse-up? I have to boot in to a Windows machine before confirming. > If we had any chance to know that > the user intends to drag we could perform a different strategy. I see from some earlier comments that the devs are stuck on this 'angle' to solve the problem. But as mentioned in the original report, 'raising at mouse-up and not immediately after mouse-down' would solve it without any need to know if a drag is being done. > > To me the issue is fixed. This bug report contains multiple suggestions on > how it should behave. Several of them even contradicting. Well, the original report mentions one problem and one solution. I understand that it is difficult to implement this with current technology - as pointed out in some earlier comment, on current Linux desktops & GUI libraries, everything seems to happen at mouse-down and not on mouse-clicks. > > Now as I'm the only one here who probably has tried this out, I ask you to > first try it before starting discussions about the state of this bug report. I am deeply sorry if my earlier comment offended you. I was afraid if it'd come out like this. But I didn't mean any disrespect. I have very high regards for devs, especially you :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 36065] dragging from a window should not raise it
https://bugs.kde.org/show_bug.cgi?id=36065 --- Comment #46 from Syam <get.so...@gmail.com> --- (In reply to Martin Gräßlin from comment #45) > > I'm not sure if that'd suffice. Consider the situation: > > We considered this situation during our discussions and came to the > conclusion that it's out of scope. The drag is performed from the active > window, for the compositor it's impossible to know that the user clicked the > window to perform a drag and that's also not how the Wayland protocol allows > to start a drag (the click must(!) be passed to the window). The problem is that this raise happens not on 'click' but on mouse-down itself. > > There are multiple ways now to circumvent the problem: Exactly! These are ways to 'circumvent' the problem. The problem exists and it is disappointing to see that it'd still need to be worked around even though we now have a perfect opportunity to fix this - Wayland new Qt etc etc. > > We also think that the users are able to realize that they cannot drag from > a maximized window and will change the geometry before. Just like users use > split screen in Dolphin to better support drag'n'drop. Hmm.. Users are not just 'able' to realise. They are forced to. And all these workaround statements can be equally applied to removing drag & drop altogether (for Dolphin, for example) saying that "users can just do Ctrl+C/X & Ctrl+V". Anyway, if this is how we are 'fixing' this bug, please close it as WONTFIX rather than FIXED. Because that's what's happening to this bug report. No offense. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 36065] dragging from a window should not raise it
https://bugs.kde.org/show_bug.cgi?id=36065 --- Comment #44 from Syam <get.so...@gmail.com> --- (In reply to Martin Gräßlin from comment #42) > > So far we concluded that the best approach is to implement a raise on hover > approach. As soon as the mouse enters another window during drag that one > will be raised to give a clear field for the drop. I'm not sure if that'd suffice. Consider the situation: 1. The 'source' window is behind the 'destination' window initially 2. The source window would cover the destination window completely if it is raised 3. Because the source window is behind the destination window initially, the destination window is visible 4. Now the user wants to drag something from the source window to the destination window 5. The user starts to drag some item from the source window. 6. If the source window is raised, the destination window is no longer visible so 'hovering' over it is not possible! PS: I am extremely happy to see this bug being worked up on. Thanks a million for all the great work you guys are doing. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 359049] New: Extracting a file by drag and drop from a ZIP archive creates the whole directory structure
https://bugs.kde.org/show_bug.cgi?id=359049 Bug ID: 359049 Summary: Extracting a file by drag and drop from a ZIP archive creates the whole directory structure Product: ark Version: 2.19 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kdemail.net Reporter: get.so...@gmail.com CC: rak...@freebsd.org Selecting a single file from a zip archive and trying to extract it by drag & drop to a Dolphin window, creates the whole directory structure. This doesn't happen for tar.bz2 or tar.gz archives where only the selected file is created. The observation is same as bug#208384, but it now happens only with zip files. Haven't tried with 7z or other formats. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353195] Copy error for folders with mixed files & folders in Split View
https://bugs.kde.org/show_bug.cgi?id=353195 Syam <get.so...@gmail.com> changed: What|Removed |Added CC||get.so...@gmail.com --- Comment #14 from Syam <get.so...@gmail.com> --- I hit this bug while doing something exactly as described in comment #13. Fedora 23 x86-64, Dolphin Version 15.08.1 KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) -- You are receiving this mail because: You are watching all bug changes.
