[frameworks-baloo] [Bug 353874] Baloo does not remove deleted files from index
https://bugs.kde.org/show_bug.cgi?id=353874 Klaus changed: What|Removed |Added CC||bauer.klaus.die...@gmail.co ||m --- Comment #32 from Klaus --- I came to this bug report via this Reddit discussion: https://www.reddit.com/r/kde/comments/nud5kj/outdated_file_results_in_application_launcher/ It describes a possible tightly related issue, where search results in KRunner and Application Launcher may lag behind the results in baloo itself, indicating that there may be some unnecessary intermediate caching. E.g. "baloosearch cardona" already gives the expected result, but KRunner/Application Launcher give no result, or an outdated location. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 310153] Images are not visible in the Main Image Window of Digikam, if the files are created as relative links.
https://bugs.kde.org/show_bug.cgi?id=310153 --- Comment #4 from Klaus --- Hello Gilles, Thank you for your message. Unfortunately I haven't followed the development of digikam in the last few years as I have little time for my photos. I don't use MS Windows, but currently openSUSE Leap 15.5 with KDE. To reproduce the error there, I installed digikam version 7.9.0 as a test and created two links via console - relative and absolute (see file test_links_digikam.txt). The photos of these two links are presented correctly in digikam (see screenshot 105.jpg). Therefore, apparently the problem I reported in 2012 no longer exists. I apologise for not following up on my bugreport from back then in the meantime. Many greetings Klaus Am 24.10.23 um 08:09 schrieb bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=310153 > > --- Comment #3 from caulier.gil...@gmail.com --- > Klaus, > > The digiKam 8.2.0 pre-release for Windows is available for testing : > > https://files.kde.org/digikam/ > > Problem still reproducible on your computer ? > > Thanks in advance > > Gilles Caulier > -- In der Laach 75a 56072 Koblenz Tel. 0261 43939 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407049] Import fails to detect duplicate photos
https://bugs.kde.org/show_bug.cgi?id=407049 klaus changed: What|Removed |Added CC||kmon...@gmail.com --- Comment #7 from klaus --- Created attachment 129333 --> https://bugs.kde.org/attachment.cgi?id=129333&action=edit Fail case where only 2 of 3 duplicates were found. This search includes 2 separate folders. One folder contains the original. The other folder ("testSearch") contains 2 duplicates of the original. The search only found the duplicates within one folder. The search unfortunately did not find duplicates among 2 separate folders. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407049] Import fails to detect duplicate photos
https://bugs.kde.org/show_bug.cgi?id=407049 --- Comment #8 from klaus --- Created attachment 129334 --> https://bugs.kde.org/attachment.cgi?id=129334&action=edit Success case where image search found all 3 duplicates. Here you can see in the Image search tab, the digiKam was able to find all 3 duplicates that exist among 2 separate folders. This kind of functionality was expected in the Duplicates search, where it only found 2 of 3 duplicates. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407049] Import fails to detect duplicate photos
https://bugs.kde.org/show_bug.cgi?id=407049 --- Comment #9 from klaus --- Eureka! I just found out that my Similarity min/max range of 100/100 was too strict. When I change the similarity range to 99/100, the search found all my duplicates! Hopefully this helps! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407049] Import fails to detect duplicate photos
https://bugs.kde.org/show_bug.cgi?id=407049 --- Comment #10 from klaus --- One more comment - There still seems to be some room for improvement with this Similarity/Duplicates Search. Even with a range of 99/100 the system couldn't find a file that is a straight duplicate in 2 separate folders. Same filename, same everything (except minor metadata difference post copy operation, maybe). When I set the range to 98/100 the image duplicate appears. This file is an exact copy so it should appear with 100/100 range. I can move forward with this, but hopefully it can still be fixed. Great work btw, thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407049] Import fails to detect duplicate photos
https://bugs.kde.org/show_bug.cgi?id=407049 --- Comment #12 from klaus --- Maik, I can agree, right now it does appear to be working with 100% Similarity among albums/folders I'm working with now. Strange how my initial test case was clearly not working. Hopefully I can find something more reproducible. I forgot to mention I'm using digiKam 6.4.0 Windows 10 64bit. Thanks for your time and effort, Klaus -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 410936] Google account address book synchronisation issues
https://bugs.kde.org/show_bug.cgi?id=410936 Klaus changed: What|Removed |Added CC||sk...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416463] New: Scrollbar on the right looks a bit strange
https://bugs.kde.org/show_bug.cgi?id=416463 Bug ID: 416463 Summary: Scrollbar on the right looks a bit strange Product: Discover Version: 5.17.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: wwa...@mailbox.org CC: aleix...@kde.org Target Milestone: --- Created attachment 125242 --> https://bugs.kde.org/attachment.cgi?id=125242&action=edit Discover SUMMARY A thin line of the scrollbar goes through the individual boxes with the program description. See also screenshot. STEPS TO REPRODUCE 1. Start discovery and Applications 2. Check scrollbar at the right 3. OBSERVED RESULT Thin line goes through the individual boxes with the program description. EXPECTED RESULT The individual boxes with the program description should not cross the scrollbar. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (preview) (available in About System) KDE Plasma Version: 5.17.90 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable
https://bugs.kde.org/show_bug.cgi?id=278935 klaus changed: What|Removed |Added CC||klaus3b-...@yahoo.de --- Comment #3 from klaus --- I currently use JPhotoTagger (http://jphototagger.org/) on win-pc and APhotoManger (https://github.com/k3b/APhotoManager/) on android to manage my 12000 photos. JPhotoTagger has hard coded "write changes only to sidecar file" and currently both use the naming convention $BASENAME.xmp so i cannot import the meta data to digiKam without renaming 12000 xmp sidecar files. I also agree that $BASENAME.$EXT.xmp makes more sense but adding this option would increase interoperability and allows me to use both JPhotoTagger and digiKam at the same time I have just added this issue to APhotoManager https://github.com/k3b/APhotoManager/issues/84 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 302924] Versioning of Metadata
https://bugs.kde.org/show_bug.cgi?id=302924 klaus changed: What|Removed |Added CC||klaus3b-...@yahoo.de --- Comment #3 from klaus --- > There is already a photo management software which provide this feature ? I use git to store my xmp sidecar files which gives me metadata history with undo functionality. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379503] New: When detecting a new jpg with xmp sidecarfile in album: tags are not read/lost
https://bugs.kde.org/show_bug.cgi?id=379503 Bug ID: 379503 Summary: When detecting a new jpg with xmp sidecarfile in album: tags are not read/lost Product: digikam Version: 5.4.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags Assignee: digikam-de...@kde.org Reporter: klaus3b-...@yahoo.de Target Milestone: --- How to reproduce: using a file manager copy some test.jpg/test.jpf.xmp file to an album-folder in the albumview select the new image test.jpg in thumbnail view note that the tags of test.jpg/test.jpf.xmp are not displayed below the thumbnail the metadata view shows that there is tag info: File name: test.jpg (XMP Schema) >>> digiKam schema <<< Tags List : Unavailable >>> Dublin Core <<< Subject : tag1, tag2 >>> Microsoft Photo <<< Last Keyword IPTC : Unavailable Last Keyword XMP : Unavailable Rating Percent : Unavailable File name: test.jpg (IPTC Records) >>> IIM Application 2 <<< Keywords : tag1 Subject : Unvailable Settings/Configure/Metadata/Advanced/Tags/ReadOptions : Xmp.dc.subject is first and checked After context-menu on thumbnail/AssignTag/tag3 The thumbnail text displays "test3" the old tags tag1 and tag2 are lost the metadata view shows that there is tag info: File name: test.jpg (XMP Schema) >>> digiKam schema <<< Tags List : test3 >>> Dublin Core <<< Subject : test3 >>> Microsoft Photo <<< Last Keyword IPTC : Unavailable Last Keyword XMP : test3 File name: test.jpg (IPTC Records) >>> IIM Application 2 <<< Keywords : test3 Subject : Unvailable This issue may be related to https://bugs.kde.org/show_bug.cgi?id=379049 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379503] When detecting a new jpg with xmp sidecarfile in album: tags are not read/lost
https://bugs.kde.org/show_bug.cgi?id=379503 klaus changed: What|Removed |Added Platform|Other |MS Windows Keywords||reproducible -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #7 from klaus --- I see, the "unique base filename" makes it much more complicated ;-( how frequent are these naming conflicts so that code must take care of it? On the android/APHotoManager side i will ignore the problem in the first run. Move/rename/delete of img.jpg will also handle img.xmp and img.jpg.xmp if they exist (no matter what xmp-naming-convention the seggings dialog has) if there is imp.jpg and img.jpeg the first one beeing moved/deleted/renamed wins the media scanner will assing the content of img.xmp to both: img.jpg and img.jpeg xmp update policy: * if there is imp.jpg.xmp update this file * else if there is img.xmp update this file * else if there is no xmp file yet create it according to xmp-naming-convention settings -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 464615] Support Enhanced Open (OWE) Wi-Fi security option
https://bugs.kde.org/show_bug.cgi?id=464615 Tobias Klaus changed: What|Removed |Added CC||ek+...@meskal.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475872] With an NVIDIA GPU on X11, resizing windows choppy when Pager widget is enabled
https://bugs.kde.org/show_bug.cgi?id=475872 Klaus Zipfel changed: What|Removed |Added Summary|With an NVIDIA GPU, |With an NVIDIA GPU on X11, |resizing windows choppy |resizing windows choppy |when Pager widget is|when Pager widget is |enabled |enabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475872] With an NVIDIA GPU on X11, resizing windows choppy when Pager widget is enabled
https://bugs.kde.org/show_bug.cgi?id=475872 --- Comment #2 from Klaus Zipfel --- I just tested it on Wayland, which seems to be unaffected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475872] New: Resizing choppy when pager enabled on nVidia GPUs
https://bugs.kde.org/show_bug.cgi?id=475872 Bug ID: 475872 Summary: Resizing choppy when pager enabled on nVidia GPUs Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: klaus@zipfel.family CC: h...@kde.org Target Milestone: 1.0 Resizing a window becomes extremely choppy when the pager is added to the taskbar on systems using an nVidia GPU. Only tested on X11 with proprietary nVidia driver (Version 535.113.01). STEPS TO REPRODUCE 1. Have a dedicated nVidia GPU as primary GPU + proprietary nVidia driver 2. Add the pager to your taskbar 3. Open e.g. Dolphin and resize it. It feels choppy and delayed 4. Remove all pagers from the taskbar 5. Resizing e.g. Dolphin now is fluent. OBSERVED RESULT Choppy resizing EXPECTED RESULT Fluent resizing SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (latest) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION [1] Link to reddit discussion: https://www.reddit.com/r/kde/comments/yogjmu/extreme_lag_on_window_redrawresize -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453423] Numpad shortcuts don't work in wayland sessions.
https://bugs.kde.org/show_bug.cgi?id=453423 Tobias Klaus changed: What|Removed |Added CC||ek+...@meskal.net --- Comment #11 from Tobias Klaus --- Reproducible on gentoo with: KDE Framework: 5.106.0 KDE Plasma: 5.27.5 Qt: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 482594] Screen sharing/recording fails with error message "Failed to connect PipeWire context"
https://bugs.kde.org/show_bug.cgi?id=482594 Tobias Klaus changed: What|Removed |Added CC||ek+...@meskal.net -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484698] New: Programmabsturz bei Namenseingabe
https://bugs.kde.org/show_bug.cgi?id=484698 Bug ID: 484698 Summary: Programmabsturz bei Namenseingabe Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: klaus@fischler.tirol Target Milestone: --- Wenn ich eine Gesichtsmarkierung selbst definiere, stürzt das Programm beim Eingeben des Namens ab. *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484698] Program crash when entered face tag name.
https://bugs.kde.org/show_bug.cgi?id=484698 --- Comment #2 from Klaus Fischler --- Ok, I have 8.2.0. I will install 8.3.0. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 418811] Events stored in the database not displayed in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=418811 Tobias Klaus changed: What|Removed |Added CC||ek+...@meskal.net --- Comment #10 from Tobias Klaus --- This still happens with kdepim-22.04.0 (gentoo/qt-5.15.3/plasma-5.24.4//kde-framework-5.93) This is a major blocker for usage of kde-pim with ews, as most of my companies events are not displayed. Can someone give me a hint, where one could look for the code that is responsible for filtering? As this bug can also be observed when using Kalendar, I suppose it is within akonadi itself? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 262811] Traffic Volume in ksysguard jumps back to 0 MB when 4 GB are reached
https://bugs.kde.org/show_bug.cgi?id=262811 --- Comment #7 from Klaus Kleber --- I cannot reproduce the exact same issue. Given that I switched to a 64bit system since then (this bug is over 7 years old), this does not surprise me. And a possible overflow at 16 EB is currently not an issue for me :-) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 431773] New: Akonadi-Server and kmail crashes after moving mails from one folder to another
https://bugs.kde.org/show_bug.cgi?id=431773 Bug ID: 431773 Summary: Akonadi-Server and kmail crashes after moving mails from one folder to another Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: kl...@muecknet.de Target Milestone: --- Application: akonadiserver (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.60-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 -- Information about the crash: - What I was doing when the application crashed: At first: I'm hosting nearly 35.000 mails. In the inbox there are nearly 15.000 mails. In summer I was updating from OpenSuse 12.x to Leap 15.2. I was starting kmail/akonadi from the scratch with postgresql. Problems: - Very slow when clicking a collection in kmail and in particular the inbox or other collections with many mails. Sometimes there is a message that it was not possible to find an item. - Often I have to start akonadi-server to see the mails. - Often there a are messages of unknown collections or other indexes. - Archiving of inbox breaks with the hint, there is a mail which is not possible to archive (... but which one?...). - akonadictl fsck reported many missing RIDs After a few days of intensive search in many communities, I found a hint how to solve these problems. - I stopped kmail and korganizer (no more akonadi-clients were activated). - I cleared all cashes in each collection with akonadiconsole (nearly 300 collections) manually ... this repaired a problem with archivng mails in the inbox folder. - Starting kmail and starting of recursive collection synchronization - There were some breaks of akonadiserver while synchronization, so I clicked manually in each collection ... nearly 300 ... - In some collections with finished synchronization by the recursive step above, were found additional mails ... ok ... strange ... - After finishing all these steps, I rebooted the system. It was only a step to reach a new fresh state of all. - Now I created 2 new collections under the inbox colection and I wanted to move older mails from the inbox to these collections for a speed up when accessing the inbox folder. - After three trials with aborting by kmail, I restarted akonadiserver. A part of the selected mails were moved. - Now I started a move again and now akonadiserver was crashing. A start of akonadiserver by clicking on the button in kmail crashed the akonadiserver again and now also kmail. Now I will reboot again after this report. That's my odysee with kmail and akonadi in the whole last week ... and I'm not really amused. Some technical questions: - Why are there two places for the mails? Inside the database and as file structure? I'm developing an application with sqlite with some million entries and references to image files in file system folders. We have to access these with real time conditions for eight channels. - I did also an import of the file structure created by kmail/akonadiserver with the import tool. What is the reason for creating the folder "new" inside an imported folder? What is the reason for saving the mails only inside the database cache and not in the file structure while doing the import step (of the own kmail structure) in difference to receiving mails, which are saved in the file structure? I do not know the reason for this design decision of the two places for the mails, but I think it is the reason for many problems, because of the need to synchronize both in particular with big mail storages. Where can I find a link, how to develop kmail and akonadi? The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted [KCrash Handler] #4 0x7f449cb3e520 in raise () from /lib64/libc.so.6 #5 0x7f449cb3fb01 in abort () from /lib64/libc.so.6 #6 0x7f449d17b016 in ?? () from /usr/lib64/libstdc++.so.6 #7 0x7f449d18688c in ?? () from /usr/lib64/libstdc++.so.6 #8 0x7f449d1868f7 in std::terminate() () from /usr/lib64/libstdc++.so.6 #9 0x7f449d55cf9b in qTerminate () at global/qglobal.cpp:3203 #10 0x7f449d58123b in QThreadPrivate::start (arg=0x55ab1e1b0670) at thread/qthread_unix.cpp:373 #11 0x7f449b9284f9 in start_thread () from /lib64/libpthread.so.0 #12 0x7f449cc00fbf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f4493f2a700 (LWP 10804) "QDBusConnection"): #1 0x7f449932a7b9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f449932a8cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f449d7b93cb in QEventDispatcherGlib::processEvents (this=0x7f448c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x0
[Akonadi] [Bug 431773] Akonadi-Server and kmail crashes after moving mails from one folder to another
https://bugs.kde.org/show_bug.cgi?id=431773 Klaus Mück changed: What|Removed |Added Version|unspecified |5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 431773] Akonadi-Server and kmail crashes after moving mails from one folder to another
https://bugs.kde.org/show_bug.cgi?id=431773 --- Comment #1 from Klaus Mück --- Another crash while moving mails Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 _mm_crc32_u64 (__V=, __C=) at /usr/lib64/gcc/x86_64-suse-linux/7/include/smmintrin.h:848 #5 crc32 (ptr=0xfefd884d04e0, len=, h=) at tools/qhash.cpp:112 #6 0x7f7f5b563e74 in hash (seed=, len=, p=) at tools/qhash.cpp:223 #7 0x5620ad56d22b in QHash::findNode (this=this@entry=0x5620aeacf5b8, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:934 #8 0x5620ad56d89a in QHash::remove (this=this@entry=0x5620aeacf5b8, akey=...) at /usr/include/qt5/QtCore/qhash.h:806 #9 0x5620ad56a8ef in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x5620aeacf580, request=0x7f7ec42135f0, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/src/server/storage/itemretrievalmanager.cpp:179 #10 0x7f7f5b711f4f in QtPrivate::QSlotObjectBase::call (a=0x7f7f4ab75710, r=0x5620aeacf580, this=0x7f7f4c018b10) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=sender@entry=0x7f7f400062c0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f7f4ab75710) at kernel/qobject.cpp:3784 #12 0x7f7f5b712547 in QMetaObject::activate (sender=sender@entry=0x7f7f400062c0, m=m@entry=0x5620ad85a1c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f7f4ab75710) at kernel/qobject.cpp:3657 #13 0x5620ad5bb7e4 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x7f7f400062c0, _t1=, _t2=...) at /usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:135 #14 0x5620ad56e1e4 in Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7f7f400062c0, watcher=) at /usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/src/server/storage/itemretrievaljob.cpp:78 #15 0x7f7f5b711f4f in QtPrivate::QSlotObjectBase::call (a=0x7f7f4ab75900, r=0x7f7f400062c0, this=0x7f7f40003e20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #16 QMetaObject::activate (sender=0x7f7f4c01b7e0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f7f4ab75900) at kernel/qobject.cpp:3784 #17 0x7f7f5b712547 in QMetaObject::activate (sender=, m=m@entry=0x7f7f5c06b5c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f7f4ab75900) at kernel/qobject.cpp:3657 #18 0x7f7f5be4ed5f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:157 #19 0x7f7f5b7129e2 in QObject::event (this=0x7f7f4c01b7e0, e=) at kernel/qobject.cpp:1261 #20 0x7f7f5b6e2311 in doNotify (event=0x7f7f4c01fd50, receiver=0x7f7f4c01b7e0) at kernel/qcoreapplication.cpp:1178 #21 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1164 #22 QCoreApplication::notifyInternal2 (receiver=0x7f7f4c01b7e0, event=0x7f7f4c01fd50) at kernel/qcoreapplication.cpp:1088 #23 0x7f7f5b6e24fe in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7f7f4c01fd50) at kernel/qcoreapplication.cpp:1476 #24 0x7f7f5b6e4ee7 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5620aeb1e810) at kernel/qcoreapplication.cpp:1825 #25 0x7f7f5b6e5488 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1679 #26 0x7f7f5b73fd93 in postEventSourceDispatch (s=0x7f7f40004b70) at kernel/qeventdispatcher_glib.cpp:276 #27 0x7f7f572b04a4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f7f572b0840 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f7f572b08cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f7f5b73f3af in QEventDispatcherGlib::processEvents (this=0x7f7f4b10, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #31 0x7f7f5b6e057a in QEventLoop::exec (this=this@entry=0x7f7f4ab75cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #32 0x7f7f5b50590a in QThread::exec (this=) at thread/qthread.cpp:531 #33 0x7f7f5b5070b2 in QThreadPrivate::start (arg=0x5620aeadd060) at thread/qthread_unix.cpp:361 #34 0x7f7f598ae4f9 in start_thread () from /lib64/libpthread.so.0 #35 0x7f7f5ab86fbf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f7f4b377700 (LWP 9504) "CacheCleaner-Th"): #1 0x7f7f572afc53 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7f572b06eb in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7f572b08cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f7f5b73f3cb in QEventDispatcherGlib::processEvents (this=0x7f7f3c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f7f5b6e057a in QEventLoop::
[kcalc] [Bug 412401] Sometimes chained operations cause 'forgetting' of inserted constants or pasted numbers
https://bugs.kde.org/show_bug.cgi?id=412401 Wolfram Klaus changed: What|Removed |Added CC||wolfram.kl...@fu-berlin.de --- Comment #2 from Wolfram Klaus --- STEPS TO REPRODUCE 1. CLICK 2*[constant]*3: Result is 5 2. CLICK 2*3*[constant]: Result is correct 3. CLICK [constant}*2*3: Result is correct -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403317] New: KMAIL2 segfaults during startup
https://bugs.kde.org/show_bug.cgi?id=403317 Bug ID: 403317 Summary: KMAIL2 segfaults during startup Product: kontact Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ek+...@meskal.net Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.13-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Whenever I try to compose a new Mail (mostly using Strg+N) kmail2 crashes with a segfault. After this happens kmail crashed during startup with the attached backtrace. This happens until I manually remove all autosaved mails from .local/share/kmail2/autosave/. If needed I can supply a backtrace of the inital crash too. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8135731800 (LWP 19357))] Thread 31 (Thread 0x7f7fe9dca700 (LWP 19404)): #0 0x7f812c0528a4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f812c00b229 in g_main_context_query () from /usr/lib64/libglib-2.0.so.0 #2 0x7f812c00b9a7 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f812c00bb3c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8132cd8c5b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f8132c84b4a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f8132ae6b4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f8132af05ef in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0 #9 0x7f813216a56f in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f7fea5cb700 (LWP 19403)): #0 0x7f813215e993 in poll () from /lib64/libc.so.6 #1 0x7f812c00ba29 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f812c00bb3c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8132cd8c5b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f8132c84b4a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f8132ae6b4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f8132af05ef in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0 #8 0x7f813216a56f in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f7feb22a700 (LWP 19402)): #0 0x7f813215e993 in poll () from /lib64/libc.so.6 #1 0x7f812c00ba29 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f812c00bb3c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8132cd8c5b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f8132c84b4a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f8132ae6b4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f8132af05ef in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0 #8 0x7f813216a56f in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f80bcd77700 (LWP 19393)): #0 0x7f8119968a58 in evutil_vsnprintf () from /usr/lib64/libevent-2.1.so.6 #1 0x7f811996bf2d in ?? () from /usr/lib64/libevent-2.1.so.6 #2 0x7f811996c21c in event_warn () from /usr/lib64/libevent-2.1.so.6 #3 0x7f811996d924 in ?? () from /usr/lib64/libevent-2.1.so.6 #4 0x7f81199636f5 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #5 0x7f81235c5331 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f81235e59fb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f812360975f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f8123605141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0 #10 0x7f813216a56f in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f80bd7fa700 (LWP 19385)): #0 0x7f812df1491a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f81235f2ad7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f81235f4037 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f81235f4122 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f81235f91a1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f81235fa53f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f8123605141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0 #8 0x7f813216a56f in clone
[kontact] [Bug 403317] KMAIL2 segfaults during startup
https://bugs.kde.org/show_bug.cgi?id=403317 --- Comment #1 from Tobias Klaus --- After activating/deactivating every of the "Editor Plugins" I could reproduce this by activating the "Share Text" plugin and mitigate this issue by deactivating this plugin. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403317] KMAIL2; "Share Text" plugin segfaults
https://bugs.kde.org/show_bug.cgi?id=403317 Tobias Klaus changed: What|Removed |Added Summary|KMAIL2 segfaults during |KMAIL2; "Share Text" plugin |startup |segfaults -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403317] KMAIL2; "Share Text" plugin segfaults
https://bugs.kde.org/show_bug.cgi?id=403317 Tobias Klaus changed: What|Removed |Added Component|general |mail -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 404135] New: UPNP Plugin not working
https://bugs.kde.org/show_bug.cgi?id=404135 Bug ID: 404135 Summary: UPNP Plugin not working Product: ktorrent Version: 5.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: bugs.kde@agowa338.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enable UPNP plugin 2. Let the plugin try to open ports. OBSERVED RESULT Port does not get opened. EXPECTED RESULT Port is forwarded properly SOFTWARE/OS VERSIONS kTorrent Version: 5.1.1 Operating System: Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.6-arch1-1-ARCH OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4300M CPU @ 2.60GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION The upnp plugin fails silently. It does not open the port, and also not show any warnings within the gui. The following is shown within the stdout log: [code] Tue Feb 5 15:39:33 2019: Detected IGD Debian/wheezy UPnP/1.1 MiniUPnPd/2.0 Tue Feb 5 15:39:33 2019: Downloading XML file http://192.168.3.254:46147/rootDesc.xml Tue Feb 5 15:39:33 2019: Doing port mappings for Debian/wheezy UPnP/1.1 MiniUPnPd/2.0 Tue Feb 5 15:39:33 2019: Forwarding port 6881 (UDP) Tue Feb 5 15:39:33 2019: Forwarding port 7881 (UDP) Tue Feb 5 15:39:33 2019: Forwarding port 8881 (UDP) Tue Feb 5 15:39:33 2019: UPnP: GetExternalIP failed: invalid reply [/code] And a wireshark capture: https://drive.google.com/open?id=1bYY3V6boVy1zpZfakVpixiozlkdWVkGi Opening these ports using upnpc works just fine. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391781] Add support for SIXEL in Konsole
https://bugs.kde.org/show_bug.cgi?id=391781 Klaus Frank changed: What|Removed |Added CC||bugs.kde@agowa338.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391781] Add support for SIXEL in Konsole
https://bugs.kde.org/show_bug.cgi?id=391781 --- Comment #3 from Klaus Frank --- I do not think adding this feature is too much. As xterm already supports it and it has only one MB total in installed package size. I think adding this is very useful, it allows building console applications that can handle captures without relying on the xserver and also works over ssh. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417695] New: Time to display.
https://bugs.kde.org/show_bug.cgi?id=417695 Bug ID: 417695 Summary: Time to display. Product: okular Version: 1.8.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: k.schr...@t-online.de Target Milestone: --- SUMMARY It takes 5 - 10 sec. after clicking on a file, until it is displayed by Okular. Is there an option (settings?) to improve this? (HP Elitebook 840 G5, 1TB SSD, with Win10 up-to-date.) STEPS TO REPRODUCE 1. Each time when Okular is used to display a pdf. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 up-to-date macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 417757] New: LivePreview error popup
https://bugs.kde.org/show_bug.cgi?id=417757 Bug ID: 417757 Summary: LivePreview error popup Product: kile Version: 2.9.93 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: bugs.kde@agowa338.de Target Milestone: --- SUMMARY When live compiling is enabled, it should fail silently if the document was edited while the compile was ongoing. Currently it throws an error popup `Could not open file:///tmp/kile-livepreview.hXnbwm/main.pdf` which disrupts the flow. STEPS TO REPRODUCE 1. Enable LivePreview 2. Set compile time to 1 sec 3. Start typing 4. Stop typing for 1 second and once it starts compiling (indicated by the console text) start typing again. 5. The error popup appears for every letter typed until the compile finished. OBSERVED RESULT Error popup and error message in console ``` [LivePreview-PDFLaTeX] crashed [LivePreview-PDFLaTeX] finished abruptly [LivePreview-PDFLaTeX] Aborted ``` EXPECTED RESULT No popup the LivePreview should in this case just fail or compile the older result, as it was when starting to compile. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux (x86_64) release 5.5.3-arch1-1 (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 (built against 5.14.1) KILE Version: 2.9.93 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412468] New: /etc/plasma/startup is ignored
https://bugs.kde.org/show_bug.cgi?id=412468 Bug ID: 412468 Summary: /etc/plasma/startup is ignored Product: plasmashell Version: 5.16.90 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ek+...@meskal.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Scripts in /etc/plasma/startup/ are not longer executed and thus no Environment variables are exported STEPS TO REPRODUCE 1. Use /etc/plasma/startup/*.sh to export some environment variables 2. upgrade to 1.16.90 3. login OBSERVED RESULT None of the variables set in /etc/plasma/startup/*.sh got exported. EXPECTED RESULT Variables exported in /etc/plasma/startup/*.sh are exported as in the plasma-versions before. Operating System: Gentoo KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 Kernel Version: 5.3.1-gentoo OS Type: 64-bit ADDITIONAL INFORMATION I use x11-Window system and sddm, so /usr/bin/startplasma-x11 seems to be in charge of initializing the desktop-system. I mitigated the issue by copying the scripts in question to ~/.config/plasma-workspace/env/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412468] /etc/plasma/startup is ignored
https://bugs.kde.org/show_bug.cgi?id=412468 Tobias Klaus changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Tobias Klaus --- Gentoo's package "plasma-workspace" ships scripts that use this feature. That's how it got my attention and thus I just assumed this to be a documented feature. Until filing the bug I even thought it is shipped by plasma-workspace. If this is undocumented and there is an alternative I will file a bug on gentoo's bugzilla. However this worked for a really long time (I can't remember when I started using /etc/plasma/startup but I assume it has been while plasma4 still was a thing.) and might break things for others that used it. Since my gpg-agent still worked with plasma-16.5 I am pretty sure it still worked there... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412468] /etc/plasma/startup is ignored
https://bugs.kde.org/show_bug.cgi?id=412468 --- Comment #4 from Tobias Klaus --- This is the gentoo bug report: https://bugs.gentoo.org/695892 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412468] /etc/plasma/startup is ignored
https://bugs.kde.org/show_bug.cgi?id=412468 --- Comment #5 from Tobias Klaus --- Obviously this has already been discovered and here is the right gentoo-bug: https://bugs.gentoo.org/688366 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415068] New: KMail2 crashes when clicking on mails containing pdf-attachments
https://bugs.kde.org/show_bug.cgi?id=415068 Bug ID: 415068 Summary: KMail2 crashes when clicking on mails containing pdf-attachments Product: kontact Version: 5.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ek+...@meskal.net Target Milestone: --- Application: kontact (5.12.3) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.2-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I wanted to open an e-Mail containing a pdf. Thus I clicked on the mail. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fcacfcf2ec0 (LWP 4702))] Thread 54 (Thread 0x7fc936ffd700 (LWP 7119)): #0 0x7fcae3897a6b in __GI___poll (fds=0x7fc92c0029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcae1bc55fe in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcae1bc571f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcae3efb22b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcae3ea11eb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcae3ccc111 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcae3ccd301 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7fcae2682427 in start_thread (arg=) at pthread_create.c:479 #8 0x7fcae38a3d5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 53 (Thread 0x7fc9377fe700 (LWP 7090)): #0 0x7fcae26899f7 in futex_wait_cancelable (private=0, expected=0, futex_word=0x7fca2001ecf8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fcae26899f7 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fca2001eca8, cond=0x7fca2001ecd0) at pthread_cond_wait.c:508 #2 0x7fcae26899f7 in __pthread_cond_wait (cond=0x7fca2001ecd0, mutex=0x7fca2001eca8) at pthread_cond_wait.c:638 #3 0x7fcacceb043b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #4 0x7fcacceb0177 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #5 0x7fcae2682427 in start_thread (arg=) at pthread_create.c:479 #6 0x7fcae38a3d5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 52 (Thread 0x7fc937fff700 (LWP 7089)): #0 0x7fcae26899f7 in futex_wait_cancelable (private=0, expected=0, futex_word=0x7fc937ffead8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fcae26899f7 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fc937ffea88, cond=0x7fc937ffeab0) at pthread_cond_wait.c:508 #2 0x7fcae26899f7 in __pthread_cond_wait (cond=0x7fc937ffeab0, mutex=0x7fc937ffea88) at pthread_cond_wait.c:638 #3 0x7fcadb84dacc in base::ConditionVariable::Wait() () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fcadb84e5b0 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcadb84e6df in base::WaitableEvent::Wait() () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fcadb806216 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fcadb8094ab in base::internal::SchedulerWorker::RunWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fcadb809a14 in base::internal::SchedulerWorker::RunSharedWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7fcadb850a4a in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7fcae2682427 in start_thread (arg=) at pthread_create.c:479 #11 0x7fcae38a3d5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 51 (Thread 0x7fc94693e700 (LWP 6956)): #0 0x7fcae26899f7 in futex_wait_cancelable (private=0, expected=0, futex_word=0x55a927cd1098) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fcae26899f7 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a927cd1048, cond=0x55a927cd1070) at pthread_cond_wait.c:508 #2 0x7fcae26899f7 in __pthread_cond_wait (cond=0x55a927cd1070, mutex=0x55a927cd1048) at pthread_cond_wait.c:638 #3 0x7fcacceb043b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #4 0x7fcacceb0177 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #5 0x7fcae2682427 in start_thread (arg=) at pthread_create.c:479 #6 0x7fcae38a3d5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 50 (Thread 0x7fc9477fe700 (LWP 6861)): #0 0x7fcae26899f7
[amarok] [Bug 411032] New: can not read local collection
https://bugs.kde.org/show_bug.cgi?id=411032 Bug ID: 411032 Summary: can not read local collection Product: amarok Version: unspecified Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Collections/Local Assignee: amarok-bugs-d...@kde.org Reporter: sallgasterno...@hotmail.com CC: ma...@laitl.cz, ralf-eng...@gmx.de Target Milestone: kf5 SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION cant read music files from a second harddisk on the computer. have linux installed parallel, works good here -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356075] Kmail:Failed to transport message. Unable to create SMTP job
https://bugs.kde.org/show_bug.cgi?id=356075 Klaus Toepfer changed: What|Removed |Added CC||k_toep...@baufach-gkr.de --- Comment #4 from Klaus Toepfer --- I confirm this bug. I am unable to send emails -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 477010] Pop up Window fails to show up in Konqueror
https://bugs.kde.org/show_bug.cgi?id=477010 --- Comment #1 from Klaus-Dieter Fietze --- In order to bring some more light into this matter, I recently went through the System Journal and looked for entries related to Konqueror (see attached text file). I found a line that says: “Wayland does not support Qwindow::requestActivate()” So, I switched my desktop session from Plasma (Wayland) to Plasma (X11). Running the X Window System, Konqueror did what it was supposed to do – the requested window opened. It looks like there is a problem with the Qt implementation in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 477010] Pop up Window fails to show up in Konqueror
https://bugs.kde.org/show_bug.cgi?id=477010 --- Comment #2 from Klaus-Dieter Fietze --- Created attachment 166440 --> https://bugs.kde.org/attachment.cgi?id=166440&action=edit System Journal with lines related to Koqueror pop-up window -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 477010] Pop up Window fails to show up in Konqueror
https://bugs.kde.org/show_bug.cgi?id=477010 Klaus-Dieter Fietze changed: What|Removed |Added Version|23.08.2 |23.08.4 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 477010] New: Pop up Window fails to show up in Konqueror
https://bugs.kde.org/show_bug.cgi?id=477010 Bug ID: 477010 Summary: Pop up Window fails to show up in Konqueror Classification: Applications Product: konqueror Version: 23.08.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kjs Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 163160 --> https://bugs.kde.org/attachment.cgi?id=163160&action=edit Konqueor Java & JavaScript settings SUMMARY *** Pop-up Window not shown *** STEPS TO REPRODUCE 1. Open Konqueror's browser function using WebEngine 2. Navigate to the website https://www.10881.ch/ 3. Click the Login button at the upper right corner of the page OBSERVED RESULT Nothing happens ! EXPECTED RESULT In other browsers, like Falkon or Firefox, a window will pop up requesting the login credentials. Konqueror behaves differently, depending on its Java Script settings. > If you tick one of the options "Allow", "Deny" or "Smart" nothing will happen. > If you choose "Ask" Konqueror will ask you, whether it should open a window > with the indicated url. No matter what you choose, nothing will happen. > However, if you copy the displayed url into a new browser window or browser > tab, it will open. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231108 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 ADDITIONAL INFORMATION Please refer to the attached Java & JavaScript settings. It is my guess that it has to with these settings but it may another reason. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 477010] Pop up Window fails to show up in Konqueror
https://bugs.kde.org/show_bug.cgi?id=477010 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 450386] New: Jitsi Meet screen sharing botton has no effect
https://bugs.kde.org/show_bug.cgi?id=450386 Bug ID: 450386 Summary: Jitsi Meet screen sharing botton has no effect Product: konqueror Version: 21.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: webenginepart Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 146820 --> https://bugs.kde.org/attachment.cgi?id=146820&action=edit Systemd output for the time in question SUMMARY *** Jitsi Meet screen sharing does not work *** STEPS TO REPRODUCE 1. Open Jitsi Meet either on their free site https://meet.jit.si/ or any other Jitsi Meet server 2. Start meeting or join in to an existing meeting 3. Hit "Toggle Screen Share" botton in the lower middle part of the screen OBSERVED RESULT Nothing happens. EXPECTED RESULT A dialogue box should appear, asking for the part of the screen to be shared. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220213 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-1-default (64-bit) Graphics Platform: X11 Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 ADDITIONAL INFORMATION Does not work on Falcon either, but works well on Firefox (same machine). -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 436957] Konqueror webbrowser does not download files attached to e-mails
https://bugs.kde.org/show_bug.cgi?id=436957 Klaus-Dieter Fietze changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Klaus-Dieter Fietze --- The problem does not exist anymore. No idea, which update made it dissapear. It works now as expected, at least with my installation: Operating System: openSUSE Tumbleweed 20211120 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-1-default (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434097] Konqueror does not open requested link
https://bugs.kde.org/show_bug.cgi?id=434097 Klaus-Dieter Fietze changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Klaus-Dieter Fietze --- This bug was resolved with one of the latest updates. Now, it works as expected. My setup: Operating System: openSUSE Tumbleweed 20211120 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 437299] Konqueror Bookmarks Editor not able to update some favicons
https://bugs.kde.org/show_bug.cgi?id=437299 --- Comment #1 from Klaus-Dieter Fietze --- Created attachment 143842 --> https://bugs.kde.org/attachment.cgi?id=143842&action=edit Konqueror bookmark editor with favicons Updated Outlook live favicon in the bookmark editor -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 437299] Konqueror Bookmarks Editor not able to update some favicons
https://bugs.kde.org/show_bug.cgi?id=437299 --- Comment #2 from Klaus-Dieter Fietze --- Created attachment 143843 --> https://bugs.kde.org/attachment.cgi?id=143843&action=edit Konqueror bookmarks bar Screen shot shows the Konqueror bookmarks bar after update of Outlook live favicon. The bookmarks editor does find the favicon, but loses the icon for some reason. -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 434427] HTML bookmarks file only partially imported
https://bugs.kde.org/show_bug.cgi?id=434427 --- Comment #1 from Klaus-Dieter Fietze --- I suggest closing this issue as there is a work-around and it seems to be of minor interest. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 451195] New: KDE Kontact crash while closing the application
https://bugs.kde.org/show_bug.cgi?id=451195 Bug ID: 451195 Summary: KDE Kontact crash while closing the application Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Application: kontact (5.19.3 (21.12.3)) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.16.11-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was closing the application when the error message appeared: "KDE Kontact closed unexpectedly" - Unusual behavior I noticed: I would like to stress that I haven't done anything unusal! It is not the first that KDE Kontact closes unexpectedly; there was neverthing unusual before. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, }, > = {_M_head_impl = }, }, }}, }} [KCrash Handler] #6 0x7f038bef8990 in KMReaderMainWin::~KMReaderMainWin (this=, this=) at /usr/src/debug/kmail-21.12.3-1.1.x86_64/src/kmreadermainwin.cpp:117 #7 0x7f038bef8b49 in KMReaderMainWin::~KMReaderMainWin (this=, this=) at /usr/src/debug/kmail-21.12.3-1.1.x86_64/src/kmreadermainwin.cpp:119 #8 0x7f041b80c24f in QObject::event (this=0x5605ef68ffc0, e=0x7f03bc06ef80) at kernel/qobject.cpp:1301 #9 0x7f041cb55429 in KXmlGuiWindow::event (this=0x5605ef68ffc0, ev=0x7f03bc06ef80) at /usr/src/debug/kxmlgui-5.91.0-1.1.x86_64/src/kxmlguiwindow.cpp:219 #10 0x7f041c3dea7f in QApplicationPrivate::notify_helper (this=, receiver=0x5605ef68ffc0, e=0x7f03bc06ef80) at kernel/qapplication.cpp:3632 #11 0x7f041b7dfe3a in QCoreApplication::notifyInternal2 (receiver=0x5605ef68ffc0, event=0x7f03bc06ef80) at kernel/qcoreapplication.cpp:1064 #12 0x7f041b7e2e77 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5605ec08f470) at kernel/qcoreapplication.cpp:1821 #13 0x7f041b837d03 in postEventSourceDispatch (s=s@entry=0x5605ec16ce10) at kernel/qeventdispatcher_glib.cpp:277 #14 0x7f0412003e22 in g_main_dispatch (context=0x7f045010) at ../glib/gmain.c:3381 #15 g_main_context_dispatch (context=0x7f045010) at ../glib/gmain.c:4099 #16 0x7f04120041b8 in g_main_context_iterate (context=context@entry=0x7f045010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175 #17 0x7f041200426f in g_main_context_iteration (context=0x7f045010, may_block=1) at ../glib/gmain.c:4240 #18 0x7f041b837384 in QEventDispatcherGlib::processEvents (this=0x5605ec17ee50, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x7f041b7de83b in QEventLoop::exec (this=this@entry=0x7ffc686ec1d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #20 0x7f041b7e6b10 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #21 0x7f041bc8025c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #22 0x7f041c3de9f5 in QApplication::exec () at kernel/qapplication.cpp:2824 #23 0x5605ea383f52 in main (argc=, argv=) at /usr/src/debug/kontact-21.12.3-1.1.x86_64/src/main.cpp:215 [Inferior 1 (process 2619) detached] Possible duplicates by query: bug 450800, bug 450494, bug 450428, bug 450241, bug 449883. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 451237] New: New Contact do not show Names
https://bugs.kde.org/show_bug.cgi?id=451237 Bug ID: 451237 Summary: New Contact do not show Names Product: kaddressbook Version: 5.19.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch CC: to...@kde.org Target Milestone: --- Created attachment 147349 --> https://bugs.kde.org/attachment.cgi?id=147349&action=edit 4 newly created contacts in KAddressbook SUMMARY *** Missing Names in new, manually created Contacts *** STEPS TO REPRODUCE 1. Open KAddressbook 2. Click on "+ New Contact" 3. Click on the three dots right to the "Name" field 4. Enter "Given name" and "Family names" and click "OK" 5. Fill in a phone number in the "Phone" field 6. Click "OK" 7. Search for the name of the just before created contact OBSERVED RESULT I have repeated the procedure 4 times with 4 dummy names. Two of them show up with their initials and their full name; two of them do only show the initials, but not the name. EXPECTED RESULT All newly created contacts should show both, initials as well as "Given name" and "Family names" SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220305 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION - Edit any of the contacts that only display initials - Open the name fields with the three dots button - Add a space behind and delete it - After closing the editor with "OK" the contact will show the initials and the full name -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 451237] New Contact do not show Names
https://bugs.kde.org/show_bug.cgi?id=451237 --- Comment #1 from Klaus-Dieter Fietze --- Created attachment 147350 --> https://bugs.kde.org/attachment.cgi?id=147350&action=edit Same contacts as above after editing their name fields -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 451237] New Contacts do not show Names
https://bugs.kde.org/show_bug.cgi?id=451237 Klaus-Dieter Fietze changed: What|Removed |Added Summary|New Contact do not show |New Contacts do not show |Names |Names -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434173] Konqueror automatic spell checking not working with WebEngine
https://bugs.kde.org/show_bug.cgi?id=434173 --- Comment #2 from Klaus-Dieter Fietze --- Created attachment 143161 --> https://bugs.kde.org/attachment.cgi?id=143161&action=edit Configure Spell Checking in Konqueror's Settings menu -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434173] Konqueror automatic spell checking not working with WebEngine
https://bugs.kde.org/show_bug.cgi?id=434173 --- Comment #3 from Klaus-Dieter Fietze --- The spell check still does not work in Konqueror (though it works well in Kate). Past updates have brought some improvements, though. Now, the Konqueror settings menu lets you choose "Configure Spell Checking". However, when working in any text input window, right click opens a multiple choice, where you can enable spell checking, but when right clicking again, "Spell Checking Enabled" is ticked but the menu point "Languages" below does not offer any choice. Operating System: openSUSE Tumbleweed 20211031 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 Spell checker: Hunspell Dictionaries: myspell de, de_DE, en, en_GB, fr_FR, pt_BR (No ispell nor aspell installed.) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434173] Konqueror automatic spell checking not working with WebEngine
https://bugs.kde.org/show_bug.cgi?id=434173 --- Comment #4 from Klaus-Dieter Fietze --- Created attachment 143162 --> https://bugs.kde.org/attachment.cgi?id=143162&action=edit Related system settings for the spell checker configuration -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434173] Konqueror automatic spell checking not working with WebEngine
https://bugs.kde.org/show_bug.cgi?id=434173 --- Comment #5 from Klaus-Dieter Fietze --- Created attachment 143163 --> https://bugs.kde.org/attachment.cgi?id=143163&action=edit Related system settings for the spell checker configuration -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 339415] Konqueror does not import bookmarks exported by Konqueror on another computer
https://bugs.kde.org/show_bug.cgi?id=339415 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch --- Comment #4 from Klaus-Dieter Fietze --- I am running into the same problem when trying to import Firefox bookmarks exported into an html file. The Konqueror import function does only import a few of the numerous bookmarks. The folder structure reproduces quite poorly and incompletely. In order to avoid frustration for users I think it is better to remove this feature as long as it is not working properly. Konqueror version 20.12.2 Operating System: openSUSE Tumbleweed 20210222 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 431004] Screen sharing non-functional at meet.jit.si (Jitsi Meet)
https://bugs.kde.org/show_bug.cgi?id=431004 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch --- Comment #2 from Klaus-Dieter Fietze --- I am experiencing the same behaviour with Falkon as well as with Konqueor, whereas Firefox works as expected. Operating System: openSUSE Tumbleweed 20210302 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 Would be nice to find a solution in order to abandon Firefox & Co. Thank you, Klaus -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434173] Konqueror automatic spell checking not working with WebEngine
https://bugs.kde.org/show_bug.cgi?id=434173 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch --- Comment #1 from Klaus-Dieter Fietze --- I confirm the described behaviour. Would like to use spell checking in the webmail client but "Settings" --> "Configure Spell Checking" does not do anthing. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210508 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Konqueror Version: 21.04.0 webenginepart version: 21.04.0 Kernel Version: 5.12.0-2-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 436957] New: Konqueror webbrowser does not download files attached to e-mails
https://bugs.kde.org/show_bug.cgi?id=436957 Bug ID: 436957 Summary: Konqueror webbrowser does not download files attached to e-mails Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: webenginepart Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 138351 --> https://bugs.kde.org/attachment.cgi?id=138351&action=edit Error message that pops up when trying to download e-mail attachments SUMMARY Konqueror webbrowser does not download files attached to e-mails STEPS TO REPRODUCE 1. Open Swisscom Webmail https://www.bluewin.ch/de/email/ 2. Log in 3. Open e-mail with attachment 4. Scroll down to attachment and click on "Download" OBSERVED RESULT Download window opens allowing to choose the folder and the name of the file to be downloaded New window opens with KIOExec error message: "Could not connect to host rich-v01.bluewin.ch: SSL negotiation failed." Only confirmation with OK is possible (see attached picture) EXPECTED RESULT After having chosen the folder and the desired file name, Konqueror should download the file to the requested place Remark: Preview works as expected! SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210508 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Konqueror Version: 21.04.0 webenginepart version: 21.04.0 Kernel Version: 5.12.0-2-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 ADDITIONAL INFORMATION No problem with Swisscom Webmail when using Firefox or Falkon Generally, it would be more comfortable if Konqueror proposed the file name of the attachment instead of showing "Downloader". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch --- Comment #4 from Klaus-Dieter Fietze --- I confirm. Same behaviour with this configuration: Operating System: openSUSE Tumbleweed 20210513 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Konqueror Version: 21.04.0 Kernel Version: 5.12.2-1-default Glad to see that there are still people out there using konqueror! -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 437299] New: Konqueror Bookmarks Editor not able to update some favicons
https://bugs.kde.org/show_bug.cgi?id=437299 Bug ID: 437299 Summary: Konqueror Bookmarks Editor not able to update some favicons Product: keditbookmarks Version: 21.04.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Application: keditbookmarks (21.04.0) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.3-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Open the Konqueror bookmark editor Right click on the Swiss Meteo entry: https://www.meteosuisse.admin.ch/ Choose "Update Favicon" and confirm After some searching the system says: "Bookmark Editor crashed unexpectedly" No icon was created Note: In some cases it works in others not; but it is always the same cases the work and the same ones that do not work. The crash can be reproduced every time. -- Backtrace: Application: Bookmark Editor (keditbookmarks), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fae0ed25880 (LWP 6872))] [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_acquire, this=) at /usr/include/c++/10/bits/atomic_base.h:741 #7 std::atomic::load (__m=std::memory_order_acquire, this=) at /usr/include/c++/10/atomic:530 #8 QAtomicOps::loadAcquire (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:251 #9 QBasicAtomicPointer::loadAcquire (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:255 #10 QBasicAtomicPointer::operator QThreadData* (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:251 #11 QObjectPrivate::connectImpl (sender=0x5619fb416dd0, signal_index=19, receiver=0x561c9aa20c36, slot=0x7ffec243d650, slotObj=0x5619fb17dad0, type=Qt::AutoConnection, types=0x0, senderMetaObject=0x7fae040b5be0 ) at kernel/qobject.cpp:5053 #12 0x7fae110e20a5 in QObject::connectImpl (sender=sender@entry=0x5619fb416dd0, signal=signal@entry=0x7ffec243d640, receiver=receiver@entry=0x561c9aa20c36, slot=slot@entry=0x7ffec243d650, slotObj=0x5619fb17dad0, type=Qt::AutoConnection, types=0x0, senderMetaObject=) at kernel/qobject.cpp:5001 #13 0x7fae040a31fc in QObject::connect (type=Qt::AutoConnection, slot=(void (QWebEngineView::*)(QWebEngineView * const, const QString &)) 0x7fae040a13a0 , receiver=0x561c9aa20c36, signal=(void (QWebEnginePage::*)(QWebEnginePage * const, const QString &)) 0x7fae04097ac0 , sender=0x5619fb416dd0) at /usr/include/qt5/QtCore/qobject.h:268 #14 QWebEngineViewPrivate::pageChanged(QWebEnginePage*, QWebEnginePage*) [clone .isra.0] (oldPage=oldPage@entry=0x0, newPage=0x5619fb416dd0, this=, this=) at api/qwebengineview.cpp:69 #15 0x7fae040964ea in QWebEnginePagePrivate::bindPageAndView (page=, view=0x5619fb416b30) at api/qwebengineview.h:140 #16 0x7fae040a4d16 in QWebEngineView::page (this=0x5619fb416b30) at api/qwebengineview.cpp:190 #17 0x7fae040e8a42 in WebEnginePart::page (this=this@entry=0x5619fb22c9d0) at /usr/src/debug/konqueror-21.04.0-1.1.x86_64/webenginepart/src/webenginepart.cpp:240 #18 0x7fae040edd2c in WebEnginePart::walletFinishedFormDetection (this=0x5619fb22c9d0, url=..., found=, autoFillableFound=) at /usr/src/debug/konqueror-21.04.0-1.1.x86_64/webenginepart/src/webenginepart.cpp:1038 #19 0x7fae110eac17 in QtPrivate::QSlotObjectBase::call (a=0x7ffec243d8e0, r=0x5619fb22c9d0, this=0x5619fb36ca60) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate (sender=0x5619fb093b90, signal_index=6, argv=argv@entry=0x7ffec243d8e0) at kernel/qobject.cpp:3886 #21 0x7fae110e3f60 in QMetaObject::activate (sender=sender@entry=0x5619fb093b90, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffec243d8e0) at kernel/qobject.cpp:3946 #22 0x7fae04115d7d in WebEngineWallet::formDetectionDone (_t3=, _t2=true, _t1=..., this=0x5619fb093b90) at /usr/src/debug/konqueror-21.04.0-1.1.x86_64/build/webenginepart/src/kwebenginepartlib_autogen/include/moc_webenginewallet.cpp:280 #23 operator() (forms=..., __closure=0x5619fb51b610) at /usr/src/debug/konqueror-21.04.0-1.1.x86_64/webenginepart/src/webenginewallet.cpp:148 #24 std::__invoke_impl&, const QVector&> (__f=...) at /usr/include/c++/10/bits/invoke.h:60 #25 std::__invoke_r&, const QVector&> (__fn=...) at /usr/include/c++/10/bits/invoke.h:153 #26 std::_Function_handler&), WebEngineWallet::detectAndFillPageForms(WebEnginePage*):: >::_M_invoke(const std::_Any_data &, const QVector &) (__functor=..., __args#0=...) at /usr/include/c++/10/bits/st
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 --- Comment #21 from Klaus-Dieter Fietze --- (In reply to Markus from comment #20) > Should be fixed in 21.04.2 and 21.08.0, so this can be closed, right? As I already said above, it is fixed. >From my point of view, this bug can be closed. Thanks again for your work! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 --- Comment #16 from Klaus-Dieter Fietze --- To my great joy, this feature works again. Thank you ! Operating System: openSUSE Tumbleweed 20210614 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-1-default (64-bit) I am glad that I can use Konqueror again. It deserves more attention and a bigger user community. How about spelling? Is there some work in progress to make work? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434097] New: Konqueror does not open requested link
https://bugs.kde.org/show_bug.cgi?id=434097 Bug ID: 434097 Summary: Konqueror does not open requested link Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- SUMMARY When Konqueror is the default web browser it does not open web pages that are requested from other applications such as terminal or KDE Kontact. STEPS TO REPRODUCE 1. set Konqueror to be the default browser: System settings –> Applications –> Default Applications –> Web browser –> Konqueror 2. open a terminal window and enter: “xdg-open https://kde.org/” OBSERVED RESULT The Konqueror icon starts jumping up and down and keeps jumping, probably till eternity. The requested web page never opens. EXPECTED RESULT When I set Firefox to be the default web browser the requested web page opens without any delay. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210302 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 ADDITIONAL INFORMATION When clicking on an url in an open Konqueror web page it works fine. Thank you for looking into this bug. Best regards, Klaus -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 434099] New: Falkon seems to lack settings (QWebEngineUrlScheme)
https://bugs.kde.org/show_bug.cgi?id=434099 Bug ID: 434099 Summary: Falkon seems to lack settings (QWebEngineUrlScheme) Product: Falkon Version: 3.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 136453 --> https://bugs.kde.org/attachment.cgi?id=136453&action=edit Error messages on Terminal SUMMARY When Falkon is the default web browser it does open web pages that are requested from a terminal but produces loads of error messages. STEPS TO REPRODUCE 1. set Falkon to be the default browser: System settings –> Applications –> Default Applications –> Web browser –> Falkon 2. open a terminal window and enter: “xdg-open https://kde.org/” OBSERVED RESULT The requested web page opens but the terminal window full of error messages (see attachment). EXPECTED RESULT When I set Firefox to be the default web browser the requested web page opens without any delay and without error messages. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210302 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 ADDITIONAL INFORMATION When clicking on an url in an open Falkon web page it works fine, of course, I cannot see potential error messages. Thank you for looking into this bug. Best regards, Klaus -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 434099] Falkon seems to lack settings (QWebEngineUrlScheme)
https://bugs.kde.org/show_bug.cgi?id=434099 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 434097] Konqueror does not open requested link
https://bugs.kde.org/show_bug.cgi?id=434097 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379408] Sender/Receiver displays Sender for both Inbox and Sent Messages
https://bugs.kde.org/show_bug.cgi?id=379408 --- Comment #2 from Klaus-Dieter Fietze --- Recently, my 12 years old laptop broke and I had to by a new computer. I decided to install openSUSE Tumbleweed: Operating System: openSUSE Tumbleweed 20210302 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 The problem I reported above does not exist anymore. Thank you, Klaus -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379408] Sender/Receiver displays Sender for both Inbox and Sent Messages
https://bugs.kde.org/show_bug.cgi?id=379408 Klaus-Dieter Fietze changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379408] Sender/Receiver displays Sender for both Inbox and Sent Messages
https://bugs.kde.org/show_bug.cgi?id=379408 Klaus-Dieter Fietze changed: What|Removed |Added CC||klaus-dieter.fietze@bluewin ||.ch -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 434427] New: HTML bookmarks file only partially imported
https://bugs.kde.org/show_bug.cgi?id=434427 Bug ID: 434427 Summary: HTML bookmarks file only partially imported Product: keditbookmarks Version: 20.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 136688 --> https://bugs.kde.org/attachment.cgi?id=136688&action=edit Bookmarks backup file that works with Firefox but not with Konqueror SUMMARY HTML bookmarks file only partially imported STEPS TO REPRODUCE 1. Open "Bookmarks" > "Edit Bookmarks" from the main menu 2. Choose "File" > "Import" > "Import Mozilla Bookmarks" 3. Select the attached html bookmarks file and Enter OBSERVED RESULT Import runs without error message. However, only the first two folders and some single bookmarks were imported. EXPECTED RESULT The entire bookmarks structure containing several folders and subfolders shall be imported. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210311 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.4-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 ADDITIONAL INFORMATION I have imported the bookmarks file into Falkon and have removed a couple of tab stops from descriptions. Then I saved the bookmarks from Falkon and imported them to Konqueror - this time all bookmarks were correctly imported. -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 434763] New: keditbookmarks crashes when updating particular favicons
https://bugs.kde.org/show_bug.cgi?id=434763 Bug ID: 434763 Summary: keditbookmarks crashes when updating particular favicons Product: keditbookmarks Version: 20.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Application: keditbookmarks (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.6-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Started "Edit Bookmarks" from the main menu Went to this entry of the Bookmarks Toobar: https://www.meteosuisse.admin.ch/ The name of the entry is spelled "Météo" (special characters) Right click on the line and choose "Update favicon" - Custom settings of the application: Default web browser engine is: qtwebengine Pixmap cash: 94 kB no proxy cookies enabled The crash can be reproduced every time. -- Backtrace: Application: Bookmark Editor (keditbookmarks), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_acquire, this=) at /usr/include/c++/10/bits/atomic_base.h:741 #5 std::atomic::load (__m=std::memory_order_acquire, this=) at /usr/include/c++/10/atomic:523 #6 QAtomicOps::loadAcquire (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:251 #7 QBasicAtomicPointer::loadAcquire (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:255 #8 QBasicAtomicPointer::operator QThreadData* (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:251 #9 QObjectPrivate::connectImpl (sender=0x5563f4e04dd0, signal_index=19, receiver=0x5566a2d2a69a, slot=0x7ffd9d1ffd50, slotObj=0x5563f4f8b970, type=Qt::AutoConnection, types=0x0, senderMetaObject=0x7f211c347bc0 ) at kernel/qobject.cpp:5053 #10 0x7f21298809c5 in QObject::connectImpl (sender=sender@entry=0x5563f4e04dd0, signal=signal@entry=0x7ffd9d1ffd40, receiver=receiver@entry=0x5566a2d2a69a, slot=slot@entry=0x7ffd9d1ffd50, slotObj=0x5563f4f8b970, type=Qt::AutoConnection, types=0x0, senderMetaObject=) at kernel/qobject.cpp:5001 #11 0x7f211c33545c in QObject::connect (type=Qt::AutoConnection, slot=(void (QWebEngineView::*)(QWebEngineView * const, const QString &)) 0x7f211c333570 , receiver=0x5566a2d2a69a, signal=(void (QWebEnginePage::*)(QWebEnginePage * const, const QString &)) 0x7f211c32a070 , sender=0x5563f4e04dd0) at /usr/include/qt5/QtCore/qobject.h:268 #12 QWebEngineViewPrivate::pageChanged(QWebEnginePage*, QWebEnginePage*) [clone .isra.0] (oldPage=oldPage@entry=0x0, newPage=0x5563f4e04dd0, this=, this=) at api/qwebengineview.cpp:69 #13 0x7f211c32866a in QWebEnginePagePrivate::bindPageAndView (page=, view=0x5563f4e0ce00) at api/qwebengineview.h:140 #14 0x7f211c336f76 in QWebEngineView::page (this=0x5563f4e0ce00) at api/qwebengineview.cpp:190 #15 0x7f211c37aa72 in WebEnginePart::page (this=) at /usr/src/debug/konqueror-20.12.3-1.1.x86_64/webenginepart/src/webenginepart.cpp:227 #16 0x7f211c386efc in WebEnginePart::walletFinishedFormDetection (this=0x5563f4d6a250, url=..., found=, autoFillableFound=) at /usr/src/debug/konqueror-20.12.3-1.1.x86_64/webenginepart/src/webenginepart.cpp:1021 #17 0x7f2129889946 in QtPrivate::QSlotObjectBase::call (a=0x7ffd9d1fffe0, r=0x5563f4d6a250, this=0x5563f4eaef40) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate (sender=0x5563f4c4a410, signal_index=6, argv=argv@entry=0x7ffd9d1fffe0) at kernel/qobject.cpp:3886 #19 0x7f2129882c60 in QMetaObject::activate (sender=sender@entry=0x5563f4c4a410, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd9d1fffe0) at kernel/qobject.cpp:3946 #20 0x7f211c3a89fd in WebEngineWallet::formDetectionDone (_t3=, _t2=true, _t1=..., this=0x5563f4c4a410) at /usr/src/debug/konqueror-20.12.3-1.1.x86_64/build/webenginepart/src/kwebenginepartlib_autogen/include/moc_webenginewallet.cpp:280 #21 operator() (forms=..., __closure=0x5563f4d9e8e0) at /usr/src/debug/konqueror-20.12.3-1.1.x86_64/webenginepart/src/webenginewallet.cpp:148 #22 std::__invoke_impl&, const QVector&> (__f=...) at /usr/include/c++/10/bits/invoke.h:60 #23 std::__invoke_r&, const QVector&> (__fn=...) at /usr/include/c++/10/bits/invoke.h:153 #24 std::_Function_handler&), WebEngineWallet::detectAndFillPageForms(WebEnginePage*):: >::_M_invoke(const std::_Any_data &, const QVector &) (__functor=..., __args#0=...) at /usr/include/c++/10/bits/std_function.h:291 #25 0x7f211c3a1132 in std::function const&)>::operator()(QVector const&am
[kate] [Bug 424073] New: Slow start on automounted home
https://bugs.kde.org/show_bug.cgi?id=424073 Bug ID: 424073 Summary: Slow start on automounted home Product: kate Version: 18.12.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kl...@vink-slott.dk Target Milestone: --- SUMMARY Searches /home for files triggers automounter which causes slow startup STEPS TO REPRODUCE 1. configure or test on a system using automount for /home 2. start kate OBSERVED RESULT Extract from using strace: 17:09:01.751209 openat(AT_FDCWD, "/dev/tty", O_RDONLY) = 12 17:09:01.751243 getcwd("/home/klaus", 4096) = 12 17:09:01.751283 lstat("/home", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 17:09:01.751313 lstat("/home/klaus", {st_mode=S_IFDIR|0710, st_size=8192, ...}) = 0 17:09:01.751353 stat("/home/klaus/.kateproject", 0x7fffe2994d30) = -1 ENOENT (No such file or directory) 17:09:01.751385 stat("/home/klaus/.git", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:01.751416 stat("/home/klaus/.svn", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:01.751446 stat("/home/klaus/.hg", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:01.751481 stat("/home", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 17:09:01.751512 lstat("/home", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 17:09:01.751544 stat("/home/.kateproject", 0x7fffe2994d30) = -1 ENOENT (No such file or directory) 17:09:04.994289 stat("/home/.git", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:08.263022 stat("/home/.svn", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:11.522903 stat("/home/.hg", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:14.774833 stat("/", {st_mode=S_IFDIR|0755, st_size=174, ...}) = 0 17:09:14.774890 stat("/.kateproject", 0x7fffe2994d30) = -1 ENOENT (No such file or directory) 17:09:14.774937 stat("/.git", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:14.774967 stat("/.svn", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:14.774995 stat("/.hg", 0x7fffe2994cf0) = -1 ENOENT (No such file or directory) 17:09:14.775040 close(12) = 0 EXPECTED RESULT not searching for anything but ~/ SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.1 KDE Frameworks 5.55.0 Qt 5.9.7 (bygget imod 5.9.7) vinduessystemet xcb ADDITIONAL INFORMATION I am not sure why kate is looking for .[something] files in /home. But on a system with automounted homedirectories this triggers the automounter to go hunting for something to mount. If this could be avoided it would speed up launch considerably -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424073] Slow start on automounted home
https://bugs.kde.org/show_bug.cgi?id=424073 Klaus Vink Slott changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED --- Comment #2 from Klaus Vink Slott --- Please allow me a second round to get this confirmed: Note that I am not talking about users home katalog, eg /home/user/.git These is already mounted and accessible at launch and gives no delay. But kate is searching for config files outside the current users home eg. /home/.git - I have never seen any software having any configuration files at this location. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424073] Slow start on automounted home
https://bugs.kde.org/show_bug.cgi?id=424073 Klaus Vink Slott changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Klaus Vink Slott --- Thanks for taking time to answer this although it was not the answer I was hoping for. To me it seems that kate is crippled in a professional environment with automounted user catalogs. I'll take a look if I can improve the situation by making the automounter ignore . prefixed mountpoints. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408030] New: Plasma crash after supend/resume to other screen setup
https://bugs.kde.org/show_bug.cgi?id=408030 Bug ID: 408030 Summary: Plasma crash after supend/resume to other screen setup Product: plasmashell Version: 5.8.7 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kl...@vink-slott.dk CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.7) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.179-99-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Suspended my labtop in dock with 2 monitors connected. Undocked and resumed with only laptop screen. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc7b0d72900 (LWP 14778))] Thread 17 (Thread 0x7fc6c37ff700 (LWP 16490)): #0 0x7fc7aa27230d in poll () at /lib64/libc.so.6 #1 0x7fc79fedb081 in () at /usr/lib64/libpulse.so.0 #2 0x7fc79fecc74c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7fc79feccdbe in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7fc79fecce70 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7fc79fedafe6 in () at /usr/lib64/libpulse.so.0 #6 0x7fc79f8733f8 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7fc7a9a78724 in start_thread () at /lib64/libpthread.so.0 #8 0x7fc7aa27ae8d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fc6d7ffe700 (LWP 16399)): #0 0x7fc7aa27230d in poll () at /lib64/libc.so.6 #1 0x7fc7a6922314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc7a692242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc7aab7f16b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc7aab2cbbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc7aa967f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc7adc613d8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc7aa96c9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc7a9a78724 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc7aa27ae8d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fc6c9568700 (LWP 16377)): #0 0x7fc7a9a7d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc7aa96d65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc6efbe042f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc6efbe3dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc6efbe3e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fc6efbe3e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7fc6efbe3e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7fc6efbe3e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7fc6efbe3e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7fc6efbe3e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7fc6efbe3e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7fc6efbde45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7fc6efbe1a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7fc7aa96c9e9 in () at /usr/lib64/libQt5Core.so.5 #21 0x7fc7a9a78724 in start_thread () at /lib64/libpthread.so.0 #22 0x7fc7aa27ae8d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fc6c9d69700 (LWP 16376)): #0 0x7fc7a9a7d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc7aa96d65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5
[kdeconnect] [Bug 459678] New: Bidirectional synchronization between Kontact and an Android Smartphone
https://bugs.kde.org/show_bug.cgi?id=459678 Bug ID: 459678 Summary: Bidirectional synchronization between Kontact and an Android Smartphone Classification: Applications Product: kdeconnect Version: 22.08.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- SUMMARY *** Bidirectional synchronization between Kontact and an Android Smartphone or any of the targeted operating systems *** WISHLIST It is a pity that currently only a one-way synchronization from a smartphone to KDE is offered. Kontact, one of the KDE flagships, should synchronize from and to 1. KAddressbook 2. KOrgnanizer 3. KNotes This is an everyday requirement for most of us. I hope this is at least a near future target. OBSERVED RESULT I have set Contacts plugin to synchronize contacts between the desktop and the connected device. KDE Connect creates the directory: Home/.local/share/kpeoplevcard/kdeconnect.../ on the desktop machine containing one .vcf file for each of my contacts on the mobile phone. KAddressbook cannot handle these files. (Probably, because they were not created by Akonadi. EXPECTED RESULT For the contacts part, I would expect a new addressbook with all transferred contacts. Synchronization should be possible with calendar entries as well. The same for KNotes and a note-taking app on the phone would be very much appreciated. SOFTWARE/OS VERSIONS **1. Desktop** Operating System: openSUSE Tumbleweed 20220922 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 Kernel Version: 5.19.8-1-default (64-bit) **2. Smartphone** LineageOS 17.1 Nexus 5X (bullhead) ADDITIONAL INFORMATION Of course, it should work for all targeted operating systems. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379408] Sender/Receiver displays Sender for both Inbox and Sent Messages
https://bugs.kde.org/show_bug.cgi?id=379408 Klaus-Dieter Fietze changed: What|Removed |Added Version|5.3.0 |5.7.3 Summary|Sender/Receiver not |Sender/Receiver displays |selctable |Sender for both Inbox and ||Sent Messages Platform|Other |openSUSE RPMs --- Comment #1 from Klaus-Dieter Fietze --- When installing openSUSE Leap 15.0 I was full of hope that the issue I had reported would have disappeared. In vain, it is still the same: I am using the “Flat date view – Classic”. I would like to see the message header, the date and the Sender when in the Inbox or the Receiver when in Sent Messages. It worked in earlier versions of KDE. Since Leap it does not anymore. I think it is not too much what I am demanding. It works in the simplest webmail application but not in the highly sophisticated KMail. Thank you, Klaus-Dieter Fietze Software openSUSE Leap 15.0 KDE Plasma 5.12.5 KDE Frameworks 5.45.0 KMail 5.7.3 Qt 5.9.4 Kernel 4.12.14-lp150.12.4-default Hardware Processor 2 x Intel Core 2 Duo CPU T8300 @ 2.40 GHz Memory 3.8 GiB RAM -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 379132] New: Startup screen does not load icons
https://bugs.kde.org/show_bug.cgi?id=379132 Bug ID: 379132 Summary: Startup screen does not load icons Product: konqueror Version: 4.14.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 105164 --> https://bugs.kde.org/attachment.cgi?id=105164&action=edit Konqueror Startup Screen When I start Konqueror it does not show the icons that are assigned to the various choices: Home Folder Network Folders Wastebin Bookmarks I have checked the image locations, such as file:///usr/share/icons/breeze/places/32/user-home.svg. They are accessible. I can open the pictures; they show up correctly. Apparently there is no command that causes Konqueror to open the icons. Thank you, Klaus-Dieter Fietze -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379408] New: Sender/Receiver not selctable
https://bugs.kde.org/show_bug.cgi?id=379408 Bug ID: 379408 Summary: Sender/Receiver not selctable Product: kmail2 Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 105299 --> https://bugs.kde.org/attachment.cgi?id=105299&action=edit Inbox with chosen header columns I would like to see the date, the subject and, depending where I am, the sender in „Inbox“ or the receiver in „Sent Items“ of my „Flat Date View“. However, when I chose „Sender/Receiver“ in the configuration menu of the „Message List“ the sender is always displayed in both in „Inbox“ and in „Sent Items“, no matter what I chose. I have tried to right click on the header. As you can see on the attached pictures, „Sender/Receiver“ is ticked but not shown. When I chose „Receiver“ from the list it is displayed in both the „Inbox“ and „Sent Items“ as everybody would expect. Moreover, I use the glider in the header to adjust the column width. But whenever I start the computer again the column sizes have squeezed together. Also, I should be able to directly key in the column size but I cannot find where. Everything is greyed out. I am using IMAP with openSUSE Leap 42.2, KDE Plasma 5.8.6., KDE Framework 5.26.0, Qt 5.6.1, Kernel 4.4.36-8 (64 bit). Thank you, Klaus-Dietrer Fietze -- You are receiving this mail because: You are watching all bug changes.