[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #14 from K G <go...@wp.pl> --- This fix do not prevent from corrupting feeds. In my case it was happening sometimes after akregator crash. It only make akregator usable with global menu. it avoids akregator crashing 100% times. After applying this patch, I didn't have any crash. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #12 from K G <go...@wp.pl> --- Created attachment 110493 --> https://bugs.kde.org/attachment.cgi?id=110493=edit The simplest fix -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #11 from K G <go...@wp.pl> --- Created attachment 110492 --> https://bugs.kde.org/attachment.cgi?id=110492=edit Trace of double initialisation -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #10 from K G <go...@wp.pl> --- I'm not sure if it's relevant for this bug but it is for sure relevant to bug 384975 marked as duplicate. The problem is that akregator kpart is initialized twice, recursively. (See attached trace #45 and #5) Akregator::MainWindow::loadPart() is called twice. Because of that in ActionManagerImpl we have corrupted reference to d->actionCollection that causes dump on calling setArticleActionsEnabled. The reason of recursive initialization seams to be method Akregator::MainWindow::saveProperties() that is called by QtWebEngine before kpart if fully initialized. The simplest solution would be to remove initialization of kpart from this method and returning if kpart it's not initialized. Or skipping initialization only in such case if possible. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #9 from K G <go...@wp.pl> --- I'm not sure if it's relevant for this bug but it is for sure relevant to bug 384975 marked as duplicate. The problem is that akregator kpart is initialized twice, recursively. (See attached trace #45 and #5) Akregator::MainWindow::loadPart() is called twice. Because of that in ActionManagerImpl we have corrupted reference to d->actionCollection that causes dump on calling setArticleActionsEnabled. The reason of recursive initialization seams to be method Akregator::MainWindow::saveProperties() that is called by QtWebEngine before kpart if fully initialized. The simplest solution would be to remove initialization of kpart from this method and returning if kpart it's not initialized. Or skipping initialization only in such case if possible. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"
https://bugs.kde.org/show_bug.cgi?id=383710 --- Comment #8 from K G <go...@wp.pl> --- from bug 384975 Steps to reproduce bug: Turn on global menu. Turn on Akregator Select any feed in Akregator Boom - Crash -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 384975] Akregator crash after selecting feed.
https://bugs.kde.org/show_bug.cgi?id=384975 K G <go...@wp.pl> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #4 from K G <go...@wp.pl> --- This is not duplicate of 383710. In 383710 crash is only when akregator was started automatically after login. After manual run there is no crash. In this case there is crash after every run (in moment of selecting first feed). Akregator is totally unusable. But problem appears only if global menu is active. After disabling global menu there is no crash after manual nor automatic run. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 384975] Akregator crash after selecting feed.
https://bugs.kde.org/show_bug.cgi?id=384975 --- Comment #2 from K G <go...@wp.pl> --- I've figured out, that crash appears only if global menu is active. After disabling global menu in widget style Akregator stops crashing. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 384975] Akregator crash after selecting feed.
https://bugs.kde.org/show_bug.cgi?id=384975 --- Comment #1 from K G <go...@wp.pl> --- I've figured out, that crash appears only if global menu is active. After disabling global menu in widget style Akregator stops crashing. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 384975] New: Akregator crash after selecting feed.
https://bugs.kde.org/show_bug.cgi?id=384975 Bug ID: 384975 Summary: Akregator crash after selecting feed. Product: akregator Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: go...@wp.pl Target Milestone: --- Application: akregator (5.6.1) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-35-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: It happens every time. After starting akregator and selecting any feed akregator crashes. It seams that feed list causes crash. The only option to avoid crashing is to turn on Combine View that do not have normal feed list. - Custom settings of the application: home directory is migrated from Kubuntu 17.4 -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcf288a7980 (LWP 16956))] Thread 21 (Thread 0x7fceb1c6c700 (LWP 16987)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fcf39b5b784 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fcf39b5b7c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fcf463416ba in start_thread (arg=0x7fceb1c6c700) at pthread_create.c:333 #4 0x7fcf4b5383dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 20 (Thread 0x7fced1ffb700 (LWP 16982)): #0 0x7fcf4b52c70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcf445cf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcf445cf49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcf4be5494b in QEventDispatcherGlib::processEvents (this=0x7fcec8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fcf4bdfd7ca in QEventLoop::exec (this=this@entry=0x7fced1ffac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fcf4bc26cd4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7fcf4bc2b989 in QThreadPrivate::start (arg=0x1129aa0) at thread/qthread_unix.cpp:368 #7 0x7fcf463416ba in start_thread (arg=0x7fced1ffb700) at pthread_create.c:333 #8 0x7fcf4b5383dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7fced27fc700 (LWP 16981)): #0 0x7fcf4b52824d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcf2d62cf61 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #2 0x7fcf33f9aa2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fcf33f9b4a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fcf33f9b560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fcf33fa97a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fcf2d65b078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7fcf463416ba in start_thread (arg=0x7fced27fc700) at pthread_create.c:333 #8 0x7fcf4b5383dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7fced2ffd700 (LWP 16980)): #0 0x7fcf4b5282ad in write () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcf4b4a9bff in _IO_new_file_write (f=0x7fcf4b7f6540 <_IO_2_1_stderr_>, data=0x7fced2ff9cb0, n=45) at fileops.c:1263 #2 0x7fcf4b4aa38a in new_do_write (to_do=45, data=0x7fced2ff9cb0 "[warn] epoll_wait: B\305\202\304\231dny deskryptor pliku\n", fp=0x7fcf4b7f6540 <_IO_2_1_stderr_>) at fileops.c:518 #3 _IO_new_file_xsputn (f=0x7fcf4b7f6540 <_IO_2_1_stderr_>, data=, n=45) at fileops.c:1342 #4 0x7fcf4b480f94 in buffered_vfprintf (s=0x7fcf4b7f6540 <_IO_2_1_stderr_>, format=, args=) at vfprintf.c:2341 #5 0x7fcf4b47e32d in _IO_vfprintf_internal (s=s@entry=0x7fcf4b7f6540 <_IO_2_1_stderr_>, format=0x7fcf3176a734 "[%s] %s\n", ap=ap@entry=0x7fced2ffc268) at vfprintf.c:1293 #6 0x7fcf4b547b89 in ___fprintf_chk (fp=0x7fcf4b7f6540 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:35 #7 0x7fcf3175245e in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #8 0x7fcf31752654 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #9 0x7fcf31756c38 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #10 0x7fcf31740e2d in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #11 0x7fcf3c2af76e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7fcf3c2ab225 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7fcf3c2c7efa in ?? () from
[kmail2] [Bug 322039] Unable to display/reply/or forward message.
https://bugs.kde.org/show_bug.cgi?id=322039 --- Comment #2 from K G go...@wp.pl --- Bug is still present in 4.11 rc2 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322038] New: Big cpu conumption.
https://bugs.kde.org/show_bug.cgi?id=322038 Bug ID: 322038 Summary: Big cpu conumption. Classification: Unclassified Product: kmail2 Version: 4.11 beta2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: go...@wp.pl Kmail, akonadiserver and mysql consuming a lot of cpu. In akonadi konsole I can see that folderlist is refreshed many times per second. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322039] New: Unable to display/reply/or forward message.
https://bugs.kde.org/show_bug.cgi?id=322039 Bug ID: 322039 Summary: Unable to display/reply/or forward message. Classification: Unclassified Product: kmail2 Version: 4.11 beta2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: go...@wp.pl After selecting message in message list it's not displayed. You can't also reply or forward message. Reproducible: Always Steps to Reproduce: 1.Choose any folder 2.Chose any message 3. Actual Results: Appears mesaage Retrieving Folder Contents Expected Results: Message displayed After choosing reply or forward dialog Please wait while message is transferred appears. Aplication itself seams to be very responsive. Sometimes message content is displayed after few minutes, but sometimes not even after half hour. You can display message in akonadi console without problems. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322039] Unable to display/reply/or forward message.
https://bugs.kde.org/show_bug.cgi?id=322039 --- Comment #1 from K G go...@wp.pl --- Created attachment 80991 -- https://bugs.kde.org/attachment.cgi?id=80991action=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 195094] Gmail IMAP: [Gmail] folder not accessible
https://bugs.kde.org/show_bug.cgi?id=195094 --- Comment #4 from K G govik wp pl 2011-02-04 13:31:15 --- Workaround working for me is: 1) Chose menage local subscriptions 2) Deselect [Gmail] folder it cause to diaper its subfolders 3) Restart Kontact/KMail 4) [Gmail] should be still unchecked but its subfolders should return and problem should gone -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 263284] New: Pernamently unread mails migrated from old kmail
https://bugs.kde.org/show_bug.cgi?id=263284 Summary: Pernamently unread mails migrated from old kmail Product: Akonadi Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mixed Maildir resource AssignedTo: kdepim-bugs@kde.org ReportedBy: go...@wp.pl CC: kevin.kram...@gmx.at Version: unspecified (using KDE 4.5.95) OS:Linux After migration from old kmail, there was some mails that are marked as unread. I can mark them as read in kmail, or in akonadi colsole, but after synchronization, they are unread again. Reproducible: Always The same it happens when i add resource without migration. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 263284] Pernamently unread mails migrated from old kmail
https://bugs.kde.org/show_bug.cgi?id=263284 --- Comment #1 from K G govik wp pl 2011-01-16 03:00:25 --- After adding second resource with the same directory different mail was treat as unread. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 257977] messages in threads marked as ignored are treated as unread
https://bugs.kde.org/show_bug.cgi?id=257977 K G go...@wp.pl changed: What|Removed |Added CC||go...@wp.pl --- Comment #1 from K G govik wp pl 2011-01-16 03:02:38 --- After adding second resource with the same directory another mails was treat as unread. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 195094] Gmail IMAP: [Gmail] folder not accessible
https://bugs.kde.org/show_bug.cgi?id=195094 K G go...@wp.pl changed: What|Removed |Added CC||go...@wp.pl --- Comment #2 from K G govik wp pl 2010-12-26 18:42:49 --- The same problem with kde 4.6rc1 and kontakt4.6b3 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259143] Kaddressbook loses addresses
https://bugs.kde.org/show_bug.cgi?id=259143 K G go...@wp.pl changed: What|Removed |Added CC||go...@wp.pl --- Comment #8 from K G govik wp pl 2010-12-11 15:35:45 --- Hi, as I see contacts are not only in Kaddresbook(4.4.8) displayed like this. It looks the same in AkonadiConsole (witch has 4.6b2 version). I store contacts in one vcard file. The file wasn't damaged anyway and it seams to be valid. In Console data are inaccessible by vcard recource as well as traditional Kdaddressbok recource. By Kaddressbok resource it sees only some rdf data, by vcard recource it sees nothing. I've got the same configuration. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
