[neon] [Bug 447008] kmail unable to receive pop3 emails since 5.19.0 (21.12.0) update a few days ago.
https://bugs.kde.org/show_bug.cgi?id=447008 Peter Wibberley changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #2 from Peter Wibberley --- I'm suffering from the same issue. Impressed, though, that a solution already exists, but I have to confess to not being clear on how to use the commit in the link. Are there any instructions on how to do this? And/or will the the solution be in an update in the next few days? Many thanks and regards -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 Peter Wibberley changed: What|Removed |Added Platform|Archlinux Packages |Neon Packages Version|5.13.1 |5.18.90 CC||p.wibber...@btinternet.com --- Comment #19 from Peter Wibberley --- Actually kmail 5.18.3. Given that a lot of email correspondents are using Outlook, this problem is a bit inconvenient, and detracts from the professionalism of the replies we make using kmail. Any solution/workaround would be much appreciated. Thanks and regards -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 433204] baloo_file SEGV
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #34 from Peter Wibberley --- (In reply to tagwerk19 from comment #31) > (In reply to Peter Wibberley from comment #30) > > ... Any clues ... > First off, I'd say create a file > /etc/sysctl.d/40-neon-inotify.conf > as per comment #12 (at least until 5.11). That would set the > max_user_watches every reboot. > > Then I'd see if > coredumpctl > gave a list of dumps as per comment #23 > > If it does, and you can get a backtrace, that would be a step forward. Tagwerk19, Sorry about the long gap, but life got in the way for a couple of months. In the meantime, I migrated from Neon LTS to the User Edition (using the instructions at https://userbase.kde.org/Neon/LTS/EOL). I had hoped that this might cure the problem, but alas not. The situation now is as follows: (1) If I use the default value for fs.inotify.max_user_watches of 8192 and run 'balooctl enable', I get a stream of messages, "kf.baloo: KDE Baloo File Indexer has reached the inotify folder watch limit. File changes will be ignored." (2) If I just double fs.inotify.max_user_watches to only 16384, and run 'balooctl enable', the watch limit error messages stop. However, 'balooctl status' shows the Baloo File Indexer as stopping after a few seconds. (3) If I run 'balooctl enable', wait for it to stop, and then run 'coredumpctl gdb ', as you recommended, I get, #0 0x7f1aff1919f4 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #1 0x7f1aff194e80 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #2 0x7f1aff195165 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #3 0x7f1aff195892 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #4 0x7f1aff195ed4 in mdb_get () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #5 0x7f1b0069d458 in Baloo::IdFilenameDB::get(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #6 0x7f1b006921aa in Baloo::DocumentUrlDB::get(unsigned long long) const () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #7 0x7f1b006afa19 in Baloo::Transaction::documentUrl(unsigned long long) const () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #8 0x55fa2c6779f3 in ?? () #9 0x7f1b006be7ac in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 ... #65486 0x7f1b006be7fe in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #65487 0x55fa2c67811c in ?? () #65488 0x7f1b001f5ff2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #65489 0x7f1b001f2bec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #65490 0x7f1aff200609 in start_thread (arg=) at pthread_create.c:477 #65491 0x7f1affd25293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (4) I've also run strace when the indexer is still running and again when it's stopped, and the outputs look completely different. If it's running, the strace terminates in an orderly manner, but if the indexer isn't running then I get the SEGV fault. The fault seems to occur when a poll command gets a timeout. No idea what to make of all this! I would try a fresh install, but I had hoped the switch to the User Edition would achieve the same thing. Any suggestions? As ever, many thanks and regards Peter -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 433204] baloo_file SEGV
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #30 from Peter Wibberley ---
Following tagwerk19's suggestion (Comment21), I've rerun 'strace baloo_file',
making sure not to index the file I'm logging the strace output to. This has
saved about 130,000 lines of output. Thank you, tagwerk19!
The final 20 lines of strace output, from Line 85841 onwards, are now,
openat(AT_FDCWD, "/home/peter/Music/Marc Maron",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 15
fstat(15, {st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0
getdents64(15, /* 10 entries */, 32768) = 520
getdents64(15, /* 0 entries */, 32768) = 0
close(15) = 0
openat(AT_FDCWD, "/home/peter/Music/Dirk Gently Series x",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 15
fstat(15, {st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0
getdents64(15, /* 8 entries */, 32768) = 528
getdents64(15, /* 0 entries */, 32768) = 0
close(15) = 0
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLPRI},
{fd=11, events=POLLIN}, {fd=14, events=POLLIN}], 5, 2577) = 0 (Timeout)
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLPRI},
{fd=11, events=POLLIN}, {fd=14, events=POLLIN}], 5, 0) = 1 ([{fd=3,
revents=POLLIN}])
read(3, "\1\0\0\0\0\0\0\0", 16) = 8
futex(0x55d72a31eca0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55d72a31ec50, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55d72a043578, FUTEX_WAKE_PRIVATE, 1) = 1
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLPRI},
{fd=11, events=POLLIN}, {fd=14, events=POLLIN}], 5, 115985 ) =
?
+++ killed by SIGSEGV +++
So, I'm still getting "+++ killed by SIGSERV +++", which presumably explains
why baloo stops running.
A bit odd, is the 3 "poll" messages. Earlier in the log file, these occur
only about once every 7000 lines, until this trio of them in the final few
lines.
There's about 12000 instances of inotify_add_watch. Running 'find . -type d
-print| wc -l' tells me I have nearly 36,000 directories. I don't know how
many of these are excluded from file indexing, so I can't say whether I've got
an 'inotify_add_watch' for every indexed directory, but I guess it's possible.
Earlier this evening, I was getting only 8000 instances of inotify_add_watch,
until I realised that max_user_watches had reverted to 8192, and I increased it
up to 129762 again. Before increasing the limit, there was also "ENOSPC (No
space left on device)" appended to the last 450 or so 'inotify_add_watch'
messages. At the moment, I can't think of anything that could have suddenly
increased the number of directories way over 8000 or so on or about 17th
December, when the problem started, but may be there was. But when I increase
the limit to circa 130,000, the problem doesn't go away: could there also be
some parameter, other than max_user_watches, which is still too low, and
causing the SIGSEGV fault?
Any clues here as to what's going wrong?
Thanks and regards
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 433204] baloo_file SEGV
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #29 from Peter Wibberley --- (In reply to tagwerk19 from comment #25) > (In reply to tagwerk19 from comment #23) > > You're the first one that's happened to :-) > Mea Culpa. > > My apologies, that should have course read > > You're *not* the first one that's happened to :-) No worries. From the tone of your comment, I just assumed you were pulling my leg! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] Baloo File Indexer will not keep running. Changing fs.inotify.max_user_watches not having any effect!
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #22 from Peter Wibberley --- (In reply to tagwerk19 from comment #21) > I think we do need someone who knows to come in here... > > A couple of observations might help though, I see lines like: > > ioctl(14, FIONREAD, [32]) = 0 > read(14, "\3\0\0\0\0\2\0\0\0\0\0\0\20\0\0\0testfile2.txt\0\0\0", 32) = 32 > > appear when I write to "testfile2.txt". Could you be logging to a file and > that file being indexed? > > I've also looked at: > > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > It's being actively updated. Maybe it can give a pointer or two. Doh! The file, "210224Baloo_file", which is referenced 42,835 times is the file to which I was redirecting the strace output! I will exclude this from indexing and see if I get more interesting (and if not more interesting, at least less) output. Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] Baloo File Indexer will not keep running. Changing fs.inotify.max_user_watches not having any effect!
https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #20 from Peter Wibberley ---
(In reply to tagwerk19 from comment #19)
> I would look though at what baloo_file had started to index when it started
> to log errors, maybe it's possible to see something strange...
>
> You can exclude folders from indexing, either through system settings /
> search or by editing the .config/baloofilerc file. Add a line:
>
> exclude folders[$e]=$HOME/dontindexme
>
> and you can skip index that folder (and its subfolders). Maybe you can pin
> down a folder that is giving trouble.
>
> Alas I cannot help with the SIGSEGV, need someone with experience of core
> dumps...
Tagewerk19,
Not a lot of obvious errors. However, the last 130,000 lines of the 210,000
lines from strace (except for the final line, "+++ killed by SIGSEGV +++")
consist of 43,000 repeats of the three lines,
ioctl(14, FIONREAD, [48]) = 0
read(14, "\1\0\0\0\2\0\0\0\0\0\0\0 \0\0\000210224Baloo_file"..., 48) = 48
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLPRI},
{fd=11, events=POLLIN}, {fd=14, events=POLLIN}], 5, 10) = 1 ([{fd=14,
revents=POLLIN}])
That seems a little strange.
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 433204] Baloo File Indexer will not keep running. Changing fs.inotify.max_user_watches not having any effect!
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #18 from Peter Wibberley --- (In reply to tagwerk19 from comment #17) Tagwerk19, Thank you for the suggestion. No need to kill the process, as it's dying anyway. You're not wrong about shedloads: over 20MB and 200,000 lines collected in just a few seconds. There's 11973 instances or 'inotify_add_watch', with an 'inotify_init1(IN_CLOEXEC) and an 'inotify_init()' very early on. There appears to be several phases with different clusters of error messages. And it ends with "+++ killed by SIGSEGV +++" and "Segmentation fault", which would seem to explain why it's not running for long. I don't want to burden you with megabytes of probably superfluous detail, but do you have any suggestions about how I should proceed? Thank you again, and regards P > I think that baloo_file watches directories (mostly) and not files. > > I get this info from a trick of killing the baloo_file process and starting > from the command line under strace. So... > > ps ax | grep baloo_file > kill ... > strace baloo_file > > This gives shedloads of information; details of every system call. You can > however see the "inotify_add_watch' calls for each individual directory and > their return values - which can either include a steadily increasing count > or the 'changes will be ignored' message. You should be able to see a bit > more about what's happening > > I haven't worked how to see what info is being passed to the > baloo_file_extractor process and what it is doing. I also haven't discovered > where baloo logs its activities, that would be good to know! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] Baloo File Indexer will not keep running. Changing fs.inotify.max_user_watches not having any effect!
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #16 from Peter Wibberley --- (In reply to Harald Sitter from comment #15) > I can't really say anything about that I know nothing about baloo. The > inotify cap needs fixing one way or another, but if increasing the cap > doesn't help you I guess your problem has nothing to do with it. Understood. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] Baloo File Indexer will not keep running. Changing fs.inotify.max_user_watches not having any effect!
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #14 from Peter Wibberley --- (In reply to Harald Sitter from comment #13) The thing I don't understand is that, up until 17 December, I would have had max_user_watches set at 8192 with the number of files not being significantly less than the current number, and it was working OK. Now, even a 16-fold increase in the value doesn't seem to make any difference. Hence I was wondering whether the problem could have been related to updates. >From my perspective, my problem is getting more diagnostic information. Thanks and regards > (In reply to Jonathan Riddell from comment #10) > > I wonder if this should be built into baloo rather than being distro > > specific > > It will sort itself with kernel 5.11. Well, to a degree. > > If my maths is correct linux 5.11 sets the watch limit to > 32G ~> 260k > 16G ~> 130k > 8G ~> 65k > 4G ~> 30k > > So this can conceivably still be easily exhausted. e.g. the original > reporter would need to have >16G or manually set the watch limit to track > their 200k files. > > As I've said, the UX is fairly weak since we don't inform the user when they > run out of inotify capacity. KDirWatch has the similar problem really > (albeit more with instances than watches). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] Baloo File Indexer will not keep running. Changing fs.inotify.max_user_watches not having any effect!
https://bugs.kde.org/show_bug.cgi?id=433204 Peter Wibberley changed: What|Removed |Added Summary|fs.inotify.max_user_watches |Baloo File Indexer will not |is set to 8192, which is|keep running. Changing |too low for Baloo to work |fs.inotify.max_user_watches |properly|not having any effect! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] fs.inotify.max_user_watches is set to 8192, which is too low for Baloo to work properly
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #11 from Peter Wibberley --- Jonathan, Tried 129762, but I still have the problem. Incidentally, I tried running 'balooctl monitor' and then 'balooctl enable' from another Konsole. I got the messages as follows: Waiting for file indexer to start Press Ctrl+C to stop monitoring File indexer is running Starting Indexing modified files Starting Checking for stale index entries Waiting for file indexer to start Press Ctrl+C to stop monitoring The 'Total number of files indexed', as reported by 'balooctl status' does not change (on my system remaining at just over 200,000). As ever, thanks to everyone for their interest and suggestions. Any further suggestions for further diagnostics I can run will be much appreciated. P -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] fs.inotify.max_user_watches is set to 8192, which is too low for Baloo to work properly
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #9 from Peter Wibberley --- I have no idea whether this is significant. As per my original message, Dolphin stopped displaying any timeline on 17 December 2020 (which is how I noticed baloo wasn't working). From an inspection of var/log/apt/history.log, for packages with 'baloo' in the name, there was an update on 13 December 2020 of (1) libkf5baloowidgets5:amd64 (4:20.08.3-0xneon+20.04+focal+build8, 4:20.12.0-0xneon+20.04+focal+build9) The next update, on 16 December 2020, included: (1) libkf5balooengine5:amd64 (5.76.0-0xneon+20.04+focal+build12, 5.77.0-0xneon+20.04+focal+build13) (2) libkf5baloo5:amd64 (5.76.0-0xneon+20.04+focal+build12, 5.77.0-0xneon+20.04+focal+build13) (3) baloo-kf5:amd64 (5.76.0-0xneon+20.04+focal+build12, 5.77.0-0xneon+20.04+focal+build13). The next update after that wasn't until 24 December 2020, with nothing obviously related to baloo being updated. The next updates of baloo packages were 8 and 11 January 2021. The current versions, according to 'apt list', are all (5.79.0-0xneon+20.04+focal+build17 amd64) Regards -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433204] fs.inotify.max_user_watches is set to 8192, which is too low for Baloo to work properly
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #5 from Peter Wibberley --- All, Thank you for your comments. I presume that the value of 8192 for max_user_watches is the Neon default, as I haven't previously changed it (unless something else did). I had thought that, even if the value were very low and were causing baloo to fail, then doubling it should have made a difference. I've now tried 65472 (i.e. 65536 less a bit) (and confirmed the change with 'cat /proc/sys/fs/inotify/max_user_watches') but the problem still persists. Do you have any suggestions of how high a value of max_user_watches I should try? And are there any other diagnostics I can run? Many thanks and best regards Peter -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 433204] New: Baloo File Indexing always stops
https://bugs.kde.org/show_bug.cgi?id=433204 Bug ID: 433204 Summary: Baloo File Indexing always stops Product: frameworks-baloo Version: 5.79.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: p.wibber...@btinternet.com Target Milestone: --- As of 17 December 2020, Dolphin is not displaying any files in timeline. Running 'balooctl status' shows "Baloo File Indexer is not running". I can run 'balooctl enable', immediately after which 'balooctl status' shows that it is running but, within a couple of seconds, running it again shows that it has stopped. No additional files get indexed. (I have just over 200,000 files indexed and the current size of index is 28.73GB.) On a couple of occasions, running 'balooctl status' gave the message "kf.baloo: KDE Baloo File Indexer has reached the inotify folder watch limit. File changes will be ignored.". This message was repeated about 470 times, following which it reported, "Baloo File Indexer is running". However, it stopped a few seconds later. I tried running "sudo sysctl -w fs.inotify.max_user_watches=16383", increasing the previous value of 8192, but this has not made any difference. I'm not sure how to obtain any more troubleshooting information. Any advice much appreciated. Thanks and regards STEPS TO REPRODUCE 1. In Konsole, run "balooctl status". 2. Run "balooctl enable". 3. Run "balooctl status" two or three times more. OBSERVED RESULT 'balooctl status' reports "Baloo File Indexer is not running" 'balooctl enable' reports "Enabling and starting the File Indexer" 'balooctl status' reports "Baloo File Indexer is running" if run immediately, but then "Baloo File Indexer is not running" 3 or 4 seconds later. EXPECTED RESULT 'balooctl status' should report "Baloo File Indexer is running". SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Plasma LTS 5.18 (available in About System) KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel Version 5.4.0-65-generic -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425503] QGIS3.10.4 installs on Kubuntu 20.04 but not KDE Neon 20.04
https://bugs.kde.org/show_bug.cgi?id=425503 Peter Wibberley changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425503] QGIS3.10.4 installs on Kubuntu 20.04 but not KDE Neon 20.04
https://bugs.kde.org/show_bug.cgi?id=425503 --- Comment #3 from Peter Wibberley --- Following an update recently - not sure exactly when - the problem is resolved, and QGIS3.10 has installed perfectly. I don't know who to thank, but thank you. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425503] QGIS3.10.4 installs on Kubuntu 20.04 but not KDE Neon 20.04
https://bugs.kde.org/show_bug.cgi?id=425503 --- Comment #1 from Peter Wibberley --- N.B. Andrew-63 was having a similar problem with KDE Neon 18.04 - https://gis.stackexchange.com/questions/351962/problem-installing-qgis-3-12-on-linux-kde-neon . -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425503] New: QGIS3.10.4 installs on Kubuntu 20.04 but not KDE Neon 20.04
https://bugs.kde.org/show_bug.cgi?id=425503 Bug ID: 425503 Summary: QGIS3.10.4 installs on Kubuntu 20.04 but not KDE Neon 20.04 Product: neon Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: p.wibber...@btinternet.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY 'QGIS 3.10.4+dfsg-1ubuntu2 (focal)' won't install on KDE Neon. I tried both before updating from 18.04 to 20.04 and after, and I also tried a fresh install of neon-user-20200815-2050. I tried both Discover and Synaptics Package Manager. In contrast, QGIS installs OK with Kubuntu 20.04. The KDE Neon installation fails on package 'qgis' broken dependencies: specifically, package 'qgis', Conflicts: uim-qt3 Breaks: qgis-common (<3.4.5) Breaks: qgis-provider-grass (<2.14.0) Recommends: qgis-provide-grass Suggests: gpsbabel Replaces: qgis-common (<3.4.5) Replaces: qgis-provider-grass (<2.14.0) STEPS TO REPRODUCE 1. Install neon-user-20200815-2050.iso 2. Open Discover or Synaptics Package Manager 3. Attempt to install QGIS OBSERVED RESULT Discover reports "Dependency resolution failed"; Synpatics reports QGIS is broken. EXPECTED RESULT QGIS installs SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Distributor ID: Neon Description:KDE neon Plasma LTS Edition 5.18 Release:20.04 Codename: focal (available in About System) KDE Plasma Version: 5.18.5 (on update of 18.04, 5.19.? on fresh install) KDE Frameworks Version: 5.72.0 (on update of 18.04) Qt Version: 5.14.2 (on update of 18.04) ADDITIONAL INFORMATION Apologies if I have omitted any important information, or misunderstood anything. Thanks and regards -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 412914] Cannot update due to PKCON error
https://bugs.kde.org/show_bug.cgi?id=412914 Peter Wibberley changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 412914] Cannot update due to PKCON error
https://bugs.kde.org/show_bug.cgi?id=412914 --- Comment #2 from Peter Wibberley --- Running sudo apt update seems to have solved the problem. It is confusing, though, as I had undestood that pkcon is supposed to be used in place of apt. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 412914] Cannot update due to PKCON error
https://bugs.kde.org/show_bug.cgi?id=412914 --- Comment #1 from Peter Wibberley --- Discover no longer seems to be crashing when I attempt an update. However, the error with 'pkcon refresh' is still occurring. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 412914] New: Cannot update due to PKCON error
https://bugs.kde.org/show_bug.cgi?id=412914 Bug ID: 412914 Summary: Cannot update due to PKCON error Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: p.wibber...@btinternet.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Discover crashes when updating. This may be due to an error when running "pkcon refresh" in a terminal. This gives the following messages: Refreshing cache [=] Loading cache [=] Downloading packages [=] Running [=] Finished [=] Fatal error: E: Repository 'http://archive.neon.kde.org/user/lts bionic InRelease' changed its 'Origin' value from 'user/lts bionic' to 'neon' E: Repository 'http://archive.neon.kde.org/user/lts bionic InRelease' changed its 'Label' value from 'KDE neon - User Edition (LTS)' to 'KDE neon - Plasma LTS Edition' System Information is as follows: KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 Kernal Version: 4.15.0-64-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411204] New: With two email accounts, SPF sees emails as being from the 'Set as Default' account, leading to authentication/DMARC problems when sending from other account
https://bugs.kde.org/show_bug.cgi?id=411204 Bug ID: 411204 Summary: With two email accounts, SPF sees emails as being from the 'Set as Default' account, leading to authentication/DMARC problems when sending from other account Product: kmail2 Version: 5.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- SUMMARY If there are two email accounts, Sending Policy Framework seems to think emails are sent always from the 'Set as Default' account, leading to authentication/DMARC problems when sending from other account. STEPS TO REPRODUCE 1.Under Accounts.Sending, set up two SMTP Sending Accounts with different ISPs 2.One of the accounts will be 'Set as Default' 3.Send a message to a Gmail account with each Account. 4. Under Account.Sending swap 'Set as Default' to the other account. OBSERVED RESULT The email from the Sending Account which is 'Set as Default' will be delivered; the email from the other account will fail on DMARC policies. When the 'Set as Default' is swapped to the other account, the account from which the email is successfully delivered and the account from which the email is rejected will swap over. EXPECTED RESULT Emails from both accounts should be sent and not rejected. SOFTWARE/OS VERSIONS KDE Plasma Version: Linux/KDE neon Plasma LTS Edition 5.12, Release 18.04 Kernel: 4.15.0-58-generic 64-bit KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kmail 5.12.0 ( Version 4:19.08.0-0xneon+18.04+bionic+build33 from ubuntu-bionic-universe (KDE neon Plasma LTS) ) ADDITIONAL INFORMATION A record in a "mail not deliverered message" was: "Received-SPF: softfail (transitioning domain of sa-prd-fep-014.btinternet.com does not designate 74.208.4.204 as permitted sender)". Here, 74.208.4.204 is an IP address belonging to 1&1, which was the service provider for the email account which was 'Set as Default'. I am not sure whether this is a duplicate of Bug 393185, which is marked as "Resolved Not a Bug". If so, it is not clear why this is not a bug, as it makes the account other than the default account almost unusable for sending emails. Thanks and regards -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 408378] New: System Monitor crashed when closing during GNU Octave hang
https://bugs.kde.org/show_bug.cgi?id=408378 Bug ID: 408378 Summary: System Monitor crashed when closing during GNU Octave hang Product: ksysguard Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Application: ksysguard (5.12.8) Qt Version: 5.12.0 Frameworks Version: 5.58.0 Operating System: Linux 4.15.0-51-generic x86_64 Distribution: KDE neon Plasma LTS Edition 5.12 -- Information about the crash: GNU Octave hung when I edited a file which was stopped at a debug breakpoint. I then closed System Monitor (which had been running since before I started GNU Octave) which crashed rather than closing normally. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efda4e7ce00 (LWP 9105))] Thread 5 (Thread 0x7efd7514e700 (LWP 9110)): #0 0x7efd988509f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x556dbcc276e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7efd988509f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x556dbcc27698, cond=0x556dbcc276c0) at pthread_cond_wait.c:502 #2 0x7efd988509f3 in __pthread_cond_wait (cond=0x556dbcc276c0, mutex=0x556dbcc27698) at pthread_cond_wait.c:655 #3 0x7efd7662edcb in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7efd7662eaf7 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7efd9884a6db in start_thread (arg=0x7efd7514e700) at pthread_create.c:463 #6 0x7efda475688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7efd82ff9700 (LWP 9108)): #0 0x7efda47450b4 in __GI___libc_read (fd=7, buf=0x7efd82ff8a20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7efd9690f2d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efd968ca0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efd968ca570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efd968ca6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efd9fe9315b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7efd9fe3464a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7efd9fc5c41a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7efda059b015 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7efd9fc5dbc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7efd9884a6db in start_thread (arg=0x7efd82ff9700) at pthread_create.c:463 #11 0x7efda475688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7efd89a66700 (LWP 9107)): #0 0x7efda4749bf9 in __GI___poll (fds=0x7efd89a65b78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7efd992bb747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7efd992bd36a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7efd8adda32a in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7efd9fc5dbc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7efd9884a6db in start_thread (arg=0x7efd89a66700) at pthread_create.c:463 #6 0x7efda475688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7efd8c0b1700 (LWP 9106)): #0 0x7efd988509f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7efd9ee29130) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7efd988509f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x556dbca50580, cond=0x7efd9ee29108) at pthread_cond_wait.c:502 #2 0x7efd988509f3 in __pthread_cond_wait (cond=0x7efd9ee29108, mutex=0x556dbca50580) at pthread_cond_wait.c:655 #3 0x7efd9f8e486c in std::condition_variable::wait(std::unique_lock&) () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x7efd9e16aae7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #5 0x7efd9e16ac29 in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #6 0x7efd9f8ea66f in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7efd9884a6db in start_thread (arg=0x7efd8c0b1700) at pthread_create.c:463 #8 0x7efda475688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7efda4e7ce00 (LWP 9105)): [KCrash Handler] #6 0x7efd9fce668a in operator==(QString const&, QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7efda1283787 in QLabel::setText(QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8
[kmail2] [Bug 406261] New: Kmail2 crashes when accepting meeting invitation
https://bugs.kde.org/show_bug.cgi?id=406261 Bug ID: 406261 Summary: Kmail2 crashes when accepting meeting invitation Product: kmail2 Version: 5.10.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-47-generic x86_64 Distribution: KDE neon LTS User Edition 5.12 -- Information about the crash: Kmail2 crashed at the moment that I clicked the Accept button in a meeting invitation. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1aa4013bc0 (LWP 10078))] Thread 30 (Thread 0x7f1939a4b700 (LWP 13399)): #0 0x7f1a7b81e57d in pa_pstream_unref () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #1 0x7f1a7b81eab9 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f1a7b81f33f in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7f1a833da108 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f1a833da4de in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f1a833da560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f1a833e83c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f1a7b82f318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #8 0x7f1a968106db in start_thread (arg=0x7f1939a4b700) at pthread_create.c:463 #9 0x7f1aa106588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f193affd700 (LWP 13380)): #0 0x7f1aa10540b4 in __GI___libc_read (fd=111, buf=0x7f193affc7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f1a94988cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1a94944027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1a949444e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1a9494464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1aa199b15b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1aa193c64a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1aa176441a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1aa1765bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f1a968106db in start_thread (arg=0x7f193affd700) at pthread_create.c:463 #10 0x7f1aa106588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f193b7fe700 (LWP 13379)): #0 0x7f1a96816ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f193b7fd710, expected=0, futex_word=0x7f193b7fd8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f1a96816ed9 in __pthread_cond_wait_common (abstime=0x7f193b7fd7b0, mutex=0x7f193b7fd8a8, cond=0x7f193b7fd8d0) at pthread_cond_wait.c:533 #2 0x7f1a96816ed9 in __pthread_cond_timedwait (cond=0x7f193b7fd8d0, mutex=0x7f193b7fd8a8, abstime=0x7f193b7fd7b0) at pthread_cond_wait.c:667 #3 0x7f1a8b775177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1a8b775ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f1a8b775bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f1a8b733851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f1a8b736387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f1a8b736974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f1a8b777cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f1a968106db in start_thread (arg=0x7f193b7fe700) at pthread_create.c:463 #11 0x7f1aa106588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f193bfff700 (LWP 13378)): #0 0x7f1a96816ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f193bffe710, expected=0, futex_word=0x7f193bffe8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f1a96816ed9 in __pthread_cond_wait_common (abstime=0x7f193bffe7b0, mutex=0x7f193bffe8a8, cond=0x7f193bffe8d0) at pthread_cond_wait.c:533 #2 0x7f1a96816ed9 in __pthread_cond_timedwait (cond=0x7f193bffe8d0, mutex=0x7f193bffe8a8, abstime=0x7f193bffe7b0) at pthread_cond_wait.c:667 #3 0x7f1a8b775177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1a8b775ada in () at
[kmail2] [Bug 394720] Akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=394720 --- Comment #1 from Peter Wibberley <p.wibber...@btinternet.com> --- NB I am using Kmail 5.8.1 with KDE Neon User Edition 5.12.5LTS. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394720] New: Akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=394720 Bug ID: 394720 Summary: Akonadi crashes Product: kmail2 Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- When I use 'Tools.Find Messages', enter a criterion and select 'Search', I get a notification, "Akonadi Server Closed Unexpectedly" and a dialogue box with the message, "The Akonadi personal information management service is not operational". Clicking the "Details" button highlights the button but has no other effect. If I exit kmail and restart, the dialogue box is still displayed, unless I do a akonadictl restart, in which case kmail starts normally (until I do another search). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394716] New: Akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=394716 Bug ID: 394716 Summary: Akonadi crashes Product: kmail2 Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- Created attachment 112888 --> https://bugs.kde.org/attachment.cgi?id=112888=edit Screenshoty of dialogue box When I use 'Tools.Find Messages', enter a criterion and select 'Search', I get a notification, "Akonadi Server Closed Unexpectedly" and a dialogue box with the message, "The Akonadi personal information management service is not operational". Clicking the "Details" button highlights the button but has no other effect. If I exit kmail and restart, the dialogue box is still displayed, unless I do a akonadictl restart, in which case kmail starts normally (until I do another search). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388861] New: Printer Properties Dialogue Box 2-up printing
https://bugs.kde.org/show_bug.cgi?id=388861 Bug ID: 388861 Summary: Printer Properties Dialogue Box 2-up printing Product: okular Version: 1.3.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: p.wibber...@btinternet.com Target Milestone: --- In the Printer Properties dialogue box, 2-up printing is shown as placing the second page BELOW the first, even though in the hardcopy the second page is TO THE RIGHT of the first page (which is what I think most users will want). Changing the Orientation between Portrait and Landscape changes the orientation of the page shown in the dialogue box but seems to make no difference to the relative positions the two pages and no difference to either the orientation or page positions of the hardcopy. My printer is a Brother DCP-L2540DW, with the driver downloaded from the Brother website: apologies if this is a printer driver problem. Thanks and regards KDE Neon 5.8.8 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 293586] E-mail sending failed: Failed to transport message. Unable to create SMTP job.
https://bugs.kde.org/show_bug.cgi?id=293586 Peter Wibberley <p.wibber...@btinternet.com> changed: What|Removed |Added CC||p.wibber...@btinternet.com --- Comment #10 from Peter Wibberley <p.wibber...@btinternet.com> --- I have just had this problem (or a problem resulting ostensibly in the same result) immediately following a fresh install of KDE Neon 5.8.8 and KMail 5.6.3. This seems to have been due to the fact that kio-smtp was not installed during the KMail installation and was solved by installing kio-smtp manually. -- You are receiving this mail because: You are watching all bug changes.
