[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 S.Trzmiel changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #12 from S.Trzmiel --- Requested info provided -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 --- Comment #11 from S.Trzmiel --- Created attachment 117230 --> https://bugs.kde.org/attachment.cgi?id=117230&action=edit udisk SU02G info output of udisksctl info -d SU02G_0x0eea8c36 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 --- Comment #10 from S.Trzmiel --- Created attachment 117229 --> https://bugs.kde.org/attachment.cgi?id=117229&action=edit udisk mmcblk0 info output of udisksctl info -b /dev/mmcblk0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 S.Trzmiel changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from S.Trzmiel --- As posted above, workaround didn't make a difference, udevadm output provided as attachements. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096
--- Comment #6 from S.Trzmiel ---
(In reply to Stefan Brüns from comment #3)
> Hardware vendors are unfortunately to dumb to properly implement standards
> ...
>
> Therefor, UDisks adds a list of quirks for known devices.
>
> Try adding a file "/etc/udev/rules.d/80-udisks2-local.rule" with the
> following contents to your system:
> --- >8 ---
> SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="0bda",ENV{ID_MODEL_ID}=="0129",
> ENV{ID_DRIVE_FLASH_CF}="1"
> --- 8< ---
>
> Also please provide the output of the following commands:
> $> udevadm info -n /dev/sdX > /tmp/udev_info_sdX.txt
> $> udevadm info -n /dev/sdXN > /tmp/udev_info_sdXN.txt
>
> replace sdX with the correct device name for your card reader, e.g. sdb, sdc
> ...
> replace N in sdXN with the number(s) of the partitions.
udevdm output provided. I've created udev rule, even rebooted OS to be sure
it's loaded (most likely unnessesary) but it made no difference, removing
SDcard still power downs the reader
Right now it loks like this:
#--- >8 ---
SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="0bda",ENV{ID_MODEL_ID}=="0129",
ENV{ID_DRIVE_FLASH_CF}="1"
#--- 8< ---
I've tried with header footer/commented out, not commented and not present,
still no difference
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 --- Comment #5 from S.Trzmiel --- Created attachment 116903 --> https://bugs.kde.org/attachment.cgi?id=116903&action=edit udev info of SDcard partition 1 of 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 --- Comment #4 from S.Trzmiel --- Created attachment 116902 --> https://bugs.kde.org/attachment.cgi?id=116902&action=edit udev info of SDCard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 --- Comment #2 from S.Trzmiel --- (In reply to Kai Uwe Broulik from comment #1) > It is probably powered down by Solid because people wanted us to power down > external hard drives... I guess so, would it be possible to offer different actions for different media types? Ie 'safe removal' for external hard drives/pendrives and 'eject' for memory cards? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402096] New: Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 Bug ID: 402096 Summary: Removing memory card causes device to disappear from the system. Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: x...@x-s.com.pl Target Milestone: 1.0 SUMMARY Removing memory card via device notifier/Dolphin causes card reader device disappear from the system, thus card reader cannot be used again untill reboot/usb port reset/physical reconnection of the device (hard do to when device is build in into your computer/laptop ;)). On system with card-reader STEPS TO REPRODUCE 1. Insert memory into the reader. 2. Mount it and browse its content 3. Remove card via device notifier/nontext menu of card in file browser:places OBSERVED RESULT Memory card disappears from the device notifier/filebrowser:places Card reader dissapears from list of usb devices (lsusb output) There's no reaction if card is removed/inserted again. EXPECTED RESULT Memory card disapears from device notifier/filebrowser:places or goes to unmouned state. lsusb still lists Card reader Device notifier reacts to card reinsertion. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 29 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52 Qt Version: 5.11.1 ADDITIONAL INFORMATION I guess it happens because action used to do so is 'safe removal' that powers down the device. So I suppose 'eject' action should be used instead output of lsusb before card is safely removed: Bus 002 Device 003: ID 8087:07da Intel Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 1bcf:2895 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 046d:0802 Logitech, Inc. Webcam C200 Bus 003 Device 003: ID 0461:4d62 Primax Electronics, Ltd HP Laser Mobile Mini Mouse Bus 003 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and after safe removal Bus 002 Device 003: ID 8087:07da Intel Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 1bcf:2895 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 046d:0802 Logitech, Inc. Webcam C200 Bus 003 Device 003: ID 0461:4d62 Primax Electronics, Ltd HP Laser Mobile Mini Mouse Bus 003 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 401765] New: Accepting updated invitation caused Kontact crash.
https://bugs.kde.org/show_bug.cgi?id=401765 Bug ID: 401765 Summary: Accepting updated invitation caused Kontact crash. Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: x...@x-s.com.pl Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.4-300.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: Crash occured when I accepted invitation update (no original initation was found according to the Kontact message) and tried to save it in Google calendar. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 28return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7f56f2184340 (LWP 9301))] Thread 33 (Thread 0x7f55ba409700 (LWP 2545)): #0 0x7f56fd914f84 in __GI___libc_read (nbytes=10, buf=0x7f55ba408a5e, fd=123) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f56fd914f84 in __GI___libc_read (fd=fd@entry=123, buf=buf@entry=0x7f55ba408a5e, nbytes=nbytes@entry=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f56b879a355 in read (__nbytes=10, __buf=0x7f55ba408a5e, __fd=123) at /usr/include/bits/unistd.h:44 #3 0x7f56b879a355 in pa_read (fd=123, buf=buf@entry=0x7f55ba408a5e, count=count@entry=10, type=type@entry=0x556ef5dcbf88) at pulsecore/core-util.c:437 #4 0x7f56d4045826 in clear_wakeup (m=) at pulse/mainloop.c:782 #5 0x7f56d4045826 in pa_mainloop_prepare (m=m@entry=0x556ef5dcbeb0, timeout=-1) at pulse/mainloop.c:789 #6 0x7f56d4046294 in pa_mainloop_iterate (m=0x556ef5dcbeb0, block=, retval=0x0) at pulse/mainloop.c:923 #7 0x7f56d4046350 in pa_mainloop_run (m=0x556ef5dcbeb0, retval=retval@entry=0x0) at pulse/mainloop.c:945 #8 0x7f56d40545bd in thread (userdata=0x556ef5dcbe70) at pulse/thread-mainloop.c:100 #9 0x7f56b87ca06c in internal_thread_func (userdata=0x556ef5dc0060) at pulsecore/thread-posix.c:81 #10 0x7f56f613a58e in start_thread (arg=) at pthread_create.c:486 #11 0x7f56fd9246a3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7f55a7aef700 (LWP 2544)): #0 0x7f56f6140b68 in futex_reltimed_wait_cancelable (private=0, reltime=0x7f55a7aee980, expected=0, futex_word=0x7f55a7aeeb68) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f56f6140b68 in __pthread_cond_wait_common (abstime=0x7f55a7aeea20, mutex=0x7f55a7aeeb18, cond=0x7f55a7aeeb40) at pthread_cond_wait.c:533 #2 0x7f56f6140b68 in __pthread_cond_timedwait (cond=0x7f55a7aeeb40, mutex=0x7f55a7aeeb18, abstime=0x7f55a7aeea20) at pthread_cond_wait.c:667 #3 0x7f56f8ac8ce7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #4 0x7f56f8aca9ba in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #5 0x7f56f8acaaa2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #6 0x7f56f8acf861 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #7 0x7f56f8ad0d41 in base::internal::SchedulerWorker::Thread::ThreadMain() () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #8 0x7f56f8adb171 in ThreadFunc() () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #9 0x7f56f613a58e in start_thread (arg=) at pthread_create.c:486 #10 0x7f56fd9246a3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7f5672ffd700 (LWP 2543)): #0 0x7f56f6140b68 in futex_reltimed_wait_cancelable (private=0, reltime=0x7f5672ffc980, expected=0, futex_word=0x7f5672ffcb68) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f56f6140b68 in __pthread_cond_wait_common (abstime=0x7f5672ffca20, mutex=0x7f5672ffcb18, cond=0x7f5672ffcb40) at pthread_cond_wait.c:533 #2 0x7f56f6140b68 in __pthread_cond_timedwait (cond=0x7f5672ffcb40, mutex=0x7f5672ffcb18, abstime=0x7f5672ffca20) at pthread_cond_wait.c:667 #3 0x7f56f8ac8ce7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #4 0x7f56f8aca9ba in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #5 0x7f56f8acaaa2 in base::WaitableEvent::TimedW
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 --- Comment #5 from S.Trzmiel --- (In reply to Christoph Feck from comment #4) > Could akonadi_imap_resource link to KCrash to get a backtrace? After update to Fedora 29/ KF5 5.52 KDE Apps 18.08.3 I finnaly managed to get valid backtrace: == Application: akonadi_imap_resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 28return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7fea2559d980 (LWP 7746))] Thread 7 (Thread 0x7fea065ed700 (LWP 7759)): #0 0x7fea30ceef84 in __GI___libc_read (nbytes=16, buf=0x7fea065ec9f0, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fea30ceef84 in __GI___libc_read (fd=17, buf=buf@entry=0x7fea065ec9f0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fea26c0baa0 in read (__nbytes=16, __buf=0x7fea065ec9f0, __fd=) at /usr/include/bits/unistd.h:44 #3 0x7fea26c0baa0 in g_wakeup_acknowledge (wakeup=0x7fe9f8003d80) at gwakeup.c:210 #4 0x7fea26bc509b in g_main_context_check (context=context@entry=0x7fe9fc000bf0, max_priority=2147483647, fds=fds@entry=0x7fe9fc004db0, n_fds=n_fds@entry=1) at gmain.c:3698 #5 0x7fea26bc5550 in g_main_context_iterate (context=context@entry=0x7fe9fc000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3917 #6 0x7fea26bc56d0 in g_main_context_iteration (context=0x7fe9fc000bf0, may_block=may_block@entry=1) at gmain.c:3981 #7 0x7fea313a082b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe9fc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7fea3134f17b in QEventLoop::exec(QFlags) (this=this@entry=0x7fea065ecc20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #9 0x7fea311b7046 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #10 0x7fea311c04bb in QThreadPrivate::start(void*) (arg=0x555839c37540) at thread/qthread_unix.cpp:367 #11 0x7fea2933558e in start_thread (arg=) at pthread_create.c:486 #12 0x7fea30cfe6a3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fea06dee700 (LWP 7753)): #0 0x7fea30cf3409 in __GI___poll (fds=0x7fe9f8003ce0, nfds=1, timeout=10068) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fea26bc55a6 in g_main_context_poll (priority=, n_fds=1, fds=0x7fe9f8003ce0, timeout=, context=0x7fe9f8000bf0) at gmain.c:4221 #2 0x7fea26bc55a6 in g_main_context_iterate (context=context@entry=0x7fe9f8000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3915 #3 0x7fea26bc56d0 in g_main_context_iteration (context=0x7fe9f8000bf0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7fea313a082b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe9f8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fea3134f17b in QEventLoop::exec(QFlags) (this=this@entry=0x7fea06dedc20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fea311b7046 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fea311c04bb in QThreadPrivate::start(void*) (arg=0x555839bef8a0) at thread/qthread_unix.cpp:367 #8 0x7fea2933558e in start_thread (arg=) at pthread_create.c:486 #9 0x7fea30cfe6a3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fea07fff700 (LWP 7750)): #0 0x7fea30cf3421 in __GI___poll (fds=0x7fea49b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fea26bc55a6 in g_main_context_poll (priority=, n_fds=1, fds=0x7fea49b0, timeout=, context=0x7fea0bf0) at gmain.c:4221 #2 0x7fea26bc55a6 in g_main_context_iterate (context=context@entry=0x7fea0bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3915 #3 0x7fea26bc56d0 in g_main_context_iteration (context=0x7fea0bf0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7fea313a082b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fea0b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fea3134f17b in QEventLoop::exec(QFlags) (this=this@entry=0x7fea07ffec20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fea311b7046 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fea311c04bb in QThreadPrivate::start(void*) (arg=0x555839b6d480) at thread/qthread_unix.cpp:367 #8 0x7fea2933558e in start_thread (arg=) at pthread_create.c:486 #9 0x7fea30cfe6a3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fea1491d700 (LWP 7749)): #0 0x7fea30cf3421 in __GI___poll (fds=0x7fea0c024810, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fea26bc55a6 in g_main_context_poll (priority=, n_
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 --- Comment #3 from S.Trzmiel --- I've uploaded abrt dump to my website, plz do not dowload if not nessesary (bandwitch limits) http://x-s.com.pl/ccpp-2018-07-19-12.19.00.992459-9987.tar.gz -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 --- Comment #2 from S.Trzmiel --- In system log i found some messages that might be revelant to this issue: lip 19 11:32:22 Xeno.localdomain akonadi_archivemail_agent[6415]: "Item query returned empty result set" lip 19 11:32:22 Xeno.localdomain akonadi_mailfilter_agent[6433]: "Item query returned empty result set" lip 19 11:32:22 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:34:54 Xeno.localdomain akonadi_archivemail_agent[6415]: "Item query returned empty result set" lip 19 11:34:54 Xeno.localdomain akonadi_mailfilter_agent[6433]: "Item query returned empty result set" lip 19 11:34:54 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:34:54 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:35:15 Xeno.localdomain akonadi_indexing_agent[6425]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/34/556634_r0" "No such file or directory" lip 19 11:35:16 Xeno.localdomain akonadi_mailfilter_agent[6433]: "Item query returned empty result set" lip 19 11:35:16 Xeno.localdomain akonadi_archivemail_agent[6415]: "Item query returned empty result set" lip 19 11:35:16 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:35:16 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:35:22 Xeno.localdomain kontact[3173]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/47/559247_r1" "No such file or directory" lip 19 11:35:22 Xeno.localdomain kontact[3173]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/47/559247_r1" "No such file or directory" lip 19 11:36:22 Xeno.localdomain akonadi_mailfilter_agent[6433]: "Item query returned empty result set" lip 19 11:36:22 Xeno.localdomain akonadi_archivemail_agent[6415]: "Item query returned empty result set" lip 19 11:36:22 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:36:34 Xeno.localdomain akonadi_imap_resource[6424]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/10/556910_r0" "No such file or directory" lip 19 11:36:34 Xeno.localdomain akonadi_imap_resource[6424]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/12/556912_r0" "No such file or directory" lip 19 11:36:34 Xeno.localdomain kontact[3173]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/81/553081_r3" "No such file or directory" lip 19 11:36:34 Xeno.localdomain kontact[3173]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/83/553083_r3" "No such file or directory" lip 19 11:36:34 Xeno.localdomain akonadi_mailfilter_agent[6433]: "Item query returned empty result set" lip 19 11:36:34 Xeno.localdomain akonadi_archivemail_agent[6415]: "Item query returned empty result set" lip 19 11:36:34 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:36:34 Xeno.localdomain akonadi_imap_resource[6424]: "Item query returned empty result set" lip 19 11:36:34 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:36:36 Xeno.localdomain akonadi_indexing_agent[6425]: "Item query returned empty result set" lip 19 11:36:36 Xeno.localdomain akonadi_indexing_agent[6425]: "Item query returned empty result set" lip 19 11:36:36 Xeno.localdomain akonadi_indexing_agent[6425]: "Item query returned empty result set" lip 19 11:36:43 Xeno.localdomain akonadi_imap_resource[6424]: org.kde.pim.imapresource: Detected inconsistency in local cache, we're missing some messages. Server: 214 Local: 213 lip 19 11:36:43 Xeno.localdomain akonadi_imap_resource[6424]: org.kde.pim.imapresource: Refetching complete mailbox. lip 19 11:36:49 Xeno.localdomain kontact[3173]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/43/451343_r25" "No such file or directory" lip 19 11:36:49 Xeno.localdomain akonadi_archivemail_agent[6415]: "Item query returned empty result set" lip 19 11:36:49 Xeno.localdomain kontact[3173]: "Item query returned empty result set" lip 19 11:36:49 Xeno.localdomain akonadi_mailfilter_agent[6433]: "Item query returned empty result set" lip 19 11:37:08 Xeno.localdomain kontact[3173]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/34/558734_r0" "No such file or directory" lip 19 11:37:08 Xeno.localdomain akonadi_indexing_agent[6425]: org.kde.pim.akonadicore: Failed to open external payload: "/home/Xeno/.local/share/akonadi/file_db_data/34/558734_r0" "No such file or directory" lip 19 11:37:08 Xeno.localdomain kontact[3173]: org.kde.pim.akonadicore: Failed to open external paylo
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 --- Comment #1 from S.Trzmiel --- I've tried to locate btrace of the process, but unfortunatelly this crach doesnt trigger drqonqui and abrt is unable to locate proper coredump. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396663] New: Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Bug ID: 396663 Summary: Imap resource crashes when large amounts of emails is moved/deleted Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: x...@x-s.com.pl Target Milestone: --- Created attachment 114011 --> https://bugs.kde.org/attachment.cgi?id=114011&action=edit suspicious changes.dat file I'm experiencing crash of imap account agent on my work account. It happens when large amount of mails (in hundrets) is moved/deleted via filtering or by hand. KMail deletes messages locally then it tries to sync changes. Then akonadi_imap_resource process usage of CPU and mem skyrockets and finally process crashes with SIGABRT. Observed anomaly: agent_config_akonadi_imap_resource_8_changes.dat gets gets larger than changes.dat files for other imap accounts (file attached) To recover I have to stop akonadi, remove changes.dat file and start akonadi again. Maybe it is trying to delete messages that not exist anymore, or file just gets corrupted. Setup: Fedora27 plasma: 5.12.6 KF5: 5.47.0 Apps: 17.12.3 Akonadi is using postgres db backend. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396127] New: Desktop Grid crashed KWin_x11
https://bugs.kde.org/show_bug.cgi?id=396127 Bug ID: 396127 Summary: Desktop Grid crashed KWin_x11 Product: kwin Version: 5.12.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: x...@x-s.com.pl Target Milestone: --- Application: kwin_x11 (5.12.6) Qt Version: 5.9.6 Frameworks Version: 5.47.0 Operating System: Linux 4.16.16-200.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: - What I was doing when the application crashed: KWin has crashed when I invoked Desktop Grid effect using hot corners (top right corner, dual display setup, screen to the right) The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc397a6940 (LWP 23620))] Thread 5 (Thread 0x7fcc0218d700 (LWP 23762)): [KCrash Handler] #6 0x7fcc2e200660 in raise () at /lib64/libc.so.6 #7 0x7fcc2e201c41 in abort () at /lib64/libc.so.6 #8 0x7fcc2e242f17 in __libc_message () at /lib64/libc.so.6 #9 0x7fcc2e2d255e in __fortify_fail_abort () at /lib64/libc.so.6 #10 0x7fcc2e2d2522 in () at /lib64/libc.so.6 #11 0x7fcc36e95348 in QV4::JIT::CompilationUnit::memoryMapCode(QString*) () at /lib64/libQt5Qml.so.5 #12 0x7fcc36e2cb3c in QV4::CompiledData::CompilationUnit::loadFromDisk(QUrl const&, QDateTime const&, QV4::EvalISelFactory*, QString*) () at /lib64/libQt5Qml.so.5 #13 0x7fcc36fdec4a in QQmlTypeData::tryLoadFromDiskCache() () at /lib64/libQt5Qml.so.5 #14 0x7fcc36fe0a85 in QQmlTypeData::dataReceived(QQmlDataBlob::SourceCodeData const&) () at /lib64/libQt5Qml.so.5 #15 0x7fcc36fd74ad in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /lib64/libQt5Qml.so.5 #16 0x7fcc36fd7d35 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /lib64/libQt5Qml.so.5 #17 0x7fcc36fd8cfb in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /lib64/libQt5Qml.so.5 #18 0x7fcc36fd8e6d in QQmlTypeLoaderThread::loadThread(QQmlDataBlob*) () at /lib64/libQt5Qml.so.5 #19 0x7fcc370488c4 in QQmlThreadPrivate::threadEvent() () at /lib64/libQt5Qml.so.5 #20 0x7fcc37048f8a in QQmlThreadPrivate::event(QEvent*) () at /lib64/libQt5Qml.so.5 #21 0x7fcc2ff2c92c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #22 0x7fcc2ff34174 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #23 0x7fcc2f0bbcd7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #24 0x7fcc2f0be45b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #25 0x7fcc2f10a0da in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #26 0x7fcc2f0baa3a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #27 0x7fcc2ef0ba1a in QThread::exec() () at /lib64/libQt5Core.so.5 #28 0x7fcc37048565 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #29 0x7fcc2ef0ff32 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #30 0x7fcc31afa50b in start_thread () at /lib64/libpthread.so.0 #31 0x7fcc2e2c116f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fcbf1102700 (LWP 23644)): #0 0x7fcc31b0082d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcc3845b604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fcc3845b649 in () at /lib64/libQt5Script.so.5 #3 0x7fcc31afa50b in start_thread () at /lib64/libpthread.so.0 #4 0x7fcc2e2c116f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fcc03fff700 (LWP 23641)): #0 0x7fcc2e2b6d66 in ppoll () at /lib64/libc.so.6 #1 0x7fcc2f108fb5 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fcc2f10a25d in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7fcc2f0baa3a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fcc2ef0ba1a in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7fcc37048565 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7fcc2ef0ff32 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fcc31afa50b in start_thread () at /lib64/libpthread.so.0 #8 0x7fcc2e2c116f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fcc1538b700 (LWP 23635)): #0 0x7fcc2e2b6d66 in ppoll () at /lib64/libc.so.6 #1 0x7fcc2f108fb5 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7fcc2f10a25d in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x
[plasmashell] [Bug 387495] New: Restarting virtual machine (KVM) caused plasma crash
https://bugs.kde.org/show_bug.cgi?id=387495 Bug ID: 387495 Summary: Restarting virtual machine (KVM) caused plasma crash Product: plasmashell Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: x...@x-s.com.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.3) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.13.15-300.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: I had Win7 VM (KVM based) opened in Virtual Machine Manager. Rebooting VM caused screen to flicker then plasma crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f684af6b940 (LWP 31396))] Thread 9 (Thread 0x7f675e8fc700 (LWP 31528)): #0 0x7f683abbf430 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f683ab79d8d in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f683ab79fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f684373735b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f68436e50ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f68435368ba in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f675ff5f577 in KCupsConnection::run() () at /lib64/libkcupslib.so #7 0x7f684353ab92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f6841c08609 in start_thread () at /lib64/libpthread.so.0 #9 0x7f68428d8e6f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f677175a700 (LWP 31506)): #0 0x7f68428c7e38 in read () at /lib64/libc.so.6 #1 0x7f683abbe0e0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f683ab799e8 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f683ab79e80 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f683ab79fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f684373735b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f68436e50ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f68435368ba in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f684353ab92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f6841c08609 in start_thread () at /lib64/libpthread.so.0 #10 0x7f68428d8e6f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f67892c0700 (LWP 31502)): #0 0x7f68428cc8bb in poll () at /lib64/libc.so.6 #1 0x7f683ab79ed9 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f683ab79fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f684373735b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f68436e50ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f68435368ba in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f68483351f6 in QQuickPixmapReader::run() () at /lib64/libQt5Quick.so.5 #7 0x7f684353ab92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f6841c08609 in start_thread () at /lib64/libpthread.so.0 #9 0x7f68428d8e6f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f681d16f700 (LWP 31500)): #0 0x7f6841c0ec3b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f684a64b604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f684a64b649 in () at /lib64/libQt5Script.so.5 #3 0x7f6841c08609 in start_thread () at /lib64/libpthread.so.0 #4 0x7f68428d8e6f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f681f5a0700 (LWP 31499)): #0 0x7f68428cc8bb in poll () at /lib64/libc.so.6 #1 0x7f683ab79ed9 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f683ab79fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f684373735b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f68436e50ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f68435368ba in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f68477992a5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f684353ab92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f6841c08609 in start_thread () at /lib64/libpthread.so.0 #9 0x7f68428d8e6f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f68254d8700 (LWP 31498)): #0 0x7f683abbf434 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f683ab7942c in g_main_context_prepa
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 S.Trzmiel changed: What|Removed |Added CC||x...@x-s.com.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368811] Screen freezed when trying to get desktop grid from desktop corner (3d effect)
https://bugs.kde.org/show_bug.cgi?id=368811 S.Trzmiel changed: What|Removed |Added CC||x...@x-s.com.pl --- Comment #14 from S.Trzmiel --- Same here, Fedora/Intel IvyBridge gfx. Can't remember when it started exactly but somwhere around Plasma 5.4. Really can't get what trigger the bug. One day I can trigger it almost every time and then it can work flawlessly for weeks. Usual running apps are Firefox, Qupzilla, Kontact, Konsole and Kate. Also Skype, qTox, Konversation and Amarok in tray. Kwin usually uses OGl 3.1 renderer, but it also hapend when using OGL 2.0 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 354949] Can't connect to gtalk account (Authentication failed: invalid-authzid)
https://bugs.kde.org/show_bug.cgi?id=354949 S.Trzmiel changed: What|Removed |Added CC||x...@x-s.com.pl -- You are receiving this mail because: You are watching all bug changes.
