[khelpcenter] [Bug 480902] Text selection gets removed instantly
https://bugs.kde.org/show_bug.cgi?id=480902 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #1 from David C. Bryant --- I cannot confirm this bug. I'm using Gentoo Linux, 6.6.13 kernel, Plasma 5.27.10, Frameworks 5.113.0, Qt 5.15.12 and X11. No problems with selecting text in Khelpcenter with the mouse . I can't get the keyboard to select text , though (Shift + -->). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460712] New: Segmentation fault when I advnced to next uread message
https://bugs.kde.org/show_bug.cgi?id=460712 Bug ID: 460712 Summary: Segmentation fault when I advnced to next uread message Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Application: kmail (5.20.3 (22.04.3)) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.15.74-gentoo-x86_64 x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I wasn't doing anything unusual. Clicked "Next" button, and it just died. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f11d30a7410 in QWidget::style() const () at /usr/lib64/libQt5Widgets.so.5 #5 0x7f11d3084114 in QApplication::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #6 0x7f11d307e70f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #7 0x7f11d26c2338 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f11d271180b in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #9 0x7f11d27120b4 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f11cc4c2cfb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #11 0x7f11cc4c2fa8 in () at /usr/lib64/libglib-2.0.so.0 #12 0x7f11cc4c305f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #13 0x7f11d27124a6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #14 0x7f11d26c0dc3 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #15 0x7f11d26c90b0 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #16 0x55fa96bf6aa5 in () #17 0x7f11d205134a in () at /lib64/libc.so.6 #18 0x7f11d20513fc in __libc_start_main () at /lib64/libc.so.6 #19 0x55fa96bf7021 in () [Inferior 1 (process 4129) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 457220] kdoctools fail to build
https://bugs.kde.org/show_bug.cgi?id=457220 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #2 from David C. Bryant --- I just compiled kdoctools without any trouble. Building kdoctools from frameworks (4/4) Updating kdoctools (to branch master) No changes to kdoctools source, proceeding to build. Compiling... succeeded (after 1 second) Installing.. succeeded (after 0 seconds) <<< PACKAGES SUCCESSFULLY BUILT >>> extra-cmake-modules karchive ki18n kdoctools :-) Your logs are saved in file:///home/david/kde/src/log/2022-07-28-01 I've had similar problems with kdesrc-build in the recent past. I suggest you delete the entire "~/kde/build" directory, Ilias, and try again. Sometimes extraneous junk left over from a previous build can cause "CMake" to hiccup, apparently. All the stuff you need to run previously compiled programs is in the "~/kde/usr" directory ... the "build" directory is just a bunch of temporary / intermediate files. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 457095] New: Khelpcenter crashes on Help --> Find Actions
https://bugs.kde.org/show_bug.cgi?id=457095 Bug ID: 457095 Summary: Khelpcenter crashes on Help --> Find Actions Product: khelpcenter Version: 5.8.22043 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Application: khelpcenter (5.8.22043) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.92.0 Operating System: Linux 5.15.52-gentoo-x86_64 x86_64 Windowing System: X11 Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed:ooking at a menu entry I had never used before: "Help--Find Action". I think I can probably make it crash again. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Help Center (khelpcenter), signal: Segmentation fault [KCrash Handler] #4 0x55b0e0227a00 in ?? () #5 0x7f9d2ae44b9e in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #6 0x7f9d2b92267f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #7 0x7f9d2ae1a338 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f9d2ae1d7f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f9d2ae6a9f3 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7f9d28e0fcfb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #11 0x7f9d28e0ffa8 in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x7f9d28e1005f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x7f9d2ae6a4a6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #14 0x7f9d2ae18dc3 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #15 0x7f9d2ae210b0 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #16 0x55b0e01fbe57 in ?? () #17 0x7f9d2a7c631a in ?? () from /lib64/libc.so.6 #18 0x7f9d2a7c63cc in __libc_start_main () from /lib64/libc.so.6 #19 0x55b0e01fbf31 in ?? () [Inferior 1 (process 4643) detached] Possible duplicates by query: bug 448911, bug 447095, bug 437923, bug 430007, bug 426203. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Books] [Bug 456375] Invalid link to download the book
https://bugs.kde.org/show_bug.cgi?id=456375 David C. Bryant changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from David C. Bryant --- I loaded the book into the new "collaborate" web site (https://collaborate.kde.org/apps/files/?dir=%2FCommunity+Notes%2FFrameworks=50425) and I fixed the broken hyperlink in https://community.kde.org/Books. -- You are receiving this mail because: You are watching all bug changes.
[Books] [Bug 456375] Invalid link to download the book
https://bugs.kde.org/show_bug.cgi?id=456375 --- Comment #9 from David C. Bryant --- I made a couple of commits in gitlab. "kdesrc-build kf5book" now creates a .pdf file, and an html file. The "epub" still dies: gmake[2]: *** [CMakeFiles/epubbook.dir/build.make:85: KDE-Frameworks-Cookbook.epub] Error 6 gmake[1]: *** [CMakeFiles/Makefile2:139: CMakeFiles/epubbook.dir/all] Error 2 gmake[1]: *** Waiting for unfinished jobs [ 86%] Built target htmlbook [ 97%] Built target pdfbook I can't figure that problem out. I checked the command syntax on line 85 of "build.make", and it looks OK to me. Albert, is it OK to load the .pdf file directly into the community wiki? Or is there some sort of auxiliary storage area where it ought to reside? -- You are receiving this mail because: You are watching all bug changes.
[Books] [Bug 456375] Invalid link to download the book
https://bugs.kde.org/show_bug.cgi?id=456375
--- Comment #8 from David C. Bryant ---
I have been digging into the CMAKE files for project kf5book
(https://invent.kde.org/documentation/kf5book). I finally got the .pdf file to
generate using "kdesrc-build kf5book". I had to do several things to get it to
go.
-- I had to install "pandocs" and also "snippetextractor". "pandocs" is part of
my distro (Gentoo), so that was easy. "snippetextractor" is sort of obscure, so
I had to clone the source for snippetextractor, after which "qmake -o Makefile
snippetextractor.pro && make" generated the object program. I then moved the
object program from the build directory into my PATH, so it woud be usable.
-- I had to change a command line in the CMakeLists.txt file:
add_custom_command(OUTPUT KDE-Frameworks-Cookbook.pdf
COMMAND ${PANDOC} --toc --number-sections ${files} -o
KDE-Frameworks-Cookbook.pdf
--template=${CMAKE_SOURCE_DIR}/pdf-template.tex
--chapters
DEPENDS ${files} pdf-template.tex
)
The "pandocs" program no longer supports a "--chapters" option. It works OK if
"--chapters" is changed to "--top-level-division=chapter".
-- I had to add some customization to the "pdf-template.tex" file from the
repo.
(add after line 131)
\providecommand{\tightlist}{%
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
because "pandocs" throws a "\tightlist" command into every itemized list it
generates, and \tightlist is not a standard LaTeX function.
-- With these changes, kdesrc-build can create an html file, and a pdf file.
The "epub" command is still not working correctly. Maybe I can get that fixed
tomorrow.
--
You are receiving this mail because:
You are watching all bug changes.
[Books] [Bug 456375] Invalid link to download the book
https://bugs.kde.org/show_bug.cgi?id=456375 David C. Bryant changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||davidbry...@gvtc.com --- Comment #7 from David C. Bryant --- After a week of hard work, I have created a reasonable facsimile of the book. You can access it on my website: https://davidcbryant.net/kf5book/kf5book.pdf. I converted the individual chapters (in .md format) and used a free on-line service to convert the markdown to TeX / LaTeX. Then I used Kile to string the whole thing together, and compiled a .pdf file that way. I put the chapters in alphabetical order, except for the chapter about writing a new frameworks app, which I placed last. There were a lot of broken hyperlinks. Most of those have been fixed, but I still need to proofread the whole thing one more time. -- You are receiving this mail because: You are watching all bug changes.
[Books] [Bug 456375] Invalid link to download the book
https://bugs.kde.org/show_bug.cgi?id=456375 --- Comment #3 from David C. Bryant --- I think he's referring to this wiki page https://community.kde.org/KDE_Documentation/KdeBooks or maybe this one: https://community.kde.org/Books I see that the source code for the book is in the Gitlab repo: https://invent.kde.org/documentation/kf5book But I'm not sure how to turn that into a .pdf file. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455423] New: Forced to reboot on dbus error.
https://bugs.kde.org/show_bug.cgi?id=455423 Bug ID: 455423 Summary: Forced to reboot on dbus error. Product: kmail2 Version: 5.19.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Created attachment 149815 --> https://bugs.kde.org/attachment.cgi?id=149815=edit Screenshot of error message. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Compose an email message 2. Choose "send" OBSERVED RESULT Message is moved to outbox folder, and hangs up there. Attempts to send using "send queued messages" always fail. The only way I know of to fix it is to reboot the system. When I do reboot, an error message is displayed: E-mail Sending Failed Failed to get D-Bus interface of mailfilteragent. This is an intermittent error. I suppose one in a thousand (0.1%) of the messages I send fail this way. A screenshot of the error message is attached. EXPECTED RESULT The KMail composer should be able to connect with mailfilteragent, and thence with my email provider via the internet. This happens about 99.9% of the time. And if there is an error with D-Bus, I should be able to see the notification without rebooting the whole system. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel version 5.15.41-gentoo (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Not a real big deal. But it happens often enough to be a nuisance. That's why I'm posting a bug report. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 454618] The sound output of system don't work. It is disabled.
https://bugs.kde.org/show_bug.cgi?id=454618 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #1 from David C. Bryant --- Khelpcenter doesn't produce any sounds. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 447210] New: KMail crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=447210 Bug ID: 447210 Summary: KMail crashed unexpectedly Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Application: kmail (5.18.3 (21.08.3)) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.88.0 Operating System: Linux 5.10.76-gentoo-r1-x86_64 x86_64 Windowing System: X11 Distribution: Gentoo/Linux DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Not much. I had just moved a message to the "trash" folder when it died. I did just install version 21.8.3 a few weeks ago (Gentoo). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7fcd0cf27ef0 in QWidget::style() const () at /usr/lib64/libQt5Widgets.so.5 #5 0x7fcd0cf05014 in QApplication::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #6 0x7fcd0ceff63f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #7 0x7fcd0c5497d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #8 0x7fcd0c598afb in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #9 0x7fcd0c5993c4 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fcd06451acb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #11 0x7fcd06451d78 in () at /usr/lib64/libglib-2.0.so.0 #12 0x7fcd06451e2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #13 0x7fcd0c5997b6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #14 0x7fcd0c548263 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #15 0x7fcd0c550580 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #16 0x560e6b97c4d5 in () #17 0x7fcd0bf297fd in __libc_start_main () at /lib64/libc.so.6 #18 0x560e6b97c6da in () [Inferior 1 (process 17295) detached] Possible duplicates by query: bug 446679, bug 446675, bug 445967, bug 445525, bug 445028. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 443364] Meinproc5 issues multiple "I/O error" messages
https://bugs.kde.org/show_bug.cgi?id=443364
David C. Bryant changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WORKSFORME |---
Status|RESOLVED|REOPENED
--- Comment #3 from David C. Bryant ---
OK, I dug into this one some more. Here's what's going on.
1. Because of other problems (with Dolphin / Konqueror --
https://bugs.kde.org/show_bug.cgi?id=443259), I devised a workaround that
involved the creation of a second user account. I set up the working directory
so that both User1 and User2 have read/write permissions.
2. This bug can be reproduced as follows:
-- Set up a second user account.
-- Create a working directory that allows any user to have read/write access
(use chmod, or Dolphin).
-- Clone a /docs directory into that working directory. The app doesn't matter,
but I've been working on KOrganizer.
-- Log in as User1 and run meinproc5 index.docbook in the working directory.
-- Log out, then log in as User2. Run meinproc5 index.docbook against the
working directory again. You will get the I/O errors.
I can work around this. And it only happens in the context of two users, both
with r/w access to the directory in which the index.docbook file resides. If
the existing .html files were created by the user who is currently logged in,
meinproc5 overwrites the .html files with nary a whimper. But if the existing
.html files were created by the other user, meinproc5 will not overwrite them,
even though the file permissions say it's OK to do so.
I suspect the existing code implicitly assumes that only one user will ever be
running meinproc5 in a particular working directory. The error message that is
issued ("QIODevice::write (QFile, "index.html"): device not open") is not very
informative. If there must be an error message in this context, it really ought
to say something about file ownership. Better yet, meinproc5 should recognize
that it has write access in the working directory, and overwrite the old files.
--
You are receiving this mail because:
You are watching all bug changes.
[khelpcenter] [Bug 443259] Help Center tells me to file a bug report
https://bugs.kde.org/show_bug.cgi?id=443259 --- Comment #6 from David C. Bryant --- The problem with khelpcenter is apparently buried somewhere in "kio". For instance, I used to be able to open html files in Konqueror. Now (in my primary user account) Konqueror hands every html file I open from my hard disk to Kate. I can still view html files that are downloaded from the internet -- Konqueror renders them just fine. But if I try to open an html file from my hard disk, I'm left looking at the raw html code, rendered as text. I managed to get around this by creating a new user account. When logged in to the new account, Konqueror works correctly. So I suspect a problem with configuration files, somewhere. But I have no idea which ones. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 443983] khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 David C. Bryant changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from David C. Bryant --- I booted into Manjaro again. The terminal command man btrfs-replace works correctly (90 lines). The same page accessed with khelpcenter throws an error message: "The process for the man protocol died unexpectedly." Just 16 lines from the man page are displayed. So it looks like a program bug, to me. BTW, I also tried browsing the man pages with khelpcenter. Most of them work fine. This one (btrfs-replace) doesn't. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 443983] khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #3 from David C. Bryant --- I booted into Manjaro a few minutes ago, and I was able to reporduce this bug. The error message said "Tne man pages protocol died unexpectedly", or something similar. Only a portion of the relevant man page was displayed. I'll play around with it as time permits. It could be a problem with the man page itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 443364] Meinproc5 issues multiple "I/O error" messages
https://bugs.kde.org/show_bug.cgi?id=443364 David C. Bryant changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from David C. Bryant --- No, it's nt consistent. It's one of those very inconvenient "intermittent" errors. Just so you konow, Luigi, I recompiled the "kdoctools" package after this had happened a couple of times. After that, the problem recurred once. And then "meinproc5" started working correctly again. I have run the program nine times (without errors) since I first filed this bug report. If the problem recurs, I'll let you know. For now I consider it resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 443364] Meinproc5 issues multiple "I/O error" messages
https://bugs.kde.org/show_bug.cgi?id=443364 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 443364] New: Meinproc5 issues multiple "I/O error" messages
https://bugs.kde.org/show_bug.cgi?id=443364 Bug ID: 443364 Summary: Meinproc5 issues multiple "I/O error" messages Product: frameworks-kdoctools Version: 5.85.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: davidbry...@gvtc.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Program "meinproc5" sometimes terminates with a lot of strange I/O errors. STEPS TO REPRODUCE 1. Open a terminal window and navigate to a documentation directory 2. Enter this command: meinproc5 index.docbook OBSERVED RESULT Here is some terminal output from 5 minutes ago. davidb@localhost $ meinproc5 index.docbook QIODevice::write (QFile, "index.html"): device not open QIODevice::write (QFile, "introduction.html"): device not open QIODevice::write (QFile, "five-minute-course.html"): device not open QIODevice::write (QFile, "course-entering-todos.html"): device not open QIODevice::write (QFile, "course-entering-journals.html"): device not open QIODevice::write (QFile, "course-rescheduling-events.html"): device not open QIODevice::write (QFile, "course-rescheduling-todos.html"): device not open QIODevice::write (QFile, "course-conclusion.html"): device not open QIODevice::write (QFile, "managing-data.html"): device not open QIODevice::write (QFile, "managing-import-export.html"): device not open QIODevice::write (QFile, "managing-get-hot-new-stuff.html"): device not open QIODevice::write (QFile, "chapter-views-and-filters.html"): device not open QIODevice::write (QFile, "categories-view.html"): device not open QIODevice::write (QFile, "filters-view.html"): device not open QIODevice::write (QFile, "search-view.html"): device not open QIODevice::write (QFile, "entering-data.html"): device not open QIODevice::write (QFile, "entering-data-to-do.html"): device not open QIODevice::write (QFile, "entering-data-required-fields.html"): device not open QIODevice::write (QFile, "group-scheduling.html"): device not open QIODevice::write (QFile, "as-organizer.html"): device not open QIODevice::write (QFile, "as-attendee.html"): device not open QIODevice::write (QFile, "free-busy.html"): device not open QIODevice::write (QFile, "examples.html"): device not open QIODevice::write (QFile, "config.html"): device not open QIODevice::write (QFile, "plugins-chapter.html"): device not open QIODevice::write (QFile, "reference.html"): device not open QIODevice::write (QFile, "other-features.html"): device not open QIODevice::write (QFile, "other-features-drag-and-drop.html"): device not open QIODevice::write (QFile, "faq.html"): device not open QIODevice::write (QFile, "credits.html"): device not open QIODevice::write (QFile, "glossary.html"): device not open EXPECTED RESULT I expect meinproc5 to run without errors. In this instance, it produced no html output at all; just a lot of error messages. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have learned that if I delete all the html output from a previous invocation of "meinproc5" from my working directory, the program wil (usually) run OK. But "meinproc5" never used to do this. It would delete the old html files automatically / overwrite them without prompting. I can work around this bug. But it's annoying, and wastes my time. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 443259] Help Center tells me to file a bug report
https://bugs.kde.org/show_bug.cgi?id=443259 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com Resolution|INTENTIONAL |WORKSFORME --- Comment #5 from David C. Bryant --- OK, I figured out how to patch my way around it. I looked inside a couple of "index.cache.bz2" files, and realized that they're just all the little html files generated by meinproc5, rolled up into one big html file. So I tried renaming "index.html" to be "index.cache", and sure enough, khelpcenter opens the renamed file without a whimper. I can do that with any of the "chunks" generated by meinproc5. Can't follow links to other "pages" the way I used to, though. I still maintain that this is a bug no matter what others may believe. An application program ought not give a diddly do damn what the file name extension associated with a particular file is, or means. It ought to do what I tell it to do (e.g., open this file) and not try to second-guess my command. If it turns out that the program can't handle the file format, it ought to complain -- after it has tried to process the file. But it really ought not care about the file name, or the filename extension, and refuse to function on account of an irrelevant detail (like what I decided to call this particular file). -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 443259] Help Center tells me to file a bug report
https://bugs.kde.org/show_bug.cgi?id=443259 --- Comment #1 from David C. Bryant --- Created attachment 142122 --> https://bugs.kde.org/attachment.cgi?id=142122=edit Screenshot of error message -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 443259] New: Help Center tells me to file a bug report
https://bugs.kde.org/show_bug.cgi?id=443259 Bug ID: 443259 Summary: Help Center tells me to file a bug report Product: khelpcenter Version: 5.7.6.21043 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- SUMMARY When I try to open an html file prepared by meinproc5 with khelpcenter, it displays an error message telling me to file a bug report. STEPS TO REPRODUCE 1. Enter a terminal command: khelpcenter ~/path/index.html (index.html created from index.docbook) 2. An error message is displayed. See attachment. OBSERVED RESULT I get an error. EXPECTED RESULT I should say the table of contents from the docbook I'm working with. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This was working OK up until two or three days ago. And it still works OK on some platforms. I currently have five distros installed: Gentoo (updated daily), Artix Linux, Manjaro, openSUSE Tumbleweed. and openSUSE LEAP 15.3. This problem occurs with Gentoo, Artix, and Tumbleweed. Manjaro and LEAP 15.3 still work OK. I suspect a "Qt" module is to blame, because all three of the failing distros recently rolled some new Qt packages. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] X-Face can break cryptographic signatures
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #15 from David C. Bryant --- Created attachment 141949 --> https://bugs.kde.org/attachment.cgi?id=141949=edit Screenshot -- signature works OK with X-Face disabled -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] X-Face can break cryptographic signatures
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #14 from David C. Bryant --- (In reply to Sandro Knauß from comment #13) > I can confirm it [snip ...] > > @David: can you check, if you get proper signatures, if you disable the > picture (X-Face)? (Picture tab of the Identity). Yes, Sandro, signatures work fine with X-Face disabled. See the screenshot I'm adding as an attachment to this bug report today. I am using the same picture as was in the X-Face header as my gravatar (see discussion below). So the message appears the same (to me) both with and without embedded X-Face headers (except that X-Face breaks the crypto signature). A friend referred me to this web page: https://datatracker.ietf.org/doc/html/draft-autocrypt-lamps-protected-headers-02 and raised the question "should the X-Face header be a protected header?" I'm not real sure of the answer. Personally, I don't care if somebody views the wrong picture in a signed message I send. Integrity of the text message is all I really care about. Others might feel differently, though. One other thing. The field used to display the "X-Face" picture is also used to display "gravatars" kept on file in KAddressbook. So people can (in effect) attach pictures to their messages without using "X-Face" (with the recipient's assistance). One can even configure KMail itself to search for gravatars on the internet (Configure KMail --> Plugins --> Gravatar Config). So "X-Face" is becoming redundant. Just a thought. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #11 from David C. Bryant --- I installed Artix Linux on July 25. At first the signati=ures worked OK in KMail. Yesterday the signature algorithm stopped working. See my post in the Artix forum https://forum.artixlinux.org/index.php/topic,2892.0.html for additional details. KMail is version 5.17.3. Here are details from an Artix mirror. kmail-21.04.3-1-x86_64.pkg.tar.zst 08-Jul-2021 19:04 6389027 Looks very much like an ArchLinux mirror: kmail-21.04.3-1-x86_64.pkg.tar.zst 2021-07-08 07:21 6.1M I have attached screenshots of two emails composed in Artix on July 28th, one in the morning (good signature) and one in the afternoon (bad signature). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #10 from David C. Bryant --- Created attachment 140392 --> https://bugs.kde.org/attachment.cgi?id=140392=edit Image from Artix Linux, 07/28, in theafternoon -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #9 from David C. Bryant --- Created attachment 140391 --> https://bugs.kde.org/attachment.cgi?id=140391=edit Image from Artix Linux, 07/28, in the morning -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 439984] Cannot import data to kaddressbook
https://bugs.kde.org/show_bug.cgi?id=439984 --- Comment #2 from David C. Bryant --- Created attachment 140149 --> https://bugs.kde.org/attachment.cgi?id=140149=edit File menu in Kaddressbook, from the Kaddressbook Handbook. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 439984] Cannot import data to kaddressbook
https://bugs.kde.org/show_bug.cgi?id=439984 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #1 from David C. Bryant --- Created attachment 140148 --> https://bugs.kde.org/attachment.cgi?id=140148=edit File menu as it appears in Kaddressbook under Neon 5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 439984] New: Cannot import data to kaddressbook
https://bugs.kde.org/show_bug.cgi?id=439984 Bug ID: 439984 Summary: Cannot import data to kaddressbook Product: kaddressbook Version: 5.17.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com CC: to...@kde.org Target Milestone: --- SUMMARY The file menu does not include import / export functions. STEPS TO REPRODUCE 1. Start kaddrressbook in KDE Neon 5.22.3 (stable). 2. Click on "File" OBSERVED RESULT The import and export functions are not available. EXPECTED RESULT The import / export functions ought to be functional. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I just installed a fresh copy of Neon (Stable) yesterday, 16 July, 2021. .iso file name = nneon-user-20210715-0945.iso. Packages are up to date, according to "Discover". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #8 from David C. Bryant --- Created attachment 140145 --> https://bugs.kde.org/attachment.cgi?id=140145=edit Test message composed under Gentoo, KMail 5.16.3. The signature is OK when the message is encrypted. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #7 from David C. Bryant --- Created attachment 140143 --> https://bugs.kde.org/attachment.cgi?id=140143=edit Screenshot of message composed under Gentoo, KMail 5.16.3 When the message is signed, but not encrypted, the crypto signature is malformed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 David C. Bryant changed: What|Removed |Added Attachment #140125|0 |1 is obsolete|| --- Comment #6 from David C. Bryant --- Created attachment 140128 --> https://bugs.kde.org/attachment.cgi?id=140128=edit Raw email composed under Tumbleweed (KMail 5.17.3). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #5 from David C. Bryant --- Created attachment 140127 --> https://bugs.kde.org/attachment.cgi?id=140127=edit Raw email message composed under Manjaro (KMail 5.17.3). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #4 from David C. Bryant --- Created attachment 140126 --> https://bugs.kde.org/attachment.cgi?id=140126=edit Raw email message composed under openSUSE LEAP 15.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #3 from David C. Bryant --- Created attachment 140125 --> https://bugs.kde.org/attachment.cgi?id=140125=edit Message composed under openSUSE Tumbleweeed (KMail 5.17.3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #2 from David C. Bryant --- Created attachment 140124 --> https://bugs.kde.org/attachment.cgi?id=140124=edit Raw Email message from KDE Neon -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 --- Comment #1 from David C. Bryant --- Created attachment 140123 --> https://bugs.kde.org/attachment.cgi?id=140123=edit Raw email message sent from Gentoo, KMail 5.16.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] New: Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 Bug ID: 439958 Summary: Error in cryptographic signatures affixed by KMail Product: kmail2 Version: 5.16.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- SUMMARY KMail composer creates invalid crypto signature. STEPS TO REPRODUCE 1. Compose a new message, select "Sign Message" but not "Encrypt Message" 2. Send the message, or save it as a draft. OBSERVED RESULT Signature invalid. See attachments. EXPECTED RESULT The signature should be valid. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I first saw this bug in November, 2020. I asked about in in gitlab, and was assured it had been fixed. But it keeps popping up all over the place. I have several different Linux platforms installed on my hard drive. Here's a list. openSUSE LEAP 15.3 (KMail 5.14.2) -- Signature works correctly. openSUSE Tumbleweed (KMail 5.17.3?) -- Signature is broken. KDE Neon 5.22.3 (KMail 5.17.3) -- Signature is broken. Manjaro (Plasma 5.22.3, Frameworks 5.84.0, KMail 5.17.3) -- Signature works OK. So on the more or less "current" distros, Manjaro Linux works correctly. I have also tested this pretty extensively using "kdesrc-build" and KDE sources. It works right with Manjaro Linux, but fails on Gentoo / Neon / Tumbleweeed (openSUSE LEAP won't play nice with kdesrc-build; Frameworks are too old). Also reported to Gentoo team: https://bugs.gentoo.org/800689 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439636] New: Segmentation Fault in Dolphin tree view
https://bugs.kde.org/show_bug.cgi?id=439636 Bug ID: 439636 Summary: Segmentation Fault in Dolphin tree view Product: dolphin Version: 20.12.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: davidbry...@gvtc.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.3) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.10.27-gentoo-x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Just like preceding report. Tried to colllapse tree viewin ~/.local/share/akonadi/... snd it died. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f5ebcc734bc in KFileItem::~KFileItem() () from /usr/lib64/libKF5KIOCore.so.5 #5 0x7f5ebd26876d in KFileItemModel::removeItems(KItemRangeList const&, KFileItemModel::RemoveItemsBehavior) () from /usr/lib64/libdolphinprivate.so.5 #6 0x7f5ebd27424a in KFileItemModel::setExpanded(int, bool) () from /usr/lib64/libdolphinprivate.so.5 #7 0x7f5ebd285e41 in KItemListController::onRelease(QPointF const&, QFlags, QFlags, bool) () from /usr/lib64/libdolphinprivate.so.5 #8 0x7f5ebd285fe5 in KItemListController::mouseReleaseEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #9 0x7f5ebd288a59 in KItemListController::processEvent(QEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #10 0x7f5ebd29895d in KItemListView::event(QEvent*) () from /usr/lib64/libdolphinprivate.so.5 #11 0x7f5ebbea3d8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7f5ebbeaca40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7f5ebb424bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7f5ebc1cbe83 in ?? () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f5ebc1cc2ae in ?? () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f5ebc1d12ac in QGraphicsScene::mouseReleaseEvent(QGraphicsSceneMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7f5ebc1de708 in QGraphicsScene::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f5ebbea3d8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f5ebbeaca40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7f5ebb424bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #21 0x7f5ebc1fb566 in QGraphicsView::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #22 0x7f5ebbee5d38 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7f5ebbf93d8e in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7f5ebc1fc32c in QGraphicsView::viewportEvent(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #25 0x7f5ebb424985 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #26 0x7f5ebbea3d7e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #27 0x7f5ebbeacd03 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #28 0x7f5ebb424bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #29 0x7f5ebbeabeb4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #30 0x7f5ebbf0073c in ?? () from /usr/lib64/libQt5Widgets.so.5 #31 0x7f5ebbf0396c in ?? () from /usr/lib64/libQt5Widgets.so.5 #32 0x7f5ebbea3d8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #33 0x7f5ebbeaca40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #34 0x7f5ebb424bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #35 0x7f5ebb8d38b3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #36 0x7f5ebb8b437b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #37 0x7f5eb6aa73ba in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #38 0x7f5eb9467acb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #39 0x7f5eb9467d78 in ?? () from /usr/lib64/libglib-2.0.so.0 #40 0x7f5eb9467e2f in
[dolphin] [Bug 439635] New: unexpected Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=439635 Bug ID: 439635 Summary: unexpected Dolphin crash Product: dolphin Version: 20.12.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: davidbry...@gvtc.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.3) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.10.27-gentoo-x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Gentoo/Linux -- Information about the crash: - I was in the tree view on ~/.local/share/akonadi ... tried to collapse a directory listing by clicking the down arrow icon, and it died. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f739b2a14bc in KFileItem::~KFileItem() () from /usr/lib64/libKF5KIOCore.so.5 #5 0x7f739b89676d in KFileItemModel::removeItems(KItemRangeList const&, KFileItemModel::RemoveItemsBehavior) () from /usr/lib64/libdolphinprivate.so.5 #6 0x7f739b8a224a in KFileItemModel::setExpanded(int, bool) () from /usr/lib64/libdolphinprivate.so.5 #7 0x7f739b8b3e41 in KItemListController::onRelease(QPointF const&, QFlags, QFlags, bool) () from /usr/lib64/libdolphinprivate.so.5 #8 0x7f739b8b3fe5 in KItemListController::mouseReleaseEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #9 0x7f739b8b6a59 in KItemListController::processEvent(QEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #10 0x7f739b8c695d in KItemListView::event(QEvent*) () from /usr/lib64/libdolphinprivate.so.5 #11 0x7f739a4d1d8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7f739a4daa40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7f7399a52bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7f739a7f9e83 in ?? () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f739a7fa2ae in ?? () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f739a7ff2ac in QGraphicsScene::mouseReleaseEvent(QGraphicsSceneMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7f739a80c708 in QGraphicsScene::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f739a4d1d8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f739a4daa40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7f7399a52bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #21 0x7f739a829566 in QGraphicsView::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #22 0x7f739a513d38 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7f739a5c1d8e in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7f739a82a32c in QGraphicsView::viewportEvent(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #25 0x7f7399a52985 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #26 0x7f739a4d1d7e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #27 0x7f739a4dad03 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #28 0x7f7399a52bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #29 0x7f739a4d9eb4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #30 0x7f739a52e73c in ?? () from /usr/lib64/libQt5Widgets.so.5 #31 0x7f739a53196c in ?? () from /usr/lib64/libQt5Widgets.so.5 #32 0x7f739a4d1d8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #33 0x7f739a4daa40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #34 0x7f7399a52bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #35 0x7f7399f018b3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #36 0x7f7399ee237b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #37 0x7f73950d53ba in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #38 0x7f7397a95acb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #39 0x7f7397a95d78 in ?? () from /usr/lib64/libglib-2.0.so.0 #40 0x7f7397a95e2f in g_main_context_iteration
[kmail2] [Bug 340014] kMail crashes when opening a new main window if the original (first) main window has been closed
https://bugs.kde.org/show_bug.cgi?id=340014 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #13 from David C. Bryant --- I think this problem has been fixed. I'm using Gentoo Packages, KMail 5.16.3, Plasma 5.21.5, Frameworks %.82.0, Qt 5.15.2. The menu item "File --> New --> Main Widow" has been removed. Simply starting KMail, then saying "kmail" in a terminal window won't fire up a second instance of the program. But "d-bus-launch kmail" will start a second (and a third) instance of the program. I fiddled around with this for a bit, and could not get any of the instances of KMail to crash. I could navigate to different folders / messages. I ran "qps" (traces process ids, like a GUI version of "top"). I saw multiple instances of the akonadi server running, which might eventually cause a problem. Memory usage was pretty high. Killing the extra instances of kmail left "phantom" instances of akonadi hanging around ... I'm too lazy to try killing them one by one, so will probably just reboot to clean up the process tree.. The only really odd thing I noticed is that the system tray icon was not recreated when I opened a second main KMail window. And if I "quit" from the system tray, the second instance of KMail keeps on running. Does anybody have any objection to marking this bug "resolved"? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429050] REGRESSION: Decryption of multi-part encrypted messages by means of "Decrypt" FILTER scrambles message structure
https://bugs.kde.org/show_bug.cgi?id=429050 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #3 from David C. Bryant --- I also verified that this is a bug. And it doesn't have to be a filter that decrypts the message. I used "Message --> Copy Decrypted to --> Recent Folders". The copied (and decryptd) message had the same problem ... the message structure has been gaarbled, somehow. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 415181] Wrong language code in docs.kde.org URL
https://bugs.kde.org/show_bug.cgi?id=415181 David C. Bryant changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||davidbry...@gvtc.com --- Comment #2 from David C. Bryant --- The Windows version of ktimetracker does not support translations. https://apps.kde.org/ktimetracker/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438090] Segmentation Fault on Logout
https://bugs.kde.org/show_bug.cgi?id=438090 David C. Bryant changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from David C. Bryant --- In Gentoo packages updated today, installation of kwin-5.21.5 resolved this problem. Looks like it was a temporary incompatibility between a KDE package and a qt package. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438090] Segmentation Fault on Logout
https://bugs.kde.org/show_bug.cgi?id=438090 --- Comment #3 from David C. Bryant --- Created attachment 139003 --> https://bugs.kde.org/attachment.cgi?id=139003=edit Third screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438090] Segmentation Fault on Logout
https://bugs.kde.org/show_bug.cgi?id=438090 --- Comment #2 from David C. Bryant --- Created attachment 139002 --> https://bugs.kde.org/attachment.cgi?id=139002=edit Another screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438090] Segmentation Fault on Logout
https://bugs.kde.org/show_bug.cgi?id=438090 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #1 from David C. Bryant --- Created attachment 139001 --> https://bugs.kde.org/attachment.cgi?id=139001=edit Screenshot of KDE error hendler -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438090] New: Segmentation Fault on Logout
https://bugs.kde.org/show_bug.cgi?id=438090 Bug ID: 438090 Summary: Segmentation Fault on Logout Product: kwin Version: 5.20.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- SUMMARY SDDM / Login works OK when system first boots up. If I log out, I can't log in again. Much discussion in Gentoo forums. See https://forums.gentoo.org/viewtopic-t-1136583.html and also https://forums.gentoo.org/viewtopic-t-1135770.html. STEPS TO REPRODUCE 1. Boot the system and log in. 2. Log out. 3. Segmentation fault in kwin; can't log in again. OBSERVED RESULT I can't log into my Plasma session unless I restart sddm. EXPECTED RESULT I should be able to log out, then log back in again. It worked until a couple of days ago. I suspect "qtcore" and/or "qtgui", which were recently upgraded in Gentoo. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm reporting this as a bug in Plasma, with the X11 windowing system. But it also appears to be killing the Wayland windiwing system. I usually don't use Wayland, but it used to work, and now it doesn't. I can't even get a decent error message out of Wayland. I also have XFCE configured ... amaxingly enough, I was able to get some screenshots of Drkonqui after kwin had crashed by logging in to XFCE and using those tools. Screenshots are attached. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 436687] Folder Properties Dialog is broken
https://bugs.kde.org/show_bug.cgi?id=436687 --- Comment #2 from David C. Bryant --- Looking at my screenshots again, it's only the "USe Default Aggregation" check box that doesn't work. I have also played with the "Theme" check box. The same thing happens there. I cannot customize either "Aggregation" or "Theme". The other options uncer "View" seem to be OK. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 436687] Folder Properties Dialog is broken
https://bugs.kde.org/show_bug.cgi?id=436687 --- Comment #1 from David C. Bryant --- Created attachment 138190 --> https://bugs.kde.org/attachment.cgi?id=138190=edit Folder Properties Dialog when I reopn it after saving the first one. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 436687] New: Folder Properties Dialog is broken
https://bugs.kde.org/show_bug.cgi?id=436687 Bug ID: 436687 Summary: Folder Properties Dialog is broken Product: kmail2 Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Created attachment 138189 --> https://bugs.kde.org/attachment.cgi?id=138189=edit Folder Properties Dialog with changes made. SUMMARY Folder Properties Dialog (View tab) doesn't preserve the changes I make. STEPS TO REPRODUCE 1. Open the "Folder Properties" dialog. 2. Change something, like "Show Column", or "Use Default Aggregation". 3. Close the dialog, then open it again. OBSERVED RESULT KMail ignores the changes Ihave made. The defaults have been reimposed. EXPECTED RESULT The changed values should have been applied, and should still be there. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This used to work correctly. I suspect the recent upgrade to 5.16.3 from 5.16.2 broke something. I'm using Gentoo packages, and compiling KMail from source. See attached screenshorts, showing first the changes I made, and then that KMail forgot them immediately. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435776] Some images in HTML display are washed out
https://bugs.kde.org/show_bug.cgi?id=435776 --- Comment #5 from David C. Bryant --- More information. This *only* happens with one sender. In most of the messages that I receive the images are fine. But if the message originates from http://groups.io, this error pops up. I'll ask about it at the groups.io web site. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 436550] Sporadic error when moving messages to trash.
https://bugs.kde.org/show_bug.cgi?id=436550 --- Comment #3 from David C. Bryant --- I guess I have a work around. I copied all the contents of ./local/share/local-mail/inbox to a new location. Then I closed KMail, stopped Akonadi, and deleted all the messages in ./local/share/local-mail/inbox. When I restarted KMail and ran "akonadictl fsck" I saw that 236 "dirty" items had been eliminated. Here is some terminal output. david@localhost ~ $ akonadictl stop david@localhost ~ $ akonadictl fsck 2>&1|grep ^Found Found 13 external files. Found 13 external parts. Found no unreferenced external files. Found 0 parts to be moved to external files Found 0 parts to be moved to database Found 5 collections without RID. Found 0 items without RID. Found 2765 dirty items. Notice the last line ... that used to say 3,001. 3,001 - 2,765 = 236. So there were 236 "dirty" items in my inbox folder. I killed KMail again, then stopped akonadi and copied the messages from the backup copy back where they had come from. I then restarted KMail, and all the inbox messages re-appeared. And when I reran akonadictl fsck, things were stil (partially) copacetic: david@localhost ~ $ akonadictl fsck 2>&1|grep ^Found Found 398 external files. Found 398 external parts. Found no unreferenced external files. Found 0 parts to be moved to external files Found 0 parts to be moved to database Found 5 collections without RID. Found 0 items without RID. Found 2765 dirty items. So I guess I can cure my KMail error messages by repeating this procedure for all the destinations in my folder tree. But I'd like to understand what created the "dirty" items in the first place. And it would also be nice to have a less labor-intensive method to correct this problem if and when it does arise. (I'm not real hot with "C++". But I used to write database driver software in assembly language on IBM mainframes. It's pretty clear to me that a bunch of the pointers in Akonadi's relational database were corrupted somehow, leading to a lot of "dirty" items. When I removed all the data from one -- well, actually, two -- folders, a whole slew of pointers were cleared from the relational database. Then, when I put the data back and restarted Akonadi, the previously corrupted pointers were rebuilt correctly. So now a bunch of "dirty" items are gone. If some clever C++ programmer could figure out how to make Akonadi reconstruct all its relational database pointers without actually moving a lot of data around, he could at least construct a recovery tool that would probably be useful. Reading a bunch of forum posts, it's obvious a lot of people are unhappy with Akonadi.) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 436550] Sporadic error when moving messages to trash.
https://bugs.kde.org/show_bug.cgi?id=436550 --- Comment #2 from David C. Bryant --- Sam James (s...@gentoo.org) asked me to post the output from "emerge --info" as part of this bug report. Here it is. david@localhost ~ $ emerge --info Portage 3.0.18 (python 3.8.8-final-0, default/linux/amd64/17.1/desktop/plasma, gcc-10.2.0, glibc-2.32-r7, 5.10.27-gentoo-x86_64 x86_64) = System uname: Linux-5.10.27-gentoo-x86_64-x86_64-Intel-R-_Core-TM-_i7-9700_CPU_@_3.00GHz-with-glibc2.2.5 KiB Mem:16087792 total, 10926892 free KiB Swap:7999484 total, 7999484 free Timestamp of repository gentoo: Mon, 03 May 2021 12:00:01 + Head commit of repository gentoo: ebccfebd1e9a5999357933ffda08b3e11fce375a sh bash 5.0_p18 ld GNU ld (Gentoo 2.35.2 p1) 2.35.2 app-shells/bash: 5.0_p18::gentoo dev-lang/perl:5.30.3::gentoo dev-lang/python: 2.7.18_p8::gentoo, 3.8.8_p1::gentoo, 3.9.2_p1::gentoo dev-lang/rust:1.51.0-r2::gentoo dev-util/cmake: 3.18.5::gentoo sys-apps/baselayout: 2.7::gentoo sys-apps/openrc: 0.42.1-r1::gentoo sys-apps/sandbox: 2.21::gentoo sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo sys-devel/automake: 1.13.4-r2::gentoo, 1.16.2-r1::gentoo sys-devel/binutils: 2.35.2::gentoo sys-devel/gcc:10.2.0-r5::gentoo sys-devel/gcc-config: 2.4::gentoo sys-devel/libtool:2.4.6-r6::gentoo sys-devel/make: 4.3::gentoo sys-kernel/linux-headers: 5.10::gentoo (virtual/os-headers) sys-libs/glibc: 2.32-r7::gentoo Repositories: gentoo location: /var/db/repos/gentoo sync-type: rsync sync-uri: rsync://rsync.gentoo.org/gentoo-portage priority: -1000 sync-rsync-verify-metamanifest: yes sync-rsync-verify-jobs: 1 sync-rsync-extra-opts: sync-rsync-verify-max-age: 24 ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-march=native -O2 -pipe" DISTDIR="/var/cache/distfiles" ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR" FCFLAGS="-march=native -O2 -pipe" FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-march=native -O2 -pipe" GENTOO_MIRRORS="https://gentoo.osuosl.org/ ftp://mirrors.rit.edu/gentoo/ https://mirror.sjc02.svwh.net/gentoo/; LANG="en_US.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j9" PKGDIR="/var/cache/binpkgs" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_TMPDIR="/var/tmp" USE="X a52 aac acl acpi activities alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdr cli crypt cups dbus declarative dri dts dvd dvdr elogind emboss encode exif flac fortran gdbm gif gpm gtk gui iconv icu ipv6 jpeg kde kdesu kipi kwallet lcms libglvnd libnotify libtirpc mad mng mp3 mp4 mpeg multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf pdfimport phonon plasma png policykit ppds qml qt5 readline scanner sdl seccomp semantic-desktop spell split-usr ssl startup-notification svg tcpd tiff truetype udev udisks uefi unicode upower usb vorbis widgets wxwidgets x264 xattr xcb xml xv xvid zlib" ABI_X86="64" ADA_TARGET="gnat_2018" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgi
[Akonadi] [Bug 436550] Sporadic error when moving messages to trash.
https://bugs.kde.org/show_bug.cgi?id=436550 --- Comment #1 from David C. Bryant --- I've done some more poking around. The messages that I can't access are asociated with "dirty" items reported by akonadictl fsck. Here's some terminal output. david@localhost ~ $ akonadictl fsck 2>&1|grep ^Found Found 13 external files. Found 13 external parts. Found no unreferenced external files. Found 0 parts to be moved to external files Found 0 parts to be moved to database Found 5 collections without RID. Found 0 items without RID. Found 3001 dirty items. I've posted inquiries in the KDE forum and in some chat rooms. I'll report back here if I get a response. I did do some spot checking, and the "dirty" items are definitely causing the problem. Every message that can't be accessed is on the list of "dirty" items. For about a year, akonadictl routinely reported 0 dirty items. Then, a couple of weeks ago, there were 3,003 of them. I have no idea how or why that happened. I think I can probably fix it by backing up all my emails and clearing all the data files out of .local/share/local-mail, then loading all the data back in there. But that would be a lot of work. I'm hopeful there's an easier way to clean the dirt out of Akonadi. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 436550] Sporadic error when moving messages to trash.
https://bugs.kde.org/show_bug.cgi?id=436550 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 436550] New: Sporadic error when moving messages to trash.
https://bugs.kde.org/show_bug.cgi?id=436550 Bug ID: 436550 Summary: Sporadic error when moving messages to trash. Product: Akonadi Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- Created attachment 138122 --> https://bugs.kde.org/attachment.cgi?id=138122=edit Terminal output when I run "akonadictl fsck" SUMMARY Occasionally when I attempt to move a message to trash, the operation fails with an error message about "resource conflict". The message then becomes inaccessible in KMail, although it's still on the hard disk. STEPS TO REPRODUCE 1. Select a message in the message list 2. Click on "Move to trash" 3. OBSERVED RESULT org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection MessageViewer-94667889766560 (0x557dcf696430) : Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: [LRCONFLICT] Resource akonadi_maildir_resource_0 tries to modify item 101543 (1618061094817.R217.localhost:2,S) (in collection 11) with dirty payload, aborting STORE. org.kde.pim.akonadiserver: Error while handling command ModifyItems on connection akonadi_maildir_resource_0 (0x557dcf6831b0) org.kde.pim.akonadiserver: ItemRetrievalJob for request 1412 finished with error: "Unable to retrieve item from resource: [LRCONFLICT] Resource akonadi_maildir_resource_0 tries to modify item 101543 (1618061094817.R217.localhost:2,S) (in collection 11) with dirty payload, aborting STORE." EXPECTED RESULT KMail / Akonadi should move the message to Trash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have reported tis to the Gentoo developers. But I suspect it's really a KDE buug, because they're not making any changes to Akonadi / KMail, just repackaging it for "Portage". Also, when I run "akonadictl fsck" I get a long list of "dirty" items. That output is attached. I would clean up the "dirty" items, if only I knew how to do that. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435776] Some images in HTML display are washed out
https://bugs.kde.org/show_bug.cgi?id=435776 --- Comment #4 from David C. Bryant --- Let me know if you want more examples. I'll do some goofing around with other image creation programs (Spectacle, Firefox "screenshot" tool, etc.) if you think that might be helpful. This doesn't happen very often, and only seems to occur when I create a screenshot myself. (In this instance, I uploaded an image to the groups.io web site, and sent the email message from the web site.) Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435776] Some images in HTML display are washed out
https://bugs.kde.org/show_bug.cgi?id=435776 --- Comment #3 from David C. Bryant --- Created attachment 137636 --> https://bugs.kde.org/attachment.cgi?id=137636=edit The raw email message (.mbox format, but called .txt). This is the raw email message I used to make the two preceding screenshots. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435776] Some images in HTML display are washed out
https://bugs.kde.org/show_bug.cgi?id=435776 --- Comment #2 from David C. Bryant --- Created attachment 137635 --> https://bugs.kde.org/attachment.cgi?id=137635=edit Screenshot of the same image when displayed as an attachment not embedded in an email message. This is what the image looks like when I view the attachment in the KMail preview pane as a separate item, and not as part of a message. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435776] Some images in HTML display are washed out
https://bugs.kde.org/show_bug.cgi?id=435776 --- Comment #1 from David C. Bryant --- Created attachment 137634 --> https://bugs.kde.org/attachment.cgi?id=137634=edit Screenshot of a washed-out image This is a screenshot of an image as it appears in the normal HTML display. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435776] New: Some images in HTML display are washed out
https://bugs.kde.org/show_bug.cgi?id=435776 Bug ID: 435776 Summary: Some images in HTML display are washed out Product: kmail2 Version: 5.16.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- SUMMARY Most images embedded in HTML messages appear just fine. But occasionally a screenshot appears to be totally overexposed / washed out when the underlying image file looks perfectly fine. STEPS TO REPRODUCE 1. Take a screenshot of something in your browser (I used Flameshot). 2. Embed the picture in an email message. 3. Send it to yourself, then look at it. OBSERVED RESULT Sometimes the image looks all washed out, even when the original image looks good. EXPECTED RESULT I expect all the embedded images in an HTML-encoded message to be displayed sharply and clearly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: * (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION See attached screenshots, which I'll upload in a minute or two. I'll also upload the raw email message file. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435431] Edit menu (Variables submenu) doesn't work as advertised
https://bugs.kde.org/show_bug.cgi?id=435431 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #1 from David C. Bryant --- Created attachment 137388 --> https://bugs.kde.org/attachment.cgi?id=137388=edit Screenshot from Composer window, illustrating the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 435431] New: Edit menu (Variables submenu) doesn't work as advertised
https://bugs.kde.org/show_bug.cgi?id=435431
Bug ID: 435431
Summary: Edit menu (Variables submenu) doesn't work as
advertised
Product: kmail2
Version: 5.16.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: davidbry...@gvtc.com
Target Milestone: ---
SUMMARY
There are a few glitches in the Edit --> Variables > menu items. In particular,
the "First Name" option extracts Last Name, not First Name.
STEPS TO REPRODUCE
1. Open the Composer, fill in "To:" and "CC:" fields ("From:" is pre-filled).
2. Position the cursor somewhere in the main Composer window.
3. Select menu item Edit --> Variable > To > To Field First Name (or ... CC >
CC
Field First Name, or ... From > From Field First Name).
OBSERVED RESULT
The selected menu item inserts the person's last name.
EXPECTED RESULT
I expected this function to insert the person's first name, as advertised.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Yes!
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
I ran across this bug while working on the documentation update project. There
are a couple of other problems with "Variables >" ... check out "Edit -->
Variables > Attachments > Names and Sizes" (appends the literal value "AND
SIZES" to the list of attachments' names ... I expected to see the size of each
attachment, sort of the way sizes are displayed in the list of attachments
underneath the main Composer window) and also try "Edit --> Variables >
Date/Time > Time" (appends the literal value "LONG" to hh:mm:ss AM/PM, where I
expected to see, e.g., "GMT" or "UTC" or "CDT").
See the attached screenshot, where I tried each of the four options (Address,
Last Name, First Name, Name) for "To >", "From >", and "CC >", respectively.
First Name and Last Name are stored as separate fields in KAddressBook, and
"Name" includes both a person's first and last names, so these functions work
almost right ... only the "First Name" option is misbehaving.
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 434636] Problem with initialization of DKIM "plugin"
https://bugs.kde.org/show_bug.cgi?id=434636 David C. Bryant changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from David C. Bryant --- Maybe this isn't really a bug. There's a drop-down box in the configuration dialog for "DKIM Checker" labeled "Save Record Key". The default value is "Nothing". If I change that to "Save", or "Save and Compare", DKIM checker seems to work correctly. I'll add that little hint to the documentation (which didn't exist until recently), and close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 434636] Problem with initialization of DKIM "plugin"
https://bugs.kde.org/show_bug.cgi?id=434636 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 434636] New: Problem with initialization of DKIM "plugin"
https://bugs.kde.org/show_bug.cgi?id=434636
Bug ID: 434636
Summary: Problem with initialization of DKIM "plugin"
Product: kmail2
Version: 5.16.2
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: config dialog
Assignee: kdepim-b...@kde.org
Reporter: davidbry...@gvtc.com
Target Milestone: ---
SUMMARY
Configure KMail --> Plugins --> DKIM Checker works OK until KMail is restarted.
Then it breaks.
STEPS TO REPRODUCE
1. Open Configure KMail --> Plugins --> DKIM Checker Configuration dialog
(click the button).
2. Make sure "Enable DKIM Support" is *not* checked; close dialog, exit KMail.
3. Restart KMail, then check the "Enable DKIM Support" option.
4. DKIM checking starts working as advertised, generally reporting either "DKIM
valid" or "DKIM not signed" (when DKIM header is not present).
5. Exit KMail and restart the program.
6. Now DKIM checking is broken: every formerly valid signature is now reported
to be invalid.
OBSERVED RESULT
DKIM Checker only works until KMail is restarted. Then it fails. The only
workaround I have found is to change the configuration file ("Not Enabled"),
shut KMail down, then restart KMail and change the configuration file again
("Enabled").
EXPECTED RESULT
If the DKIM Checker is turned on, it should still function correctly when KMail
is stopped and re-started. Something is not being initialized correctly when
KMail starts up. Reconfiguring the DKIM Checker forces proper initialization
once and once only.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
This may be related, indirectly, to bug #204712. I hadn't even noticed this
feature of KMail until recently, when I added new documentation for the
"Plugins" configuration page. I discovered the bug when I was experimenting
with DKIM Checker so I could write some documentation for this feature.
--
You are receiving this mail because:
You are watching all bug changes.
[docs] [Bug 97136] Better documentation of kioslave format, especially number of needed slashes
https://bugs.kde.org/show_bug.cgi?id=97136 David C. Bryant changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED CC||davidbry...@gvtc.com --- Comment #5 from David C. Bryant --- This is not really a bug. Poorly informed user. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 192444] documentation: document file formats for changing Desktop Theme Details
https://bugs.kde.org/show_bug.cgi?id=192444 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from David C. Bryant --- KDE 4.2.2 is pretty old. I'm on 5.20.5 (per Info Center). I'm closing this bug. Info Center documentation is sketchy here and there, but adequate. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 129278] Alfabetic ordering in help menus and listings
https://bugs.kde.org/show_bug.cgi?id=129278 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from David C. Bryant --- This is not a bug. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 166930] Typo Suggestion: Style improvement possible use second_person instead of the_user
https://bugs.kde.org/show_bug.cgi?id=166930 --- Comment #4 from David C. Bryant --- My previous comment was scrambled by the software. In my judgment, this is not a bug. And all of us working on the English documentation do our best to make the documentation easy to use / understand. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 166930] Typo Suggestion: Style improvement possible use second_person instead of the_user
https://bugs.kde.org/show_bug.cgi?id=166930 David C. Bryant changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||davidbry...@gvtc.com --- Comment #3 from David C. Bryant --- Speaking as an English grammar maven / fussbudget, ththe second person. Other times it's in the third person. Nobody cares, so long as it's comprehensible. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 431589] Dolphin handbook requires Konqueror handbook
https://bugs.kde.org/show_bug.cgi?id=431589 --- Comment #4 from David C. Bryant --- On Thursday, January 14, 2021 8:05:02 AM CST you wrote: > The main purpose of Konqueror is WWW. ... OK. I'll try to work on it, as time permits. I'm pretty busy with other stuff right now (I volunteer to help elderly people who don't much like computers file their income tax returns, and the season is upon us). And I'm in the middle of rewriting the KMail documentation. But it might not be hard to do, if I just have to copy some xml code from one index.docbook file and paste it into another one. And maybe copy some .png files as well. I'll try to get to it. David Bryant Canyon Lake, Texas I wear many hats. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 431589] Dolphin handbook requires Konqueror handbook
https://bugs.kde.org/show_bug.cgi?id=431589 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #2 from David C. Bryant --- Didn't Dolphin and Konqueror spring from the same root? I remember using Konqueror ca 2002 or 2003. It seems to me Dolphin started life as Konqueror without all thehttp & ftp bells and whistles, around 2010, or o. There was smething called Nautilus along the way, as well. I ws on openSUSE back then. But it was KDE allthe way for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431536] New: Dolphim crashed while I was viewing directory structure on a USB flash drive.
https://bugs.kde.org/show_bug.cgi?id=431536 Bug ID: 431536 Summary: Dolphim crashed while I was viewing directory structure on a USB flash drive. Product: dolphin Version: 20.08.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: davidbry...@gvtc.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.3) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.80-gentoo-x86_64 x86_64 Windowing system: X11 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: I do daily backups of my important data files using rsync. Yesterday I did a large amount of archiving email from the year 2020 (I keep about 3 GiB of emsil archives, in total). After running the rsync script, I started Dolphin to look at the backed up copy of the email archive, which had been recetnly reorganized. It worked fine at first -- I drilled all the way down (tree view) through 4 levels of directories to an actual list of files. The crash occuirred when I clicked the down arrow to collapse the file list. No other application programs were running except yakuake and the usual cadre of kde framework stuff. I started dolphin again, repeated my previous sequence of actions, and boom! It died the same way. The only difference I can see is that the "KDE Crash Handler" was running the second time it crashed. I should mention that i re-compiled a lot of kde-framework packages just two days ago, on 11 January. Big package upgrade at Gentoo (I try to run emerge --sync once a day). 60 packages were affected. Upgraded from 5.74 to 5.77. It took 7.5 hours to compile those 60 packages (I maintain a complete set of "portage" log files for all 1288 packages installed on my system). The day before (10 January) I installed qt5.15.2 and a few additional packages (firefox, libre-office) dependent on qt. 4.5 hours for that one, My poor CPUs are getting tired. :-) The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7fe460073aec in KFileItem::~KFileItem() () from /usr/lib64/libKF5KIOCore.so.5 #5 0x7fe4606d3c10 in KFileItemModel::removeItems(KItemRangeList const&, KFileItemModel::RemoveItemsBehavior) () from /usr/lib64/libdolphinprivate.so.5 #6 0x7fe4606e0a65 in KFileItemModel::setExpanded(int, bool) () from /usr/lib64/libdolphinprivate.so.5 #7 0x7fe4606f4e00 in KItemListController::mouseReleaseEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #8 0x7fe4606f6321 in KItemListController::processEvent(QEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #9 0x7fe4607053f6 in KItemListView::event(QEvent*) () from /usr/lib64/libdolphinprivate.so.5 #10 0x7fe45f21fd8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x7fe45f228a40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7fe45e74b337 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #13 0x7fe45f547e83 in ?? () from /usr/lib64/libQt5Widgets.so.5 #14 0x7fe45f5482ae in ?? () from /usr/lib64/libQt5Widgets.so.5 #15 0x7fe45f54d2ac in QGraphicsScene::mouseReleaseEvent(QGraphicsSceneMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7fe45f55a708 in QGraphicsScene::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7fe45f21fd8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7fe45f228a40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7fe45e74b337 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x7fe45f577566 in QGraphicsView::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #21 0x7fe45f261d38 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #22 0x7fe45f30fd8e in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7fe45f57832c in QGraphicsView::viewportEvent(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7fe45e74b146 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #25 0x7fe45f21fd7e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #26 0x7fe45f228d03 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #27 0x7fe45e74b337 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from
[kmail2] [Bug 386006] KMAIL dies on startup
https://bugs.kde.org/show_bug.cgi?id=386006 David C. Bryant changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from David C. Bryant --- @JustinZobel: This was also on an old release of openSUSE, Hasn't happened in years. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 385484] Unexpected termination of Konqueror
https://bugs.kde.org/show_bug.cgi?id=385484 David C. Bryant changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from David C. Bryant --- @JustinZobel: I can't possibly reproduce the bug. It was three years ago, and I've upgraded my openSUSE system at leats three or four times since then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385941] Plasma crashed after initiating automatic updates
https://bugs.kde.org/show_bug.cgi?id=385941 --- Comment #4 from David C. Bryant --- This was a long time ago. I was able to obtain the back trace (that takes some effort), so I filed the report. It's fine to forget about it, as far as I'm concerned, It only happened once. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385941] Plasma crashed after initiating automatic updates
https://bugs.kde.org/show_bug.cgi?id=385941 David C. Bryant changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 427264] multi-tabs, multi-window interface
https://bugs.kde.org/show_bug.cgi?id=427264 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #1 from David C. Bryant --- Just a suggestion. All the KDE application documentation is available for viewing online. For English, start here: https://docs.kde.org/stable5/en/ Browse the various subdirectories for the application you wish to consult. For instance, "kmail2" is in the "pim" subdirectory: https://docs.kde.org/stable5/en/pim/kmail2/ You can open those HTML pages in Firefox, or Chromium, or some other browser with tabbing support, and use just as many tabs as your little heart desires. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412516] copied text pasted in multiple locations
https://bugs.kde.org/show_bug.cgi?id=412516 --- Comment #6 from David C. Bryant --- (In reply to Justin Zobel from comment #5) > David do you still experience this issue in more recent versions of > Kate/Framework/Plasma? No. It was apparently related to an old version of KWrite, or maybe Klipper. I finally got brave enough to build Gentoo Linux. Kate is now version 20.04.3, Frameworks is 5.74.0, qt 5.15.1, and I haven't had this problem -- not even once -- since I got Gentoo working (about four months ago). I guess we should close this bug. Thanks for asking. :-) -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 428280] Keyboard Shortcuts should be consistent with KDE Fundamentals
https://bugs.kde.org/show_bug.cgi?id=428280 --- Comment #1 from David C. Bryant --- Created attachment 132763 --> https://bugs.kde.org/attachment.cgi?id=132763=edit Extract from KHelpCenter "Fundamentals" Ctrl+M should toggle the Menu Bar always and everywhere. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 428280] New: Keyboard Shortcuts should be consistent with KDE Fundamentals
https://bugs.kde.org/show_bug.cgi?id=428280 Bug ID: 428280 Summary: Keyboard Shortcuts should be consistent with KDE Fundamentals Product: kolourpaint Version: 20.04 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: davidbry...@gvtc.com Target Milestone: --- Created attachment 132762 --> https://bugs.kde.org/attachment.cgi?id=132762=edit Screenshot of KolourPaint keyboard shortcuts, default settings The "Fundamentals" handbook says one can toggle the Menu Bar on and off by pressing Ctrl+M. This won't work in KolourPaint, because Ctrl+M has been assigned as a local shortcut. STEPS TO REPRODUCE 1. Start KolourPaint 2. Press Ctrl+M OBSERVED RESULT Opens the "More Image Effects" dialog box. EXPECTED RESULT Toggle the Menu Bar on and off. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Gentoo Linux with KDE desktop (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION See also bug #418908 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 418908] Add option to hide menubar
https://bugs.kde.org/show_bug.cgi?id=418908 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #3 from David C. Bryant --- Created attachment 132761 --> https://bugs.kde.org/attachment.cgi?id=132761=edit Screenshot from KDE Help "why would one want to see no menubar ?" Because the "Fundamentals" handbook says this always works, maybe? Look at KHelpCenter, select "Fundamentals". In table of contents, select "The Settings Menu" (help:/fundamentals/menus.html#menus.settings). Every KDE application program is supposed to provide a facility for turning the menu bar on and off. See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421156] Discover crashes / Segmentation Fault
https://bugs.kde.org/show_bug.cgi?id=421156 David C. Bryant changed: What|Removed |Added CC||davidbry...@gvtc.com --- Comment #2 from David C. Bryant --- Created attachment 128479 --> https://bugs.kde.org/attachment.cgi?id=128479=edit Screenshot of KInfoCenter, so you can see which versions I'm running. That's a convenient out, Alex. As you can see, my installation is current. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421156] New: Discover crashes / Segmentation Fault
https://bugs.kde.org/show_bug.cgi?id=421156 Bug ID: 421156 Summary: Discover crashes / Segmentation Fault Product: Discover Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: davidbry...@gvtc.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: I queried "Application Addons". In about 30 seconds, Discover crashed. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb1540c0800 (LWP 19230))] Thread 12 (Thread 0x7fb11d5fb700 (LWP 19261)): #0 0x7fb1584fd819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb156d21136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb156d2125c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb158a11743 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb1589bf15b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb15880ee76 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb158818a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb1579b1fa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7fb1585084cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 11 (Thread 0x7fb11e7fc700 (LWP 19248)): #0 0x7fb1584fd819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb13f131684 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.430.34 #2 0x7fb13f21b9d4 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.430.34 #3 0x7fb13f10f3be in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.430.34 #4 0x7fb149ce4604 in ?? () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #5 0x7fb153dce146 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #6 0x7fb15923fc7b in QOpenGLContext::swapBuffers(QSurface*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7fb15a2be686 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fb15a2c2228 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fb158818a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb1579b1fa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7fb1585084cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 10 (Thread 0x7fb11effd700 (LWP 19246)): #0 0x7fb1584fd819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb156d21136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb156d2125c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb158a11743 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb1589bf15b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb15880ee76 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb158818a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb1579b1fa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7fb1585084cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7fb135fb1700 (LWP 19240)): #0 0x7fb156d6ae84 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb156d21266 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb158a11743 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb1589bf15b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb15880ee76 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb158818a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb1579b1fa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7fb1585084cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7fb136ce0700 (LWP 19238)): #0 0x7fb1584fd819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb156d21136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb156d2125c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb158a11743 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb1589bf15b in
[khelpcenter] [Bug 408690] Area containing Start Page text not properly displayed on KHelpCenter
https://bugs.kde.org/show_bug.cgi?id=408690 --- Comment #7 from David C. Bryant --- On Sunday, April 19, 2020 11:34:20 AM CDT John Hayes wrote: > https://bugs.kde.org/show_bug.cgi?id=408690 > > John Hayes changed: > >What|Removed |Added > > CC||jdhayes.li...@gmail.com > > --- Comment #5 from John Hayes --- > When I started Help from the menu the graphic was distorted. It looked like > a newline was inserted between the words Start and Page with the horizontal > line covering up most of the word Page This bug must only be showing up with certain packages. I just checked it in OpenSUSE (Leap 15.1), Debian 10, and KDE Neon 15.8.2 (base package is Ubuntu 18.04). It worked fine in all three environments -- there was no garbled image. D. Bryant Canyon Lake, Texas -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412516] copied text pasted in multiple locations
https://bugs.kde.org/show_bug.cgi?id=412516 --- Comment #4 from David C. Bryant --- (In reply to Christoph Cullmann from comment #3) > No, I didn't imply that you need to compile that stuff, just wanted to know > if you can try with a more up-to-date version. > > But you did that already given you state below > SUSE LEAP 15.1 (Plasma 5.12.8 Frameworks 5.55.0 Qt 5.9.7) > Neon 5.16.4(Plasma 5.16.5 Frameworks 5.62.0 Qt 5.13.1) > SUSE LEAP 15.1 (Plasma 5.12.8 Frameworks 5.55.0 Qt 5.9.7) > Debian 10.0(Plasma 5.14.5 Frameworks 5.54.0 Qt 5.11.3) > > I would really like to fix this, but after inspecting the code a bit, I > can't think of any "obvious" reason this should happen :( I honestly doubt that the problem is in Kate itself. But I had to report it somewhere if I wanted to report it at all. Let me explain. About a year ago I noticed a change in the way the "Clipboard" works. Previously (on SUSE LEAP 42.3, and going all the way back to SUSE 9.0, starting in 2003) I could select a block of text in just about any program whatsoever, and it would not be copied to the "Clipboard" until I hit ^C, or ^X. When I installed LEAP 15.0 (December, 2018) I noticed a change. Text was automatically copied to the "Clipboard" as soon as it was highlighted (either by dragging the mouse, or by holding Shift and striking --> on the keyboard). This was very annoying for a while, because I had been in the habit, when surfing the web, of selecting a URL somewhere (with the right-click context menu in Firefox --> Copy Link Location) and then pasting it in the navigation bar of a Firefox tab that was already open. The new behavior of the "Clipboard" made this procedure more difficult, because when I selected the text I wanted to replace with the copied URL, a new entry was made in the "Clipboard"'s stack of saved items, effectively erasing the new data I was trying to copy. So I had to either open the "Clipboard" from the system tray and move the data I wanted to copy back to the top of the stack, or alter my old habits and erase the text I wanted to replace (with backspace, or delete) instead of just selecting it and then overwriting it with ^V. The new procedure wasn't any more work than the old procedure, but old habits are hard to break. I still have trouble with the recent change in "Clipboard" behavior. Anyway, I don't have the trouble with Gnome programs like gedit (I have configured both Debian and SUSE with multiple desktops on my new PC). I don't log into the Gnome environment very often, because I've used KDE since 2003, and I'm used to it. But I can invoke gedit from either desktop. Anyway, the "Clipboard" is different in Gnome -- I don't think there's a stack of saved items in that environment, because there isn't any system tray. At a minimum, if there is a stack, I don't know where to find it. To make a long story short, I suspect that KDE sticks its "hooks" pretty deep into the Linux / X11 environment to maintain the stack of items on the "Clipboard" that appears in the system tray, because ^C and ^X work just about the same way in every program that runs (including things like LibreOffice, and Firefox). I'm not really an expert on Linux internals. But I wrote a lot of programs in assembler (almost machine language) on IBM mainframes, so I know that "system-wide" features can do unexpected things, because i/o interrupt routines are very hard to get exactly right. (^C and ^V cause interruption events, which are buffered inside the keyboard and passed through to the PIC / CPU on the motherboard at somewhat sporadic intervals, as I understand it.) Thanks again for helping, Christoph. If I think of something else that might be useful information, I'll report it here. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412516] copied text pasted in multiple locations
https://bugs.kde.org/show_bug.cgi?id=412516 --- Comment #2 from David C. Bryant --- (In reply to Christoph Cullmann from comment #1) > Hmm, can not really reproduce that here. > Is there a chance that you could update your KDE Frameworks version? Probably not. I'm not ready to try compiling something as complex as that from source. I'm basically a user who depends on pre-compiled binary packages, who *used* to be a programmer (IBM mainframes, in assembly language, mainly -- I'm old), and who is willing to help write KDE documentation. I have observed this bug on three different Linux platforms, all of which are installed on the same PC (Dell XPS 8930). Neon 5.16.4(Plasma 5.16.5 Frameworks 5.62.0 Qt 5.13.1) SUSE LEAP 15.1 (Plasma 5.12.8 Frameworks 5.55.0 Qt 5.9.7) Debian 10.0(Plasma 5.14.5 Frameworks 5.54.0 Qt 5.11.3) Kate / Kwrite version is 18.12.3 on SUSE, 18.08.0 on Debian. I don't have either Kate or KWrite installed on the Neon system any longer. That is where I first noticed the problem (in late August). I eventually moved my KAddressBook documentation project to the SUSE platform, and only used Neon for "arcanist", to upload stuff to Phabricator. I uninstalled Kate / KWrite because there were already enough updates to apply every time I booted into Neon. As a former programmer, I understand that this is the worst kind of bug, because it doesn't happen very often, and it's almost impossible to reproduce. I don't suppose it will get resolved unless a lot of other people also report it. Not to worry ... I haven't had the problem with gedit, and Kate / Kwrite works fine when I'm editing smaller documents. So I can patch around the problem. I didn't report this as a bug for about two months after I first noticed it. I knew Neon was buggy because there are a lot of new packages going in regularly. I finally decided to file this bug after it bit me on three different platforms. It generally happened with very large documents (2,000 lines of text, or so). I am certain it did in fact occur many times -- I would copy a small snippet of XML text (or straight data, like half of a sentence) and paste it in exactly one place (^C and ^V -- I rarely use the edit menu -- force of habit, I suppose), but when I ran "checkXML5" (a syntax checking program for .docbook files written in XML), it would report four or five errors, which were usually about CDATA (text appearing in areas between XML tags that ought not contain anything except white space) or breaking the DTD rules (XML tags appearing somewhere where the syntax rules said "No way, José"). When I tracked the errors down, they were all exactly the same "CDATA" or XML code sprinkled around the document in locations far away from the place where my cursor had been when I hit ^V. And I always recognized the errant character string as a bit of text I had copied from one spot to another during my previous editing session. Thanks for looking into it, Christoph! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412807] Discover crashes -- segmentation fault
https://bugs.kde.org/show_bug.cgi?id=412807 --- Comment #2 from David C. Bryant --- On Thursday, October 10, 2019 9:13:18 AM CDT you wrote: > https://bugs.kde.org/show_bug.cgi?id=412807 > > Aleix Pol changed: > >What|Removed |Added > > Resolution|--- |FIXED > Status|REPORTED|RESOLVED > > --- Comment #1 from Aleix Pol --- > This issue was fixed recently, it was a packaging issue in Qt. You will have > to use the terminal to update. You can do so by calling "pkcon update". > > Sorry for the inconvenience. :/ Sorry to tell you this, Aleix, but it's still a problem. I ran pkcon and got as far as entering root's pwd. Then I got this message: Fatal error: E: http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgl1-mesa-dri amd64 19.0.8-0ubuntu0~18.04.2 is not (yet) available (404 Not Found [IP: 91.189.91.24 80]) So it looks like something about the repository is still all hosed up. Thanks! D. Bryant Canyon Lake, Texas -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412807] New: Discover crashes -- segmentation fault
https://bugs.kde.org/show_bug.cgi?id=412807 Bug ID: 412807 Summary: Discover crashes -- segmentation fault Product: Discover Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: lei...@leinir.dk Reporter: davidbry...@gvtc.com CC: aleix...@kde.org Target Milestone: --- SUMMARY I hadn't started Neon in a few days (I'm running multiple versions of Linux on one machine). When I booted it up today, the automatic updater said I had updates to install.I said OK, Discover started up, I saw the wheel spinning for about 2 seconds, and then it died with a segmentation fault. STEPS TO REPRODUCE 1. Boot Neon 2. When automatic updater says "updates available" say "install then" 3. Discover runs for 2 seconds, then dies OBSERVED RESULT I tried, several times, to use the automatic bug reporting system to report this crash. That runs OK for a while, then it asks me to install some missing DEBUG packages. I say OK, but that never works. I get "the backtracking report is useless". So I'm filing this bug report manually, from my Debian system. EXPECTED RESULT Automatic updater should fetch a bunch of updates and install them. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I guess I'll read up on using "apt-get" to fetch the updates, and see if I can get the updates installed that way. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412516] New: copied text pasted in multiple locations
https://bugs.kde.org/show_bug.cgi?id=412516 Bug ID: 412516 Summary: copied text pasted in multiple locations Product: kate Version: 18.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: davidbry...@gvtc.com Target Milestone: --- SUMMARY This is an intermittent error, but very annoying. It also occurs when I'm running Debian. Sometimes, when I try to copy text from one spot in a document to another location, the same text is pasted in several places, often far removed from the "target" location where I had positioned the cursor before hitting "Ctrl + v" (^v). STEPS TO REPRODUCE 1. open any text document. select some text, hit ^c or ^x 2. move the cursor somewhere else and hit ^v. 3. usually this works the way it's supposed to. 4. but if you do it often enough, the bug will eventually bite you. OBSERVED RESULT Pastes text in locations far removed from the cursor's location when ^v is pressed. EXPECTED RESULT Pastes the copied text only where it's supposed to. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ✔ (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION Kate has been my preferred text editor for many years. Up until about two months ago, I had never experienced this problem. It only started happening after I switched from Kate 17.12.3 (under openSUSE LEAP 15.0) to Kate 18.12.3 (LEAP 15.1). The past couple of months I've been working on KDE documentation, so I have been using the text editor a lot. The first few times this happened I was totally confused. I would make a small change near say line 2000 of an XML document, and when I ran "checkXML5" it would report errors at lines 46, 500, and 750. The errors were caused by text getting inserted in a bad spot (like after a tag, and before the following tag). I started using Kwrite instead of Kate, but the problem persisted. So now I'm using gedit to do most of my text editing. I haven't had this problem with the gnome text editor ... just the KDE versions. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412363] Drafts folder doesn't work as intended
https://bugs.kde.org/show_bug.cgi?id=412363 --- Comment #2 from David C. Bryant --- OK. So it's not really a bug. I guess I'll change the description to say the documentation is out of date, and assign this task to myself. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412363] New: Drafts folder doesn't work as intended
https://bugs.kde.org/show_bug.cgi?id=412363
Bug ID: 412363
Summary: Drafts folder doesn't work as intended
Product: kmail2
Version: 5.9.3
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: davidbry...@gvtc.com
Target Milestone: ---
SUMMARY
The documentation (help:/kmail2/composer-window-menus.html) says, when
referring to the "drafts" folder, "Save the message in the drafts folder so you
can later edit and send it." ("Message" menu, "Save as Draft" option)
I can select this option, and it does save the message in "drafts". But there's
no convenient way to open this message for further editing. The draft message
is pretty useless if I'm not allowed to edit it. What happened to "...later
edit and send it"?
STEPS TO REPRODUCE
1. Open a composer window ad type some text.
2. Select "Message" --> "Save as Draft".
3. Navigate to Drafts folder, select the new message, try to edit it.
OBSERVED RESULT
This used to work, through (I believe) version 5.6.x. I know it worked
correctly on openSUSE through release LEAP 42.3; I first encountered this bug
in openSUSE LEAP 15.0 (KMail 5.7.3). There was an option under the "Message"
menu that said "Edit Message". It was very handy. I could select any saved
message anywhere and say "Edit Message" ... Voila! it was in a message
composition window, ready to change / edit / send.
The "Edit Message" menu item has been supplanted by "Send Again", and that
option is always grayed out for messages that have been saved as drafts. I have
discovered a couple of workarounds. The most obvious one is to send an
incomplete message to myself, and then move the message from "sent-mail" to
"drafts". If I do that, the "Send Again" option is activated, and I can edit my
saved message. I can also move the message from "drafts" to "templates", and
then use the KMail "File --> New --> Message from Template" dialog to open and
edit the draft message. But if I have to do that, why make a distinction
between "drafts" and "templates" at all? I could just save the message as a
template in the first place.
EXPECTED RESULT
If I save a message as a draft, I should be able to open it for editing from
the drafts folder without a bunch of extraneous steps (send it to myself / move
it to "templates") thrown in.
Conceptually, there is a real difference between a "draft" and a "template". If
I'm writing a long message, or a sensitive one, and I want to save it for a day
or two, until I can give it the attention it deserves, it's a "draft" message.
If I have a form letter that will be used again and again, with just a few
variable details (who's the recipient, etc.), it's a template.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: ✔
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
In thinking about this, I'm struck by the possibility that the basic structure
of K-Mail is becoming anachronistic. The first real e-mail program I ever used
was Netscape Navigator 2.0 running under a Windows 3.1 OS (80386 chip - 1995).
That program, the predecessor of Firefox / Thunderbird, had six "folders" for
messages: inbox, outbox, sent, trash, drafts, & templates. Guess what? KMail
uses the same six names.
The names themselves are redolent of a paperwork culture. The physical inbox /
outbox once sat on most managers' desks, filled with incoming and outgoing
memoranda on paper. Old paperwork was archived in a filing cabinet, inside
actual manila folders. The trash had to be emptied by the janitor at the end of
the day. The steno pool existed mostly to type up and revise items that were
marked "draft", and "templates" aka "form letters" were a staple in every large
business enterprise.
All this is obvious enough. I wonder, though: do younger people really
appreciate the meanings these old names once had? An inbox still makes sense,
because it takes time to read a message. An outbox is increasingly
anachronistic: most of the time, the message is only there for a split-second.
After that it's gone into the ether, with a copy in the "sent-mail" folder.
Given the obsession with text messaging, etc., I suppose the same thing will
eventually happen to "drafts". We can't stop to re-read the things we've
written. We're in far too much of a hurry for that! Nobody cares about
spelling, or good grammar, or punctuation anyway. Boring.
Maybe that's why "drafts" don't work right in KMail now. The next generation of
programmers sees this feature as a superfluity, and ignores it.
--
You are receiving this mail because:
You are watching all bug changes.
[kaddressbook] [Bug 409998] Documentation does not exist
https://bugs.kde.org/show_bug.cgi?id=409998 David C. Bryant changed: What|Removed |Added Latest Commit||D22799 at ||https://phabricator.kde.org ||/ -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 409998] Documentation does not exist
https://bugs.kde.org/show_bug.cgi?id=409998 David C. Bryant changed: What|Removed |Added Assignee|kdepim-b...@kde.org |davidbry...@gvtc.com URL||https://davidcbryant.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411265] Error Message on startup -- Two actions want to use the same shortcut (Ctrl+T)
https://bugs.kde.org/show_bug.cgi?id=411265 --- Comment #1 from David C. Bryant --- Created attachment 122338 --> https://bugs.kde.org/attachment.cgi?id=122338=edit Picture of Help --> About Dolphin (version info) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411265] New: Error Message on startup -- Two actions want to use the same shortcut (Ctrl+T)
https://bugs.kde.org/show_bug.cgi?id=411265 Bug ID: 411265 Summary: Error Message on startup -- Two actions want to use the same shortcut (Ctrl+T) Product: dolphin Version: 18.08.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: task Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: davidbry...@gvtc.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 122337 --> https://bugs.kde.org/attachment.cgi?id=122337=edit Error message from Dolphin 18.08.0 at startup SUMMARY Dolphin issues an error message on startup, and asks me to file a bug report. STEPS TO REPRODUCE 1. Start up Dolphin 18.08.0 under Debian 10.0.0, Gnome desktop. 2. Read the message that appears. OBSERVED RESULT See attached screenshots EXPECTED RESULT No error on startup. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I don't get this error with KDE desktop -- only with Gnome (Gnome has its own file manager, but I like Dolphin, so I installed it there as well). -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 410933] "Tags" label is present, but inoperative
https://bugs.kde.org/show_bug.cgi?id=410933 --- Comment #8 from David C. Bryant --- On Friday, August 16, 2019 8:29:09 AM CDT you wrote: > https://bugs.kde.org/show_bug.cgi?id=410933 > > --- Comment #7 from Laurent Montel --- > categorieseditwidgetplugin.so is generated by akonadi-contact. > So if you don't have it it's a problem on your distro. Please help me understand. I know that KDE software gets re-packaged by different distributions (SUSE, Gentoo, Ubuntu, and many others). After reading quite a bit of stuff, it looks to me as if the "Discover" software package manager and the "Neon" operating system were the nearest thing to an "official" early release of KDE software that exists. Am I wrong about that? (I understand that if I really want to keep up to date I need to compile / build programs from the source code. Maybe some day. Right now I just want to supply the missing documentation for KAddressBook.) I'm about half-way through the process of writing "index.docbook". I can pretty easily work around little glitches in the software I actually work with. I guess I'll just write some documentation, and let others fix any problems they notice. I appreciate your assistance. -- You are receiving this mail because: You are watching all bug changes.
