[KBibTeX] [Bug 484421] KBibTex sometimes loses track of the active element, resulting in shortcuts affecting the wrong item and other issues
https://bugs.kde.org/show_bug.cgi?id=484421 Thomas Fischer changed: What|Removed |Added Latest Commit||7790859456a50ff8e31e918da28 ||35b03cda51075 Version Fixed In||0.10.1 Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Thomas Fischer --- I am having trouble reproducing the described problem *sometimes*, i.e. sometimes I get the result you describe, sometimes not. I suspect the issue you describe is cause when the information what is selected (no, one, or several lines) diverges from what is the 'current' line. Maybe there is a deeper problem or a bug in Qt, but it seems to suffice to set the current line to be one of the selected ones (if there are any) when the main list receives focus after closing the menu. Please let me know if this commit fixes your problem: https://invent.kde.org/thomasfischer/kbibtex/-/commit/7790859456a50ff8e31e918da2835b03cda51075 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484418] Support for searching and adding book citations (e.g. from Google Books, WorldCat)
https://bugs.kde.org/show_bug.cgi?id=484418 Thomas Fischer changed: What|Removed |Added Latest Commit|ffe0fb736ac6a377b772bc6f5a7 |37858b41ce6a19158586546d5ca |b7edb0e004b18 |15998dc4124b1 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484418] Support for searching and adding book citations (e.g. from Google Books, WorldCat)
https://bugs.kde.org/show_bug.cgi?id=484418 Thomas Fischer changed: What|Removed |Added Latest Commit|8e723e9f3cf7b0f8b9895edeb6b |ffe0fb736ac6a377b772bc6f5a7 |83147c4e4033c |b7edb0e004b18 --- Comment #3 from Thomas Fischer --- (In reply to Adam Fontenot from comment #2) > Thanks for working on this! It took some effort to build against Qt6, but I > did succeed and all the books I've tried so far are working. KBibTeX's master branch (still) supports Qt5 and Qt6 equally well, so you can continue to use it with your existing KF5 installation. > It probably makes sense to synthesize an ID field rather than using the > Google Books ones that look like "GoogleBooks:fnG8BAAAQBAJ". Ok, changed to use the ISBN. > The URL field has a bunch of useless stuff in it, all of the following links > for this book are previews of the book: >[..] > It would be better to link to the official Google Books page, even if the > link has to be synthesized: https://books.google.com/books?id=fnG8BAAAQBAJ Fixed. There were some other issues and bugs I fixed as well. I also noted that Google Books allows to download BibTeX code directly via another URL, but the data, even for the same book, is not the same. Thus, this revised search uses both sources/methods and then merges the results. I made a force-push, in case you wonder. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484418] Support for searching and adding book citations (e.g. from Google Books, WorldCat)
https://bugs.kde.org/show_bug.cgi?id=484418 Thomas Fischer changed: What|Removed |Added Latest Commit||8e723e9f3cf7b0f8b9895edeb6b ||83147c4e4033c Version Fixed In||0.11 Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Thomas Fischer --- I agree that having an ISBN search is useful. I was not aware that Google Books offered an API for that without the need for registration or API keys. I made an initial version. Please test and check if it is working. https://invent.kde.org/thomasfischer/kbibtex/-/commit/8e723e9f3cf7b0f8b9895edeb6b83147c4e4033c For WorldCat OCLC, KBibTeX had support until 5-10 years ago. It was removed as API keys became necessary and KBibTeX didn't get one. Scrapping webpages would only a last resort as it can break at any point in time. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483987] New: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients
https://bugs.kde.org/show_bug.cgi?id=483987 Bug ID: 483987 Summary: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- Similar to the existing "Check Before Send Mail" plugin, Kmail should warn and ask for an extra confirmation if an email is about to be sent to a potentially large number of recipients. Criteria to test for: - Number of recipients in To, CC, and BCC fields is about a certain threshold - A mail address previously configured by the user as a "distribution address" is used. A "distribution address" would be a mail address like "every...@example.com", where the mail server then takes are to distribute the mail to a large number of recipients. Those check should not be limited to cases when the user chooses "reply all". Even a 'normal' reply to a distribution address should trigger a warning. Implementation detail/suggestion: Before sending, KMail or Akonadi counts the number of mail addresses (To, CC, BBC). Every mail address which is in the list of known distribution addresses counts 1000 (or any sufficiently large number). The threshold for a warning is 10. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483987] New: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients
https://bugs.kde.org/show_bug.cgi?id=483987 Bug ID: 483987 Summary: "Reply all" protection: ask for confirmation before replying to a potentially large number of recipients Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- Similar to the existing "Check Before Send Mail" plugin, Kmail should warn and ask for an extra confirmation if an email is about to be sent to a potentially large number of recipients. Criteria to test for: - Number of recipients in To, CC, and BCC fields is about a certain threshold - A mail address previously configured by the user as a "distribution address" is used. A "distribution address" would be a mail address like "every...@example.com", where the mail server then takes are to distribute the mail to a large number of recipients. Those check should not be limited to cases when the user chooses "reply all". Even a 'normal' reply to a distribution address should trigger a warning. Implementation detail/suggestion: Before sending, KMail or Akonadi counts the number of mail addresses (To, CC, BBC). Every mail address which is in the list of known distribution addresses counts 1000 (or any sufficiently large number). The threshold for a warning is 10. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425912] Send video stream from phone to computer with kdeconnect (phone as webcam/security camera)
https://bugs.kde.org/show_bug.cgi?id=425912 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #3 from Thomas Fischer --- Microsoft is working on such a solution for Windows 11: https://blogs.windows.com/windows-insider/2024/02/29/ability-to-use-a-mobile-devices-camera-as-a-webcam-on-your-pc-begins-rolling-out-to-windows-insiders/ “We are gradually rolling out the ability to use your Android phone or tablet camera in any video application on your Windows 11 PC … [Y]ou’ll be able to wirelessly enjoy the high quality of your mobile device’s camera on your PC with flexibility and ease. Some of the abilities include being able to switch between front and back camera, pausing the stream during interruptions, and enjoying effects provided by your mobile model. … Please ensure that your mobile device has Android 9.0+ and that your version of the Link to Windows phone application is 1.24012* or greater.” -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 479848] KBibTeX defaults to the wrong PDF viewer when I click "View Document"
https://bugs.kde.org/show_bug.cgi?id=479848 Thomas Fischer changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Thomas Fischer --- KBibTeX does not decide on its own how to open the PDF file; this decision is delegated to the KDE subsystem via KIO::OpenUrlJob: https://api.kde.org/frameworks/kio/html/classKIO_1_1OpenUrlJob.html I guess that for KDE no PDF viewer is configured and, as it is not aware about Gnome's settings, simply picks the "first" PDF viewer which happens to be Xournal++. As a short-term solution, you can change it either via KDE's system settings or in Dolphin via the "Open with" setting for the PDF mime type in the properties dialog available via right-click on an arbitrary PDF file. https://userbase.kde.org/Special:MyLanguage/System_Settings/File_Associations As a long-term solution, you can push both Gnome and KDE to figure out a way to easily synchronize file associations or honor each other's settings. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 478701] New: Dark mode icons in class browser
https://bugs.kde.org/show_bug.cgi?id=478701 Bug ID: 478701 Summary: Dark mode icons in class browser Classification: Applications Product: kdevelop Version: 5.12.230804 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- Created attachment 164279 --> https://bugs.kde.org/attachment.cgi?id=164279=edit Icon for "namespace" in dark blue, virtually invisible in dark mode Whereas most icons on the user interface are adapting to dark mode, i.e. being drawn in white instead of black for normal/light mode, this is not the case for all icons. Notably, the icons in the class browser (side panel "Classes") for namespaces are not. See the attached screenshot for an example. While this is only one example, I would like to suggest a systematic review of all used icons if they correctly adopt to dark mode. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 433084] KBibTeX crashes when opening .bib file
https://bugs.kde.org/show_bug.cgi?id=433084 --- Comment #24 from Thomas Fischer --- It is a little bit unclear, but does this problem still exist? Have you tested the latest code either from branch 'master' or 'kbibtex/0.10'? -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 458668] kbibtex crashes when opening bib file
https://bugs.kde.org/show_bug.cgi?id=458668 --- Comment #3 from Thomas Fischer --- It is a little bit unclear, but does this problem still exist? Have you tested the latest code either from branch 'master' or 'kbibtex/0.10'? -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 468667] Panels cannot be pinned after making them floating
https://bugs.kde.org/show_bug.cgi?id=468667 Thomas Fischer changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 478056] Linked Documents are opened via resolved path, not given path
https://bugs.kde.org/show_bug.cgi?id=478056 --- Comment #4 from Thomas Fischer --- Git commit 754c8b688d06d9e1216b93aa92251e7fa81538b0 by Thomas Fischer. Committed on 16/12/2023 at 00:34. Pushed by thomasfischer into branch 'master'. Using absolute paths, not canonical paths In the previous behaviour, absolute paths where used when showing file paths to the user. In absolute paths, symbolic links are resolved to the actual file and path names. However, it may be in the user's interest to use human-readable symbolic links that point to 'cryptic' actual filenames. Thus, it is better to keep the symbolic links. Cherry-pick of commit 46fcd010575a577bc from branch 'kbibtex/0.10'. M +1-0ChangeLog M +5-5src/io/fileinfo.cpp https://invent.kde.org/office/kbibtex/-/commit/754c8b688d06d9e1216b93aa92251e7fa81538b0 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470169] KBibTeX keeps asking to be set as default editor for bibliography formats
https://bugs.kde.org/show_bug.cgi?id=470169 --- Comment #3 from Thomas Fischer --- Git commit e2073d8e71817a0f03b67637d4d1ebe6e67ac0aa by Thomas Fischer. Committed on 16/12/2023 at 00:34. Pushed by thomasfischer into branch 'master'. Add 'don't ask again' when notifying on the default bibliography editor Add a 'don't ask again' checkbox when notifying the user that KBibTeX is not the default bibliography editor. In the 'General' settings widget, add a push button that allow to clear all 'don't ask again' settings. Cherry-pick of commit f6bcfa9baca44e4000d9 from branch 'kbibtex/0.10'. M +2-0ChangeLog M +20 -1src/gui/preferences/settingsgeneralwidget.cpp M +2-2src/program/mainwindow.cpp https://invent.kde.org/office/kbibtex/-/commit/e2073d8e71817a0f03b67637d4d1ebe6e67ac0aa -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 478056] Linked Documents are opened via resolved path, not given path
https://bugs.kde.org/show_bug.cgi?id=478056 Thomas Fischer changed: What|Removed |Added Latest Commit|4ff1ad50249d58b1315f296d586 |https://invent.kde.org/offi |6d420c8050856 |ce/kbibtex/-/commit/46fcd01 ||0575a577bca750afd7155b304ef ||6e5e39 --- Comment #3 from Thomas Fischer --- Git commit 46fcd010575a577bca750afd7155b304ef6e5e39 by Thomas Fischer. Committed on 16/12/2023 at 00:08. Pushed by thomasfischer into branch 'kbibtex/0.10'. Using absolute paths, not canonical paths In the previous behaviour, absolute paths where used when showing file paths to the user. In absolute paths, symbolic links are resolved to the actual file and path names. However, it may be in the user's interest to use human-readable symbolic links that point to 'cryptic' actual filenames. Thus, it is better to keep the symbolic links. FIXED-IN: 0.10.1 M +1-0ChangeLog M +6-6src/io/fileinfo.cpp https://invent.kde.org/office/kbibtex/-/commit/46fcd010575a577bca750afd7155b304ef6e5e39 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470169] KBibTeX keeps asking to be set as default editor for bibliography formats
https://bugs.kde.org/show_bug.cgi?id=470169 Thomas Fischer changed: What|Removed |Added Latest Commit|18eccc2585c19b716d207da3e8e |https://invent.kde.org/offi |b863b77911ec3 |ce/kbibtex/-/commit/f6bcfa9 ||baca44e4000d98096d45d7addfb ||6a51f2 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Thomas Fischer --- Git commit f6bcfa9baca44e4000d98096d45d7addfb6a51f2 by Thomas Fischer. Committed on 15/12/2023 at 23:36. Pushed by thomasfischer into branch 'kbibtex/0.10'. Add 'don't ask again' when notifying on the default bibliography editor Add a 'don't ask again' checkbox when notifying the user that KBibTeX is not the default bibliography editor. In the 'General' settings widget, add a push button that allow to clear all 'don't ask again' settings. FIXED-IN: 0.10.1 M +2-0ChangeLog M +20 -1src/gui/preferences/settingsgeneralwidget.cpp M +2-2src/program/mainwindow.cpp https://invent.kde.org/office/kbibtex/-/commit/f6bcfa9baca44e4000d98096d45d7addfb6a51f2 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470750] 'View Document' should check for existance of local PDF at keypress, not on list build
https://bugs.kde.org/show_bug.cgi?id=470750 Thomas Fischer changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 478056] Linked Documents are opened via resolved path, not given path
https://bugs.kde.org/show_bug.cgi?id=478056 Thomas Fischer changed: What|Removed |Added Latest Commit||4ff1ad50249d58b1315f296d586 ||6d420c8050856 Version Fixed In||0.10.1 Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #1 from Thomas Fischer --- If I understood the problem correctly, it was sufficient to replace QFileInfo::canonicalFilePath() with QFileInfo::absoluteFilePath() at a few locations. Please test and confirm. https://invent.kde.org/thomasfischer/kbibtex/-/commit/4ff1ad50249d58b1315f296d5866d420c8050856 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470750] 'View Document' should check for existance of local PDF at keypress, not on list build
https://bugs.kde.org/show_bug.cgi?id=470750 --- Comment #5 from Thomas Fischer --- > There's still the issue that KBibTeX seems to resolve the document path > completely, getting rid of all symlinking on the way. In the case of > git-annex, this is quite fatal as the target files are named after the file > hashes and are completely cryptic. I think it would make more sense if > KBibTeX would not resolve the path. But this probably belongs into an extra > bug. Yes, please. Also, please provide a MWE so that I have a use-case to work with. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470750] 'View Document' should check for existance of local PDF at keypress, not on list build
https://bugs.kde.org/show_bug.cgi?id=470750 --- Comment #4 from Thomas Fischer --- Git commit d340c9da1b4d9196c60424642537de9e4509617d by Thomas Fischer. Committed on 03/12/2023 at 21:21. Pushed by thomasfischer into branch 'master'. Check if 'View Document' should be enabled more often Previously, the enable status menu item 'View Document' and list of associated documents got updated when the entry selection got changed, i.e. a different entry got selected from the list. This did not take into account the possibility that a file that can be associated with an entry becomes available only after selecting an entry. There is a user-reported use case when using git-annex. This commit address the issue in the following two ways: 1. A window shortcut (QShortcut) with the same key sequence (Ctrl+D) got added, but it is disabled by default, gets enabled when the 'View Document' menu item disabled and vice versa. Activating this shortcut will first update and possibly enable the 'View Document' action and then trigger the original 'view document' code of the 'View Document' action. This is transparent to the user. 2. Whenever the context menu on top of an entry in the main list is opened, the 'View Document' menu will get updated and enabled if files to open got located that were not available earlier. This commit is a cherry-pick of commit ebbfbf9f94d8bd456464246072 from branch 'kbibtex/0.10'. M +1-0ChangeLog M +5-0src/gui/file/fileview.cpp M +2-0src/gui/file/fileview.h M +37 -10 src/parts/part.cpp https://invent.kde.org/office/kbibtex/-/commit/d340c9da1b4d9196c60424642537de9e4509617d -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470750] 'View Document' should check for existance of local PDF at keypress, not on list build
https://bugs.kde.org/show_bug.cgi?id=470750 Thomas Fischer changed: What|Removed |Added Latest Commit|f144df19d6fd2b2f5b5a22a6ebd |https://invent.kde.org/offi |c3380f3edbd88 |ce/kbibtex/-/commit/ebbfbf9 ||f94d8bd4564642460722fadfc2d ||cf43dd Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Thomas Fischer --- Git commit ebbfbf9f94d8bd4564642460722fadfc2dcf43dd by Thomas Fischer. Committed on 03/12/2023 at 21:15. Pushed by thomasfischer into branch 'kbibtex/0.10'. Check if 'View Document' should be enabled more often Previously, the enable status menu item 'View Document' and list of associated documents got updated when the entry selection got changed, i.e. a different entry got selected from the list. This did not take into account the possibility that a file that can be associated with an entry becomes available only after selecting an entry. There is a user-reported use case when using git-annex. This commit address the issue in the following two ways: 1. A window shortcut (QShortcut) with the same key sequence (Ctrl+D) got added, but it is disabled by default, gets enabled when the 'View Document' menu item disabled and vice versa. Activating this shortcut will first update and possibly enable the 'View Document' action and then trigger the original 'view document' code of the 'View Document' action. This is transparent to the user. 2. Whenever the context menu on top of an entry in the main list is opened, the 'View Document' menu will get updated and enabled if files to open got located that were not available earlier. FIXED-IN: 0.10.1 M +1-0ChangeLog M +6-1src/gui/file/fileview.cpp M +3-1src/gui/file/fileview.h M +37 -10 src/parts/part.cpp https://invent.kde.org/office/kbibtex/-/commit/ebbfbf9f94d8bd4564642460722fadfc2dcf43dd -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470750] 'View Document' should check for existance of local PDF at keypress, not on list build
https://bugs.kde.org/show_bug.cgi?id=470750 Thomas Fischer changed: What|Removed |Added Latest Commit||f144df19d6fd2b2f5b5a22a6ebd ||c3380f3edbd88 Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO Version Fixed In||0.10.1 --- Comment #1 from Thomas Fischer --- I implemented a piece of code that hopefully fixes the issue for you. The code is not yet in KBibTeX's repository but only in my own one: https://invent.kde.org/thomasfischer/kbibtex/-/commits/bugs/kde470750?ref_type=heads The relevant commit is f144df19d6fd2b2f5b5a22a6ebdc3380f3edbd88. To test the new version, proceed as follows. None of the steps requires sudo/su, as all files will be stored in /tmp. 1. Get this script: https://invent.kde.org/thomasfischer/kbibtex-related/-/raw/master/run/run-kbibtex.sh?inline=false 2. Run as normal user: bash run-kbibtex.sh https://invent.kde.org/thomasfischer/kbibtex.git bugs/kde470750 Please test and confirm that this bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 476502] binary and libraries are compiled with rpath
https://bugs.kde.org/show_bug.cgi?id=476502 Thomas Fischer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #5 from Thomas Fischer --- > I don't see anything that can explain this. RPATH is not mentioned. As far > as I understand the default cmake behavior is that RPATH is used during > build but removed during install, so no special treatment should be > necessary. > [...] > This is really not my area of expertise. Sorry. Ok, I'll close this bug for now as "not a bug". I am not aware that any other Linux distribution's packager has similar problems, so it could be something specific to openSUSE and/or RPM. Best if you would ask in the openSUSE/KDE community how to proceed. Feel free to re-open this bug in case new information becomes available. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 426856] File encoding is not always stored
https://bugs.kde.org/show_bug.cgi?id=426856 Thomas Fischer changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |4c2d0c3acdcfea0ab263a5ba688 |ce/kbibtex/commit/1e649222e |0ed22ebe7a6d8 |d54060eb561fcc5b70568ba7f60 | |98fb| Version Fixed In|0.10|0.10.1 --- Comment #9 from Thomas Fischer --- Comment #7 has the important point here: probably every of your BibTeX files where you reported that KBibTeX switched from LaTeX encoding to UTF-8 was due to KBibTeX not knowing how to map an Unicode character to a LaTeX equivalent. Thus is was falling back to UTF-8 encoding in order to preserve the data, i.e. it is a feature, not a bug ;-) This is for two reasons: First, the mapping is manually crafted and simply does not cover the thousands of characters and symbols that are in use. Second, for some symbols, no clear mapping is possible. One particular example is the Greek letter mu. Unicode knows U+00B5 (micro sign), U+03BC (Greek small letter mu), U+1D6CD (Mathematical bold small mu), and possibly others. On the LaTeX side you have \mu (in math mode), \textmu, \upmu, \muup, \textmugreek, and possibly others. Anyhow, I added U+00A0, U+2010, and U+202F to the manual mapping, as those were mentioned earlier and seem most pressing. U+2010 and U+202F are "unidirectional", i.e. they will be mapped to a simple ASCII dash/minus/hyphen and '\,', respectively, and when again encoded to UTF-8 will stay ASCII minus or become U+2009, respectively. If you want to add more manual mappings or update existing ones, please let me know, e.g. by commenting in this bug report and providing both Unicode number and corresponding LaTeX command. The manual mapping is coded in src/io/encoderlatex.cpp, in case you want to look at the technical details. (In reply to nobodyinperson from comment #7) > Thanks for bringing this up again. It's currently also a big pain point for > me. It seems that KBibTeX v0.10.0 doesn't how to encode some Unicode > characters (non-breaking spaces, weird dashes, etc.) to LaTeX. Ran from the > terminal, these are the errors for me (a location in the file would be > helpful): > > ```bash > kbibtex.io: Don't know how to encode Unicode char "0x00a0" > > kbibtex.io: Don't know how to encode Unicode char "0x2010" > kbibtex.io: Don't know how to encode Unicode char "0x2010" > > kbibtex.io: Don't know how to encode Unicode char "0x202f" > > ``` > > When I find-replace those characters in the file (in vim, do > `:%s/\%u202f/ /g`and `%s/\%u00a0/-/g` etc.), then KBibTeX is finally > stable when saving the encoding again and stays at LaTeX encoding. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 476502] binary and libraries are compiled with rpath
https://bugs.kde.org/show_bug.cgi?id=476502 --- Comment #3 from Thomas Fischer --- (In reply to Cor Blom from comment #2) > Sorry, cannot help you with that. I maintain kbibtex for openSUSE and with > this new version there is a rpmlint check that complains about RPATH. There > is a workaround that I use (chrpath). I don't know anything about build > systems apart from being able to compile a program. Ok. Can you check how other KDE program's packages handle RPATH? For example, passing additional arguments to cmake, patching the build system, or simply ignoring the whole issue? Best check for Extra Gear programs that are not (yet) part of the KDE Applications release. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 473070] Feature request: add Engine to get recent papers
https://bugs.kde.org/show_bug.cgi?id=473070 Thomas Fischer changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |RESOLVED Latest Commit||9a28bcc86b9ca28d71348481349 ||c9ecd24edc1b3 Version Fixed In||0.11 --- Comment #2 from Thomas Fischer --- I implemented a basic version of this feature, supporting the two search engine suggested in the original request. More may follow in the future. The code is not yet in KBibTeX's repository but only in my own one: https://invent.kde.org/thomasfischer/kbibtex/-/commits/bugs/kde473070?ref_type=heads Main change happened in commit 9a28bcc86b9ca28d71348481349c9ecd24edc1b3. To test the new version, proceed as follows. None of the steps requires sudo/su, as all files will be stored in /tmp. 1. Get this script: https://invent.kde.org/thomasfischer/kbibtex-related/-/raw/master/run/run-kbibtex.sh?inline=false 2. Run as normal user: bash run-kbibtex.sh https://invent.kde.org/thomasfischer/kbibtex.git bugs/kde473070 Please test and confirm that this bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 473070] Feature request: add Engine to get recent papers
https://bugs.kde.org/show_bug.cgi?id=473070 Thomas Fischer changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Thomas Fischer --- Sounds like a good idea. I'll look into it. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 476502] binary and libraries are compiled with rpath
https://bugs.kde.org/show_bug.cgi?id=476502 Thomas Fischer changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Thomas Fischer --- There is no explicit setting of RPATH in KBibTeX's source code. Please provide additional information how/where KBibTeX differs from other KDE applications in respect of its handling of RPATH. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 476993] KBibTex crash when trying to save a element with a crossref
https://bugs.kde.org/show_bug.cgi?id=476993 Thomas Fischer changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Thomas Fischer --- > -- Information about the crash: > KBibTex crash when trying to save a element with a crossref, it happens > quite offent but not always. > > The crash can be reproduced sometimes. I have been neither able to reproduce this bug. You DrKonqi backtrace is lacking some details, so it may help if you could look into this ArchLinux wiki page how to get better information next time KBibTeX crashes. https://wiki.archlinux.org/title/Debugging/Getting_traces Also, it would help if you could identify a reproducible way to trigger a crash. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471994] Support hidden services from TOR (.onion) or I2P to allow connections between devices in different networks
https://bugs.kde.org/show_bug.cgi?id=471994 --- Comment #2 from Thomas Fischer --- (In reply to Pedro V from comment #1) > Given that many people/entities are afraid of the mentioned overlay > networks, Yes, that is my understanding as well. Non-technical people may boggle at words like "TOR network" which they may associate with "hackers". If at all, such settings should be well hidden and rephrased, like "overlay network". > - You could probably already do this by using a P2P VPN taking care of most > of the hurdles and connecting the devices by IP address. Unfortunately the > current common FOSS options aren't too great as most of them don't tend to > take care of common P2P needs like peer discovery and NAT, but sacrificing > some security and using proprietary options like ZeroTier or Tailscale could > already work as a solution. This is obviously the easiest approach from the > point of view of developers as there's nothing to change in KDE Connect for > this to work. True, and indeed such a solution is working for me. As you mention is the associated cost (money, security, FOSS principles, setup time). > - Generic SOCKS support would implicitly support some overlay networks too. > Not fully sure about the development effort, but both Qt and Java seems to > have okay support for it. Likely the Java side is the more interesting one, > at least I'd run a Tor service on the desktop side and let the phone connect > through it through Orbot as one possible way. The "Add devices by IP" option > deceivingly implies the restriction of accepting only IP addresses, but then > later the prompt is asking for "Hostname or IP address", so given proxy > support an onion address may work without further work. Do note though that > common Tor and I2P implementations aren't really focusing on what's needed > here, so for example I wouldn't expect proper handling of the primary route > failing while another route is available, at least not before let's say Tor > adopts MPTCP, but not sure if that's even being considered currently. This sounds like the most viable option: to improve the UI to enable (technologically and knowledge-wise) the user to proxies like Orbot. > - A native full-blown P2P implementation with all the bells and whistles > like Syncthing would be the best, but it would also require the most > development effort. I wish there would be a FOSS VPN solution that's as good > as Syncthing to be piggybacked on with the proxy option, although a native > implementation would be always superior mostly on mobile devices with > limited battery life. This could be still combined with the usage of an > overlay network if more privacy or security is desired. This sounds similar to Tor Browser, which combines Firefox/Fennec with a Tor proxy. I am not familiar with Android programming, but out of context I guess there is no easy-to-use plug-and-play Tor proxy to KDE Connect to use. tl;dr: thank you for your detailed answer. Two results: (1) KDE Connect can improve its UI to better support/integrate with Orbot, starting by rewording labels suggesting that it is possible. (2) For a solution to connect KDE Connect on Android/iOS with a desktop across network boundaries, use an existing VPN. While not a perfect solution, it is the most practical one. Pedro, Albert: unless you want to add some technical aspects on integrating overlay networks, I suggest to re-classify this bug as a request to change the UI, or close the bug as "not a bug" (nothing is broken) or "unmaintained" (nobody will every implement it). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473593] New: Ability to mark calendars as read-only independent of backend
https://bugs.kde.org/show_bug.cgi?id=473593 Bug ID: 473593 Summary: Ability to mark calendars as read-only independent of backend Classification: Frameworks and Libraries Product: Akonadi Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de CC: c...@carlschwan.eu Target Milestone: --- Currently, the UI (e.g. Akonadi Console, "Folder Properties" on a calendar) offers no option to mark a calendar as read-only, i.e. to disallow changes or removal of events or adding new events. This should be implemented independent of the backend, irrespective of whether it is a local calendar or a DAV resource. Background: in my groupware server account, I have several calendars: one for events I maintain (add/edit events) and several that are subscriptions to external calendar feeds which are read-only. Either the groupware server does not relay the information which calendars are read-only, or Akonadi does not interpret this information correctly. At least in KOrganizer, changes can be made to calendars that are technically read-only. To block those changes, the user should have the choice to mark a calendar read-only even if changes are technically possible, e.g. to avoid accidental changes to calendars. The Folder Properties dialog has a "ACL" tab, but it warns to make changes here. Even if my request can be "solved" by making changes here, it sounds like a dangerous path and it deters users from making the changes. Instead, there should be a simple checkbox in the "General" tab next to the "custom icon" setting that allows the user to make the calendar read-only (or not). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473593] New: Ability to mark calendars as read-only independent of backend
https://bugs.kde.org/show_bug.cgi?id=473593 Bug ID: 473593 Summary: Ability to mark calendars as read-only independent of backend Classification: Frameworks and Libraries Product: Akonadi Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fisc...@unix-ag.uni-kl.de CC: c...@carlschwan.eu Target Milestone: --- Currently, the UI (e.g. Akonadi Console, "Folder Properties" on a calendar) offers no option to mark a calendar as read-only, i.e. to disallow changes or removal of events or adding new events. This should be implemented independent of the backend, irrespective of whether it is a local calendar or a DAV resource. Background: in my groupware server account, I have several calendars: one for events I maintain (add/edit events) and several that are subscriptions to external calendar feeds which are read-only. Either the groupware server does not relay the information which calendars are read-only, or Akonadi does not interpret this information correctly. At least in KOrganizer, changes can be made to calendars that are technically read-only. To block those changes, the user should have the choice to mark a calendar read-only even if changes are technically possible, e.g. to avoid accidental changes to calendars. The Folder Properties dialog has a "ACL" tab, but it warns to make changes here. Even if my request can be "solved" by making changes here, it sounds like a dangerous path and it deters users from making the changes. Instead, there should be a simple checkbox in the "General" tab next to the "custom icon" setting that allows the user to make the calendar read-only (or not). -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 --- Comment #13 from Thomas Fischer --- Git commit b4c9036b5d9bb39dac6dc3abe4e3534ba27a2800 by Thomas Fischer. Committed on 29/07/2023 at 21:39. Pushed by thomasfischer into branch 'master'. Accepting empty string as valid copy reference command When storing a new configuration setting for the 'copy reference' command, accept an empty string (equivalent to 'No command' in the UI) as a valid configuration string. Forward-port of commit 4c8f24c20c8145f9843dd from branch 'kbibtex/0.10'. M +6-2ChangeLog M +2-2src/config/preferences.cpp M +1-0src/config/preferences.json M +1-1src/gui/preferences/settingsfileexporterpdfpswidget.cpp https://invent.kde.org/office/kbibtex/-/commit/b4c9036b5d9bb39dac6dc3abe4e3534ba27a2800 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471994] New: Support hidden services from TOR (.onion) or I2P to allow connections between devices in different networks
https://bugs.kde.org/show_bug.cgi?id=471994 Bug ID: 471994 Summary: Support hidden services from TOR (.onion) or I2P to allow connections between devices in different networks Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: fisc...@unix-ag.uni-kl.de CC: andrew.g.r.hol...@gmail.com Target Milestone: --- If a mobile device running KDE Connect and the corresponding desktop are located in different network subnets (e.g. mobile network and an organization's firewalled LAN, respectively) and the distance in between is too large for Bluetooth, communication between both endpoints may be impossible unless manual steps like establishing a VPN first are taken. My proposal is that all KDE Connect instances (mobile and desktop apps) have either TOR or I2P or both built-in, so that both endpoints have a better chance of communicating with each other if other means fail. Using either hidden service comes at the cost of additional latency and limited bandwidth, so it should only be a fallback if 'normal' network and Bluetooth are not available. To avoid security/trust issues and to not bother the user with technical questions, two endpoints should automatically exchange public keys and hashes when connected the first time via WiFi or Bluetooth, and make use of those credentials for future connections via hidden services if the need arises. The use of hidden services should be both compile-time configurable (if packages do not want to have this feature included) and run-time configurable (if users want to avoid generating traffic that may look suspicious to network security). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469385] Device.qml does not make use of available space on screen
https://bugs.kde.org/show_bug.cgi?id=469385 --- Comment #3 from Thomas Fischer --- Created attachment 159410 --> https://bugs.kde.org/attachment.cgi?id=159410=edit Screenshot of font settings Attaching a screenshot of my font settings. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 470169] KBibTeX keeps asking to be set as default editor for bibliography formats
https://bugs.kde.org/show_bug.cgi?id=470169 Thomas Fischer changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Latest Commit||18eccc2585c19b716d207da3e8e ||b863b77911ec3 Version Fixed In||0.10.1 --- Comment #1 from Thomas Fischer --- Please check this Git commit if it fixes the problem for you: https://invent.kde.org/thomasfischer/kbibtex/-/commit/18eccc2585c19b716d207da3e8eb863b77911ec3 It essentially modifies the dialog box with a 'don't ask again' checkbox. Once you have checked this, you shouldn't get bothered again until you reset all 'don't ask again' checkbox in the settings under 'General'. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 469385] New: Device.qml does not make use of available space on screen
https://bugs.kde.org/show_bug.cgi?id=469385 Bug ID: 469385 Summary: Device.qml does not make use of available space on screen Classification: Plasma Product: Bluedevil Version: 5.27.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: now...@gmail.com Reporter: fisc...@unix-ag.uni-kl.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 158708 --> https://bugs.kde.org/attachment.cgi?id=158708=edit Visualizing the wasted horizontal space while text is still wrapped. The page in the system settings that shows a Bluetooth device's properties does not make proper use of space available on screen. The concerned QML file is most likely src/kcm/package/contents/ui/Device.qml As shown in the attached screenshot, the checkboxes "Trusted" and "Blocked" wrap the text so that it looks like "Truste d" and "Blocke d" despite that there is plenty of horizontal space available; even the TextField for the device's name consumes more horizontal space. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 468667] Panels cannot be pinned after making them floating
https://bugs.kde.org/show_bug.cgi?id=468667 --- Comment #4 from Thomas Fischer --- Created attachment 158340 --> https://bugs.kde.org/attachment.cgi?id=158340=edit KBibTeX main window with re-attached dock -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 468667] Panels cannot be pinned after making them floating
https://bugs.kde.org/show_bug.cgi?id=468667 --- Comment #3 from Thomas Fischer --- Created attachment 158339 --> https://bugs.kde.org/attachment.cgi?id=158339=edit KBibTeX main window showing location where panel will be placed if mouse button gets released -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 468667] Panels cannot be pinned after making them floating
https://bugs.kde.org/show_bug.cgi?id=468667 --- Comment #2 from Thomas Fischer --- Created attachment 158338 --> https://bugs.kde.org/attachment.cgi?id=158338=edit KBibTeX main window with detached panel -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 468667] Panels cannot be pinned after making them floating
https://bugs.kde.org/show_bug.cgi?id=468667 Thomas Fischer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Thomas Fischer --- Floating panels can be re-attached to the main window by grabbing them at their own small title bars with your mouse cursor and dragging them towards the left or right border of the main window. Then, in the main window some visual feedback is shown where the panel will be placed if you release the mouse button. I'll attach some screenshots for demonstration. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 Thomas Fischer changed: What|Removed |Added Latest Commit|28e5a77bc88f7938f289225d915 |https://invent.kde.org/offi |54669898bf610 |ce/kbibtex/commit/4c8f24c20 ||c8145f9843dd1d685dce14cc6c1 ||8971 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #12 from Thomas Fischer --- Git commit 4c8f24c20c8145f9843dd1d685dce14cc6c18971 by Thomas Fischer. Committed on 01/04/2023 at 15:13. Pushed by thomasfischer into branch 'kbibtex/0.10'. Accepting empty string as valid copy reference command When storing a new configuration setting for the 'copy reference' command, accept an empty string (equivalent to 'No command' in the UI) as a valid configuration string. M +5-1ChangeLog M +2-2src/config/preferences.cpp M +1-0src/config/preferences.json M +1-1src/gui/preferences/settingsfileexporterpdfpswidget.cpp https://invent.kde.org/office/kbibtex/commit/4c8f24c20c8145f9843dd1d685dce14cc6c18971 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 Thomas Fischer changed: What|Removed |Added Latest Commit|774be9be04d204bd70a74f2650c |28e5a77bc88f7938f289225d915 |035c8b470c44a |54669898bf610 --- Comment #10 from Thomas Fischer --- Please check the new code. I force-pushed, so you may have to check out anew. First, I missed to reproduce the bug as I only tried to switch between various commands, but never tried the "No command" option. Then, while testing the preferences code, I noticed that free-text fields like "babel language" and "bibliography style" did not work correctly and incorrect assumed that was the bug you reported. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 --- Comment #6 from Thomas Fischer --- (In reply to Kishore Gopalakrishnan from comment #5) > I can still reproduce the bug after uninstalling kbibtex and building it > using the command you mentioned. You can test if you are actually running the bugfix version if you go to the Babel language combobox. Before, there was just English, Swedish, and German. Now there is a much longer list (taken from Babel's docs). Which list do you have? Then, maybe I fixed a different bug. Can you please specify exactly for which setting you can reproduce the bug? In case of doubt, add a screenshot (in English, please). Then, start KBibTeX from the command line and submit anything printed to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 --- Comment #4 from Thomas Fischer --- > I can still reproduce this bug with the 'Settings > Configure Kbibtex > > Saving and Exporting > Command for Copy reference' option. I think I > correctly built kbibtex from the branch you mentioned (kbibtex --versions > says `kbibtex 8261be23 (HEAD), near 0.10.0`). > Is there any debug output I can provide to help with this? KBibTeX is composed of a number of shared libraries and it may be possible that, despite you are running the kbibtex binary compiled from Git, the shared libraries installed from the ArchLinux package (with bug) are loaded. Try to uninstall the KBibTeX package to remove the libraries. Then, I have a special Bash script prepared that simplifies the task of fetching the code from Git, compiling it, and setting some environment variables for execution: https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git The invocation would be: bash run-kbibtex.sh https://invent.kde.org/thomasfischer/kbibtex bugs/kde467803 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 Thomas Fischer changed: What|Removed |Added Version Fixed In||0.10.1 Status|CONFIRMED |ASSIGNED Latest Commit||774be9be04d204bd70a74f2650c ||035c8b470c44a --- Comment #2 from Thomas Fischer --- I think I fixed this bug. Please check branch 'bugs/kde467803' in my personal Git repository and confirm that it got indeed fixed: https://invent.kde.org/thomasfischer/kbibtex/-/tree/bugs/kde467803 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 Thomas Fischer changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Thomas Fischer --- First I had problems reproducing the report, as I tested various settings which indeed get stored and later restored correctly. The reported issue concerns "free-text" configuration options, for example the language to be used for Babel. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467439] New: Crash when selecting multiple mails while pressing Ctrl
https://bugs.kde.org/show_bug.cgi?id=467439 Bug ID: 467439 Summary: Crash when selecting multiple mails while pressing Ctrl Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After first filtering mails in the list of mails for a keyword and while selecting (mouse cursor) several of the found mails while pressing Ctrl, KMail crashed: Using Fedora 37, the following program/library versions were used: KMail 22.12.3 KF5 KMime 22.12.3 Q5 5.15.8 Frameworks 5.103.0 Output on command line up to crash: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [New Thread 0x7fff36ffd6c0 (LWP 12933)] [New Thread 0x7fff367fc6c0 (LWP 12934)] [New Thread 0x7fff35ffb6c0 (LWP 12935)] [New Thread 0x7fff357fa6c0 (LWP 12936)] qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [New Thread 0x7fff1e1bd6c0 (LWP 12942)] [New Thread 0x7fff1d9bc6c0 (LWP 12943)] [Detaching after fork from child process 12947] [Detaching after fork from child process 12949] [Detaching after fork from child process 12951] [New Thread 0x7fff0bbff6c0 (LWP 12953)] [New Thread 0x7fff0abbe6c0 (LWP 12956)] [New Thread 0x7fff09f2d6c0 (LWP 12957)] [New Thread 0x7fff0970c6c0 (LWP 12958)] [New Thread 0x7fff08f0b6c0 (LWP 12959)] [New Thread 0x7ffef3fff6c0 (LWP 12960)] [Thread 0x7fff57fff6c0 (LWP 12908) exited] [Thread 0x7fff767fc6c0 (LWP 12904) exited] [Thread 0x7fff777fe6c0 (LWP 12902) exited] [New Thread 0x7fff767fc6c0 (LWP 13009)] [New Thread 0x7fff777fe6c0 (LWP 13010)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5702e190) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56e4b8b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff57fff6c0 (LWP 13019)] [Detaching after fork from child process 13095] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606; Using Firefox executable "/usr/bin/firefox" [Thread 0x7fff57fff6c0 (LWP 13019) exited] [New Thread 0x7fff57fff6c0 (LWP 13197)] [Detaching after fork from child process 13210] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606; Using Firefox executable "/usr/bin/firefox" qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup,
[kmail2] [Bug 467439] New: Crash when selecting multiple mails while pressing Ctrl
https://bugs.kde.org/show_bug.cgi?id=467439 Bug ID: 467439 Summary: Crash when selecting multiple mails while pressing Ctrl Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After first filtering mails in the list of mails for a keyword and while selecting (mouse cursor) several of the found mails while pressing Ctrl, KMail crashed: Using Fedora 37, the following program/library versions were used: KMail 22.12.3 KF5 KMime 22.12.3 Q5 5.15.8 Frameworks 5.103.0 Output on command line up to crash: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [New Thread 0x7fff36ffd6c0 (LWP 12933)] [New Thread 0x7fff367fc6c0 (LWP 12934)] [New Thread 0x7fff35ffb6c0 (LWP 12935)] [New Thread 0x7fff357fa6c0 (LWP 12936)] qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [New Thread 0x7fff1e1bd6c0 (LWP 12942)] [New Thread 0x7fff1d9bc6c0 (LWP 12943)] [Detaching after fork from child process 12947] [Detaching after fork from child process 12949] [Detaching after fork from child process 12951] [New Thread 0x7fff0bbff6c0 (LWP 12953)] [New Thread 0x7fff0abbe6c0 (LWP 12956)] [New Thread 0x7fff09f2d6c0 (LWP 12957)] [New Thread 0x7fff0970c6c0 (LWP 12958)] [New Thread 0x7fff08f0b6c0 (LWP 12959)] [New Thread 0x7ffef3fff6c0 (LWP 12960)] [Thread 0x7fff57fff6c0 (LWP 12908) exited] [Thread 0x7fff767fc6c0 (LWP 12904) exited] [Thread 0x7fff777fe6c0 (LWP 12902) exited] [New Thread 0x7fff767fc6c0 (LWP 13009)] [New Thread 0x7fff777fe6c0 (LWP 13010)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56efca90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5702e190) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56e4b8b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff57fff6c0 (LWP 13019)] [Detaching after fork from child process 13095] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606; Using Firefox executable "/usr/bin/firefox" [Thread 0x7fff57fff6c0 (LWP 13019) exited] [New Thread 0x7fff57fff6c0 (LWP 13197)] [Detaching after fork from child process 13210] Recognized the following URL or filename: "https://fortimail.his.se/releasecontrol?release=1%3Athomas.fischer%40his.se%3AMTY3ODk1OTc0Mi4zNTIwXzU4NTkxMF8xMDkxNDAuMTcwNTczI1EjMzJHOUIyVDQwMjk0MTQwMDAwLCNGI1MjNTY2Njc2I0U%3D%3Aver%3A2%3A01%3A01%3A59cbce3b04f7780ddb461e6fdf6f90f3f0f58606; Using Firefox executable "/usr/bin/firefox" qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56a48840) which does not match the current topmost grabbing popup,
[kmail2] [Bug 467436] New: Crash when moving mails between folders
https://bugs.kde.org/show_bug.cgi?id=467436 Bug ID: 467436 Summary: Crash when moving mails between folders Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After observing regular crashes in KMail when moving mails between folders (via context menu, then "Move to", on mail in list of mails), I ran kmail via gdb with debuginfod enabled. Akonadi is no affected by crash, I still get popups on incoming mails even after KMail had crashed. Version numbers of concerned programs/libraries: KMail 22.12.3, Fedora release 1.fc37 QWayand 5.15.8, Fedora release 1.fc37 KF5 KXmlGui 5.103.0, Fedora release 1.fc37 Most recent output in terminal before crash: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/6”" "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/5”" [Thread 0x7fff75bfb6c0 (LWP 9496) exited] kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [Thread 0x7fff773fe6c0 (LWP 9633) exited] [Thread 0x7fff753fa6c0 (LWP 8215) exited] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e7000) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff753fa6c0 (LWP 11224)] [New Thread 0x7fff773fe6c0 (LWP 11225)] [New Thread 0x7fff75bfb6c0 (LWP 11226)] [New Thread 0x7ffeecbfc6c0 (LWP 11326)] [New Thread 0x7ffeebbfa6c0 (LWP 11328)] [New Thread 0x7ffeec3fb6c0 (LWP 11327)] [New Thread 0x7ffeeb3f96c0 (LWP 11329)] [New
[kmail2] [Bug 467436] New: Crash when moving mails between folders
https://bugs.kde.org/show_bug.cgi?id=467436 Bug ID: 467436 Summary: Crash when moving mails between folders Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- After observing regular crashes in KMail when moving mails between folders (via context menu, then "Move to", on mail in list of mails), I ran kmail via gdb with debuginfod enabled. Akonadi is no affected by crash, I still get popups on incoming mails even after KMail had crashed. Version numbers of concerned programs/libraries: KMail 22.12.3, Fedora release 1.fc37 QWayand 5.15.8, Fedora release 1.fc37 KF5 KXmlGui 5.103.0, Fedora release 1.fc37 Most recent output in terminal before crash: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/6”" "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/5”" [Thread 0x7fff75bfb6c0 (LWP 9496) exited] kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [Thread 0x7fff773fe6c0 (LWP 9633) exited] [Thread 0x7fff753fa6c0 (LWP 8215) exited] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e1880) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6c0678b0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x56dff750) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x571e7000) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [New Thread 0x7fff753fa6c0 (LWP 11224)] [New Thread 0x7fff773fe6c0 (LWP 11225)] [New Thread 0x7fff75bfb6c0 (LWP 11226)] [New Thread 0x7ffeecbfc6c0 (LWP 11326)] [New Thread 0x7ffeebbfa6c0 (LWP 11328)] [New Thread 0x7ffeec3fb6c0 (LWP 11327)] [New Thread 0x7ffeeb3f96c0 (LWP 11329)] [New
Release of KBibTeX 0.9.3.2
Hello everyone, I would like to announce the release of KBibTeX 0.9.3.2, a bibliography (BibTeX) editor using KDE Frameworks. The release announcement is available as a blog posting here: https://blog.t-fischer.net/post/kbibtex-0-9-3-2-released.html Happy compiling and packaging! Bye, Thomas -- Thomas Fischer PGP/GPG/GnuPG key: 1808CB466328F4380685A3B1A264FD738D861F41 signature.asc Description: PGP signature
[kontact] [Bug 463450] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=463450 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #1 from Thomas Fischer --- I may have encountered the same or a very similar problem. I have kmail crashing several times a day when moving mails between folders (via context menu in mail list) on a Fedora Linux KDE spin system that is not even one week old. I ran the kmail binary via gdb with debuginfod enabled to get the following output. The first few lines may be older and not directly related to the crash: qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5737bdf0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56bbb930) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [Thread 0x7ffee9bff6c0 (LWP 32407) exited] [Thread 0x7fff66c0 (LWP 32406) exited] [Thread 0x7fff75ffb6c0 (LWP 29371) exited] Downloading separate debug info for /usr/lib64/qt5/plugins/kf5/FrameworkIntegrationPlugin.so Downloading separate debug info for /usr/lib64/libcanberra-0.30/libcanberra-pulse.so [New Thread 0x7fff75ffb6c0 (LWP 32420)] [Detaching after fork from child process 32421] [Detaching after fork from child process 32423] [New Thread 0x7fff66c0 (LWP 32426)] [Detaching after fork from child process 32427] [Thread 0x7fff66c0 (LWP 32426) exited] org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history [New Thread 0x7fff66c0 (LWP 32471)] [New Thread 0x7ffee9bff6c0 (LWP 32472)] [New Thread 0x7ffeea7ff6c0 (LWP 32473)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6003f460) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5729bca0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents malloc(): unaligned fastbin chunk detected Thread 1 "kmail" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc-2.36-9.fc37.x86_64/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7fffee2afec3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7fffee25fa76 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7fffee2497fc in __GI_abort () at abort.c:79 #4 0x7fffee2a408e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fffee3bd465 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #5 0x7fffee2b9b9c in malloc_printerr (str=str@entry=0x7fffee3c0400 "malloc(): unaligned fastbin chunk detected") at malloc
[kontact] [Bug 463450] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=463450 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #1 from Thomas Fischer --- I may have encountered the same or a very similar problem. I have kmail crashing several times a day when moving mails between folders (via context menu in mail list) on a Fedora Linux KDE spin system that is not even one week old. I ran the kmail binary via gdb with debuginfod enabled to get the following output. The first few lines may be older and not directly related to the crash: qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5737bdf0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56bbb930) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents [Thread 0x7ffee9bff6c0 (LWP 32407) exited] [Thread 0x7fff66c0 (LWP 32406) exited] [Thread 0x7fff75ffb6c0 (LWP 29371) exited] Downloading separate debug info for /usr/lib64/qt5/plugins/kf5/FrameworkIntegrationPlugin.so Downloading separate debug info for /usr/lib64/libcanberra-0.30/libcanberra-pulse.so [New Thread 0x7fff75ffb6c0 (LWP 32420)] [Detaching after fork from child process 32421] [Detaching after fork from child process 32423] [New Thread 0x7fff66c0 (LWP 32426)] [Detaching after fork from child process 32427] [Thread 0x7fff66c0 (LWP 32426) exited] org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history org.kde.pim.messagelist: Requested invariant for storage row index 3809 not found in history [New Thread 0x7fff66c0 (LWP 32471)] [New Thread 0x7ffee9bff6c0 (LWP 32472)] [New Thread 0x7ffeea7ff6c0 (LWP 32473)] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fff6003f460) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x570d4e70) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5729bca0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents malloc(): unaligned fastbin chunk detected Thread 1 "kmail" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc-2.36-9.fc37.x86_64/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7fffee2afec3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7fffee25fa76 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7fffee2497fc in __GI_abort () at abort.c:79 #4 0x7fffee2a408e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fffee3bd465 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #5 0x7fffee2b9b9c in malloc_printerr (str=str@entry=0x7fffee3c0400 "malloc(): unaligned fastbin chunk detected") at malloc
[kate] [Bug 467097] New: Welcome: select multiple files from "Recent Documents and Projects"
https://bugs.kde.org/show_bug.cgi?id=467097 Bug ID: 467097 Summary: Welcome: select multiple files from "Recent Documents and Projects" Classification: Applications Product: kate Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- When starting Kate, a special page to welcome the user is shown and a list of recent documents is presented. Currently, only a single recently opened file can selected to be opened, but it would be nice to select several files at once to be opened. Related, the list is vertically quite narrow, showing only the last 8 files without scrolling. On a large desktop screen however, there is much empty (unused) space around the welcome widgets. The layout should make better use of the available space on large screens. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 464606] Translations are not installed
https://bugs.kde.org/show_bug.cgi?id=464606 --- Comment #2 from Thomas Fischer --- Git commit 7d513a2da1fa6b4cc3674e4671be1b892366f8db by Thomas Fischer. Committed on 07/02/2023 at 21:06. Pushed by thomasfischer into tag 'v0.9.3.2'. Fixing installation of translations Replacing erroneous macro_optional_add_subdirectory(po) with ki18n_install(po) Fixing faulty commit 1dd33a18bb0d26a1a. M +2-3CMakeLists.txt https://invent.kde.org/office/kbibtex/commit/7d513a2da1fa6b4cc3674e4671be1b892366f8db -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453455] KBibTeX 0.9.90 won't start after I updated to Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453455 Thomas Fischer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #15 from Thomas Fischer --- > KBibTeX seems to be not installed completely. KBibTeX could not locate its > own KPart. > Only limited functionality will be available The easiest way for you to test KBibTeX without needing to run "sudo make install" would have been the script I have prepared for such occassions: https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git Otherwise, I interpret your answer that the bug has been fixed and this report can be closed. Thank you for your feedback! -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 464607] Unused QtNetworkAuth dependency
https://bugs.kde.org/show_bug.cgi?id=464607 Thomas Fischer changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/offi ||ce/kbibtex/commit/6b7246b5a ||a258e8e3d58c48410817d699fb7 ||45bd Resolution|--- |FIXED --- Comment #1 from Thomas Fischer --- Git commit 6b7246b5aa258e8e3d58c48410817d699fb745bd by Thomas Fischer. Committed on 01/02/2023 at 20:11. Pushed by thomasfischer into branch 'kbibtex/0.9'. Removing dependency on Qt5's NetworkAuth ... which was erroneously added in commit 6860474d423c47f06. M +0-1CMakeLists.txt M +1-0ChangeLog https://invent.kde.org/office/kbibtex/commit/6b7246b5aa258e8e3d58c48410817d699fb745bd -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 464606] Translations are not installed
https://bugs.kde.org/show_bug.cgi?id=464606 Thomas Fischer changed: What|Removed |Added Latest Commit||https://invent.kde.org/offi ||ce/kbibtex/commit/1dd33a18b ||b0d26a1a138a1144f5814481837 ||cc5d Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Thomas Fischer --- Git commit 1dd33a18bb0d26a1a138a1144f5814481837cc5d by Thomas Fischer. Committed on 01/02/2023 at 20:11. Pushed by thomasfischer into branch 'kbibtex/0.9'. Reactivating installation of translations M +3-3CMakeLists.txt M +4-0ChangeLog https://invent.kde.org/office/kbibtex/commit/1dd33a18bb0d26a1a138a1144f5814481837cc5d -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 463398] Predefined keywords are not remembered
https://bugs.kde.org/show_bug.cgi?id=463398 --- Comment #5 from Thomas Fischer --- Git commit cad23e2ada3515cc78a88ece1647eec3fb77708a by Thomas Fischer. Committed on 04/01/2023 at 22:00. Pushed by thomasfischer into branch 'master'. Predefined keywords are not remembered When the list of predefined keywords in the settings dialog is changed (keyword added, removed, or modified), those changes should trigger a status changed that this dialog's settings got changed and therefore should get applied when the user clicks "Ok" or "Apply". This commit is a forward port of commit a71b5d77862a696f0b4da4326 from branch 'kbibtex/0.10'. M +1-0CMakeLists.txt M +3-1src/gui/preferences/settingsglobalkeywordswidget.cpp M +4-0src/gui/preferences/settingsglobalkeywordswidget.h M +19 -0src/test/kbibtexguitest.cpp https://invent.kde.org/office/kbibtex/commit/cad23e2ada3515cc78a88ece1647eec3fb77708a -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453455] KBibTeX 0.9.90 won't start after I updated to Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453455 --- Comment #12 from Thomas Fischer --- Git commit ee125af91d7d4e8dfc8927cad85694b55de27a84 by Thomas Fischer. Committed on 04/01/2023 at 22:00. Pushed by thomasfischer into branch 'master'. Fixing crash when opening .bib file In certain situations, also depending on Linux distributions (varying Qt and KDE Frameworks versions), opening a bibliography file can cause crashes (segmentation faults) due to an invalid model or its underlying data. This commit changes the order of two instructions. Now first an internal variable is properly set. Only then an update on the model is applied. The largest part of this commit is a new test that reproducibly crashes without the changed order of two instructions, but passes after the fix has been applied. This commit is a forward-port of commit 4aea6ed35b1629b3dba65a44 from branch 'kbibtex/0.10'. Related: bug 433084 M +36 -0src/test/CMakeLists.txt A +66 -0src/test/kbibtexguitest.cpp [License: GPL (v2+)] https://invent.kde.org/office/kbibtex/commit/ee125af91d7d4e8dfc8927cad85694b55de27a84 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 433084] KBibTeX crashes when opening .bib file
https://bugs.kde.org/show_bug.cgi?id=433084 --- Comment #23 from Thomas Fischer --- Git commit ee125af91d7d4e8dfc8927cad85694b55de27a84 by Thomas Fischer. Committed on 04/01/2023 at 22:00. Pushed by thomasfischer into branch 'master'. Fixing crash when opening .bib file In certain situations, also depending on Linux distributions (varying Qt and KDE Frameworks versions), opening a bibliography file can cause crashes (segmentation faults) due to an invalid model or its underlying data. This commit changes the order of two instructions. Now first an internal variable is properly set. Only then an update on the model is applied. The largest part of this commit is a new test that reproducibly crashes without the changed order of two instructions, but passes after the fix has been applied. This commit is a forward-port of commit 4aea6ed35b1629b3dba65a44 from branch 'kbibtex/0.10'. Related: bug 453455 M +36 -0src/test/CMakeLists.txt A +66 -0src/test/kbibtexguitest.cpp [License: GPL (v2+)] https://invent.kde.org/office/kbibtex/commit/ee125af91d7d4e8dfc8927cad85694b55de27a84 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453455] KBibTeX 0.9.90 won't start after I updated to Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453455 --- Comment #11 from Thomas Fischer --- As you can see in the previous comment, a commit was made to apply the patch I published earlier. There is a helper script that allows you to test this code with little hassle. Please proceed as follows: 0. Uninstall the distribution-provided KBibTeX installation 1. Get this script: https://invent.kde.org/thomasfischer/kbibtex-related/-/raw/master/run/run-kbibtex.sh?inline=false 2. Run as normal user: bash run-kbibtex.sh https://invent.kde.org/office/kbibtex.git kbibtex/0.10 None of the steps above requires root/sudo/su as everything happens in /tmp. If cmake complains about missing development libraries, simply install those via your Linux distribution's package manager and restart the script. Later, you can remove those packages if you see no further need. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 433084] KBibTeX crashes when opening .bib file
https://bugs.kde.org/show_bug.cgi?id=433084 --- Comment #22 from Thomas Fischer --- Git commit 4aea6ed35b1629b3dba65a441db7567eece5eab0 by Thomas Fischer. Committed on 01/01/2023 at 22:04. Pushed by thomasfischer into branch 'kbibtex/0.10'. Fixing crash when opening .bib file In certain situations, also depending on Linux distributions (varying Qt and KDE Frameworks versions), opening a bibliography file can cause crashes (segmentation faults) due to an invalid model or its underlying data. This commit changes the order of two instructions. Now first an internal variable is properly set. Only then an update on the model is applied. The largest part of this commit is a new test that reproducibly crashes without the changed order of two instructions, but passes after the fix has been applied. Related: bug 453455 M +1-1src/gui/file/sortfilterfilemodel.cpp M +36 -0src/test/CMakeLists.txt A +66 -0src/test/kbibtexguitest.cpp [License: GPL (v2+)] https://invent.kde.org/office/kbibtex/commit/4aea6ed35b1629b3dba65a441db7567eece5eab0 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 463398] Predefined keywords are not remembered
https://bugs.kde.org/show_bug.cgi?id=463398 --- Comment #4 from Thomas Fischer --- Git commit a71b5d77862a696f0b4da432607b35c04eafe989 by Thomas Fischer. Committed on 02/01/2023 at 23:09. Pushed by thomasfischer into branch 'kbibtex/0.10'. Predefined keywords are not remembered When the list of predefined keywords in the settings dialog is changed (keyword added, removed, or modified), those changes should trigger a status changed that this dialog's settings got changed and therefore should get applied when the user clicks "Ok" or "Apply". This commit is a forward port of commit 3d32f7724f1471a355a2aad7487 from branch 'kbibtex/0.9', but test 'settingsGlobalKeywordsWidgetAddRemove' in 'KBibTeXGUITest' was added only in this commit here. M +1-0CMakeLists.txt M +3-1src/gui/preferences/settingsglobalkeywordswidget.cpp M +4-0src/gui/preferences/settingsglobalkeywordswidget.h M +19 -0src/test/kbibtexguitest.cpp https://invent.kde.org/office/kbibtex/commit/a71b5d77862a696f0b4da432607b35c04eafe989 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453455] KBibTeX 0.9.90 won't start after I updated to Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453455 --- Comment #10 from Thomas Fischer --- Git commit 4aea6ed35b1629b3dba65a441db7567eece5eab0 by Thomas Fischer. Committed on 01/01/2023 at 22:04. Pushed by thomasfischer into branch 'kbibtex/0.10'. Fixing crash when opening .bib file In certain situations, also depending on Linux distributions (varying Qt and KDE Frameworks versions), opening a bibliography file can cause crashes (segmentation faults) due to an invalid model or its underlying data. This commit changes the order of two instructions. Now first an internal variable is properly set. Only then an update on the model is applied. The largest part of this commit is a new test that reproducibly crashes without the changed order of two instructions, but passes after the fix has been applied. Related: bug 433084 M +1-1src/gui/file/sortfilterfilemodel.cpp M +36 -0src/test/CMakeLists.txt A +66 -0src/test/kbibtexguitest.cpp [License: GPL (v2+)] https://invent.kde.org/office/kbibtex/commit/4aea6ed35b1629b3dba65a441db7567eece5eab0 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 463178] Crash when opening file due to "no installation of BibUtils found"
https://bugs.kde.org/show_bug.cgi?id=463178 Thomas Fischer changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Thomas Fischer --- I am quite sure that KBibTeX does not crash because it does not find BibUtils. Lacking any more information, I am suspecting that this bug report here is a duplicate of bug 453455. I will add more information there (soon-ish) so that you can check if the information posted there fixes your problem. Then, this bug report here can be closed as a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 463398] Predefined keywords are not remembered
https://bugs.kde.org/show_bug.cgi?id=463398 Thomas Fischer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Latest Commit|3d32f7724f1471a355a2aad7487 |https://invent.kde.org/offi |a82e6dd1a067d |ce/kbibtex/commit/3d32f7724 ||f1471a355a2aad7487a82e6dd1a ||067d --- Comment #3 from Thomas Fischer --- Git commit 3d32f7724f1471a355a2aad7487a82e6dd1a067d by Thomas Fischer. Committed on 01/01/2023 at 21:29. Pushed by thomasfischer into branch 'kbibtex/0.9'. Predefined keywords are not remembered When the list of predefined keywords in the settings dialog is changed (keyword added, removed, or modified), those changes should trigger a status changed that this dialog's settings got changed and therefore should get applied when the user clicks "Ok" or "Apply". M +3-1src/gui/preferences/settingsglobalkeywordswidget.cpp https://invent.kde.org/office/kbibtex/commit/3d32f7724f1471a355a2aad7487a82e6dd1a067d -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 290478] KHTML/KJS fails to load JavaScript-heavy site The People's Dictionary (Folkets Lexikon)
https://bugs.kde.org/show_bug.cgi?id=290478 Thomas Fischer changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Thomas Fischer --- (In reply to Justin Zobel from comment #5) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? Using Konqueror 22.08.3, I can no longer reproduce this bug, i.e. the webpage "The People's Dictionary" works as expected. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 463398] Predefined keywords are not remembered
https://bugs.kde.org/show_bug.cgi?id=463398 Thomas Fischer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO Version Fixed In||0.9.3 Latest Commit||3d32f7724f1471a355a2aad7487 ||a82e6dd1a067d --- Comment #1 from Thomas Fischer --- I can confirm this bug. Can you please check the latest commit in the 'kbibtex/0.9' in my personal Git repository (not KBibTeX's official one)? https://invent.kde.org/thomasfischer/kbibtex/commit/3d32f7724f1471a355a2aad7487a82e6dd1a067d You should be able to test this code with a small helper script I have published in a separate repository. Please perform the following steps: 0. Uninstall the distribution-provided KBibTeX installation (not sure if actually necessary; try if problems in following steps arise) 1. Get this script: https://invent.kde.org/thomasfischer/kbibtex-related/-/raw/master/run/run-kbibtex.sh?inline=false 2. Run as normal user: bash run-kbibtex.sh https://invent.kde.org/thomasfischer/kbibtex.git kbibtex/0.9 None of the steps above requires root/sudo/su as everything happens in /tmp. If cmake complains about missing development libraries, simply install those via your Linux distribution's package manager and restart the script. Later, you can remove those packages if you see no further need. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 433084] KBibTeX crashes when opening .bib file
https://bugs.kde.org/show_bug.cgi?id=433084 --- Comment #21 from Thomas Fischer --- This bug and bug 453455 may be related. Please check the patch in comment 9 if it solves your problem, too. https://bugs.kde.org/show_bug.cgi?id=453455#c9 https://bugs.kde.org/attachment.cgi?id=154903 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453455] KBibTeX 0.9.90 won't start after I updated to Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453455 --- Comment #9 from Thomas Fischer --- Created attachment 154903 --> https://bugs.kde.org/attachment.cgi?id=154903=edit Reversing order of two instructions I think I have found the solution for this problem. Please apply this patch to see if it solves your problem. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460316] Command-Line tool for auto-formatting BibTeX file
https://bugs.kde.org/show_bug.cgi?id=460316 --- Comment #9 from Thomas Fischer --- Git commit cd0875e0a8dcb3670e6ae9cf1f8213efffa162ac by Thomas Fischer. Committed on 22/12/2022 at 20:37. Pushed by thomasfischer into branch 'master'. Adding command line program Adding a command line program that offers basic functionality of KBibTeX without a user interface and without many dependencies (basically just Qt::Core and some KBibTeX libraries). Initial implementation can only load a bibliographic file of any recognized file format and write it back to another file or the standard output. M +28 -0src/program/CMakeLists.txt A +105 -0src/program/commandline.cpp [License: GPL(v2.0+)] https://invent.kde.org/office/kbibtex/commit/cd0875e0a8dcb3670e6ae9cf1f8213efffa162ac -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461810] New: Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810
Bug ID: 461810
Summary: Crash with malloc(): mismatching next->prev_size
(unsorted)
Classification: Applications
Product: kmail2
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: fisc...@unix-ag.uni-kl.de
Target Milestone: ---
Since an update on ArchLinux in late October, KMail crashes quite often when
moving mails between folders, e.g. when sorting mails form Inbox to some other
folder. According to the package manager, both kmail and Akonadi have the
version number 22.08.3-1.
To collect information, I stopped Akonadi (akonadictl stop) and restarted it in
a console to see any relevant debug output during a crash. Same with kmail. No
special settings for extra debug output e.g. via kdebugsettings were made.
Akonadi made only some initial output but nothing later or during a crash.
kmail, however, gave the following output. I think but are not sure that the
output up to the last "DispatchModeAttribute" was before the crash.
Error loading text-to-speech plug-in "speechd"
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
d->folderTreeWidget->selectedCollection() Collection ID: 199remote ID:
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxUoQAAA="
name: "Personal"
url: QUrl("akonadi:?collection=199")
parent: 38
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxTaMAAA="
resource: "akonadi_ews_resource_0"
rights: QFlags(AllRights)
contents mime type: ("message/rfc822", "inode/directory")
isVirtual: false
CachePolicy:
inherit: true
interval: -1
timeout: -1
sync on demand: false
local parts: ()
CollectionStatistics:
count: 3620
unread count: 1
size: 561984064
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
malloc(): mismatching next->prev_size (unsorted)
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
malloc(): unaligned fastbin chunk detected
Let me know if I should try to re-create the crash with some additional debug
settings enabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 461810] Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810 --- Comment #1 from Thomas Fischer --- Just restarted kmail. It crashed again when moving a mail (context menu to move mail to another folder). This time, the output was different: malloc(): unaligned tcache chunk detected *** KMail got signal 6 (Exiting) *** Dead letters dumped. malloc(): unaligned tcache chunk detected malloc(): unaligned tcache chunk detected Unable to start Dr. Konqi Re-raising signal for core dump handling. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461810] Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810 --- Comment #1 from Thomas Fischer --- Just restarted kmail. It crashed again when moving a mail (context menu to move mail to another folder). This time, the output was different: malloc(): unaligned tcache chunk detected *** KMail got signal 6 (Exiting) *** Dead letters dumped. malloc(): unaligned tcache chunk detected malloc(): unaligned tcache chunk detected Unable to start Dr. Konqi Re-raising signal for core dump handling. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461810] New: Crash with malloc(): mismatching next->prev_size (unsorted)
https://bugs.kde.org/show_bug.cgi?id=461810
Bug ID: 461810
Summary: Crash with malloc(): mismatching next->prev_size
(unsorted)
Classification: Applications
Product: kmail2
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: fisc...@unix-ag.uni-kl.de
Target Milestone: ---
Since an update on ArchLinux in late October, KMail crashes quite often when
moving mails between folders, e.g. when sorting mails form Inbox to some other
folder. According to the package manager, both kmail and Akonadi have the
version number 22.08.3-1.
To collect information, I stopped Akonadi (akonadictl stop) and restarted it in
a console to see any relevant debug output during a crash. Same with kmail. No
special settings for extra debug output e.g. via kdebugsettings were made.
Akonadi made only some initial output but nothing later or during a crash.
kmail, however, gave the following output. I think but are not sure that the
output up to the last "DispatchModeAttribute" was before the crash.
Error loading text-to-speech plug-in "speechd"
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
d->folderTreeWidget->selectedCollection() Collection ID: 199remote ID:
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxUoQAAA="
name: "Personal"
url: QUrl("akonadi:?collection=199")
parent: 38
"AAMkADdjYzdhYjJkLTBjNGItNDRhZS05NjZjLWIxNzY5OTI2MTllNwAuAAA5OWMvCOhAR7niCe/yxRIKAQCzEcl00IXvRLelEuHv21iGxTaMAAA="
resource: "akonadi_ews_resource_0"
rights: QFlags(AllRights)
contents mime type: ("message/rfc822", "inode/directory")
isVirtual: false
CachePolicy:
inherit: true
interval: -1
timeout: -1
sync on demand: false
local parts: ()
CollectionStatistics:
count: 3620
unread count: 1
size: 561984064
org.kde.pim.mailtransportakonadi: Item doesn't have DispatchModeAttribute.
malloc(): mismatching next->prev_size (unsorted)
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
malloc(): unaligned fastbin chunk detected
Let me know if I should try to re-create the crash with some additional debug
settings enabled.
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 460316] Command-Line tool for auto-formatting BibTeX file
https://bugs.kde.org/show_bug.cgi?id=460316 Thomas Fischer changed: What|Removed |Added Latest Commit|6d94c8f836ca6ce3339c75da222 |2c60618d2fd1a74009d4f89eb0f |2f613f54aff7b |75ffbe62a1749 Version Fixed In||0.11 --- Comment #7 from Thomas Fischer --- (In reply to nobodyinperson from comment #5) > Would is also be possible to make a cli flag for auto-generating the IDs? > That would be awesome! https://invent.kde.org/thomasfischer/kbibtex/commit/2c60618d2fd1a74009d4f89eb0f75ffbe62a1749 The format string is found in the Preferences -> Id Suggestions -> select one -> Edit -> See top of editing dialog. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460315] Sorting in output file
https://bugs.kde.org/show_bug.cgi?id=460315 --- Comment #10 from Thomas Fischer --- Git commit f3f7b16ac93eab91033a20f7b7a227ca98dfd187 by Thomas Fischer. Committed on 22/10/2022 at 20:52. Pushed by thomasfischer into branch 'master'. Making detection of sorting less sensitive Previous commit eb510bdfdc46afaa520a9 introduced a heuristic to detect whether entries and macros in a BibTeX file where (partially) sorted and then tried to impose a complete sorting on the file when writing back to disk. As it turned out, the chosen threshold for detecting sorting was too sensitive thus sorting bibliographies that are not meant to be (forcefully) sorted, e.g. to keep the difference between two Git commits small. This commit here decreases the sensitivity to a (still arbitrary) value that seems to be a good compromise that still detects (partially) sorted bibliographies, but does not errornously assess almost unsorted bibliographies as sorted. M +1-1src/io/fileimporterbibtex.cpp https://invent.kde.org/office/kbibtex/commit/f3f7b16ac93eab91033a20f7b7a227ca98dfd187 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460316] Command-Line tool for auto-formatting BibTeX file
https://bugs.kde.org/show_bug.cgi?id=460316 Thomas Fischer changed: What|Removed |Added Status|ASSIGNED|NEEDSINFO Resolution|--- |WORKSFORME Latest Commit|696ebd4dc39817c58d317782ac8 |6d94c8f836ca6ce3339c75da222 |391ae262fb5c2 |2f613f54aff7b --- Comment #4 from Thomas Fischer --- > Would it be very difficult to have the normal 'kbibtex' executable provide > this functionality? Just for the sake of having less executables flying > around... I am favoring two separate binaries. First 'kbibtex' and 'kbibtex-cli' may have different arguments and options for various operations that may be in conflict if the "command line" gets more elaborate. Second, the latest commit (6d94c8f836ca6ce33, unless I force-push) contains a refactored build system that allows to build just 'kbibtex-cli' without any graphical libraries. That means to compile only 60 instead of about 200 code files and less dependencies. Viable for server or container deployments where automated processing of BibTeX files is required. Please test for yourself by switching on option BUILD_APP_COMMAND_LINE and disabling options BUILD_APP_DESKTOP and BUILD_KPART. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 457499] No doi or url fields available in Edit Element window, but not allowed to create doi or url fields in Other Fields tab
https://bugs.kde.org/show_bug.cgi?id=457499 --- Comment #4 from Thomas Fischer --- Created attachment 153103 --> https://bugs.kde.org/attachment.cgi?id=153103=edit Message widget explain where to put DOI and URL -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 457499] No doi or url fields available in Edit Element window, but not allowed to create doi or url fields in Other Fields tab
https://bugs.kde.org/show_bug.cgi?id=457499 Thomas Fischer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |NOT A BUG --- Comment #3 from Thomas Fischer --- > This does solve the problem! I didn't realize that DOIs and URLs should go > in the External tab, or that simply typing in a DOI or a URL was > automatically recognized for what it was, and included in the source as doi > = "..." and url = "...". You are not the first who had this problem. Starting from KBibTeX 0.10, there will a message widget explaining where to put URLs and DOIs. > Is this documented somewhere? Are there other > formats that External automatically recognizes? Thanks again! Well, it is documented in code. - Every field that starts with "postscript", "localfile", "file", "url", "doi", "ee", or "biburl" goes into the External list. - Writing back to BibTeX code: src/gui/element/elementwidget.cpp, function FilesWidget::apply(..). Using regular expressions, it will check if the user's input looks like a DOI or a URL, respectively, and treat everything else as a local file's name. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 Thomas Fischer changed: What|Removed |Added Latest Commit||58c75501646fc2024b6f637bf0a ||fd98234e92f6f --- Comment #10 from Thomas Fischer --- > All three commands successfully open the PDF in Okular. There is a warning > in the terminal "Unable to open QuickAnnotatingTools XML definition" but > that seems to come from Okular itself and doesn't have a negative > consequence. Although that is good for you, it does not help me in locating the problem. I added some debug output near the opening of the PDF document to the bug's Git branch. Maybe that gives some useful data. Please run the previous 'run-kbibtex.sh' command with 'bugs/kde459911' at the end. Verify that the script's output states that you run commit 58c75501646fc2024b6f63 as well as that when you try to open a PDF document, there is a debug output similar to: [info] kbibtex (/path/to/kbibtex/src/parts/part.cpp:903) - About to open URL "file:///path/to/wu2019compression.pdf" -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 460684] New: Support timestamps as number system
https://bugs.kde.org/show_bug.cgi?id=460684
Bug ID: 460684
Summary: Support timestamps as number system
Classification: Applications
Product: kcalc
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: ete...@alum.rit.edu
Reporter: fisc...@unix-ag.uni-kl.de
Target Milestone: ---
In addition to decimal, octal, or binary number systems, kcalc should support
timestamps as number systems.
For example, if the user enters "0:30.5" this should be interpreted as 30
seconds and 500 milliseconds. Adding another number like "0:42" should be
possible, resulting in the output of "1:12.5".
It should be possible to do multiplications and divisions of timestamps with
"regular" numbers. For example, "1:20" divided by 5 should give "0:16".
For internal purposes, user-entered timestamp strings can be converted to a
floating-point number.
For example, the following regular expression can be used to make sense of the
user's input:
(?:(?:(?P\d+):)?(?P\d{1,2}):)?(?P\d{1,2})(?P[,.]\d+)?
Expressed in Python, the floating-point representation gets computed as
follows:
hour = int(m.group("hour")) if m.group("hour") else 0
minute = int(m.group("minute")) if m.group("minute") else 0
second = int(m.group("second")) if m.group("second") else 0
fraction = float("0" + m.group("fraction").replace(",", ".")) if
m.group("fraction") else 0.0
result = (hour * 60 + minute) * 60 + second + fraction
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 457499] No doi or url fields available in Edit Element window, but not allowed to create doi or url fields in Other Fields tab
https://bugs.kde.org/show_bug.cgi?id=457499 Thomas Fischer changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #1 from Thomas Fischer --- > The fact that the +Add button goes gray seems to indicate that KBibTex knows > that the doi and url fields are special. But they're not available among all > the other fields in the other tabs of the New Element / Edit Element window. URLs and DOIs go into the "External" tab, where you add a new line with +Add, then enter or paste the DOI or URL you want to have. Does this solve your problem? -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460316] Command-Line tool for auto-formatting BibTeX file
https://bugs.kde.org/show_bug.cgi?id=460316 Thomas Fischer changed: What|Removed |Added Latest Commit|93bfb10deb49e0c688b3625e3a1 |696ebd4dc39817c58d317782ac8 |a4301a4797425 |391ae262fb5c2 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460316] Command-Line tool for auto-formatting BibTeX file
https://bugs.kde.org/show_bug.cgi?id=460316 Bug 460316 depends on bug 460315, which changed state. Bug 460315 Summary: Sorting in output file https://bugs.kde.org/show_bug.cgi?id=460315 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460315] Sorting in output file
https://bugs.kde.org/show_bug.cgi?id=460315 Thomas Fischer changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #8 from Thomas Fischer --- I forgot to run one test that needs manual configuration. It turns out, the threshold to recognize whether a partially sorted file is to be sorted when writing it to disk was too low. In file src/io/fileimporterbibtex.cpp at line 1297, I would like the multiplicator from 3 to 10. This basically means that are for a file to be recognized as sorted, it must be already somewhat sorted, but to a larger extend than with the previous value of 3. Please check if the value of 10 is still ok for you. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453850] Flathub package
https://bugs.kde.org/show_bug.cgi?id=453850 Thomas Fischer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Thomas Fischer --- (In reply to Matthias Mailänder from comment #0) > Hi, I created https://github.com/flathub/flathub/pull/3152 Hello, sorry for my late answer. Thank you for your work and contribution! -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460315] Sorting in output file
https://bugs.kde.org/show_bug.cgi?id=460315
Thomas Fischer changed:
What|Removed |Added
Latest Commit|658106cd9a5cb50320ab557f881 |https://invent.kde.org/offi
|a17c16da1b4a2 |ce/kbibtex/commit/eb510bdfd
||c46afaa520a9aa71c640c881ea6
||eaba
--- Comment #7 from Thomas Fischer ---
Git commit eb510bdfdc46afaa520a9aa71c640c881ea6eaba by Thomas Fischer.
Committed on 16/10/2022 at 12:27.
Pushed by thomasfischer into branch 'master'.
BibTeX file property: sort by identifier
A new property can be set for BibTeX files: whether elements (foremost
entries and macros) should be sorted by their identifier or key,
respectively.
This patch includes the following aspects to implement this feature:
- when importing a BibTeX file, the Statistics struct counts how often
two consecutive entries/macros in an imported file have identifiers/
keys in sorted order and how often not. Depending on the result, the
SortedByIdentifier flag is set true or false.
- when exporting a BibTeX file and the SortedByIdentifier flag is set,
the File list will be copied and then sorted by identifier and key,
respectively before writing to disk.
- The file settings docklet and the properties dialog at "Save As"
operations allow to set the SortedByIdentifier flag.
- Sorting is implemented as a static function in class File, in case it
will be used in other cases like other exporters in the future.
- In KBibTeXDataTest, a new test ('sortFileByIdentifier') has been added
to test the sorting functionality.
Unsetting the SortedByIdentifier flag has no immediate consequence,
there is no shuffling made.
M +53 -1src/config/preferences.cpp
M +13 -1src/config/preferences.h
M +7-0src/config/preferences.json
M +5-0src/data/element.cpp
M +2-0src/data/element.h
M +41 -0src/data/file.cpp
M +8-0src/data/file.h
M +9-0src/gui/widgets/filesettingswidget.cpp
M +1-0src/gui/widgets/filesettingswidget.h
M +18 -5src/io/fileexporterbibtex.cpp
M +19 -3src/io/fileimporterbibtex.cpp
M +105 -0src/test/kbibtexdatatest.cpp
https://invent.kde.org/office/kbibtex/commit/eb510bdfdc46afaa520a9aa71c640c881ea6eaba
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 460315] Sorting in output file
https://bugs.kde.org/show_bug.cgi?id=460315 Thomas Fischer changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #6 from Thomas Fischer --- (In reply to nobodyinperson from comment #5) > Seems to work very well! Also very nice the fuzzy detection of the > "sortedness" of a file! Thank you very much, Thomas! Nice to hear ☺ I guess that means I can merge the change and close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460316] Command-Line tool for auto-formatting BibTeX file
https://bugs.kde.org/show_bug.cgi?id=460316 Bug 460316 depends on bug 460315, which changed state. Bug 460315 Summary: Sorting in output file https://bugs.kde.org/show_bug.cgi?id=460315 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460316] Command-Line tool for auto-formatting BibTeX file
https://bugs.kde.org/show_bug.cgi?id=460316
Thomas Fischer changed:
What|Removed |Added
Latest Commit||93bfb10deb49e0c688b3625e3a1
||a4301a4797425
Ever confirmed|0 |1
Status|REPORTED|ASSIGNED
--- Comment #2 from Thomas Fischer ---
Rudimentary implementation of this request is available in this commit:
https://invent.kde.org/thomasfischer/kbibtex/commit/93bfb10deb49e0c688b3625e3a1a4301a4797425
As of now, it just loads a bibliographic file and writes its back out to stdout
or a file (file formats determined by filenames). "inplace" is technically
possible by providing the same filename both for input and output (not tested
but should work as input file is closed before output file is written).
Formatting is implicit, as the output is build from an internal representation
of the bibliography, not the input file directly.
The code does not contain any changes proposed for bug 460315, so no sorting
yet, only once both bugfix branches are merged back into the main branch.
As "kbibtex-cli" is a command line tool, it should have a man page
("kbibtex-cli.1"). This may be something for you to contribute ...
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911
--- Comment #8 from Thomas Fischer ---
(In reply to Florian Edelmann from comment #7)
> Created attachment 152794 [details]
> Minimal reproduction
I tested the file by placing another PDF file named "wu2019compression.pdf"
next to it. The PDF file can be opened in the main view both via Ctrl+D and the
context menu ("View Document" -> "Local files") as well as when opening the
editing dialog, switching to tab "External" and opening the file using the
button next to the filename's entry.
I suspect that there is another problem on your machine, causing problems here.
Opening a PDF file is, for KBibTeX, a simple operation asking the desktop
environment to open a file with the associated tool (e.g. Okular). KBibTeX does
not receive any feedback whether this succeeded or not.
To mimic KBibTeX's opening request, using a terminal in KDE, navigate to the
directory where "wu2019compression.pdf" is located. Then, issue these commands:
xdg-open wu2019compression.pdf
kde-open wu2019compression.pdf
kde-open5 wu2019compression.pdf
I am not sure which will be available, may depend on your distribution and
package selection. Please report back what happens (output in terminal, error
message, success?).
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 460315] Sorting in output file
https://bugs.kde.org/show_bug.cgi?id=460315 Thomas Fischer changed: What|Removed |Added Version Fixed In||0.11 Latest Commit||658106cd9a5cb50320ab557f881 ||a17c16da1b4a2 --- Comment #4 from Thomas Fischer --- (In reply to nobodyinperson from comment #3) > That sound absolutely awesome, thank you Thomas! Looking forward to > trying it! So, I had to fix some small issues here and there and added a test function as well. You can see the current commit here: https://invent.kde.org/thomasfischer/kbibtex/commit/658106cd9a5cb50320ab557f881a17c16da1b4a2 You can test the code by following the instructions here: https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git with the adjusted script invocation: bash run-kbibtex.sh 'https://invent.kde.org/thomasfischer/kbibtex.git' 'bugs/kde460315' -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 460315] Sorting in output file
https://bugs.kde.org/show_bug.cgi?id=460315 Thomas Fischer changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Thomas Fischer --- I agree that this is a useful feature. I was able to make a basic implementation, but I want to check it first with a fresh pair of eyes before pushing it to the Git repo. Regarding the source code, you were on the right track. To have a sorted output, one has to look into FileExporterBibTeX::saveAsString(.., const File *). There, I introduced const File *_bibtexfile = sortedByIdentifier ? File::sortByIdentifier(bibtexfile) : bibtexfile; ... and use a search to make use of _bibtexfile instead of the original bibtexfile in the remainder of this function. File::sortByIdentifier(..) is a new function that basically employs std::sort(..) with a custom comparison function to get the desired result. To make it more useful, the code expands on FileImporterBibTeX::Private::Statistics to track if two subsequent entries' ids are in lexicographic order. When opening a BibTeX file, based on this counter it is guessed if this file is "sorted" or not. This information is tracked as a file property and then used when saving a file as described above. The property can also toggled in the per-file properties widget. Activating it will only have an effect when writing. Deactivation has no practical effect, there is no shuffling in this case ;-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 460301] New: Highlighting indicates error in correct Bash's coproc statement
https://bugs.kde.org/show_bug.cgi?id=460301
Bug ID: 460301
Summary: Highlighting indicates error in correct Bash's coproc
statement
Classification: Frameworks and Libraries
Product: frameworks-syntax-highlighting
Version: 5.98.0
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: syntax
Assignee: kwrite-bugs-n...@kde.org
Reporter: fisc...@unix-ag.uni-kl.de
CC: walter.von.entfer...@posteo.net
Target Milestone: ---
The following text is correct Bash code:
coproc { ls thisfiledoesntexist; read; } 2>&1
Syntax highlighting for Bash, however, indicates that the closing curly bracket
(after "read;", before "2) is wrong.
Example on coproc taken from
https://wiki.bash-hackers.org/syntax/keywords/coproc
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 --- Comment #6 from Thomas Fischer --- > In the list, Ctrl+D still works as expected, but "View document" in the > context menu still does only work for online entries, not for local PDF > files. Are you using localfile="abc.pdf" or something else? Can you please provide a minimal BibTeX file that reproducible does not work with KBibTeX? -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 --- Comment #3 from Thomas Fischer --- (In reply to Florian Edelmann from comment #2) > A workaround I just discovered: Opening the PDF with the keyboard shortcut > (Ctrl+D) works fine. Using your instructions in the linked issue, I could > verify that it does still not work in the 0.9 git version. Ok, I found and fixed some other issues related to locating the right URL to open. Please try this here: bash run-kbibtex.sh 'https://invent.kde.org/thomasfischer/kbibtex.git' 'bugs/kde459911' > When trying to run the 0.10 git version, I got this build error: > [..] > /tmp/flo-kbibtex-usr/bin/kbibtex: error while loading shared libraries: > libkbibtexprocessing.so.0: cannot open shared object file: No such file or > directory You cannot simply compile the code and run the resoluting kbibtex binary. There are some shared libraries such as libkbibtexprocessing which are not found then as they lurk somewhere in the build directory. Please use the run-kbibtex.sh script which will setup a temporary installation inside /tmp without interfering with your regular installation and without using su or sudo. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 Thomas Fischer changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Thomas Fischer --- It is possible that your bug report is a duplicate of bug 459150. Can you please test if the fix commit to branch kbibtex/0.9 fixed you problem and/or if the bug still exists in branch kbibtex/0.10 which will become the future KBibTeX 0.10? For instructions, please see comment 1 for bug bug 459150: https://bugs.kde.org/show_bug.cgi?id=459150#c1 -- You are receiving this mail because: You are watching all bug changes.
