[digikam] [Bug 485981] "Open in File Manager" causes 100% CPU usage in process: kde-open5 file://
https://bugs.kde.org/show_bug.cgi?id=485981 Hauke changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #2 from Hauke --- I can confirm the bug under Arch Linux with kioclient 6.0.4 (output of "kde-open --version"). When executing xdg-open like "xdg-open /path/to/file.txt", the kde-open5 command is called with a "file://path/to/file.txt" parameter and directly fails (as far as I can see with exit code 1 but without logging to stdout/stderr). When using xdg-open, this process is endlessly recreated causing a high CPU load. My expected behavior is that kde-open/kde-open5 is able to deal with "file://..." parameters. Relevant environment variables on my machine might be XDG_CURRENT_DESKTOP=KDE and KDE_SESSION_VERSION=5. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] "setFcc: collection invalid" after answering an e-mail
https://bugs.kde.org/show_bug.cgi?id=449898 --- Comment #5 from Hauke --- Fixed for me with KMail 21.12.2-2 (more details here: https://bugs.kde.org/show_bug.cgi?id=449872#c11). -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 449872] Kontact crashed while trying to reply to email
https://bugs.kde.org/show_bug.cgi?id=449872 Hauke changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #10 from Hauke --- This is probably the same bug as #449898 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449952] KMail crashes in qgpgme when entering text in To: field
https://bugs.kde.org/show_bug.cgi?id=449952 Hauke changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #2 from Hauke --- Can confirm: 1. Create a new mail with an attached GPG key 2. Enter anything in the "To" field When starting from the terminal, the log output of KMail looks pretty much the same as describes in #449898 comment 2 (https://bugs.kde.org/show_bug.cgi?id=449898#c2) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449927] kmail crashes on startup after crashing when switching folders
https://bugs.kde.org/show_bug.cgi?id=449927 Hauke changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #1 from Hauke --- Can confirm: When I open an encrypted message, KMail crashes. It look like this is related to #449898 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] "setFcc: collection invalid" after clicking on mail address in e-mail message body
https://bugs.kde.org/show_bug.cgi?id=449898 Hauke changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #2 from Hauke --- Can confirm this bug (also using Arch with KMail 5.19.2). But for me answering any mails (not only mail with an mail-adress in the message body) causes this crash. Removing all files in ~./local/share/kmail2/autosave/ solved the startup issue and KMail starts normally. Answering a mail results in a crash again. After the crash this autosave folder contains one file with the following (anonymized) content: To: ??? ??? Date: ??? Message-ID: <1962715.oMNUckLgyt@???> X-KMail-Identity: 1229347080 X-KMail-Transport: 435071032 X-KMail-Fcc: -7 X-KMail-Link-Message: 120072 X-KMail-Link-Type: reply X-KMail-Identity-Name: ???@??? X-KMail-Transport-Name: ??? In-Reply-To: References: <973d58b5-9acb-5694-14de-2???@???.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" The log output in the moment of the crash is the following: *** KMail got signal 11 (Exiting) *** Dead letters dumped. /tmp/messageviewer_oqpWBI.index.2 was not removed . /tmp/messageviewer_oqpWBI.index.2 was removed . KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = /usr/bin pid = 7740 KCrash: Arguments: /usr/bin/kmail [warn] epoll_wait: Ungültiger Dateideskriptor [warn] epoll_wait: Ungültiger Dateideskriptor [warn] epoll_wait: Ungültiger Dateideskriptor [warn] epoll_wait: Ungültiger Dateideskriptor .. This epoll_wait warning is printed a thousand times. The string "Ungültiger Dateideskriptor" is German for "Bad file descriptor". -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444781] MIPS: wrong syscall numbers used
https://bugs.kde.org/show_bug.cgi?id=444781 Hauke Mehrtens changed: What|Removed |Added CC||k...@hauke-m.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444781] New: MIPS: wrong syscall numbers used
https://bugs.kde.org/show_bug.cgi?id=444781 Bug ID: 444781 Summary: MIPS: wrong syscall numbers used Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: k...@hauke-m.de Target Milestone: --- Created attachment 143104 --> https://bugs.kde.org/attachment.cgi?id=143104=edit [PATCH] mips: Fix new syscall numbers MIPS uses special syscall numbers on Linux, we can not use the vki/vki-scnums-32bit-linux.h and vki/vki-scnums-shared-linux.h files on MIPS. With valgrind 3.18.1 on MIPS 32 BE I am getting this error message with dropbear and musl 1.2.2 ``` root@OpenWrt:/# valgrind ssh 192.168.10.3 ==1910== Memcheck, a memory error detector ==1910== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1910== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==1910== Command: ssh 192.168.10.3 ==1910== ==1910== Conditional jump or move depends on uninitialised value(s) ==1910==at 0x407E198: ??? (in /lib/libc.so) ==1910==by 0x4091BCC: ??? (in /lib/libc.so) ==1910== ==1910== Conditional jump or move depends on uninitialised value(s) ==1910==at 0x407D77C: ??? (in /lib/libc.so) ==1910==by 0x407DCA0: ??? (in /lib/libc.so) ==1910== --1910-- WARNING: unhandled mips32-linux syscall: 4403 --1910-- You may be able to write your own handler. --1910-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --1910-- Nevertheless we consider this a bug. Please report --1910-- it at http://valgrind.org/support/bug_reports.html. --1910-- WARNING: unhandled mips32-linux syscall: 4403 --1910-- You may be able to write your own handler. --1910-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --1910-- Nevertheless we consider this a bug. Please report --1910-- it at http://valgrind.org/support/bug_reports.html. ==1910== Conditional jump or move depends on uninitialised value(s) ==1910==at 0x407E198: ??? (in /lib/libc.so) ==1910==by 0x4057F64: ??? (in /lib/libc.so) ==1910== --1910-- WARNING: unhandled mips32-linux syscall: 4403 --1910-- You may be able to write your own handler. --1910-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --1910-- Nevertheless we consider this a bug. Please report --1910-- it at http://valgrind.org/support/bug_reports.html. --1910-- WARNING: unhandled mips32-linux syscall: 4403 --1910-- You may be able to write your own handler. --1910-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --1910-- Nevertheless we consider this a bug. Please report --1910-- it at http://valgrind.org/support/bug_reports.html. --1910-- WARNING: unhandled mips32-linux syscall: 4403 --1910-- You may be able to write your own handler. --1910-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --1910-- Nevertheless we consider this a bug. Please report --1910-- it at http://valgrind.org/support/bug_reports.html. . ``` I expect that it detects the syscall mumber 4403 as the valid syscall clock_gettime64. OpenWrt master with musl 1.2.2 and Linux 5.10 with valgrind 3.18.1 on MIPS BE 32 bit on MIPS malta in qemu. The attached patch fixes the problem. I only really tested the clock_gettime64 syscall on MIPS 32 BE, but not the rest. My test application do not issue these syscalls. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 420185] New: File rename function silenty fails when more than one file is opened
https://bugs.kde.org/show_bug.cgi?id=420185 Bug ID: 420185 Summary: File rename function silenty fails when more than one file is opened Product: gwenview Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: hauke@fam-hell.de Target Milestone: --- SUMMARY When several image files are openend in one window, it is possible to go through them, view one after the other and use the rename function from the file menu. The new name is accepted and Gwenview takes it into the title bar. But the actual file is not renamed. When opening only one file in a Gwenview instance, the file is renamed as expected. STEPS TO REPRODUCE 1. Open 2 or more image files in one Gwenview instance 2. Double-click to view image 3. Click rename from the file menu and enter new file name OBSERVED RESULT The file name in the file system it is not changed EXPECTED RESULT The file name should be like entered in Gwenview 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.
[plasma4] [Bug 282552] plasma desktop crash on add default panel
https://bugs.kde.org/show_bug.cgi?id=282552 Hauke <m...@hauke-stieler.de> changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #115 from Hauke <m...@hauke-stieler.de> --- (In reply to sompom01 from comment #112) > Since this bug is in the top 100 duplicates of all time, I assume you want > it to be reopened, even though everyone else has had no problems for two > years... > I have had a crash that meets the same symptoms just tonight on 4.11.11, > although I don't know enough about the internals of KDE to compare the > backtrace to see if they are actually the same. I will attach the error > report file. > Note that I was not able to reproduce the bug, so it could just be some kind > of exciting and exceedingly rare race condition (I seem to have a lot more > threads going than the majority of other crash reports I looked at :P). > > I believe I can't reopen this bug, so I hope someone will read this who can > and does. I think the bug still exists (s. bug 372881), but it's probably a but in Qt and not in plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 350516] kde4: remove default panel / add default panel
https://bugs.kde.org/show_bug.cgi?id=350516 Hauke <m...@hauke-stieler.de> changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #1 from Hauke <m...@hauke-stieler.de> --- With "no default panel was created..." you mean after you restarted plasma, there was no panel visible? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372881] Plasmashell crashes when adding default panel
https://bugs.kde.org/show_bug.cgi?id=372881 Hauke <m...@hauke-stieler.de> changed: What|Removed |Added CC||m...@hauke-stieler.de --- Comment #8 from Hauke <m...@hauke-stieler.de> --- I can also confirm this bug. Application: plasmashell (5.8.7) Qt Version: 5.6.1 Frameworks Version: 5.35.0 Operating System: Linux 4.8.0-53-generic x86_64 Distribution: Linux Mint 18.2 Sonya -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 158264] Terminal panel (konsole part) blocks the umount of removable media
https://bugs.kde.org/show_bug.cgi?id=158264 Hauke Laging <ha...@laging.de> changed: What|Removed |Added CC||ha...@laging.de --- Comment #30 from Hauke Laging <ha...@laging.de> --- This problem still exists in Dolphin 16.08.2 / KDE 5.27.0 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361115] daylight savings time is handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=361115 --- Comment #4 from Hauke Laging <ha...@laging.de> --- An interesting addition: I cannot set the time back within the next hour. Now it is 12:12. If I need an alarm at 13:30 then I can set it to 12:30 in order to activate at the right time. But if I need an alarm at 12:30 I cannot set it to 11:30. The dialog complains that this time had already passed. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361115] daylight savings time is handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=361115 --- Comment #2 from Hauke Laging <ha...@laging.de> --- (In reply to David Jarvie from comment #1) > Which version of KDE and KAlarm are you using? Version 2.11.4-5ak (I could not select that one in the bug report form). KDE Frameworks 5.20.0 Qt 5.5.1 (kompiliert gegen 5.5.1) Das xcb Fenstersystem > Which time zone is configured as the default for KAlarm? Europe/Berlin > Do you use KAlarm's default time zone for your alarms? To verify this, open > an alarm and if you're using the default, no time zone will be listed beside > the Time Zone button. Nothing is listed there for both existing and new alarms. I have to click on "more options" (in German) in order to see the time zone setting at all. And I don't think I ever clicked that before. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361115] New: daylight savings time is handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=361115 Bug ID: 361115 Summary: daylight savings time is handled incorrectly Product: kalarm Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kalarmd Assignee: djar...@kde.org Reporter: ha...@laging.de My computer was in suspend mode during the daylight saving time switching. The system time was correct afterwards but the configured events have been moved by one hour. The usual time is 20:00, now it is 21:00. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 359267] New: show current clipboard entry in system tray or separate widget
https://bugs.kde.org/show_bug.cgi?id=359267 Bug ID: 359267 Summary: show current clipboard entry in system tray or separate widget Product: klipper Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: plasma-widget Assignee: mgraess...@kde.org Reporter: ha...@laging.de Klipper could be used much faster with shortcuts for moving forward and backward through the history if you could see immediately what the current top entry is. If you do not know that then you are at risk to insert something wrong and that cannot everywhere be removed easily / quickly. There is not much space in the systray but it would usually be enough to show the first three to five characters. Alternatively the history stack actions could create a fly-over help in the systray which shows more characters. A further alternative would be a separate widget which can be configured in width. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 359267] show current clipboard entry in system tray or separate widget
https://bugs.kde.org/show_bug.cgi?id=359267 --- Comment #2 from Hauke Laging <ha...@laging.de> --- (In reply to Martin Gräßlin from comment #1) > The tooltip shows the current selection. That is correct but useless. The new Klipper is really slow. My intention is to accelerate its use. One way to do that is to use the keyboard shortcuts. If I have to use the mouse in order to get the tooltip then there is no point in using the keyboard actions at all (especially during typing). In that case I can simply click the Klipper icon and select the entry with the mouse. -- You are receiving this mail because: You are watching all bug changes.
[kmailcvt] [Bug 358725] TheBat! mail-account does not show in list for import to kmail
https://bugs.kde.org/show_bug.cgi?id=358725 --- Comment #3 from Hauke <hkleybo...@web.de> --- Hello Laurent, I'm sorry, I don't understand fully what you did and what I will have to do. I understand you changed something in the code. Thank you for that first of all. I have kde (inkluding kmail) ver. 4.14.2-0. I don't find any version 5.2. Where do I get it? Or can I just add the line M +0 -2 importwizard/autodetect/thebat/thebatimportdata.cpp somewhere? Thanks Hauke -- You are receiving this mail because: You are watching all bug changes.
[kmailcvt] [Bug 358725] New: TheBat! mail-account does not show in list for import to kmail
https://bugs.kde.org/show_bug.cgi?id=358725 Bug ID: 358725 Summary: TheBat! mail-account does not show in list for import to kmail Product: kmailcvt Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: hkleybo...@web.de The above boxes seem not to be working properly... I newly installed linux mint rosa 17.3 with kde, containing kmail 4.14.2. I used The Bat! on my Win-System (linux-accessible and mounted partition on same laptop). Tried to import Mail, settings, addressbook to kmail: Started the import-assisstant, but nothing showed in the opening window. So I gave Thunderbird a try: Installed it, but could not import data from the TheBat! to TBird either. Now "Thunderbird" shows up in the window when I try to import any settings to kmail. Next step: Installed TheBat with wine. Works fine so far (!) - but I'm not sure how it will work in the future - prefer linux application for mail. Tried to import to kmail: Still nothing. Reproducible: Always Actual Results: I did as written in the helpfiles. Seems so simple. Nothing. Expected Results: The Bat! should show up as a prog in the opening box. Asus f5rl- notebook, 32 bit, dual-core cpu pentium duoT2370 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 356453] New: only valid (signed) openpgp certificates (keys) can be assigned
https://bugs.kde.org/show_bug.cgi?id=356453 Bug ID: 356453 Summary: only valid (signed) openpgp certificates (keys) can be assigned Product: kaddressbook Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ha...@laging.de CC: to...@kde.org OpenPGP certificates have several levels of validity: They can be invalid (expired, revoked, locally disabled), neutral and marginally or fully valid. Certificates become valid by assinging ultimate trust (which should be limited to one's own keys) or by being signed by one ore more keys with trust privilege. It is perfectly OK to use neutral / non-valid certificates. KMail does allow you to do that (with a warning; as it should be). You can assign certificates to a contact (assigning to an email address would make more sense, though). The problem is that the key selection dialog allows you to select valid certificates only which doesn't make sense. If you encrypt to an email address which does not appear in any certificate then the same dialog appears (within KMail, not within KAddressbook) and then it does allow you to select a non-valid certificate... Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
