[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 Pierre changed: What|Removed |Added CC||d...@wismill.eu --- Comment #6 from Pierre --- This is another occurrence of the infamous “need to kick hotkeys on release, not press” (see: https://gitlab.freedesktop.org/xorg/xserver/-/issues/258). This is not a bug per se, but a known limitation of the XKB protocol. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 Pierre changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 476591] Part of the skrooge flatpak's user interface is not translated and remains in English
https://bugs.kde.org/show_bug.cgi?id=476591 --- Comment #8 from Jean-Pierre V --- Hi Skierpage, I confirm your point : adding this symlink to org.kde.skrooge makes skrooge works perfectly in French. So there is a weird thing in the process of building this package. To me it is not only for the french language, in the skrooge gitlab/po repository you have about 43 languages available. However only 19 symlinks available in the ./files/share/locale/ directory... strange. I am not skilled enough to help ... hope some experts can help. Thanks for the fix JP -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 476591] Part of the skrooge flatpak's user interface is not translated and remains in English
https://bugs.kde.org/show_bug.cgi?id=476591 --- Comment #6 from Jean-Pierre V --- May be it can help : If I type the below commands , I cannot see any link to the french locale, would it be a reason ? flatpak run --command=bash org.kde.skrooge Then [ org.kde.skrooge locale] cd /app/share/locale [ org.kde.skrooge locale]$ ls -l total 8 lrwxrwxrwx 1 nfsnobody nfsnobody 47 24 févr. 15:06 ca@valencia -> ../../share/runtime/locale/ca/share/ca@valencia lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 da -> ../../share/runtime/locale/da/share/da drwxr-xr-x 3 nfsnobody nfsnobody 4096 1 janv. 1970 en_GB drwxr-xr-x 3 nfsnobody nfsnobody 4096 1 janv. 1970 en_US lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 eu -> ../../share/runtime/locale/eu/share/eu lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 fi -> ../../share/runtime/locale/fi/share/fi lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 ga -> ../../share/runtime/locale/ga/share/ga lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 gl -> ../../share/runtime/locale/gl/share/gl lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 ia -> ../../share/runtime/locale/ia/share/ia lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 ja -> ../../share/runtime/locale/ja/share/ja lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 ko -> ../../share/runtime/locale/ko/share/ko lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 mr -> ../../share/runtime/locale/mr/share/mr lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 ms -> ../../share/runtime/locale/ms/share/ms lrwxrwxrwx 1 nfsnobody nfsnobody 40 24 févr. 15:06 nds -> ../../share/runtime/locale/nds/share/nds lrwxrwxrwx 1 nfsnobody nfsnobody 41 24 févr. 15:06 pt_BR -> ../../share/runtime/locale/pt/share/pt_BR lrwxrwxrwx 1 nfsnobody nfsnobody 38 24 févr. 15:06 ug -> ../../share/runtime/locale/ug/share/ug lrwxrwxrwx 1 nfsnobody nfsnobody 41 24 févr. 15:06 zh_CN -> ../../share/runtime/locale/zh/share/zh_CN lrwxrwxrwx 1 nfsnobody nfsnobody 41 24 févr. 15:06 zh_TW -> ../../share/runtime/locale/zh/share/zh_TW -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 476591] Part of the skrooge flatpak's user interface is not translated and remains in English
https://bugs.kde.org/show_bug.cgi?id=476591 --- Comment #5 from Jean-Pierre V --- Created attachment 166126 --> https://bugs.kde.org/attachment.cgi?id=166126=edit Skrooge screenshot with a native installation (via pacman) To show what it should be -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 476591] Part of the skrooge flatpak's user interface is not translated and remains in English
https://bugs.kde.org/show_bug.cgi?id=476591 --- Comment #4 from Jean-Pierre V --- (In reply to skierpage from comment #3) > Created attachment 166122 [details] > incomplete localization of the Skrooge flatpak from flathub Yes exactly ! confirm , same screenshot you sent ! The menu items "configuration" and "aide" are in French as well as the second line (Nouveau/ouvrir) whereas the others menu items remain in English. As we can see in your screenshot the items (DashBoard, Accounts, ) remains also in English. I will send a screenshot of a native installation of skrooge (pacman -Syu skrooge on Arch Linux) where everything is translated to compare. Thanks JP -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481019] New: kscreenlocker 5.27.10 unable to unlock with pam_krb5
https://bugs.kde.org/show_bug.cgi?id=481019 Bug ID: 481019 Summary: kscreenlocker 5.27.10 unable to unlock with pam_krb5 Classification: Plasma Product: kscreenlocker Version: git-stable-Plasma/5.27 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pierre.sau...@stwm.de Target Milestone: --- kscreenlocker unlock does not work in combination with pam_krb5 Relevant lines from the journal (sensitive information redacted): Feb 07 18:07:42 $HOSTNAME kscreenlocker_greet[40929]: pam_krb5(kde:auth): (user $USER) attempting authentication as USER@REALM Feb 07 18:07:42 $HOSTNAME kscreenlocker_greet[40929]: pam_krb5(kde:auth): (user $USER) credential verification failed: Permission denied Feb 07 18:07:42 $HOSTNAME kscreenlocker_greet[40929]: pam_krb5(kde:auth): authentication failure; logname=$USER uid= euid= tty= ruser= rhost= Feb 07 18:07:42 $HOSTNAME kscreenlocker_greet[40929]: pam_krb5(kde:auth): pam_sm_authenticate: exit (failure) Feb 07 18:07:42 $HOSTNAME kscreenlocker_greet[40929]: pam_unix(kde:auth): authentication failure; logname= uid= euid=10236 tty= ruser= rhost= user=$USER Feb 07 18:07:45 $HOSTNAME kscreenlocker_greet[40929]: pam_krb5(kde:auth): pam_sm_authenticate: entry Our pam common-auth: authsufficient pam_krb5.so minimum_uid=1 debug authrequiredpam_unix.so try_first_pass nullok_secure Note that user homes are on NFS4 with sec=krb5p. I assume this behaviour was introduced by: https://invent.kde.org/plasma/kscreenlocker/-/commit/132adacf3d01fc4adf8a873e0debc3adb17972ec "Cleanup kcheckpass" setuid root kcheckpass was removed. How is that supposed to work now? SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.10-0ubuntu1~ubuntu22.04~ppa1 KDE Plasma Version: 5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472268] Kmail crashed attempting to search "Find Action"
https://bugs.kde.org/show_bug.cgi?id=472268 --- Comment #6 from Pierre Métras --- Created attachment 165385 --> https://bugs.kde.org/attachment.cgi?id=165385=edit New crash information added by DrKonqi kmail (5.22.3 (22.12.3)) using Qt 5.15.8 Any input from keyboard in menu Help > Find Action... results in KMail crash. -- Backtrace (Reduced): #4 0x7fb0c3f5d168 in QAction::text() const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #9 0x7fb0c3281d9b in QSortFilterProxyModel::columnCount(QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb0c41e95bb in QHeaderView::initializeSections() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fb0c41ee36a in QHeaderView::reset() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #13 0x7fb0c324c11d in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472268] Kmail crashed attempting to search "Find Action"
https://bugs.kde.org/show_bug.cgi?id=472268 Pierre Métras changed: What|Removed |Added CC||pie...@alterna.tv -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362579] Segfault when selecting multiple adresses from contact list
https://bugs.kde.org/show_bug.cgi?id=362579 Pierre Métras changed: What|Removed |Added CC||pie...@alterna.tv --- Comment #13 from Pierre Métras --- Still present in January 2024 with Kmail 5.22.3 (22.12.3) from Debian 12.4. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475763] Kdenlive 23.08.2 AppImage crashes at startup
https://bugs.kde.org/show_bug.cgi?id=475763 --- Comment #8 from Pierre Nerzic --- Hi everyone, As I said, kdenlive-23.08.4-x86_64-A.AppImage solved the issue that was specified by capedmadman1941 in his first ticket (many missing .so). I cannot reproduce his next issue with X server on Mate. Best wishes and happy new year ! Pierre -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475763] Kdenlive 23.08.2 AppImage crashes at startup
https://bugs.kde.org/show_bug.cgi?id=475763 --- Comment #6 from Pierre Nerzic --- Hello Jean-Baptiste and all, Good news from me : the new kdenlive-23.08.4-x86_64-A.AppImage works perfectly on my Debian Bookworm. No message/alert when launched from GUI. And launched from terminal, I only have info messages: some missing avfilter plugins, some missing services, some "shared memfd open() failed", but nothing related to missing libraries. For me now, this is "the release". I wonder why it does not work on Ubuntu Mate for capedmadman1941. I can see nothing like that. I wish this is not related to this AppImage. Many thanks for all your awesome work on Kdenlive, Pierre -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475763] Kdenlive 23.08.2 AppImage crashes at startup
https://bugs.kde.org/show_bug.cgi?id=475763 Pierre Nerzic changed: What|Removed |Added CC||pierre.ner...@free.fr --- Comment #3 from Pierre Nerzic --- Hello everyone, Same problem with newer AppImages : kdenlive-23.08.3-x86_64.AppImage and kdenlive-23.08.3-x86_64-A.AppImage both show these missing versions of libstdc++.so.6 on a Debian stable. Best regards, Pierre -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 476591] New: Part of the user interface is not translated and remains in English
https://bugs.kde.org/show_bug.cgi?id=476591 Bug ID: 476591 Summary: Part of the user interface is not translated and remains in English Classification: Applications Product: skrooge Version: Trunk from git Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: steph...@mankowski.fr Reporter: jpvit...@free.fr Target Milestone: --- SUMMARY ***I I am using the latest flatpak version 2.31.0 on flathub. Part of the GUI is not translated in local language (Fr) and remains in English. The proposed additional languages are only English US or GB. Can you publish a full i10n version with all xx.po files supported by skrroge (with the french language) ? *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.1.60-1lts/5.27.9 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476572] New: Display the colour of an email when selected
https://bugs.kde.org/show_bug.cgi?id=476572 Bug ID: 476572 Summary: Display the colour of an email when selected Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- Bonjour, Example : in the list of emails, if the text of one email is displayed in red (= important), it becomes white on a blue line background when selected. The color selected for an email must be visible when the email is selected, whichever is this color. When changing the color, this must be acknowledged / visible on the display. Pierre STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476497] New: Checking words spelling
https://bugs.kde.org/show_bug.cgi?id=476497 Bug ID: 476497 Summary: Checking words spelling Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- Kmail must not check the text which is not part of the answer typed !!! The text of the original email must not be checked. Pierre STEPS TO REPRODUCE 1. Answer an email with spell mistakes 2. 3. OBSERVED RESULT EXPECTED RESULT Only the text typed for the answer must be checked, nothing else. SOFTWARE/OS VERSIONS Mageia 9/KDE Plasma: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476321] Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 --- Comment #5 from Pierre THOMAS --- (In reply to Laurent Montel from comment #3) > I understand french :) (I am french :) ) > > I tested your text by when I reply it's quoted => it will not show warning. > > Could you paste a screenshot from your composer when you reply and you see > warning. > > For me I have ">" at the beginning of each line > => code will not check this text. > > so it's ok for me. > > thanks Bonjour, For the email in the screenshot, the warning is displayed after having just clicked "Répondre", nothing else. The problem is similar for spell checking: the spell checking must absolutely be limited to the text typed for the answer ... Pierre -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476321] Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 --- Comment #4 from Pierre THOMAS --- Created attachment 162835 --> https://bugs.kde.org/attachment.cgi?id=162835=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476321] Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 --- Comment #2 from Pierre THOMAS --- (In reply to Laurent Montel from comment #1) > I don't understand how to reproduce it. > We check if text has "attachment" words. > but we mustn't check when text is quoted > > => please provide a test email please. > > Thanks I thank you Laurent for considering my request. Example Email received : Bonjour à tous, Je vous laisse découvrir le programme qui vous a été concocté par la commission animation pour le week-end avec hébergement des 4 et 5 mai 2024. Vous trouverez en pièce jointe la fiche d'inscription et le descriptif du séjour. Le nombre de places étant limité, priorité est donnée aux adhérents. Toutefois, il vous sera possible d'inscrire un invité non adhérent sur votre bulletin d'inscription, sachant que son inscription ne pourra être validée que sous réserve de places disponibles. Amicalement Catherine When I click to locate the mouse cursor at the beginning of the text of my answer to type, and then I type Enter, without having typed anything else, I get the warning : Le message que vous avez composé fait référence à un fichier joint, mais vous n'avez rien joint. Voulez-vous joindre un fichier à votre message ? (I hope you understang French !) I didn’t type any word concerning a file to attach !!! This warning must not be displayed !!! I guess the warning comes from the fact that the text of the the original email contains « en pièce jointe » (???). The text of the original email must not be analyzed by KMail !!! Pierre -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #66 from Jean-Pierre Boucher --- It' a good news, Frank Zappa said “*A mind is like a parachute. It doesn't work if it is not open*.” Keep progressing digikam for a long time... Jean-Pierre Boucher Le lun. 30 oct. 2023 à 14:22, a écrit : > https://bugs.kde.org/show_bug.cgi?id=398166 > > --- Comment #65 from caulier.gil...@gmail.com --- > We currently switch from MXE to VCPKG framework to build digiKam for > Windows. > > The port is under progress. I hope finalize this step in next week. > > In VCPKG project i see this entry about Gphoto2 under Windows, especially > this > comment : > > https://github.com/Microsoft/vcpkg/issues/5075#issuecomment-633519224 > > If M$ can provide a patch to use natively Gphoto2 under Windows, as the > camera > interface is out-to -date, this will be nice... > > Gilles Caulier > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #6 from Jean-Pierre Boucher --- That's great ! The menu works as expected ! This is not a bug ! There is nothing more to say... Only the fact that the translation of digiKam into French is still at a standstill, it's just a window opening on a wall... . Sorry to bother you with the French translation. That's all folk . You can close the bug. JP. Boucher Le lun. 30 oct. 2023 à 10:35, a écrit : > https://bugs.kde.org/show_bug.cgi?id=476316 > > --- Comment #4 from caulier.gil...@gmail.com --- > All is well explained in DK doc git repo README : > > > https://invent.kde.org/documentation/digikam-doc/-/blob/master/README.md?ref_type=heads#translations > > The status of translations is given at this page : > > https://l10n.kde.org/stats/gui/trunk-kf5/package/digikam-doc/ > > Even if DE and FR translations are branched in the doc, nobody working on > yet. > Branched want means ready to use with the Sphinx framework used to render > the > doc. But if translations are empty (English words still untranslated), the > page > will rest in English. > > Why branched rules exists if no translations yet : to render pages with not > complete translations, to help translators. > > In other words : menu work as expected. > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #5 from Jean-Pierre Boucher --- good investigation in fact the translation hat I have is carried out by the Google Chrome translator, I did not realize that the pop-up was that of Google Chrome. The translation is quite good ! Jean-Pierre Le lun. 30 oct. 2023 à 10:09, Maik Qualmann a écrit : > https://bugs.kde.org/show_bug.cgi?id=476316 > > --- Comment #3 from Maik Qualmann --- > I suspect that the cause is the redirection to a mirror server, depending > on > which country you are in. I can also reproduce it here in Germany, no > French, > it stays in English. Other languages, Italian or Spanish also work. German > also > remains in English, but I don't know if there is a German translation yet. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476321] New: Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 Bug ID: 476321 Summary: Answering an email to which a file is attached Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- Kmail must not propose to join a file if nothing in the answer to an original email suggests a file to be joined. If the original email has a file joined (and perhaps words saying a file is joined), Kmail proposes to join a file to the answer !!! Pierre STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Mageia 9 / Plasma 5.27.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #2 from Jean-Pierre Boucher --- Windows 10 22H2 Jean-Pierre Boucher Le lun. 30 oct. 2023 à 09:21, a écrit : > https://bugs.kde.org/show_bug.cgi?id=476316 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > Version|8.1.0 |8.2.0 > > --- Comment #1 from caulier.gil...@gmail.com --- > Hi, > > which web browser did you use ? > > Here using Windows 10 22H2 : > > - Firefox 119 => ok > - Chrome 118 => ok > - Edge 117 => ok > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] New: The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 Bug ID: 476316 Summary: The drop-down menu located at the bottom left in digiKam on-line documentation does not work Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- Created attachment 162720 --> https://bugs.kde.org/attachment.cgi?id=162720=edit Screen copies in a pdf file Hello everyone, after 10 months of resuming the translations of the digiKam online documentation in another environment, I noticed a strange behavior in the online help which prevented me from understanding that all the translations in French was apparently completed. If you wish to change the language, by default the language presented (despite the choice of language configuration in digiKam) is English. If you want to have the online documentation in French, and if you click on a language option in the drop-down menu located at the bottom left it does not work (?), but surprisingly if you switch back to English a popup appears at the top right of the screen, with the English and French (?) options and if you choose French, after a few seconds the text is correctly translated into French and without looking everywhere, it seems working throughout the documentation, it's just wonderful! Congratulations to the translation teams, but still a little surprising, because you actually have to not use the drop-down menu (?) but the pop-up presented... You will find attached some screenshots to illustrate my Remarks. Despite this inconvenience, congratulations to all, and my greetings to Gilles Caullier, Jean-Pierre Boucher STEPS TO REPRODUCE 1. Manuel utilisateur en ligne 2. Click on French in drop-down menu located at the bottom left 3. OBSERVED RESULT the documentation remains in English EXPECTED RESULT documentation version SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION it works with the proposed pop-up, with a latency time -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476185] New: Editing an email saved as a draft
https://bugs.kde.org/show_bug.cgi?id=476185 Bug ID: 476185 Summary: Editing an email saved as a draft Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- Bonjour, First of all, saving an email as a draft must not close the compose window : saving an email as a draft does not mean that the composition of the email is finished ! And, after having saved an email as a draft, when using the menu "Modify as new", the logo image used as a signature is lost ! Pierre STEPS TO REPRODUCE: see above EXPECTED RESULT - The compose window must not be closed when saving as a draft. - When editing again a draft, it must be presented as it was previously composed with the signature. Linux/KDE Plasma: Mageia 9 / Plasma KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476050] Sender of a new email
https://bugs.kde.org/show_bug.cgi?id=476050 --- Comment #1 from Pierre THOMAS --- And it is risky: a sent email to an association (3 association) may be sent by the default account which my private account and which is not the account I must use for this association !! I consider this as a severe bug ! Pierre -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 461233] Default time unit for suspending
https://bugs.kde.org/show_bug.cgi?id=461233 --- Comment #2 from Pierre THOMAS --- Bonjour, What does that mean ? The regression in KOrganizer will not be corrected ? Pierre -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476050] Sender of a new email
https://bugs.kde.org/show_bug.cgi?id=476050 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476049] Allow the distant content in an email
https://bugs.kde.org/show_bug.cgi?id=476049 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 461233] Default time unit for suspending
https://bugs.kde.org/show_bug.cgi?id=461233 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476075] Sending a link to a web page from Firefox
https://bugs.kde.org/show_bug.cgi?id=476075 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476075] New: Sending a link to a web page from Firefox
https://bugs.kde.org/show_bug.cgi?id=476075 Bug ID: 476075 Summary: Sending a link to a web page from Firefox Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- I use Mageia Linux. I defined KMail as the default mail client. When clicking on the button "Envoyer par e-mail un lien vers la page" (Send by email a link to the page), this opens a compose windows of KMail, it is OK. But the sending account is not the account of the default identity : it must be the account of the default identity ! Or what else ??!! What is the account chosen by KMail ? (if there is a choice ??) Pierre -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476050] New: Sender of a new email
https://bugs.kde.org/show_bug.cgi?id=476050 Bug ID: 476050 Summary: Sender of a new email Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- When creating a new email to send, the sender of this new email must be the account / identity corresponding to the folder selected (main folder, subfolders: Received, Sent, Draft). If the main folder is selected : OK If a subfolder is selected : the account by default is the sender !!! This is not correct Pierre -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476049] New: Allow the distant content in an email
https://bugs.kde.org/show_bug.cgi?id=476049 Bug ID: 476049 Summary: Allow the distant content in an email Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- After having tested the possibilities, I guess there is a bug somewhere … For one email, by a right click on the sender address : ◦ I marked both cases Afficher le format HTML (Display HTML format), ◦ In the contact details, I marked the case Autoriser les contenus distants dans les messages HTML reçus (Allow distant contents in received HTML emails). But when the same email or another email of the same sender is selected and displayed, the warning is displayed again (Ce message HTML peut contenir des références externes à des images ...) !!! This is very annoying. Allowing the distant content in an email must be possible with 2 mouse clicks once for all. Pierre -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 475916] Line spacing in quoted text
https://bugs.kde.org/show_bug.cgi?id=475916 Pierre THOMAS changed: What|Removed |Added CC||pitho...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 475916] New: Line spacing in quoted text
https://bugs.kde.org/show_bug.cgi?id=475916 Bug ID: 475916 Summary: Line spacing in quoted text Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- When answering to an email, even this received email is displayed correctly, the text of the original email quoted is displayed with very very large spacing between the lines : this is a bug which must be corrected ! I can’t send such emails. Pierre STEPS TO REPRODUCE 1. Click on Answer button 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475529] New: Possible database corruption by running rescans in parallel
https://bugs.kde.org/show_bug.cgi?id=475529 Bug ID: 475529 Summary: Possible database corruption by running rescans in parallel Classification: Applications Product: kphotoalbum Version: 5.11.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Backend Assignee: kpab...@willden.org Reporter: pe-...@concept-micro.com Target Milestone: --- SUMMARY Starting a rescan while another rescan is in progress can lead to duplicate entries being added to the database. Upon database reload, KPhotoAlbum may detect the inconsistency and exit. STEPS TO REPRODUCE 1. Create new image(s) 2. Start a disk rescan 3. Start a disk rescan again while previous one is still in progress OBSERVED RESULT Duplicate images in the database. If database is saved, upon reloading KPhotoAlbum may detect the issue and exit: ~ ᐅ kphotoalbum kphotoalbum.DB: Merging duplicate entry for file "jean-pierre/Post mortem/Inventaire/I10/I10,1/200105 b.tif" ~ ᐅ EXPECTED RESULT Either queue the rescan, or inform the user that a rescan is ongoing and ask whether it should be cancelled and rescan started over. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.3 (only using KDE libs) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I'm scanning a NAS shared folder, so rescanning can take a few minutes and there's no visual clue that a rescan is still in progress. So it genuinely happened a few times. I've seen reloading fix the duplicates once, maybe image checksums helped? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475339] Sort folders by "natural order"
https://bugs.kde.org/show_bug.cgi?id=475339 --- Comment #3 from Pierre Etchemaïté --- Works great, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475339] New: Sort folders by "natural order"
https://bugs.kde.org/show_bug.cgi?id=475339 Bug ID: 475339 Summary: Sort folders by "natural order" Classification: Applications Product: kphotoalbum Version: 5.11.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: pe-...@concept-micro.com Target Milestone: --- Created attachment 162151 --> https://bugs.kde.org/attachment.cgi?id=162151=edit Folders in lexicographic order Since I'm doing an inventory I have lots of numbered subfolders, and they're not sorted in the most convenient way; One issue is that they're sorted lexicographically instead of using "natural" order. STEPS TO REPRODUCE 1. Create subfolders folder-1, folder-2, folder-15. Add images in each 2. Index the whole 3. Browse the indexed result by "Directories" OBSERVED RESULT Folders in folder-1, folder-15, folder-2 order EXPECTED RESULT Folders in folder-1, folder-2, folder-15 order SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.3 LTS (not using the KDE desktop, only libs) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION kPhotoAlbum v5.11.0-67-g35164270 compiled from sources -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station.
https://bugs.kde.org/show_bug.cgi?id=471198 --- Comment #6 from Pierre Racz --- Hello, I sent another crash report, but I could not find the button to get more symbols. Could you point me to some info on how to get the symbols ? Thanks Pierre From: David Hurka Sent: Thursday, June 22, 2023 06:30 PM To: Pierre Racz Subject: [okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station. https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D471198=05%7C01%7Cpracz%40genetec.com%7C51b4195934544bf9d33308db737056b8%7C7ba8d2fb46604a19802e4d015a17e167%7C0%7C0%7C638230698583324266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=UyWxF1DfSSSg00Q2lrZKyDLr%2Bhx4rGlOlOyGA2Dx%2Bjc%3D=0<https://bugs.kde.org/show_bug.cgi?id=471198> --- Comment #3 from David Hurka --- (In reply to Pierre Racz from comment #2) > > 1. Are you able to install debugging symbols, so we get a more detailed > > backtrace? > > Yes, tell me where to get the symbols, as I have not complied KDE myself. You reported this with DrKonqi. That dialog should have a button to install debug symbols, it usually works fine, and otherwise describes what exactly is necessary. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station.
https://bugs.kde.org/show_bug.cgi?id=471198 Pierre Racz changed: What|Removed |Added CC||pr...@genetec.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station.
https://bugs.kde.org/show_bug.cgi?id=471198 --- Comment #4 from Pierre Racz --- OK -Original Message- From: David Hurka Sent: Thursday, June 22, 2023 18:31 To: Pierre Racz Subject: [okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station. https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.o rg%2Fshow_bug.cgi%3Fid%3D471198=05%7C01%7Cpracz%40genetec.com%7C51b4195 934544bf9d33308db737056b8%7C7ba8d2fb46604a19802e4d015a17e167%7C0%7C0%7C63823 0698583324266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=UyWxF1DfSSSg00Q2lrZKyDLr% 2Bhx4rGlOlOyGA2Dx%2Bjc%3D=0 --- Comment #3 from David Hurka --- (In reply to Pierre Racz from comment #2) > > 1. Are you able to install debugging symbols, so we get a more detailed > > backtrace? > > Yes, tell me where to get the symbols, as I have not complied KDE myself. You reported this with DrKonqi. That dialog should have a button to install debug symbols, it usually works fine, and otherwise describes what exactly is necessary. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station.
https://bugs.kde.org/show_bug.cgi?id=471198 --- Comment #2 from Pierre Racz --- Hello Dave, > 3. I notice the backtrace contains a call to drawImage(), which happens for > text annotations. Does the crash happen only when a document or page with > annotations is displayed? The PDF in question was GoLang_UGN-FE-39.pdf (which is used to be free) : * [Ultimate Go Notebook | Ardan Labs](https://www.ardanlabs.com/ultimate-go-notebook/) That PDF does not have annotations. > 2. Do you have a hiDPI screen, i. e. an other screen scale than 100%? This is the Description of the Physical Setup: * "Dell Thunderbolt Docking Station (WD22TB4)" is plugged into the USB-C port of my laptop (HP_Spectre_x360_Convertible_13-aw2xxx), * Dell Keyboard * Dell Mouse The two external HDMI display are : * [32" Dell S3220DGF - Specifications](https://www.displayspecifications.com/en/model/21491b82) - Resolution on the External Monitor: 2560x1440 60hz - Resolution on the Internal Monitor: 2560x1440 60hz - Scaling on both external monitors is 1.5 > 1. Are you able to install debugging symbols, so we get a more detailed > backtrace? Yes, tell me where to get the symbols, as I have not complied KDE myself. Pierre -Original Message- From: David Hurka Sent: Wednesday, June 21, 2023 01:11 To: Pierre Racz Subject: [okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station. https://bugs.kde.org/show_bug.cgi?id=471198 David Hurka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Hurka --- Thanks for reporting. 1. Are you able to install debugging symbols, so we get a more detailed backtrace? 2. Do you have a hiDPI screen, i. e. an other screen scale than 100%? 3. I notice the backtrace contains a call to drawImage(), which happens for text annotations. Does the crash happen only when a document or page with annotations is displayed? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471198] New: Ocular crashes when unplugging UCB-C multi-monitor docking station.
https://bugs.kde.org/show_bug.cgi?id=471198 Bug ID: 471198 Summary: Ocular crashes when unplugging UCB-C multi-monitor docking station. Classification: Applications Product: okular Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: pr...@genetec.com Target Milestone: --- Application: okular (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-20-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: While reading a document that is displayed on a external monitor, the USB-C cable is unplugged. The open applications attempt to redisplay themselves on the laptop's screen. Ocular is unsuccessful and crashes. The crash can be reproduced sometimes. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7efc207b53e5 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7efc2060279a in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x7efc20604390 in QRasterPaintEngine::drawImage(QPointF const&, QImage const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7efc084c06e5 in PagePainter::paintCroppedPageOnPainter(QPainter*, Okular::Page const*, Okular::DocumentObserver*, int, int, int, QRect, Okular::NormalizedRect const&, Okular::NormalizedPoint*) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #8 0x7efc085510c1 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #9 0x7efc08547315 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #10 0x7efc20baec28 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7efc20c5b792 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7efc1febaba3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7efc20b6bf82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7efc1febae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7efc20ba6e59 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7efc20ba7751 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7efc20ba8a66 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7efc20ba88c9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7efc20ba73cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7efc20ba8a66 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7efc20ba88c9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7efc20ba73cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7efc20ba8a66 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7efc20ba88c9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7efc20ba88c9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7efc20ba73cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7efc20ba8a66 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&,
[systemsettings] [Bug 470627] New: Crash Upon Changing Page in SystemSettings if AMD Drivers Installed
https://bugs.kde.org/show_bug.cgi?id=470627 Bug ID: 470627 Summary: Crash Upon Changing Page in SystemSettings if AMD Drivers Installed Classification: Applications Product: systemsettings Version: 5.24.6 Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: hicksc...@gmail.com Target Milestone: --- Good afternoon, I've tried using Neon but unfortunately the AMD proprietary drivers won't compile. So I've switched to Kubuntu LTS (Kernel is `5.19.0-43-generic`, distro itself is `Ubuntu 22.04.2 LTS`). I have a bunch of computers, and SystemSettings works great on all except one, and after I install AMD proprietary GPU drivers. The rest seems to work OK. Interestingly, uninstalling the AMD drivers immediatelly fixes the issue without a reboot - so this might be useful. When using `amdgpu-uninstall` the packages that are removed are: ``` The following packages will be REMOVED amdgpu* amdgpu-core* amdgpu-dkms* amdgpu-dkms-firmware* amdgpu-lib* amdgpu-lib32* amdgpu-pro* amdgpu-pro-core* amdgpu-pro-lib32* amdgpu-pro-oglp* amdgpu-pro-oglp:i386* clinfo-amdgpu-pro* gst-omx-amdgpu* libdrm-amdgpu-amdgpu1* libdrm-amdgpu-amdgpu1:i386* libdrm-amdgpu-common* libdrm-amdgpu-radeon1* libdrm-amdgpu-radeon1:i386* libdrm2-amdgpu* libdrm2-amdgpu:i386* libegl1-amdgpu-mesa* libegl1-amdgpu-mesa:i386* libegl1-amdgpu-mesa-drivers* libegl1-amdgpu-mesa-drivers:i386* libegl1-amdgpu-pro-oglp* libegl1-amdgpu-pro-oglp:i386* libgbm1-amdgpu* libgbm1-amdgpu:i386* libgl1-amdgpu-mesa-dri* libgl1-amdgpu-mesa-dri:i386* libgl1-amdgpu-mesa-glx* libgl1-amdgpu-mesa-glx:i386* libgl1-amdgpu-pro-oglp-dri* libgl1-amdgpu-pro-oglp-dri:i386* libgl1-amdgpu-pro-oglp-ext* libgl1-amdgpu-pro-oglp-gbm* libgl1-amdgpu-pro-oglp-glx* libgl1-amdgpu-pro-oglp-glx:i386* libglapi-amdgpu-mesa* libglapi-amdgpu-mesa:i386* libgles1-amdgpu-pro-oglp* libgles1-amdgpu-pro-oglp:i386* libgles2-amdgpu-pro-oglp* libgles2-amdgpu-pro-oglp:i386* libllvm15.0.50405-amdgpu* libllvm15.0.50405-amdgpu:i386* libxatracker2-amdgpu* libxatracker2-amdgpu:i386* mesa-amdgpu-omx-drivers* mesa-amdgpu-va-drivers* mesa-amdgpu-va-drivers:i386* mesa-amdgpu-vdpau-drivers* mesa-amdgpu-vdpau-drivers:i386* ocl-icd-libopencl1-amdgpu-pro* opencl-legacy-amdgpu-pro-icd* vulkan-amdgpu* xserver-xorg-amdgpu-video-amdgpu* ``` And of course DKMS kicks in and removes all the `ko` modules. But as soon as the drivers are re-installed (Using `amdgpu-install --usecase=workstation -y --vulkan=amdvlk --opencl=legacy`), SystemSettings crashes as soon as I change page in it. The interesting part is that if I open SystemSettings using `krunner` on a specific page, that page loads fine. But as soon as I change page within SystemSettings, it crashes immediately and with close to no information (Nothing in `syslog`). If I run `systemsettings` directly from my terminal, this is what the output looks like at the time of the crash: ``` systemsettings file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ ]' to bind to all of them. QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ ]' to bind to all of them. QQmlEngine::setContextForObject():
[kwalletmanager] [Bug 469221] KWallet under Wayland crashes when pressing any key
https://bugs.kde.org/show_bug.cgi?id=469221 Pierre changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Pierre --- I do not face this bug anymore. Happy to close it, but I still wonder what caused it, because if it is not known it could regress again! -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 469221] KWallet under Wayland crashes when pressing any key
https://bugs.kde.org/show_bug.cgi?id=469221 --- Comment #2 from Pierre --- (In reply to Nicolas Fella from comment #1) > Can you please attach a backtrace of the crash using the coredumpctl > command-line program I run `coredumpctl --reverse` but there is no entry for the time of the crash. In System Monitor, I can see `kwalletd5` and `kwalletmanager5` before the crash, then after the crash only `kwalletd5`. I have not much space left on my storage, so it seems that install debuginfo is not an option for me. Is there another way I can get you the info? Can you reproduce this bug on your side? -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 469221] New: KWallet under Wayland crashes when pressing any key
https://bugs.kde.org/show_bug.cgi?id=469221 Bug ID: 469221 Summary: KWallet under Wayland crashes when pressing any key Classification: Applications Product: kwalletmanager Version: 23.04.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: d...@wismill.eu Target Milestone: --- SUMMARY *** Under Wayland, when opening KWallet manager for the first time in the session, pressing any modifier key crashes it. After relaunching it it does work. *** STEPS TO REPRODUCE 1. Have KWallet entry in the system tray. 2. Start a Plasma Wayland session. 3. Use the KWallet entry in the system tray to open KWallet manager. 4. Optionally select an item. Then press any key. OBSERVED RESULT KWallet crashes, entry in system tray is not available anymore. When relaunching KWallet (I use KRunner), the system tray entry gets enabled and the issue not reproducible anymore until a new Plasma session. EXPECTED RESULT KWallet processes the key as usual. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230427 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx Memory: 6.7 Gio of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFORMATION I use 2 screens, each one with its task bar. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Pierre Racz changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #8 from Pierre Racz --- Bug is resolved in plasmashell 5.27.3 Qt: 5.15.6 KDE Frameworks: 5.104.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #7 from Pierre Racz --- On 3/5/23 11:31, Pierre wrote: Ref: https://bugs.kde.org/show_bug.cgi?id=466730 Hello Nate, I was able to reproduced the KDE Plasma crash in the version 5.27.2 as you requested. It is a very deterministic bug and easy to reproduce: set the scaling to 150%, connect a USB-C monitor and try to reopen "System Settings". -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 467903] Datebar sometimes grays out non-empty units
https://bugs.kde.org/show_bug.cgi?id=467903 Pierre Etchemaïté changed: What|Removed |Added CC||pe-...@concept-micro.com --- Comment #1 from Pierre Etchemaïté --- Created attachment 157681 --> https://bugs.kde.org/attachment.cgi?id=157681=edit unit <= minUnit Thanks for creating the bug report! Oldest picture in the selection is dated 08:39 something, but 08:00-09:59 unit is grayed when it shouldn't -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467551] New: changing speed only affects the video & audio clips, not the titles, which incorrectly stay at their place in the timeline
https://bugs.kde.org/show_bug.cgi?id=467551 Bug ID: 467551 Summary: changing speed only affects the video & audio clips, not the titles, which incorrectly stay at their place in the timeline Classification: Applications Product: kdenlive Version: 22.12.2 Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: bugskde-...@fasterix.frmug.org Target Milestone: --- Created attachment 157407 --> https://bugs.kde.org/attachment.cgi?id=157407=edit Timeline screenshot: original grouped clip (left), duplicated grouped clip with speed changed to 25 % (right) SUMMARY Changing the speed of a clip only works on the video and audio, not the title(s), causing titles to stay at their original place. STEPS TO REPRODUCE 1. add a video + audio clip in the timeline 2. add title(s) clip(s) on a video track above 3. group everything 4. select everything 5. right click on one of the pieces and select "change speed" 6. set speed to 25% OBSERVED RESULT Only the right-clicked clip has its speed changed, all of the rest stays in place, which means the titles are not at the right place anymore. EXPECTED RESULT Titles follow the speed change, staying at their correct relative position. SOFTWARE/OS VERSIONS FreeBSD 13.1 KDE 5.101.1 Qt Version 5.15.7 Kdenlive 22.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Pierre Racz changed: What|Removed |Added Version|5.25.5 |5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #6 from Pierre Racz --- Created attachment 156941 --> https://bugs.kde.org/attachment.cgi?id=156941=edit New crash information added by DrKonqi systemsettings (5.27.2) using Qt 5.15.6 Here is the report of the problem using KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- Backtrace (Reduced): #4 0x7fe0d2b976b9 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #6 0x7fe0d2d057d1 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fe0d2baeb1f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fe0d2b6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fe0d1cbae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #5 from Pierre Racz --- Created attachment 156940 --> https://bugs.kde.org/attachment.cgi?id=156940=edit New crash information added by DrKonqi systemsettings (5.27.2) using Qt 5.15.6 Here is the problem reproduced with KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- Backtrace (Reduced): #4 0x7f3cc01976b9 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #6 0x7f3cc03057d1 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f3cc01aeb1f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f3cc016bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f3cbf4bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Pierre Racz changed: What|Removed |Added CC||pr...@genetec.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #4 from Pierre Racz --- Created attachment 156939 --> https://bugs.kde.org/attachment.cgi?id=156939=edit New crash information added by DrKonqi systemsettings (5.27.2) using Qt 5.15.6 Here is the crash report updated for KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- Backtrace (Reduced): #4 0x7f71933976b9 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #6 0x7f71935057d1 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f71933aeb1f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f719336bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f71924bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Pierre Racz changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- Ever confirmed|0 |1 --- Comment #3 from Pierre Racz --- I can reproduce it with KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #1 from Pierre Racz --- Problems goes away when Global Scale set to 100%. Problem is present when Global Scale is 150%. This set in: System Settings > Hardware / Display and Monitor > Display Configuration > Global Scale [ Slider and input field ] Save display properties : "For any display arrangement" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] New: System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Bug ID: 466730 Summary: System Setting Crash when Multi-Monitor Docking Station plugged in. Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pr...@genetec.com Target Milestone: --- Application: systemsettings (5.25.5) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-35-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: When a "Dell Thunderbolt Docking Station (WD22TB4)" is plugged into the USB-C port of my laptop (HP_Spectre_x360_Convertible_13-aw2xxx), the system's setting application crashes. Actually other system applications, such as the "info center" also crash repeatably. The Docking Station is plugged into an ATEN-CS17916 KVM Switch. The USB Peripherals are * Dell Keyboard * Dell Mouse The HDMI display is an "ASUS VP28U" Resolution on the External Monitor: 2560x1440 60hz Resolution on the Internal Monitor: 2560x1440 60hz Scaling on both monitors is 1.5 The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f18365976b9 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f1836700c35 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f18367057d1 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f18365aeb1f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f183656bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f18358bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f183659fef2 in QWidgetPrivate::updateFont(QFont const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f18365af09e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f183656bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f18358bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f18365c7ce6 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f18365c7d16 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f18365c7de6 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f18358f372c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f1835d45b03 in QWindow::screenChanged(QScreen*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7f1835d46373 in QWindowPrivate::emitScreenChangedRecursion(QScreen*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #20 0x7f18365a10c5 in QWidgetPrivate::create() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f18365a141f in QWidget::create(unsigned long long, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f18367031b3 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f1836703589 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f18366c4fd2 in QMainWindow::menuBar() const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f1836fdfd9a in KXmlGuiWindow::createGUI(QString const&) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #26 0x7f1836fe071b in KXmlGuiWindow::setupGUI(QSize const&, QFlags, QString const&) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #27 0x7f1836fe0863 in KXmlGuiWindow::setupGUI(QFlags, QString const&) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #28 0x55e73c05f23f in ?? () #29 0x55e73c05aff1 in ?? () #30 0x7f1834e23510 in __libc_start_call_main (main=main@entry=0x55e73c05a610, argc=argc@entry=1, argv=argv@entry=0x7ffea6270c08) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f1834e235c9 in __libc_start_main_impl (main=0x55e73c05a610, argc=1, argv=0x7ffea6270c08, init=, fini=, rtld_fini=, stack_end=0x7ffea6270bf8) at ../csu/libc-start.c:381 #32 0x55e73c05b9f5 in ?? () [Inferior 1 (process 6849) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464344] New: "Replica of" not linked to actual configuration
https://bugs.kde.org/show_bug.cgi?id=464344 Bug ID: 464344 Summary: "Replica of" not linked to actual configuration Classification: Applications Product: systemsettings Version: 5.20.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: pie...@nothos.net CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Plug second screen, make it not a replica of primary screen 2. Run qonk game, switch to full screen, then back to windowed 3. Go to system settings > Display and monitors OBSERVED RESULT The second screen is now a replica of the primary, but in the second screen's config, "Replica of" is set to "None". Setting it to primary screen then back to "None" doesn't change what's on the second screen. EXPECTED RESULT "Replica of" should be the primary screen. Setting it to "None" stops mirroring. The following command stops the mirroring: $ xrandr --output $SECOND --auto --right-of $PRIMARY SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462226] No Tool Bar in Presentation Tool in action
https://bugs.kde.org/show_bug.cgi?id=462226 --- Comment #3 from Jean-Pierre Boucher --- Hello Gilles & Maik, I finally found the reason for the non-display of the toolbar in the presentation tool, in fact I use two screens and if digiKam is on screen 2 it does not work, and if digiKam is on screen 1 it works ! Wonderful isn't it ! (But why ?), Good day to you Jean Pierre PS: For camera import it doesn't work on Linux Mint either. Le ven. 25 nov. 2022 à 08:35, Maik Qualmann a écrit : > https://bugs.kde.org/show_bug.cgi?id=462226 > > Maik Qualmann changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > > --- Comment #2 from Maik Qualmann --- > Same here, tested on Windows 10, overlay toolbars appear at the top of the > screen. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462230] New: Wording error tooltips (french version) in the left sidebar map tool first icon to search by area
https://bugs.kde.org/show_bug.cgi?id=462230 Bug ID: 462230 Summary: Wording error tooltips (french version) in the left sidebar map tool first icon to search by area Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Engine Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** Wording error tooltips (french version) in the left sidebar map tool, first icon to search by area, tooltip says "Supprimez des images en traçant un rectangle" which should be "sélectionnez des images en traçant un rectangle" , it's a lit bit different (Delete instead Select ...) ... Thanks Jean-Pierre *** STEPS TO REPRODUCE 1. Map (left sidebar) see Tooltip for the first icon to search by area 2. 3. OBSERVED RESULT "Supprimez des images en traçant un rectangle" EXPECTED RESULT "sélectionnez des images en traçant un rectangle" SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462227] New: Wrong title in automatic color correction tool
https://bugs.kde.org/show_bug.cgi?id=462227 Bug ID: 462227 Summary: Wrong title in automatic color correction tool Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Editor-AutoColors Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** in the image editor ( French version) , menu "Couleur" the name of the tool "Colorer la correction automatique..." besides that it does not mean much should be "Correction automatique des couleurs...", it is not no big deal ! :-) It's also for my french translation of the digiKam user manual Thanks Jean-Pierre *** STEPS TO REPRODUCE In Image editor (french version) 1. Couleur --> Colorer la correction automatique... 2. 3. OBSERVED RESULT Colorer la correction automatique... :-( EXPECTED RESULT Correction automatique des couleurs... :-) SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462226] New: No Tool Bar in Presentation Tool in action
https://bugs.kde.org/show_bug.cgi?id=462226 Bug ID: 462226 Summary: No Tool Bar in Presentation Tool in action Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-Presentation Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** In the Presentation tool (very nice), the toolbar described in §6.2 of the digiKam Manual does not appear (I tried in the four corners of the screen but nothing), whereas it appears well in the slide show (Menu View --> Slide show) *** STEPS TO REPRODUCE 1. View --> Presentation 2. Start the presentation 3. OBSERVED RESULT No Tool Bar :-( EXPECTED RESULT Tool Bar :-) SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462225] New: Import Cameras impossible on Windows
https://bugs.kde.org/show_bug.cgi?id=462225 Bug ID: 462225 Summary: Import Cameras impossible on Windows Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Import-Gphoto2 Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** As I have been translating the digiKam User Manual into French for more than a month, I would really like to make the tool for importing images from cameras work, so that I can take screenshots in the current version. (7.8.0) and try the features described. It does not work on Windows 10 or Linux Mint, and it's unfortunate because the Manual presents the import of a camera as an advantage of digiKam, should I remove the chapters concerning the import of camera ? (No I don't) ,and it's the same with the scanner. I know perfectly well that you can use other means to import photographs (from cameras and from the scanner) into the digiKam, but I thought it was nice to be able to do it as it was described in the Manual. Many thanks if you can find a Solution even a workaround. Sincerely Jean-Pierre I have already reported this bug, i know perfectly that it is not obvious but i hope *** STEPS TO REPRODUCE 1. Import Camera (I tried many times and in every way) 2. 3. OBSERVED RESULT Failed to connect the camera make sure it is connected properly and turned on EXPECTED RESULT that the tool operates as described in the manual and also for my french translation ;-) ! SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461871] New: importing images does not work on images but on folders
https://bugs.kde.org/show_bug.cgi?id=461871 Bug ID: 461871 Summary: importing images does not work on images but on folders Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Import-Albums Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** it seems that importing images does not work on images but on folders? *** STEPS TO REPRODUCE 1. Import --> Add Images (in album vieuws) 2. Try to select an image 3. OBSERVED RESULT Nothing ! While the folder contains a lot off images I tried everywhere and it's the same EXPECTED RESULT To see the Images and to be able to select images SOFTWARE/OS VERSIONS Windows/10 Linux ADDITIONAL INFORMATION The behavior is the same as Import --> Add folder -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461819] New: Synchronized display and Per Pair display of the Light Table editor --> in all editor images tools
https://bugs.kde.org/show_bug.cgi?id=461819 Bug ID: 461819 Summary: Synchronized display and Per Pair display of the Light Table editor -->in all editor images tools Classification: Applications Product: digikam Version: 7.8.0 Platform: unspecified OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: ImageEditor-Plugins Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- This wish for improvement concerns all the tools of the image editor (for displaying comparison views) : It would indeed be very desirable to have the same synchronized display functionalities for the zooms and in pairs in the panoramas for the "before" and "after" views in the same way as those of the light table SOFTWARE/OS VERSIONS digiKam all OS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461248] New: Sort key on Tags
https://bugs.kde.org/show_bug.cgi?id=461248 Bug ID: 461248 Summary: Sort key on Tags Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Tags-Manager Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** Given the performance and the range of possibilities for searching for images on digiKam, it might be useful to be able to sort the result of a search by labels, captions, ratings, dates, etc. I did not find this possibility anywhere... And this possibility would come to perfect this product already very successful in terms of image management It's just a wish *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461236] New: G'MIC buttons are not documented (and Inpainting documentation doesn't correspond at any enhancement tool )
https://bugs.kde.org/show_bug.cgi?id=461236 Bug ID: 461236 Summary: G'MIC buttons are not documented (and Inpainting documentation doesn't correspond at any enhancement tool ) Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Plugin-Editor-GmicQt Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** G'MIC-Qt's buttons are not documented in the manual, and the Inpainting documentation doesn't match any product enhancement tools *** STEPS TO REPRODUCE 1. Try to understand the G'MIC buttons with digiKam Manual 2. Nothing in the Manual 3. But there is a description of an "Inpainting" improvement tool that doesn't exist in the product ??? 4. Fortunately the internal documentation of G'IMC-Qt is clear and complete OBSERVED RESULT There is no documentation on the buttons of the G'MIC-Qt enhancement tool The "Inpainting" documentation doesn't correspond at any enhancement tool EXPECTED RESULT G'MIC-Qt enhancement tool buttons correctly documented SOFTWARE/OS VERSIONS Windows: 10 Family digiKam V4.8.0 ADDITIONAL INFORMATION I am in the process of translating the entire manual into French (with screenshots of the French version of the product), still a short month of work but there are many shortcomings and inconsistencies (problems of updating versions). I am nevertheless delighted with the product despite its shortcomings and its needs for improvement I will continue again and again to annoy you to achieve perfection ;-) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 461233] New: Default time unit for suspending
https://bugs.kde.org/show_bug.cgi?id=461233 Bug ID: 461233 Summary: Default time unit for suspending Classification: Applications Product: korganizer Version: 5.16.0 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- Bonjour, I use KOrganizer as my only calendar. The default time unit for suspending warning is minutes. I wish the default time unit for suspending warnings is a parameter in the preferences of KOrganizer, for being able to set it to hours. My best regards. Pierre -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461231] New: Import Cameras impossible on Windows
https://bugs.kde.org/show_bug.cgi?id=461231 Bug ID: 461231 Summary: Import Cameras impossible on Windows Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: grave Priority: NOR Component: Import-Gphoto2 Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- SUMMARY *** I have a Nikon DSC 7500 and it's impossible to connect this camera by Import → cameras. digiKam 7.8.0 (french version) run on Windows 10. And i have the following Message: "Impossible de se connecter à l'appareil photo. Veuillez vous assurer qu'il est connecté correctement et sous tension." In english : Unable to connect to the camera. Please make sure it is connected correctly and powered on. That I did several times following the requirements and always the same answer ... ??? I am just a basic user ... and the digiKam Manual don't help me *** STEPS TO REPRODUCE 1. Connection of the camera on PC 2. Click on Import → Cameras → Nikon DSC D7500 3. and ... Impssoible to Import OBSERVED RESULT Impossible to connect the camera Message: "Unable to connect to the camera. Please make sure it is connected correctly and powered on." EXPECTED RESULT Simply Connect my camera SOFTWARE/OS VERSIONS Windows: 10 Family ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456492] Copy and paste Motion Tracker keyframes does not work
https://bugs.kde.org/show_bug.cgi?id=456492
Pierre Nerzic changed:
What|Removed |Added
CC||pierre.ner...@free.fr
--- Comment #5 from Pierre Nerzic ---
Hi,
As far as I can see, it seems related to the timestamps of the keyframes. It
looks like the import does not take "in" and "out" fields of the JSON to make
the keyframes relative.
Because: I paste the clipboard into a text editor, then I edit every keyframe
so that the timestamp is relative to 0 instead of "in", then copy it back to
clipboard (^C), then I can import it successfully into the effect.
An example:
1) what I had into the clipboard after "copy keyframes to keyboard" :
>[
>{
>"DisplayName": "Rectangle",
>"in": 420,
>"max": 0,
>"min": 0,
>"name": "results",
>"opacity": false,
>"out": 570,
>"type": 9,
>"value": "420~=1649 179 453 263 0;425~=1619 185 453 263 0;430~=1586
> 190 453 263 0;435~=1563 197 453 263 0;440~=1540 204 453 263 0;445~=1525 213
> 453 263 0;450~=1516 222 453 263 0;455~=1511 225 453 263 0;460~=1504 220 453
> 263 0;465~=1497 215 453 263 0;470~=1492 212 453 263 0;475~=1481 213 453 263
> 0;480~=1462 212 453 263 0;485~=1427 213 453 263 0;490~=1380 206 453 263
> 0;495~=1323 201 453 263 0;500~=1262 196 453 263 0;505~=1195 193 453 263
> 0;510~=1124 180 453 263 0;515~=1055 175 453 263 0;520~=1008 168 453 263
> 0;525~=983 163 453 263 0;530~=964 162 453 263 0;535~=957 155 453 263
> 0;540~=972 138 453 263 0;545~=1009 125 453 263 0;550~=1058 110 453 263
> 0;555~=1115 97 453 263 0;560~=1182 102 453 263 0;565~=1259 121 453 263
> 0;570~=1336 144 453 263 0"
>}
>]
2) what I changed manually (in, out and all the timestamps subtracted from in):
>[
>{
>"DisplayName": "Rectangle",
>"in": 0,
>"max": 0,
>"min": 0,
>"name": "results",
>"opacity": false,
>"out": 150,
>"type": 9,
>"value": "0~=1649 179 453 263 0;5~=1619 185 453 263 0;10~=1586 190 453
> 263 0;15~=1563 197 453 263 0;20~=1540 204 453 263 0;25~=1525 213 453 263
> 0;30~=1516 222 453 263 0;35~=1511 225 453 263 0;40~=1504 220 453 263
> 0;45~=1497 215 453 263 0;50~=1492 212 453 263 0;55~=1481 213 453 263
> 0;60~=1462 212 453 263 0;65~=1427 213 453 263 0;70~=1380 206 453 263
> 0;75~=1323 201 453 263 0;80~=1262 196 453 263 0;85~=1195 193 453 263
> 0;90~=1124 180 453 263 0;95~=1055 175 453 263 0;100~=1008 168 453 263
> 0;105~=983 163 453 263 0;110~=964 162 453 263 0;115~=957 155 453 263
> 0;120~=972 138 453 263 0;125~=1009 125 453 263 0;130~=1058 110 453 263
> 0;135~=1115 97 453 263 0;140~=1182 102 453 263 0;145~=1259 121 453 263
> 0;150~=1336 144 453 263 0"
>}
>]
The latter can be imported without any trouble as keyframes into a transform
effect.
I hope it will not be hard to repair :-)
My best regards,
Pierre
--
You are receiving this mail because:
You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Pierre Choffet changed: What|Removed |Added CC||ct@peuc.net -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Pierre Choffet changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #8 from Pierre Choffet --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456001] Frequent okular crashes
https://bugs.kde.org/show_bug.cgi?id=456001 --- Comment #2 from Pierre David --- It means that on an idle machine, okular crashes sometimes. I am sorry to have no more information, nor any way to reproduce this inconsistent behaviour. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456001] New: Frequent okular crashes
https://bugs.kde.org/show_bug.cgi?id=456001
Bug ID: 456001
Summary: Frequent okular crashes
Product: okular
Version: 21.12.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: pda...@gmail.com
Target Milestone: ---
Application: okular (21.12.3)
Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-40-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
PDF file was rebuilt by pdflatex
But okular regularly crashes, even if I don't do anything
- Since okular was started from zsh inside konsole, using "(okular file.pdf &)"
, I see the following error message on konsole:
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
Opening in existing browser session.
kf.i18n.kuit: "Tag 'p' is not defined in message
{<__kuit_internal_top__>The bug report's title is often written by its
r...}."
kf.i18n.kuit: "Tag 'p' is not defined in message
{<__kuit_internal_top__>The bug report's title is often written by its
r...}."
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Okular (okular), signal: Aborted
[KCrash Handler]
#4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140562186930624)
at ./nptl/pthread_kill.c:44
#5 __pthread_kill_internal (signo=6, threadid=140562186930624) at
./nptl/pthread_kill.c:78
#6 __GI___pthread_kill (threadid=140562186930624, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#7 0x7fd7333bb476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8 0x7fd7333a17f3 in __GI_abort () at ./stdlib/abort.c:79
#9 0x7fd715549e08 in OutlineItem::open() () from
/lib/x86_64-linux-gnu/libpoppler.so.118
#10 0x7fd715549e4d in OutlineItem::hasKids() () from
/lib/x86_64-linux-gnu/libpoppler.so.118
#11 0x7fd72412287b in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so
#12 0x7fd72410c022 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so
#13 0x7fd72c7a0603 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#14 0x7fd72c5bad4a in Okular::Document::openDocument(QString const&, QUrl
const&, QMimeType const&, QString const&) () from
/lib/x86_64-linux-gnu/libOkular5Core.so.9
#15 0x7fd72c6fd5a5 in Okular::Part::doOpenFile(QMimeType const&, QString
const&, bool*) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#16 0x7fd72c6ff84b in Okular::Part::openFile() () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#17 0x7fd7351dd325 in ?? () from /lib/x86_64-linux-gnu/libKF5Parts.so.5
#18 0x7fd7351e1ba7 in KParts::ReadOnlyPart::openUrl(QUrl const&) () from
/lib/x86_64-linux-gnu/libKF5Parts.so.5
#19 0x7fd72c6fec42 in Okular::Part::slotAttemptReload(bool, QUrl const&) ()
from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#20 0x7fd72c708b25 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#21 0x7fd733abe783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fd733ac27ee in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fd733ab432f in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fd73460a713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7fd733a86e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7fd733adf3db in QTimerInfoList::activateTimers() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7fd733adfcdc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7fd732117d1b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fd73216c6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7fd7321153c3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7fd733ae00a8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7fd733a8574b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x7fd733a8dce4 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x555a8a700c5a in ?? ()
#35 0x7fd7333a2d90 in __libc_start_call_main
(main=main@entry=0x555a8a6ff700, argc=argc@entry=2,
argv=argv@entry=0x7fff00835c98) at ../sysdeps/nptl/libc_start_call_main.h:58
#36 0x7fd7333a2e40 in __libc_start_main_impl
[krita] [Bug 453884] Krita 5.0.6 crashes during saving
https://bugs.kde.org/show_bug.cgi?id=453884 --- Comment #3 from Pierre "bloodywing" Geier --- (In reply to Halla Rempt from comment #1) > I suspect that this is an arch deps build problem. Probably the kde plasma > qt platform plugin broke. You can either disable native file dialogs in > Krita's settings, fix your arch installation or use the appimage. Appimage works for me, that is my workaround at the moment native file dialog works, until i want to actually open a file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453884] Krita 5.0.6 crashes during saving
https://bugs.kde.org/show_bug.cgi?id=453884 --- Comment #2 from Pierre "bloodywing" Geier --- Created attachment 148887 --> https://bugs.kde.org/attachment.cgi?id=148887=edit New crash information added by DrKonqi krita (5.0.6) using Qt 5.15.3 - What I was doing when the application crashed: I started krita, klicked open file I tried it only with hotkeys, same happend File selection dialogs, for example resource manager makes krita crash as well -- Backtrace (Reduced): #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x2) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/bits/atomic_base.h:481 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #6 0x7fba3fab6eea in QBasicAtomicInteger::loadRelaxed (this=0x2) at /usr/include/qt5/QtCore/qbasicatomic.h:107 [...] #8 0x7fba3facbc6d in QList::~QList (this=0x562b9418e130, __in_chrg=) at /usr/include/qt5/QtCore/qlist.h:873 #9 0x7fba3fb72072 in KToolBar::Private::~Private (this=0x562b9418e080, __in_chrg=) at /home/pierre/kritatest/krita-5.0.6/libs/widgetutils/xmlgui/ktoolbar.cpp:83 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453884] Krita 5.0.6 crashes during saving
https://bugs.kde.org/show_bug.cgi?id=453884 Pierre "bloodywing" Geier changed: What|Removed |Added CC||bloodyw...@tastyespresso.de -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451648] Markdown: do not remove two trailing spaces aka line break when "remove trailing spaces" is set
https://bugs.kde.org/show_bug.cgi?id=451648 Pierre Fernagu--Berthier changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from Pierre Fernagu--Berthier --- I have check and I have found the solution. In Settings->Configure Kate, than Open/Save->General and change 'Remove trailing spaces' to never. None the less, thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451648] Markdown: do not remove two trailing spaces aka line break when "remove trailing spaces" is set
https://bugs.kde.org/show_bug.cgi?id=451648 --- Comment #3 from Pierre Fernagu--Berthier --- (In reply to Eric Armbruster from comment #2) > Can you still reproduce this in 22.04? I think this has been fixed for > Markdown files. Yes, I can still reproduce it in 22.04. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453319] New: When saving a Markdown file, all double spaces are removed which is problematic because it is needed to format the layout of the document.
https://bugs.kde.org/show_bug.cgi?id=453319 Bug ID: 453319 Summary: When saving a Markdown file, all double spaces are removed which is problematic because it is needed to format the layout of the document. Product: kate Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: pierr...@outlook.fr Target Milestone: --- SUMMARY *** When saving a Markdown file, all double spaces are removed which is problematic because it is needed to format the layout of the document. *** STEPS TO REPRODUCE 1. Create or open a Mardown file 2. Add a double scace at the end of a line 3. Save the file OBSERVED RESULT The double space is removed. EXPECTED RESULT Living the double space as it was written. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 35 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 452458] Broken URLs generated for non-ascii character filenames
https://bugs.kde.org/show_bug.cgi?id=452458 --- Comment #4 from Pierre Etchemaïté --- Problem fixed indeed, thanks for this quick reply! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 452458] Broken URLs generated for non-ascii character filenames
https://bugs.kde.org/show_bug.cgi?id=452458 --- Comment #1 from Pierre Etchemaïté --- Extra information: filesystem: ext4 locale: $ locale LANG=fr_FR.UTF-8 LANGUAGE= LC_CTYPE="fr_FR.UTF-8" LC_NUMERIC="fr_FR.UTF-8" LC_TIME="fr_FR.UTF-8" LC_COLLATE="fr_FR.UTF-8" LC_MONETARY="fr_FR.UTF-8" LC_MESSAGES="fr_FR.UTF-8" LC_PAPER="fr_FR.UTF-8" LC_NAME="fr_FR.UTF-8" LC_ADDRESS="fr_FR.UTF-8" LC_TELEPHONE="fr_FR.UTF-8" LC_MEASUREMENT="fr_FR.UTF-8" LC_IDENTIFICATION="fr_FR.UTF-8" LC_ALL= -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 452458] New: Broken URLs generated for non-ascii character filenames
https://bugs.kde.org/show_bug.cgi?id=452458 Bug ID: 452458 Summary: Broken URLs generated for non-ascii character filenames Product: kphotoalbum Version: GIT master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: HTML generator Assignee: kpab...@willden.org Reporter: pe-...@concept-micro.com Target Milestone: --- SUMMARY Filenames containing accented characters are latin1(?) percent encoded in URLs (eg é -> ) in the generated index.html, leading to broken links both locally and when browsed thru an Apache server STEPS TO REPRODUCE 1. Create an image with extended ascii characters in name (é, è, ê,...), $ ls *Carré\).* '200416 a (Carré).jpg' $ ls *Carré\).*|od -c 000 2 0 0 4 1 6 a ( C a r r 303 251 020 ) . j p g \n 026 2. Generate an HTML page containing that image 3. (publish result on a web server) 4. Browse the page (tested with Konqueror, Firefox, Chromium) OBSERVED RESULT Thumbnail for the image is okay, but mouse-over preview and full image are broken links EXPECTED RESULT All images to appear in generated page SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.10 with KDE libs KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 452025] New: Crash when drag'n'dropping folders to dolphin sidebar
https://bugs.kde.org/show_bug.cgi?id=452025
Bug ID: 452025
Summary: Crash when drag'n'dropping folders to dolphin sidebar
Product: kio-extras
Version: 22.03.80
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: SFTP
Assignee: plasma-b...@kde.org
Reporter: pina...@pinaraf.info
Target Milestone: ---
SUMMARY
When dropping a sftp folder in dolphin sidebar, I get the following crash:
```
Application: kioslave5 (kioslave5), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#6 0x7f693a6bec4a in sftp_close () from /usr/lib/libssh.so.4
#7 0x7f693fa422bf in SFTPInternal::close (this=0x55a5de333920) at
/usr/src/debug/kio-extras-22.03.80/sftp/kio_sftp.cpp:1198
#8 SFTPInternal::mimetype (url=..., this=0x55a5de333920) at
/usr/src/debug/kio-extras-22.03.80/sftp/kio_sftp.cpp:1868
#9 SFTPSlave::mimetype (this=0x7ffca8f9aa10, url=...) at
/usr/src/debug/kio-extras-22.03.80/sftp/kio_sftp.cpp:2328
#10 0x7f693f92a89f in KIO::SlaveBase::dispatch (this=0x7ffca8f9aa10,
command=70, data=...) at /usr/src/debug/kio-5.92.0/src/core/slavebase.cpp:1264
#11 0x7f693f923126 in KIO::SlaveBase::dispatchLoop (this=0x7ffca8f9aa10) at
/usr/src/debug/kio-5.92.0/src/core/slavebase.cpp:330
#12 0x7f693fa426e0 in kdemain (argc=, argv=)
at /usr/src/debug/kio-extras-22.03.80/sftp/kio_sftp.cpp:92
#13 0x55a5dd9d720a in main (argc=5, argv=0x7ffca8f9ac88) at
/usr/src/debug/kio-5.92.0/src/kioslave/kioslave.cpp:146
[Inferior 1 (process 1143393) detached]
```
STEPS TO REPRODUCE
1. Open a sftp folder
2. Drag a folder to dolphin's sidebar
OBSERVED RESULT
Crash of kio
EXPECTED RESULT
No crash
SOFTWARE/OS VERSIONS
Linux: 5.16.13
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3 + KDE patches
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[i18n] [Bug 447627] New: Translation error "un fonds d'écran"
https://bugs.kde.org/show_bug.cgi?id=447627 Bug ID: 447627 Summary: Translation error "un fonds d'écran" Product: i18n Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: fr Assignee: kde-francoph...@kde.org Reporter: jp-...@inbox.ru Target Milestone: --- On plasma desktop 5.23.4, a translation mistake is shown in the desktop right-click menu. The text should say "un fond d'écran" (-s) in the singular form. A quick checkout of i18n messages from svn indicates this occurrence is not unique. plasma-desktop/plasma_applet_org.kde.desktopcontainment.po ``` 397:msgstr "Configurer un bureau et un fonds d'écran…" ``` plasma-workspace/plasma_wallpaper_org.kde.image.po ``` 285-msgstr "" 286-"Le fichier demandé pour servir comme fonds d'écran n'existe pas ou ne peut " 287:"être considéré comme compatible pour un fonds d'écran : %1" ``` websites-kde-org/frameworks_announcements.po ``` 9914:msgstr "Ajout d'un « kapptemplate » pour le fonds d'écran de Plasma" ``` websites-kde-org/www_www.po ``` 33446:#~ msgstr "Ajout d'un « kapptemplate » pour le fonds d'écran de Plasma" ``` -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446382] New: feature request with contributed code: import .kino files
https://bugs.kde.org/show_bug.cgi?id=446382 Bug ID: 446382 Summary: feature request with contributed code: import .kino files Product: kdenlive Version: unspecified Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: bugskde-...@fasterix.frmug.org Target Milestone: --- Created attachment 144150 --> https://bugs.kde.org/attachment.cgi?id=144150=edit Python script SUMMARY You might be interested by this Python script I wrote to convert old .kino projects. I published it on Github: https://github.com/pbeyssac/kino-kdenlive -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442631] motion tracker: re-analysis after reset does nothing
https://bugs.kde.org/show_bug.cgi?id=442631 --- Comment #3 from Pierre Nerzic --- Hi Julius, I tested with the nightly build and I can confirm, the bug has been solved. It now works very well. We can close and forget this ticket. I saw many improvements in this build. It gives me a lot of ideas: zoom into the area enclosed by the tracking, and more generally link to an effect whose area is delimited by the tracking. I also found a discussion, https://invent.kde.org/multimedia/kdenlive/-/issues/1155 reporting exactly the same problem. I am sorry, I was not aware of this website, the bug report form always forwards to bugs.kde.org, where, I was sure, there was no report about my problem. If I knew about invent*org, I would not send such a duplicate report :-) Have a very nice day! Pierre -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442631] motion tracker: re-analysis after reset does nothing
https://bugs.kde.org/show_bug.cgi?id=442631 --- Comment #1 from Pierre Nerzic --- After some experiments, I must add some informations to my report. First, it does not happen with every footage. I am not sure, but it may be related to the duration of the sequence. With a less than 7 seconds clip, the problem does not happen, but appears with a 10 seconds clip: only the first run of the Motion Tracker effect is successful, and after a Reset, next analysis do nothing and terminate much quicker. I would like to get some detailed log inside Kdenlive, to be more helpful. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442631] New: motion tracker: re-analysis after reset does nothing
https://bugs.kde.org/show_bug.cgi?id=442631 Bug ID: 442631 Summary: motion tracker: re-analysis after reset does nothing Product: kdenlive Version: 21.08.1 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: pierre.ner...@free.fr Target Milestone: --- SUMMARY In Motion Tracker effect, only the first analysis works: the progress bar fills, then the "tracking data" button and link appear. But after that, when I want to change a parameter (algo, spacing) and redo another analysis, almost nothing happens: I can see the bar filling much quicker, but the "tracking data" button does not re-appear. STEPS TO REPRODUCE 1. Add a Motion Tracker effect to a video clip 2. Click Analyze 3. Click Reset 4. Click Analyze again OBSERVED RESULT The Tracking data button and link do not appear. They show only the first time, before reset. EXPECTED RESULT I should be able to do any number of analysis, with different parameters (tracker algorithm and keyframe spacing). SOFTWARE/OS VERSIONS Windows: not tested, but I will macOS: cannot test Linux/KDE Plasma: debian stable (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION As a work-around, I just have to restart Kdenlive to be able to do another analysis. I tried to remove the Motion Tracker effect, then to add it again but it does not seem to always solve the problem. I suspect some cache to remain, blocking next analysis. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379874] Crash opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379874 Pierre Ducroquet changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #8 from Pierre Ducroquet --- Hi Isaac Thank you for your answer. Considering this, it is going to be quite complicated for us to do anything on this matter, and I will thus close this bug report. Regards -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot
https://bugs.kde.org/show_bug.cgi?id=402154 --- Comment #14 from Pierre Baldensperger --- (In reply to tagwerk19 from comment #12) > > Try a simple test... > > (...) > > Interesting to know if the device number has changed, and whether the > balooshow details have also changed... Thank you very much for the helpful hints in diagnosing this. You are spot on !! Indeed the device number changes after every reboot. $ diff stat1.log stat2.log < Périphérique : 35h/53d Inœud : 24588954Liens : 1 --- > Périphérique : 37h/55d Inœud : 24588954Liens : 1 And there is also a corresponding change in balooshow. $ diff baloo1.log baloo2.log < 177329a0035 53 24588954 testfile.txt [/home/test/testfile.txt] --- > 177329a0037 55 24588954 testfile.txt [/home/test/testfile.txt] A baloosearch returns the same file twice. And I do indeed have a bunch of subvols. Now hopefully somebody who knows the internals of baloo deduplication criteria might be able to understand where this behaviour is coming from, and confirm that this is likely a BTRFS-specific problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot
https://bugs.kde.org/show_bug.cgi?id=402154 Pierre Baldensperger changed: What|Removed |Added CC||baloo-bugs-n...@kde.org Version|5.75.0 |5.81.0 Component|general |Baloo File Daemon --- Comment #11 from Pierre Baldensperger --- Still same behaviour with frameworks 5.81.0 (OpenSuSE Leap 15.2, BTRFS file system). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428755] wrong color for combo boxes titles and items in Composition/Effect window for Fusion style and Breeze light themes
https://bugs.kde.org/show_bug.cgi?id=428755 --- Comment #2 from Pierre Nerzic --- Hi Julius, Unfortunately no, the latest version 20.12.3a does not solve this issue. The combos are still very dark gray on black, and when clicking on the title, it shows a very light list, very light gray on white... weird. The dark Color Themes are ok with Fusion, but both light color themes are bad. It may be caused by my system only, Xfce, or perhaps a bug in KDE? I don't know how to get the relevant information. Have a nice day! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428789] panel splitting problem in the "Title Clip" window
https://bugs.kde.org/show_bug.cgi?id=428789 --- Comment #2 from Pierre Nerzic --- Hi, Actually, this bug did not show as hard in the 20.12.2 appimage. Maybe it depends on the width of the video and the width of the title window? I can see two "anchor points" of the separator, about 25% to the right when the parameters are hidden, and one to the left when the video is hidden. It looks like when the window is too narrow, those anchors are not behaving well, and the parameter panel and video appears or disappears weirdly. Ok to close the bug for now, but maybe it would be better to remove the anchor points. Have a nice day and stay safe -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428794] fatal error on pixelize effect when the block size becomes negative due to smooth interpolation
https://bugs.kde.org/show_bug.cgi?id=428794 --- Comment #4 from Pierre Nerzic --- Thanks a lot. I agree, this is related to MLT. Have a nice day! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 434161] New: kmail does not properly quote From field when replying
https://bugs.kde.org/show_bug.cgi?id=434161 Bug ID: 434161 Summary: kmail does not properly quote From field when replying Product: kmail2 Version: 5.15.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: jplej...@quoininc.com Target Milestone: --- This is the existing Bug 343812 which was closed since it was not demonstrated on KDE Frameworks (5.x). I've since been able to confirm that it continues to exist on Debian Bullseye (current Debian testing) which has version 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
