[kjots] [Bug 481621] New: No option to create a note or a notebook
https://bugs.kde.org/show_bug.cgi?id=481621 Bug ID: 481621 Summary: No option to create a note or a notebook Classification: Applications Product: kjots Version: 5.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: igor.pobo...@gmail.com Reporter: li...@drmartinus.de Target Milestone: --- SUMMARY I want to try out kjots but am unable to do anything. The only option, that is available, is "delete notebook", all other options are grayed out. I noticed that my KJots has version 5.1.1, I installed it using yay from within Manjaro. There it actually says 5.1.1-3 STEPS TO REPRODUCE 1. start kjots 2. click on "file" menu 3. OBSERVED RESULT Only "delete", "print preview" and "end" are enabled, all other options are disabled. I can also not write directly into any field. EXPECTED RESULT I should be able to create a notebook and notes in order to write down ideas etc. within the notebook SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 461861] Search via Internet doesn't work properly - dialog defective
https://bugs.kde.org/show_bug.cgi?id=461861 Martin Senftleben changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 461861] Search via Internet doesn't work properly - dialog defective
https://bugs.kde.org/show_bug.cgi?id=461861 --- Comment #4 from Martin Senftleben --- I fiddled around a little. First to your question, which I obviously missed: I call Tellico from the desktop via an icon. The call goes like: tellico -qwindowtitle %c %u The arguments weren't added by me, and removing them doesn't change anything. I now noticed that when I change the datasource, which was set to "search all" (alles durchsuchen), to something else, the combo box for what to search for gets filled. So it seems only to be related to this setting "search all". -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 461861] Search via Internet doesn't work properly - dialog defective
https://bugs.kde.org/show_bug.cgi?id=461861 --- Comment #3 from Martin Senftleben --- Created attachment 155212 --> https://bugs.kde.org/attachment.cgi?id=155212=edit Second Snapshot -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 461861] Search via Internet doesn't work properly - dialog defective
https://bugs.kde.org/show_bug.cgi?id=461861 --- Comment #2 from Martin Senftleben --- Created attachment 155211 --> https://bugs.kde.org/attachment.cgi?id=155211=edit snapshot of search dialog This is how it first appears -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 461861] New: Search via Internet doesn't work properly - dialog defective
https://bugs.kde.org/show_bug.cgi?id=461861 Bug ID: 461861 Summary: Search via Internet doesn't work properly - dialog defective Classification: Applications Product: tellico Version: 3.4.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: li...@drmartinus.de Target Milestone: --- SUMMARY *** After I started tellico in order to add new books, I open the Internet Search. Previously, I could select by a combo-box wether to search for ISBN, title or other things. Now, this combo box is empty. Mostly, after I opened the settings and went to data sources, I can open the Search Internet dialog again and find the combo box filled with the options that should be there already the first time, when I opened it. *** STEPS TO REPRODUCE 1. Start tellico 2. open "Search Internet" 3. check the combo box right of the search field OBSERVED RESULT There are no options in the combo box EXPECTED RESULT there are options available like ISBN, Title, person, keyword or LCCN SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.99.0 (available in About System) KDE Plasma Version: 5.99.0 KDE Frameworks Version: Qt Version: 5.15.6 ADDITIONAL INFORMATION After opening settings - tellico (last option in the settings menu) and going to data sources, maybe also changing the selection in the list to "all sources", and then opening the Internet Search again, the options are there in the combo box. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 Martin Senftleben changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #11 from Martin Senftleben --- Sorry again, after writing the previous message I thought I send the entire error message through a search engine, and lo, there were some insights provided by people who suffered the same problem. I had totally forgotten that I named another user for the database. After setting that (command "mariadb-upgrade -u username -p"), the upgrade ran through and now I can start digikam again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 Martin Senftleben changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #10 from Martin Senftleben --- Sorry for not replying earlier. I did try "sudo mariadb-upgrade" and get only the following message: "Version check failed. Got the following error when calling the 'mysql' command line client ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) FATAL ERROR: Upgrade failed" And of course: I entered the password for sudo (correctly). I tried it a hundred times. But I guess the message means that there is a password required by mariadb, but the config says no password, and maybe even root is not the user with which the upgrade should be run? I'm confused... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 Martin Senftleben changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #8 from Martin Senftleben --- OK, you lost me. I followed those duplicate bug links to some level (each one ended somewhere with "this is a duplicate bug of..."), and I am only little wiser than before. I did the obvious and tried to downgrade mariadb, but there are dependencies which don't allow me to downgrade. If I remove the entire package with its dependencies, I can only install the actual package, which I can't downgrade, because those dependencies are required by so many packages, that I would render my PC almost useless, if I uninstall all those packages (which I would have to do to get rid of those dependencies). So I rather do not use digikam any more - at least until this problem is solved. :-( -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #4 from Martin Senftleben --- If it's Mariadb, it has the version 10.6.4-1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #3 from Martin Senftleben --- Thank you, Mike, that was a helpful hint. Here is the output: "digikam.widgets: Use installed icons digikam.general: Switch to widget style: "breeze" digikam.general: AlbumWatch is disabled digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name:"digikam" DB Face Name: "digikam" DB Similarity Name:"" Connect Options: "" Host Name: "localhost" Host port: Internal Server: false Internal Server Path: "" Internal Server Admin Cmd: "mysqladmin" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "drmartin" Password: "XXX" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 12 digikam.coredb: Core database: makeUpdates 12 to 13 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Die Abfrage konnte nicht ausgeführt werden" "Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50537, now running 100604. Please use mariadb-upgrade to fix this error" "1558" 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ] Statement [ "\nDROP PROCEDURE IF EXISTS create_index_if_not_exists;\n" ] digikam.coredb: Core database: schema update to V 13 failed! digikam.coredb: Core database: cannot process schema initialization" I hope this answers Gilles questions as well. It seems it's using MariaDB? As mentioned above, I do not know what digikam is doing in the background, I was always content with what it does, until this bug occured. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] New: digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 Bug ID: 79 Summary: digikam doesn't start, instead "cannot process schema initialization" Product: digikam Version: 7.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Database-Schema Assignee: digikam-bugs-n...@kde.org Reporter: li...@drmartinus.de Target Milestone: --- When starting digikam, it stops and opens a window saying (in German) that upgrading the database schema hadn't been successful and that I should start it from the konsole and send the error message which is shown there. When I start it from the CLI, I get the following message (nothing more, only this one line): "digikam.coredb: Core database: cannot process schema initialization" STEPS TO REPRODUCE 1. start digikam 2. 3. OBSERVED RESULT See summary above EXPECTED RESULT digikam working SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Manjaro shows me the version number 7.3.0-5 for digikam. I am totally lost here. Digikam doesn't give any useful information except the above, and I have no clue where to look for the database (I'm sorry, but digikam worked for me most of the time during the last 20 or so years, and I don't remember what settings there are, so questions like "what database" I simply can't answer unless I am told where to look for this info). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 Martin Senftleben changed: What|Removed |Added CC||li...@drmartinus.de --- Comment #14 from Martin Senftleben --- Just to let you know: I have the same problem, with the only difference that none of the offered solutions have worked for me. Whenever I try to update mariadb, I get the message: "Version check failed. Got the following error when calling the 'mysql' command line client ERROR 2002 (HY000): Can't connect to local server through socket '$HOME/.local/share/digikam/db_misc/mysql.socket' (2)" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354742] Digikam shouldn't change to an album when right clicking on it
https://bugs.kde.org/show_bug.cgi?id=354742 Martin Senftleben changed: What|Removed |Added Version|4.14.0 |6.4.0 --- Comment #3 from Martin Senftleben --- I'm now at version 6.4.0 and it still behaves as described. I'm waiting for my distro to provide version 7. I've changed the version above. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 420220] New: bigger zip archives (>~3.2 GB) can't be opened
https://bugs.kde.org/show_bug.cgi?id=420220 Bug ID: 420220 Summary: bigger zip archives (>~3.2 GB) can't be opened Product: ark Version: 19.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: li...@drmartinus.de CC: rthoms...@gmail.com Target Milestone: --- g to open a zip archive which was created by another program and is bigger than ~2 GB will result in an error message saying that the file is not a zip file. STEPS TO REPRODUCE 1. select a zip archive larger than ~3.2 GB 2. Open it with Ark OBSERVED RESULT as said above, Ark claims that the file is not a zip file. Since other, smaller zip files created by the same program can be opened by Ark without any problems, I guess this is a problem with Ark. EXPECTED RESULT The zip file should be opened and contents should be able to be extracted with Ark. SOFTWARE/OS VERSIONS Linux/KDE Plasma: s. above (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I am not sure where the exact threshold is. A zip archive of 4.2 GB size generates this error message, a zip archive of 3.1 GB size can be opened. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 417740] Abruf der Kontoauszüge von ING-Konto funktioniert nicht
https://bugs.kde.org/show_bug.cgi?id=417740 --- Comment #2 from Martin Senftleben --- Sorry for not writing in English. I should have thought of that. To your questions: aqbanking: 6.0.2-1 gwenhywfar: 5.1.2-1 Settings for AqBanking: Benutzername: mein Name Server-URL: https://fints.ing-diba.de/fints/ HBCI-Version: 3.0 HTTP-Version: 1.1 Ausgewählte TAN-Methode: 900 (es gibt nichts anderes zur Auswahl) Override TAN-Input Mechanism: Auto TAN-Medienkennung: (leer) Nicht BASE64 kodieren: 0 SMS-Konto überspringen: 0 I just tried to retrieve the iTAN-Modi and got this error: HBCI: 9800 - Der Dialog wurde abgebrochen. (M) HBCI: 9391 - Unbekannte Kundensystem-ID, bitte synchronisieren Sie neu. (M) Dialog wurde von der Bank abgebrochen. PIN scheint ungültig zu sein Dialog aborted by server I'm sure I'm doing something wrong, but these things are not so well known to me. Thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 417740] New: Abruf der Kontoauszüge von ING-Konto funktioniert nicht
https://bugs.kde.org/show_bug.cgi?id=417740 Bug ID: 417740 Summary: Abruf der Kontoauszüge von ING-Konto funktioniert nicht Product: kmymoney Version: 5.0.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: li...@drmartinus.de Target Milestone: --- Ich wollte nach langer Zeit dank eines Artikels in Linux User mal wieder KMyMoney ausprobieren, da ich dachte, es könne mir helfen, von moneyplex loszukommen. Leider kriege ich aber die Kontoauzszüge nicht runtergeladen. Ich wähle "Konto/Konto aktualisieren" und werde zur Eingabe der PIN aufgefordert, was ich dann auch tue. Im Ergebnis kommt Folgendes: HBCI: 9800 - Der Dialog wurde abgebrochen. (M) HBCI: 9400 - Der anonyme Dialog wird nicht unterstützt. (M) Dialog aborted by server Ich weiß leider nicht, was das bedeutet, und wäre für Hilfe dankbar. STEPS TO REPRODUCE 1. Wähle Konto/Konto aktualisieren 2. Gib nach Aufforderung die PIN ein 3. OBSERVED RESULT Der Vorgang bricht mit obiger Fehlermeldung ohne Ergebnis ab. EXPECTED RESULT Kontoauszüge werden abgeholt und offline zur Verfügung gestellt. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 5.4.18-1-MANJARO x86_64 KDE Plasma Version: KDE Plasma 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412899] export tool to flickr doesn't submit privacy settings
https://bugs.kde.org/show_bug.cgi?id=412899 --- Comment #4 from Martin Senftleben --- Just an addition, maybe it is really my fault: I use the "organize your fotos" option i flickr to check the access rights. This I do by moving the images from the bottom where all images are shown and drag them into the area "arrange your fotos" or similar. Then I check "Rights" and see that the images which I moved into that area have the right "visible to everybody". Consequently I set the rights to "family only". When I do the same procedure later with the same fotos, the images have the "family only" access right. Did you follow the same procedure? If not, could you check this? Maybe it's a bug within flickr? Then I would report to them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412899] export tool to flickr doesn't submit privacy settings
https://bugs.kde.org/show_bug.cgi?id=412899 --- Comment #3 from Martin Senftleben --- Is there a way to figure out what could be the reason? I do not know where the target server is set, but it would be strange, I think, if flickr uses different ways of accepting fotos just because there is a different server involved. I have this problem for a long time (years) and only now thought it might be good to open a bug report (I'd always hoped for a silent fix). But if it's only me who has the problem, I need to get to the bottom of it and some guidance on how to do that. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412899] New: export tool to flickr doesn't submit privacy settings
https://bugs.kde.org/show_bug.cgi?id=412899 Bug ID: 412899 Summary: export tool to flickr doesn't submit privacy settings Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: li...@drmartinus.de Target Milestone: --- SUMMARY Before uploading images to flickr, I set the tool to restrict views to family members. When I open the uploaded images and check the access rights, the images are visible to everybody and not just family members. So I have always to change access rights for those uploaded images after uploading them, which is not only awkward. Some images may be sensitive, and being public for even a second may become harmful to the persons depicted on the images. STEPS TO REPRODUCE 1. select images for exporting to flickr and select the export to flickr tool 2. change visibility setting to "visible to family only" (or similar, I use a different language than English) 3. upload the images 4. check in flickr the access rights to the images OBSERVED RESULT images are visible to everybody on flickr EXPECTED RESULT images are visible to only familiy members on flickr SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (up to date) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383987] Flickr tool no longer authenticates to Flickr
https://bugs.kde.org/show_bug.cgi?id=383987 --- Comment #5 from Martin Senftleben --- Alright, I have a similar bug just reported, and now see that it seems to be different. I am using version 5.9 of kipi-plugins and version 6.0.0 of digikam, so according to this bug report the problem should be fixed, but it isn't or rather it has reappeared. In my case the export/export to flickr tool doesn't open a browser (which it never did!), and it doesn't request authentication at all. It just doesn't connect to flickr at all, it seems. So either this one has to be set to REOPENED, or I have to reopen the other bug report again...??? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406616] flickr upload doesn't find my account and doesn't allow to add an account
https://bugs.kde.org/show_bug.cgi?id=406616 --- Comment #3 from Martin Senftleben --- Thank you for the quick reply, and sorry for the duplicate. I didn't find the other bug 383987 when searching for anything similar. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406616] New: flickr upload doesn't find my account and doesn't allow to add an account
https://bugs.kde.org/show_bug.cgi?id=406616 Bug ID: 406616 Summary: flickr upload doesn't find my account and doesn't allow to add an account Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: li...@drmartinus.de Target Milestone: --- When I try to upload some images to flickr, the dialog opens and then shows a blank "account" field (with a blue background). When I click on "add another account" (or similar, i use the German version and need to translate from there), the window opens where I should be able to add another flickr account, but in fact I can't. The cursor is indicating that it's waiting for something to happen. I can't write anything anywhere. STEPS TO REPRODUCE 1. select some fotos 2. click on export/export to flickr 3. try to add a flickr account OBSERVED RESULT I can't enter anything, the existing account which was working in previous version doesn't show. EXPECTED RESULT actually it should show the account that I have entered already in former versions of digikam (I use it since version 2 or so), at least it should allow me to add the account credentials once again. But it doesn't. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.15.3 (I believe) KDE Frameworks Version: 5.56.0-1 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 390449] New: KDE crashes when pressing the K button
https://bugs.kde.org/show_bug.cgi?id=390449 Bug ID: 390449 Summary: KDE crashes when pressing the K button Product: kde Version: 4.14.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: li...@drmartinus.de Target Milestone: --- I had this occuring several times, also in previous upgrades, for about a month or so, and sometimes (after a system upgrade) it was ok again, but now it's back: When I hit the K-button (application menu) in the control panel, KDE crashes completely, i.e. I see a black screen, the control panel disappears, and after a short while everything returns. Once it didn't even return, so I could only switch to console mode and shutdown there in order to get back a working system. This isn't good for unsaved work, and I'm worried. It happened now several times. Right now it's every time I hit the K-Button. Wanted shutdowns are only possible via Ctrl-Alt-Del, which is ok, I guess. Regards -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 372581] New: font too big for numbers in printed forms
https://bugs.kde.org/show_bug.cgi?id=372581 Bug ID: 372581 Summary: font too big for numbers in printed forms Product: okular Version: 0.26.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: li...@drmartinus.de Target Milestone: --- I have often to do with pdf forms, and want to use okular to fill them in and then print them. However, numbers, while appearing just like other letters on the screen, are printed way too big on the printout. It seems as if they are automatically scaled to the field size, which is nonsense in my view. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 Martin Senftleben <li...@drmartinus.de> changed: What|Removed |Added CC||li...@drmartinus.de --- Comment #45 from Martin Senftleben <li...@drmartinus.de> --- I'm not sure if it's wise to add to this thread, but the topic is the same: for three days now baloo_file_extractor is, according to my ksysguard, the top RAM and particularly swap memory eater. The most peculiar, but maybe normal thing is, that it doesn't eat up all RAM (I have 16 GB installed, but bsysguard shows only 9 GB being used), but feeds on swap memory. The swap file is now at its limit (6.3/6.3 GB) and the machine is slowing down. I tried various commands mentioned here, all failed on my machine or produce no usable output: "ps aux | grep baloo_file_extractor" produces: "username 3076 43.5 49.3 272558692 8087596 ? DNl Okt24 3018:54 /usr/bin/baloo_file_extractor username 3575 0.0 0.0 10776 2016 pts/1S+ 12:03 0:00 grep --color=tty -d skip baloo_file_extractor" and "sudo echo 3 > /proc/sys/vm/drop_caches" (in the hope that this might clear up space) produces: "Keine Berechtigung" (= no permission) Other things I didn't try. I run Manjaro Arch-Linux up-to-date, 64 bit. -- You are receiving this mail because: You are watching all bug changes.
