[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 S Clark changed: What|Removed |Added CC||smc+kdebugs@dogphilosophy.n ||et --- Comment #10 from S Clark --- I'm not certain if the problem I'm experiencing is exactly the same, but for the last few versions (of both qt5 and akregator), the "preview" flickers and never shows anything. I see a stream of "org.kde.pim.webengineviewer: WebEngine render process crashed" messages if I start akregator from a terminal. Haven't had time to try to custom-build a "debug" installation (Arch Linux, if that matters). Oddly, I actually tried downgrading qt5, akregator, kdepim, etc. and have not been able to find a version that _doesn't_ do this on my system for akregator any more. Falkon, on the other hand, still works normally, so I'm assuming this isn't a problem with qt5 webengine itself. At one point I'd found a posting on one of the QT websites that (as I recall) was blaming this on some kind of thread-safety issue in the way kdepim/akregator was using it, but I can't find the page any more and may be mis-remembering. Not sure if that helps, but figured I'd throw in what information I have. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 S Clark <smc+kdeb...@dogphilosophy.net> changed: What|Removed |Added CC||smc+kdebugs@dogphilosophy.n ||et --- Comment #5 from S Clark <smc+kdeb...@dogphilosophy.net> --- If it helps, what seems to be happening is the feeds.opml file that akregator reads its feeds from gets truncated to 1 byte. Not sure what *exactly* is happening, but that's what I see every time this happens (about once every few weeks for the last couple of months). I have to remember to export my feedlist regularly so that I can replace/reimport after each crash. -- 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
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 S Clark <smc+kdeb...@dogphilosophy.net> changed: What|Removed |Added CC||smc+kdebugs@dogphilosophy.n ||et --- Comment #4 from S Clark <smc+kdeb...@dogphilosophy.net> --- Also confirmed... This seems to specifically be a problem with the behavior around the "mark selected article read after..." advanced setting. I think this defaults to 0 seconds (i.e. immediately) which is what I used to have it set to. Previously, this just meant the article was marked "read" as soon as it was clicked, and if you had the unread filter set, it would then disappear from the list AFTER you clicked away from it to another article. Now the article is immediately removed from the list, causing the selection to automagically drop to the next, mark *it* unread, remove it, etc. You can watch it happen more slowly if you go to settings -> configure akregator -> advanced and set it to mark as read after, say, 5 seconds. Perhaps this bug should just read "Read articles should not be removed by the unread filter while the article is selected"? -- 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 276077] unable to send queued message
https://bugs.kde.org/show_bug.cgi?id=276077 --- Comment #25 from S Clark smc+kdebugs dogphilosophy net 2011-09-07 21:43:58 --- I've only tried it once so far, but I've just updated to 4.7.1, and now kmail does seem to be correctly popping up the request for access to kwallet and send on the first try. Perhaps this is now fixed in 4.7.1? -- 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 276077] unable to send queued message
https://bugs.kde.org/show_bug.cgi?id=276077 --- Comment #22 from S Clark smc+kdebugs dogphilosophy net 2011-08-31 20:49:22 --- I wanted to follow up and report that my AUDITSYSCALL thing does, indeed, turn out to be unrelated. KMail is still doing this (i.e. silently refusing to send) to me. I have noticed that on occasion if log out of KDE and back in, then restart kmail, I get the kwallet popup once which is apparently for the incoming (IMAP) mail. On a couple of occasions at least, I can then close kmail, disconnect from the network (via wicd), then reconnect...and all of a sudden I get another kwallet popup asking for permission, and when granted, I finally get an email sent notice (note that kmail appears to have been closed at this point, but evidently the process trying to send via SMTP is still running in the background, blocked on whatever the heck it is that's causing this problem). Is KMail maybe not asking for access to the password wallet for SMTP on the assumption that it has already accessed the wallet for the IMAP password and doesn't think it needs to again, or something? (Just grasping at metaphorical straws here, I have no idea and this bug is starting to drive me Nucking Futs...) -- 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 276077] unable to send queued message
https://bugs.kde.org/show_bug.cgi?id=276077 --- Comment #19 from S Clark smc+kdebugs dogphilosophy net 2011-07-29 17:17:42 --- Here's a strange thought: for people having this problem, what do you get if you do zcat /proc/config.gz | grep AUDITSYSCALL? I finally got around to tracking down an unrelated irritation (relating to udisks permissions) that came down to this, which also solved the no 'shut down' option in the menu issue that I've been having but not caring about for so long. Maybe coincidentally, I've not seen this kmail issue since then, either. I'm just wondering if issues with the network state detection might be another consolekit-related problem (consolekit evidently requires CONFIG_AUDITSYSCALL=y to function properly). -- 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 276077] unable to send queued message
https://bugs.kde.org/show_bug.cgi?id=276077 S Clark smc+kdeb...@dogphilosophy.net changed: What|Removed |Added CC||smc+kdebugs@dogphilosophy.n ||et --- Comment #7 from S Clark smc+kdebugs dogphilosophy net 2011-07-14 01:12:01 --- I'm having this problem right now, and I'm not using NetworkManager - I'm using WICD. Messages just sit in the outgoing folder and refuse to go anywhere, and there are no messages or other indication why. This has continued through a full shutdown and restart. This just started happening today on the latest 4.6.x version, so I tried upgrading to the 4.7 RC2 - same problem on 4.7RC2 as well. -- 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 276077] unable to send queued message
https://bugs.kde.org/show_bug.cgi?id=276077 --- Comment #8 from S Clark smc+kdebugs dogphilosophy net 2011-07-14 01:16:49 --- Oh, additional note: I'm RECEIVING email (via IMAP) just fine, only sending is failing for me. -- 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 276077] unable to send queued message
https://bugs.kde.org/show_bug.cgi?id=276077 --- Comment #9 from S Clark smc+kdebugs dogphilosophy net 2011-07-14 01:40:51 --- Okay, one last note and I'll shut up - I finally got it to send by disconnecting and reconnecting, which I assume made KDE notice that I was connected (I had originally connected to the network before starting KDE). Once I did that, it looks like the stuck messages finally went through. It looks to me like solid/KDE has gotten stuck in the NetworkManager why would you be connected to the network without starting a GUI login first? thinking, so KDE assumes you're offline unless it gets a we've just connected to the network signal after starting. That would also explain the report on the forum from someone seeing this problem with a static IP as well. That's my guess anyway. The aspect of this bug that I would argue belongs to kmail is the lack of a warning or indication that the reason it's not sending is because it hasn't been told the network has been started (even though it runs IMAP just fine in the meantime.) Should a separate bug be opened for solid(?) about it not checking for a pre-existing network connection when KDE starts? -- 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
