[frameworks-kio] [Bug 423031] [Wayland] Modifier keys to move (shift), copy (ctrl) and create a link (ctrl+shift) don't work if pressed after I start to drag the file/folder
https://bugs.kde.org/show_bug.cgi?id=423031 MartinG changed: What|Removed |Added CC||grons...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449255] Dolphin/KIO fails when opening DFS
https://bugs.kde.org/show_bug.cgi?id=449255 --- Comment #3 from MartinG --- I'd like to add that the following works for me (and can be used as a workaround): 1. Add the following lines to /etc/request-key.conf: create cifs.spnego * * /usr/sbin/cifs.upcall %k create dns_resolver * * /usr/sbin/cifs.upcall %k 2. Mount the DFS share manually: mkdir ~/mnt/dfs-share sudo mount.cifs -o username=DOMAINUSERNAME,domain=DOMAIN,uid=1000,gid=1000 //HOST/dfs/xxx/yyy/zzz/ ~/mnt/dfs-share/ where my local uid and gid is 1000 (check yours with the "id" command). So I guess the changes that are needed to kioslave etc are minimal, right? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449255] Dolphin/KIO fails when opening DFS
https://bugs.kde.org/show_bug.cgi?id=449255 --- Comment #1 from MartinG --- I confirm this, and would like to add that for me I can access such shares (SMB with DFS) in Thunar file manager. I would love to the this functionality in Dolphin of course, since it is superior for everything else in my opinion. Fedora 36. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449255] Dolphin/KIO fails when opening DFS
https://bugs.kde.org/show_bug.cgi?id=449255 MartinG changed: What|Removed |Added CC||grons...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453554] turning one monitor off kills the panel configuration of the second monitor
https://bugs.kde.org/show_bug.cgi?id=453554 MartinG changed: What|Removed |Added CC||grons...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 MartinG changed: What|Removed |Added CC||grons...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 MartinG changed: What|Removed |Added CC||grons...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450435] Panels missing after unlocking screen after sleep mode
https://bugs.kde.org/show_bug.cgi?id=450435 MartinG changed: What|Removed |Added CC||grons...@gmail.com --- Comment #13 from MartinG --- I'm on 5.24.4-1.fc34.x86_64 and see similar behavior: When I connect my docking station (Thunderbolt), the monitors are often messed up showing partial screens and the panels are gone or shown on the wrong screen. When I disconnect the docking (and thereby the external monitors), I sometimes are left with no panel on my single laptop screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440587] Crash when using facial recognition tool
https://bugs.kde.org/show_bug.cgi?id=440587 --- Comment #2 from MartinG --- (In reply to Maik Qualmann from comment #1) > I suspect you didn't download the binary files required by the face engine? > Did you cancel the download and or did not restart digikam after the > download? > Please enter the terminal log from the console with the debug variable > active as described here: > > https://www.digikam.org/contribute/ > > Maik Thanks for the reply Maik. Indeed, this is probably the reason: I did download the binaries via the popup in the GUI, but I probably forgot to restart. It worked the second time I tried. (I had already downloaded the package for "showfoto", and restarted that, but got frustrated when I couldn't find any info on how to use it - therefore I tried in digiKam.) digikam could perhaps give a warning rather than a crash in case the required restart wasn't done. This bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440587] New: Crash when using facial recognition tool
https://bugs.kde.org/show_bug.cgi?id=440587 Bug ID: 440587 Summary: Crash when using facial recognition tool Product: digikam Version: 7.2.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: grons...@gmail.com Target Milestone: --- Application: digikam (7.2.0) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.13.5-200.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: I entered the People tab, and used "Scan collection for faces" (with "Detect faces" active) for the first time ever. In the window to the right, I entered a name for one face, pressed enter and then digiKam crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: digiKam (digikam), signal: Aborted [KCrash Handler] #4 0x7f048cda82a2 in raise () from /lib64/libc.so.6 #5 0x7f048cd918a4 in abort () from /lib64/libc.so.6 #6 0x7f048e8ce188 in std::__replacement_assert(char const*, int, char const*, char const*) () from /lib64/libdigikamcore.so.7.2.0 #7 0x7f048eddbc93 in Digikam::FullObjectDetection::part(unsigned long) () from /lib64/libdigikamcore.so.7.2.0 #8 0x7f048edded4b in Digikam::OpenfacePreprocessor::process(cv::Mat const&) () from /lib64/libdigikamcore.so.7.2.0 #9 0x7f048eddf34b in Digikam::RecognitionPreprocessor::Private::preprocess(cv::Mat const&) const () from /lib64/libdigikamcore.so.7.2.0 #10 0x7f048eddf506 in Digikam::RecognitionPreprocessor::preprocess(cv::Mat const&) const () from /lib64/libdigikamcore.so.7.2.0 #11 0x7f048f6d4b12 in Digikam::DNNFaceExtractor::getFaceEmbedding(cv::Mat const&) () from /lib64/libdigikamgui.so.7.2.0 #12 0x7f048f6d6d62 in Digikam::OpenCVDNNFaceRecognizer::Private::ParallelTrainer::operator()(cv::Range const&) const () from /lib64/libdigikamgui.so.7.2.0 #13 0x7f048bba0c9a in cv::parallel_for_(cv::Range const&, cv::ParallelLoopBody const&, double) () from /lib64/libopencv_core.so.4.5 #14 0x7f048f6d396a in Digikam::OpenCVDNNFaceRecognizer::train(QList const&, int, QString const&) () from /lib64/libdigikamgui.so.7.2.0 #15 0x7f048f6cec4a in Digikam::FacialRecognitionWrapper::train(QList const&, Digikam::TrainingDataProvider*, QString const&) () from /lib64/libdigikamgui.so.7.2.0 #16 0x7f048f8ab926 in Digikam::TrainerWorker::process(QExplicitlySharedDataPointer) () from /lib64/libdigikamgui.so.7.2.0 #17 0x7f048f899ad7 in Digikam::TrainerWorker::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libdigikamgui.so.7.2.0 #18 0x7f048d446809 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f048deea423 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f048d41c098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f048d41f606 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x7f048d46dbf7 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x7f048b2724cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f048b2c64e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #25 0x7f048b26fc03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f048d46d698 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f048d41aab2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f048ea8e8a3 in Digikam::WorkerObjectRunnable::run() () from /lib64/libdigikamcore.so.7.2.0 #29 0x7f048d262560 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #30 0x7f048d25f456 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #31 0x7f048aacc299 in start_thread () from /lib64/libpthread.so.0 #32 0x7f048ce6b353 in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f03c0ff9640 (LWP 212765) "Qt bearer threa"): #1 0x7ffdc23f89ba in clock_gettime () #2 0x7f048ce32a25 in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6 #3 0x7f048b272a7a in g_main_context_check () from /lib64/libglib-2.0.so.0 #4 0x7f048b2c637b in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #5 0x7f048b26fc03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #6 0x7f048d46d70e in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f048d41aab2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #8 0x7f048d25e25a in QThread::exec() () from /lib64/libQt5Core.so.5 #9
[plasmashell] [Bug 423526] "Switch user" functionality has disappeared from Kicker and Kickoff
https://bugs.kde.org/show_bug.cgi?id=423526 MartinG changed: What|Removed |Added CC||grons...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever
https://bugs.kde.org/show_bug.cgi?id=406917 --- Comment #12 from MartinG --- I checked mine today, and mine is also back in none-sync mode. The sad thing is, that I have put in a number of events in Korganizer, that are now not shown in my shared Nextcloud calendar. I guess I will have to reset the connection and lose all of those. I tend to import flight events into my calendar, and those are often not fully sanitized. I'd much rather be confronted with an error when this happens, with an option to ignore and move on, rather than to be left in "offline mode" without knowing it! Please let me know if any more info is needed. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 412155] New: Gwenview freezes when opening single file in directory with many files
https://bugs.kde.org/show_bug.cgi?id=412155
Bug ID: 412155
Summary: Gwenview freezes when opening single file in directory
with many files
Product: gwenview
Version: 18.12.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: grons...@gmail.com
Target Milestone: ---
SUMMARY
When I open a single file in a directory with many files, Gwenview freezes in
several seconds. The reason seems to be that Gwenview insists on reading
(meta?) info of every file in the directory.
This is very annoying when opening a single image on a remote share (eg.
mounted via sshfs or cifs), since startup may be delayed for more than a
minute.
STEPS TO REPRODUCE
1. Open an image with Gwenview in a directory with many files (thousands)
2. Image shows fully or partly, and Gwenview is frozen. Eg cannot go to next
image in folder
3. Wait for a certain time, and Gwenview functions normally again.
OBSERVED RESULT
I did a strace in a folder pointing to a remotely connected filesystem
containing ca 12000 jpeg files:
$ strace gwenview file_2019_09_20_12_00_03.jpg
Gwenview then spits out thousands of lines:
stat("/home/user/mnt/host/share/file_2019_01_15_06_00_00.jpg",
{st_mode=S_IFREG|0755, st_size=231511, ...}) = 0
openat(AT_FDCWD, "/home/user/mnt/host/share/file_2019_01_15_06_00_00.jpg",
O_RDONLY|O_CLOEXEC) = 26
statx(26, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_BASIC_STATS, stx_attributes=0, stx_mode=S_IFREG|0755,
stx_size=231511, ...}) = 0
close(26) = 0
statx(AT_FDCWD, "/home/user/mnt/host/share/file_2019_01_15_06_30_01.jpg",
AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_BASIC_STATS,
stx_attributes=0, stx_mode=S_IFREG|0755, stx_size=231348, ...}) = 0
EXPECTED RESULT
Gwenview should show the single image, maybe start caching "next" and
"previous" image in a background thread, not freeze.
SOFTWARE/OS VERSIONS
Operating System: Fedora 30
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4
Kernel Version: 5.2.13-200.fc30.x86_64
OS Type: 64-bit
Processors: 12 × Intel® Core™ i9-8950HK CPU @ 2.90GHz
Memory: 31.0 GiB of RAM
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 404405] Needs to unlock twice occasionally
https://bugs.kde.org/show_bug.cgi?id=404405 MartinG changed: What|Removed |Added CC||grons...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406917] New: Sync of webdav calendar stuck forever
https://bugs.kde.org/show_bug.cgi?id=406917
Bug ID: 406917
Summary: Sync of webdav calendar stuck forever
Product: Akonadi
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: DAV Resource
Assignee: kdepim-b...@kde.org
Reporter: grons...@gmail.com
Target Milestone: ---
SUMMARY
When akonadi fails to read a calendar event from eg. a Nextcloud/Owncloud
remote calendar (or any webdav resource I guess), it will enter a stale state
making all other calendar interactions impossible
STEPS TO REPRODUCE
1. Setup a webdav remote calendar in korganizer
2. Be unlucky and end up with an event that for some reason is expected to
exist, but it doesn't
3. Register state "Fetching collection (0 %)" or "Ready (0%)" forever. Not
possible to get out of that state with "akonadictl restart" or even restart of
computer.
OBSERVED RESULT
DAV resource becomes unusable.
EXPECTED RESULT
Akonadi should handle the bad state in some way, and move on, letting me use
the calendar resource.
SOFTWARE/OS VERSIONS
linux 5.0.9-200.fc29.x86_64
kdelibs-common-4.14.38-9.fc29.x86_64
kdelibs-4.14.38-9.fc29.x86_64
korganizer-libs-18.12.2-1.fc29.x86_64
kontact-18.12.2-1.fc29.x86_64
kontact-libs-18.12.2-1.fc29.x86_64
kdelibs-webkit-4.14.38-9.fc29.x86_64
kf5-kdelibs4support-5.55.0-1.fc29.x86_64
kf5-kdelibs4support-libs-5.55.0-1.fc29.x86_64
kdelibs-ktexteditor-4.14.38-9.fc29.x86_64
korganizer-18.12.2-1.fc29.x86_64
Linux/KDE Plasma: 5.14.5
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.55.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
I'm running Nextcloud 15.0.7, and have set up the calendar as a webdav
resource. At some point, it stopped working, and in
Kontact->Settings->Configure korganizer->General->Calendars, the resource is
stuck at "Fetching collection (0 %)" or "Ready (0 %)" forever.
If I run "akonadictl restart" in the terminal, I get the following:
org.kde.pim.davresource: Error when uploading item: 420 "There was a problem
with the request. The item was not modified on the server.\nAn unexpected error
(412) occurred while attempting to upload
https://USERNAME@MYURL/NEXTCLOUNDNAME/remote.php/dav/calendars/USERNAME/CALENDARNAME/1551289068.R271.ics.
(412)."
parse error from icalcomponent_new_from_string. string= "\nhttp://sabredav.org/ns\;>\n
Sabre\\DAV\\Exception\\NotFound\n
Calendar object not found\n\n"
org.kde.pim.davresource: DavGroupwareResource::onItemFetched: Failed to parse
item data.
"https://USERNAME@MYURL/NEXTCLOUNDNAME/remote.php/dav/calendars/USERNAME/CALENDARNAME/1551289068.R271.ics;
Here is the corresponding error on the nextcloud server (15.0.7,
nextcloud.log):
{"reqId":"BX7CkUh0Wd4i4Vl9crBA",
"level":4,
"time":"2019-04-26T09:49:21+00:00",
"remoteAddr":"192.168.1.1",
"user":"USERNAME",
"app":"webdav",
"method":"PUT",
"url":"\/NEXTCLOUDNAME\/remote.php\/dav\/calendars\/USERNAME\/CALENDARNAME\/1551289068.R271.ics",
"message":{"Exception":"Sabre\\DAV\\Exception\\BadRequest",
"Message":"Calendar object with uid already exists in this calendar
collection.",
"Code":0,
"Trace":[{"file":"\/var\/www\/html\/NEXTCLOUDNAME\/3rdparty\/sabre\/dav\/lib\/CalDAV\/Calendar.php",
"line":201,
"function":"createCalendarObject",
"class":"OCA\\DAV\\CalDAV\\CalDavBackend",
"type":"->",
"args":["3",
"1551289068.R271.ics",
"BEGIN:VCALENDAR\r\nPRODID:-\/\/K Desktop
Environment\/\/NONSGML libkcal
4.3\/\/EN\r\nVERSION:2.0\r\nX-KDE-ICAL-IMPLEMENTATION-VERSION:1.0\r\nBEGIN:VEVENT\r\nDTSTAMP:20190227T174129Z\r\nCREATED:20190227T173728Z\r\nUID:a151d2ad-e962-459f-a291-705071fe62ef\r\nSEQUENCE:2\r\nLAST-MODIFIED:20190227T174129Z\r\nDESCRIPTION:Test\\,
with commas\r\nSUMMARY:Test comma\r\nLOCATION:Location\\,
with
comma\r\nDTSTART;VALUE=DATE:20190227\r\nDTEND;VALUE=DATE:20190228\r\nTRANSP:OPAQUE\r\nEND:VEVENT\r\nEND:VCALENDAR\r\n"]},
{"file":"\/var\/www\/html\/NEXTCLOUDNAME\/3rdparty\/sabre\/dav\/lib\/DAV\/Server.php",
"line":1096,
"function":"createFile",
"class":"Sabre\\CalDAV\\Calendar",
"type":"->",
"args":["1551289068.R271.ics",
"BEGIN:VCALENDAR\r\nPRODID:-\/\/K Desktop
Environment\/\/NONSGML libkcal
4.3\/\/EN\r\nVERSION:2.0\r\nX-KDE-ICAL-IMPLEMENTATION-VERSION:1.0\r\nBEGIN:VEVENT\r\nDTSTAMP:20190227T174129Z\r\nCREATED:20190227T173728Z\r\nUID:a151d2ad-e962-459f-a291-705071fe62ef\r\nSEQUENCE:2\r\nLAST-MODIFIED:20190227T174129Z\r\nDESCRIPTION:Test\\,
with commas\r\nSUMMARY:Test comma\r\nLOCATION:Location\\,
with
[Akonadi] [Bug 398011] stopped getting gmail
https://bugs.kde.org/show_bug.cgi?id=398011 MartinG changed: What|Removed |Added CC||grons...@gmail.com --- Comment #2 from MartinG --- Had the same after updating to latest version on Fedora 28. kontact-18.04.3-1.fc28.x86_64 kdepim-runtime-18.04.3-1.fc28.x86_64 kdepimlibs-4.14.10-26.fc28.x86_64 kdepim-runtime-libs-18.04.3-1.fc28.x86_64 kdepim-apps-libs-18.04.3-1.fc28.x86_64 kf5-libkdepim-akonadi-18.04.3-1.fc28.x86_64 The problem went away after enabling "less secure" application via the gmail web interface. Also, at #fedora-kde on freenode (IRC), it was said that the "less secure" option is needed until support for oauth(?) is made available - it should be in the next version. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388440] scrolling in KMail: "page down" only works once
https://bugs.kde.org/show_bug.cgi?id=388440 MartinG <grons...@gmail.com> changed: What|Removed |Added CC||grons...@gmail.com --- Comment #3 from MartinG <grons...@gmail.com> --- I'm having the same problem as described by the initial report. I use KMail 5.7.3 on Fedora 27, so it doesn't seem to be fixed in 5.7.1. What I see, is that when I use pagedown (PGDOWN), it only works once. I can sometimes manage to get two pages down by using SPACE once, and PGDOWN once. If i use DOWN, and press PGDOWN, the view will skip back to the place it was before I pressed the DOWN. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 385825] New: Krunner crashes on ENTER
https://bugs.kde.org/show_bug.cgi?id=385825 Bug ID: 385825 Summary: Krunner crashes on ENTER Product: krunner Version: 5.10.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: grons...@gmail.com Target Milestone: --- Application: krunner (5.10.5) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.13.5-200.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: - What I was doing when the application crashed: I typed "gwenview" and pressed enter. Krunner crashed, and gwenview didn't start. The bug reporting tool was shown in the tray. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc22c743d80 (LWP 4538))] Thread 14 (Thread 0x7fc1dd7fa700 (LWP 21107)): #0 0x7fc224c4290b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc228e593fb in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fc1fbdea985 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fc1fbdee8f8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fc1fbde9b4d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fc1fbdec83b in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fc228e58c9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fc224c3c36d in start_thread () at /lib64/libpthread.so.0 #8 0x7fc22823fbbf in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fc1ddffb700 (LWP 21106)): [KCrash Handler] #6 0x7fc20e91774f in Solid::Backends::Fstab::FstabHandling::_k_updateMtabMountPointsCache() () at /lib64/libKF5Solid.so.5 #7 0x7fc20e9179f3 in Solid::Backends::Fstab::FstabHandling::deviceList() () at /lib64/libKF5Solid.so.5 #8 0x7fc20e912c0e in Solid::Backends::Fstab::FstabManager::_k_updateDeviceList() () at /lib64/libKF5Solid.so.5 #9 0x7fc20e913669 in Solid::Backends::Fstab::FstabManager::onMtabChanged() () at /lib64/libKF5Solid.so.5 #10 0x7fc20e91c78d in Solid::Backends::Fstab::FstabManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libKF5Solid.so.5 #11 0x7fc2290258da in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7fc229adb5dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7fc229ae2c74 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7fc228ffd627 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #15 0x7fc228fff85b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #16 0x7fc22904bdd3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #17 0x7fc22019a247 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #18 0x7fc22019a5e8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #19 0x7fc22019a67c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #20 0x7fc22904be4f in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #21 0x7fc228ffc60a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7fc1f2fcf5a6 in SearchRunner::match(Plasma::RunnerContext&) () at /usr/lib64/qt5/plugins/krunner_baloosearchrunner.so #23 0x7fc2041d97d0 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /lib64/libKF5Runner.so.5 #24 0x7fc1fbdee0b8 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5 #25 0x7fc1fbdece30 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5 #26 0x7fc1fbdec8fd in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #27 0x7fc228e58c9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #28 0x7fc224c3c36d in start_thread () at /lib64/libpthread.so.0 #29 0x7fc22823fbbf in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fc1de7fc700 (LWP 21105)): #0 0x7fc224c4290b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc228e593fb in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fc1fbdea985 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fc1fbdee8f8 in
[gwenview] [Bug 354750] asks for ssh key password on viewing a local image due to fish:// place in places list
https://bugs.kde.org/show_bug.cgi?id=354750 MartinG <grons...@gmail.com> changed: What|Removed |Added CC||grons...@gmail.com --- Comment #5 from MartinG <grons...@gmail.com> --- I confirm this, as I did in 2014 in comment https://bugs.kde.org/show_bug.cgi?id=274673#c1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 333754] KOrganizer does not retain custom category colors
https://bugs.kde.org/show_bug.cgi?id=333754 MartinG <grons...@gmail.com> changed: What|Removed |Added CC||grons...@gmail.com --- Comment #59 from MartinG <grons...@gmail.com> --- Brilliant, huge thank you from me! -- You are receiving this mail because: You are watching all bug changes.
