[frameworks-bluez-qt] [Bug 483944] Mx master's scroll wheel slows down after a while since upgrading to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483944 Christoph Vogtländer changed: What|Removed |Added CC||k...@mockies.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482911] kernel: traps: kwin_wayland trap divide error ip:7483ca3c9321 sp:7ffdb043b9c0 error:0 in i965_dri.so
https://bugs.kde.org/show_bug.cgi?id=482911 --- Comment #5 from Christoph Vogtländer --- Switching to "mesa" (instead of "mesa-amber") and using iris instead of i965 actually works. My previous attempts to switch, already some while ago, had not been successful. I now realized that I also had to remove the old xf86-video-intel package in order for SDDM to start up properly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482911] New: kernel: traps: kwin_wayland trap divide error ip:7483ca3c9321 sp:7ffdb043b9c0 error:0 in i965_dri.so
https://bugs.kde.org/show_bug.cgi?id=482911 Bug ID: 482911 Summary: kernel: traps: kwin_wayland trap divide error ip:7483ca3c9321 sp:7ffdb043b9c0 error:0 in i965_dri.so Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@mockies.de Target Milestone: --- Created attachment 166730 --> https://bugs.kde.org/attachment.cgi?id=166730=edit Journal log with stack trace SUMMARY *** After upgrading to Plasma 6, the plasma wayland session does not start anymore. Using X11 works as expected. Previously, I was using Plasma 5 wayland without problems. *** STEPS TO REPRODUCE 1. start Plasma 6 wayland session from SDDM OBSERVED RESULT blinking cursor, after a while SDDM is shown again EXPECTED RESULT Plasma 6 should start SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 ADDITIONAL INFORMATION I'm running on a fairly old system with a VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) which requires "mesa-amber". See also attached journal with stack trace. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468992] Cannot start akonadi, FATAL ERROR: Upgrade failed
https://bugs.kde.org/show_bug.cgi?id=468992 --- Comment #4 from Christoph Vogtländer --- After a reboot, the error went away for me and akonadi is able to connect to the DB again. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468992] Cannot start akonadi, FATAL ERROR: Upgrade failed
https://bugs.kde.org/show_bug.cgi?id=468992 --- Comment #3 from Christoph Vogtländer --- Created attachment 158559 --> https://bugs.kde.org/attachment.cgi?id=158559=edit akonadictl start --verbose I'm also experiencing this issue on arch after updating from 22.12.3 -> 23.04.0 "~/.local/share/akonadi/db_data/mysql" exists and my user has access rights. Attached output of $ akonadictl start --verbose -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468992] Cannot start akonadi, FATAL ERROR: Upgrade failed
https://bugs.kde.org/show_bug.cgi?id=468992 Christoph Vogtländer changed: What|Removed |Added CC||k...@mockies.de -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 449570] New: Implement "waiting for"
https://bugs.kde.org/show_bug.cgi?id=449570 Bug ID: 449570 Summary: Implement "waiting for" Product: zanshin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: er...@kde.org Reporter: k...@mockies.de CC: mbe...@ipsquad.net Target Milestone: already done SUMMARY *** GTD defines "Waiting For" tasks. It would be nice to have support for this concept in zanshin. Currently I work around by defining "Waiting For" context, but this somewhat contradicts the idea of the state. Optimally, zanshin would allow me to link contacts from my addressbook. Waiting tasks should be highlighted/marked somehow. Additionally I would like to have an option to hide waiting tasks. *** -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 446857] New: Add feature to define work-day hours
https://bugs.kde.org/show_bug.cgi?id=446857 Bug ID: 446857 Summary: Add feature to define work-day hours Product: kalendar Version: 0.3.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: k...@mockies.de CC: c...@carlschwan.eu Target Milestone: --- SUMMARY As a user I want to be able to define my default work day hours (e.g. 7:00 to 18:00). Hours outside this time frame should be visually dimmed in week view. The week view should focus on the defined time frame independent of the current time. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 446856] New: Add Work Week view
https://bugs.kde.org/show_bug.cgi?id=446856 Bug ID: 446856 Summary: Add Work Week view Product: kalendar Version: 0.3.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: k...@mockies.de CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Please add a "Work Week" view, only showing Monday to Friday SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438448] EVERY Login Discover-Notifier tells me to restart
https://bugs.kde.org/show_bug.cgi?id=438448 Christoph Vogtländer changed: What|Removed |Added CC||k...@mockies.de -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 439494] New: Downloading currency using skrooge-yahoodl.py fails with UnicodeDecodeError
https://bugs.kde.org/show_bug.cgi?id=439494
Bug ID: 439494
Summary: Downloading currency using skrooge-yahoodl.py fails
with UnicodeDecodeError
Product: skrooge
Version: 2.25.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: guillaume.deb...@gmail.com
Reporter: k...@mockies.de
CC: steph...@mankowski.fr
Target Milestone: ---
SUMMARY
Downloading currency using skrooge-yahoodl.py fails with UnicodeDecodeError
STEPS TO REPRODUCE
1. Create a currency
2. Set Source to Yahoo, set code to e.g. ^DJI
3. Click "Download"
alternatively run
/usr/share/skrooge/skrooge-yahoodl.py ^DJI 2021-06-29 2021-07-04 1d
directly
OBSERVED RESULT
Traceback (most recent call last):
File "/usr/share/skrooge/skrooge-yahoodl.py", line 127, in
for l in load_yahoo_quote(sys.argv[1], sys.argv[2], sys.argv[3],
sys.argv[4]):
File "/usr/share/skrooge/skrooge-yahoodl.py", line 97, in load_yahoo_quote
_get_cookie_crumb(ticker)
File "/usr/share/skrooge/skrooge-yahoodl.py", line 69, in _get_cookie_crumb
alines = f.read().decode('utf-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid
start byte
EXPECTED RESULT
Date,Open,High,Low,Close,Adj Close,Volume
2021-07-02,34642.421875,34821.929688,34613.488281,34786.351563,34786.351563,30186
2021-07-01,34507.320313,34640.281250,34498.851563,34633.531250,34633.531250,26828
2021-06-30,34290.738281,34553.160156,34245.480469,34502.511719,34502.511719,29556
2021-06-29,34338.890625,34469.828125,34266.828125,34292.289063,34292.289063,28236
2021-06-28,34428.101563,34449.648438,34186.128906,34283.269531,34283.269531,28028
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Kernel Version: 5.12.14-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600
ADDITIONAL INFORMATION
It seems that Yahoo now returns gzipped data.
--
You are receiving this mail because:
You are watching all bug changes.
[skrooge] [Bug 435203] New: Monthly report shows huge percentage for variation
https://bugs.kde.org/show_bug.cgi?id=435203 Bug ID: 435203 Summary: Monthly report shows huge percentage for variation Product: skrooge Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: k...@mockies.de CC: steph...@mankowski.fr Target Milestone: --- Created attachment 137215 --> https://bugs.kde.org/attachment.cgi?id=137215=edit Monthly report screenshot SUMMARY Huge variations are no longer shown as "∞" in the monthly report. The report will get very wide. STEPS TO REPRODUCE 1. add a new account 2. add a operation with e.g. value "8000" with date in previous month 3. create a monthly report OBSERVED RESULT The variation is shown like 0,00 € 8.000,00 € +1.000.000.000.000.000.052.504.760.255.204.420.248.704.468.581.108.159.154.915.854.115.511.802.457.988.908.195.786.371.375.080.447.864.043.704.443.832.883.878.176.942.523.235.360.430.575.644.792.184.786.706.982.848.387.200.926.575.803.737.830.233.794.788.090.059.368.953.234.970.799.945.081.119.038.967.640.880.074.652.742.780.142.494.579.258.788.820.056.842.838.115.669.472.196.386.865.459.400.540.160,00 % EXPECTED RESULT In previous versions of skrooge huge values had been shown as "∞" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.10-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 Skrooge Version 2.24.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 433514] New: Currency download from Yahoo uses "low" instead of "close" value
https://bugs.kde.org/show_bug.cgi?id=433514 Bug ID: 433514 Summary: Currency download from Yahoo uses "low" instead of "close" value Product: skrooge Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: k...@mockies.de CC: steph...@mankowski.fr Target Milestone: --- Created attachment 136100 --> https://bugs.kde.org/attachment.cgi?id=136100=edit quick and dirty workaround SUMMARY Version: 2.24.6 When downloading currency values using skrooge-yahoodl.py, Skrooge will use column "Low" instead of column "Close" (Skrooge does not seem to inspect the header but rather simply uses column "4" if I interpret the observed behavior correctly). STEPS TO REPRODUCE 1. download currency EURUSD=X with Yahoo 2. get raw data with "/usr/share/skrooge/skrooge-yahoodl.py EURUSD=X 2021-02-18 2021-02-18 1d" OBSERVED RESULT value for 17.02.2021 in Skrooge is 1,20 (1.202559) EXPECTED RESULT value for 17.02.2021 should be 1,21 (1.209248) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 ADDITIONAL INFORMATION When using stock values the effect is even more visible because stock values tend to vary a lot more over a day. As a quick and dirty workaround I modified skrooge-yahoodl.py and switch column 5 and 4. See attached patch (don't know if this would be an acceptable solution, it is rather ugly). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430167] Changing global scale does not work when entering a value directly
https://bugs.kde.org/show_bug.cgi?id=430167 --- Comment #5 from Christoph Vogtländer --- Created attachment 133958 --> https://bugs.kde.org/attachment.cgi?id=133958=edit Screencast Add screencast to illustrate the issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430167] Changing global scale does not work when entering a value directly
https://bugs.kde.org/show_bug.cgi?id=430167 Christoph Vogtländer changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Christoph Vogtländer --- Changing status back to REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430167] Changing global scale does not work when entering a value directly
https://bugs.kde.org/show_bug.cgi?id=430167 --- Comment #3 from Christoph Vogtländer --- I'm using the KCM on X11 Using TAB works for me, too. It is reproducible here when using the steps as mentioned in my initial post. More exactly: 1. Select whole text in spinbox by clicking three times 2. type new value: 150 3. press ENTER 4. click "Apply" -> value changes back to 100% (and no info message at the top of the KCM appears as it should) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430167] Changing global scale does not work when entering a value directly
https://bugs.kde.org/show_bug.cgi?id=430167 --- Comment #1 from Christoph Vogtländer --- Side note: using the scroll wheel also seems to work fine -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430167] New: Changing global scale does not work when entering a value directly
https://bugs.kde.org/show_bug.cgi?id=430167 Bug ID: 430167 Summary: Changing global scale does not work when entering a value directly Product: systemsettings Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: k...@mockies.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Changing the global display scale (X11) only works when using the slider or by using the spin box buttons. Setting the value directly by typing a value will reset the scale to "100%" when the spin box looses focus STEPS TO REPRODUCE 1. Set a new scale by typing e.g. "150 -> Enter" 2. The slider will move as expected, "Apply" button becomes active 3. Change focus, e.g. by clicking "Apply" OBSERVED RESULT The scale factor is reset to 100% EXPECTED RESULT The chosen scale factor should be applied SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.12-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Christoph Vogtländer changed: What|Removed |Added CC||k...@mockies.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421377] Inconsistant search results
https://bugs.kde.org/show_bug.cgi?id=421377 --- Comment #1 from Christoph Vogtländer --- Created attachment 128377 --> https://bugs.kde.org/attachment.cgi?id=128377=edit No item count with message in list -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421377] New: Inconsistant search results
https://bugs.kde.org/show_bug.cgi?id=421377 Bug ID: 421377 Summary: Inconsistant search results Product: kmail2 Version: 5.14.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: k...@mockies.de Target Milestone: --- Created attachment 128376 --> https://bugs.kde.org/attachment.cgi?id=128376=edit Serch dialogue with result and no hits SUMMARY Searching for e.g. "Important" messages will sometimes result in messages to be shown in the search dialogue, but at the bottom "0 matches" are stated (see attachment). Leaving the dialogue will show an empty search folder. The message is marked as "Important" and should be shown. Eventually (not after simply pressing F5, though), the message will be shown correctly even in the search folder. Also, the message count of the search folder is not shown correctly. Even when a message is present in the messages list, the item count in the tool tip and folder list is "". Behaviour seems to be triggered when using "Search in all folders", but also has been observed when using "Search only in" Restarting kmail seems to solve the issue STEPS TO REPRODUCE 1. create a new search 2. "Search in all folders" 3. "Message Status" is "Important" 4. Press "Search" -> Message is shown, but "0 matches", search folder is empty 5. Switch to "Search only in" and select top level entry, with sub-folders 6. Press "Search" -> Nothing changes 7. Press "Search" (why pressing twice is needed is unclear) -> "1 match" is shown OBSERVED RESULT Unexpected and inconstant search result behaviour EXPECTED RESULT With any setting, the correct results should be shown SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.6.11-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15,3 GiB -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420679] New: feature request: optionally show absolute number of messages in favourites
https://bugs.kde.org/show_bug.cgi?id=420679 Bug ID: 420679 Summary: feature request: optionally show absolute number of messages in favourites Product: kmail2 Version: 5.14.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: k...@mockies.de Target Milestone: --- SUMMARY Beside showing the number of "new" messages it would be nice to also (optionally) show the number of all messages beside a favourites folder name. Especially when adding a search filter like "mails with tasks" this would be a benefit. I propose to show the absolute number of messages in square brackets. The behaviour should be configurable on a per folder basis. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.6.6-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15,3 GiB -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420644] New: feature request: be able to show message account/folder in message list
https://bugs.kde.org/show_bug.cgi?id=420644 Bug ID: 420644 Summary: feature request: be able to show message account/folder in message list Product: kmail2 Version: 5.14.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: k...@mockies.de Target Milestone: --- SUMMARY When showing mails in a search folder or in a unified mailbox there does not seem to be an easy way to show the actual message folder (or mailbox account). The only way to see the folder seems to be by opening the mail in a separate window (the containing folder will then be shown in the title bar). It would be nice to be able to add a "folder" and/or "account" field to the theme. Additionally, the folder might also be shown in the messages tool-tip which would also allow quick access without opening an extra window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.6.6-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15,3 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 419720] New: Message status filter broken
https://bugs.kde.org/show_bug.cgi?id=419720 Bug ID: 419720 Summary: Message status filter broken Product: kmail2 Version: 5.13.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: k...@mockies.de Target Milestone: --- Created attachment 127324 --> https://bugs.kde.org/attachment.cgi?id=127324=edit Find Messages dialogue screen shot SUMMARY The message status filter reads "message status" for all fields. Only the icon gives a hint of what is actually meant. Using such a filter does not work. E.g. using "action item" entry, will show mails even without an action item marker. Re-opening the "Find Messages" dialogue seems to reset the selection in the drop down to the first entry. STEPS TO REPRODUCE 1. open "Find Messages" 2. select "Message Status" 3. select type "[action item icon] message status" entry OBSERVED RESULT Mails without action item marker are included in the result EXPECTED RESULT Only mails with action item marker should be included in the result SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Saved filters seem to work fine. I have an old filter which is searching for "important" mails that is still working. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394784] KMAIl 5.8.1: Reply to HTML-mail in text mode includes content from last mail
https://bugs.kde.org/show_bug.cgi?id=394784 --- Comment #11 from Christoph Vogtländer --- I'm running Arch Linux also with KMail 5.13.3 (19.12.3) with Qt 5.14.1. The bug i still present. But, if the bug is related to the Qt version rather than to KMail this would explain this. Either OpenSUSE uses a newer Qt version or ships with a patch. Would the problem be solved by simply compiling against Qt >= 5.14.2? Or are code changes needed? For the former case this would be up to the distribution to solve this by updating to a more recent Qt version. For the latter case something like "#if (QT_VERSION >= QT_VERSION_CHECK(5, 14, 2))" or similar would be required (and compiling against a new Qt version or course). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 418005] New: "Only quote selected text when replying" does not work
https://bugs.kde.org/show_bug.cgi?id=418005 Bug ID: 418005 Summary: "Only quote selected text when replying" does not work Product: kmail2 Version: 5.13.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@mockies.de Target Milestone: --- SUMMARY "Only quote selected text when replying" does not work. Even when text is selected, the complete message will be quoted STEPS TO REPRODUCE 1. Enable "Only quote selected text when replying" option in E-Mail-Editor -> General -> Format 2. Select text in a mail and reply OBSERVED RESULT The complete message is quoted EXPECTED RESULT Only the selected text should be quoted SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION I'm using the default "Reply" template: %REM="Default reply template"%- On %ODATE %OTIMELONG you wrote: %QUOTE %CURSOR -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417763] New: Removing an entry from exluded folder will also rewrite "folders" entry in baloofilerc
https://bugs.kde.org/show_bug.cgi?id=417763 Bug ID: 417763 Summary: Removing an entry from exluded folder will also rewrite "folders" entry in baloofilerc Product: systemsettings Version: 5.18.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: baloo-bugs-n...@kde.org Reporter: k...@mockies.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY removing and entry from the exclude folder using systemsettings, will not just remove the entry from "exclude folders[$e]" but also resets "folders[$e]" to "$HOME". Any custom set folders are removed. STEPS TO REPRODUCE 1. add a custom entry in baloofilerc "folders[$e]=$HOME,/home/share/ 1. remove an entry from the excluded folder list OBSERVED RESULT folders[$e] will be reset to "$HOME": folders[$e]=$HOME EXPECTED RESULT The entry should be left as is. AFAIK, the GUI does not allow customisation of "folders[$e]" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.28.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417762] New: Setting exclude folders under HOME do not work
https://bugs.kde.org/show_bug.cgi?id=417762
Bug ID: 417762
Summary: Setting exclude folders under HOME do not work
Product: systemsettings
Version: 5.18.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_baloo
Assignee: baloo-bugs-n...@kde.org
Reporter: k...@mockies.de
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
Setting exclude folders does not work because "$HOME" already contains a
trailing slash, resulting in double slashes. Files in excluded folders will be
indexed.
STEPS TO REPRODUCE
1. add a folder to exclude list via systemsettings, e.g. "tmp"
OBSERVED RESULT
Entry in baloofilerc "exclude folders[$e]=$HOME/tmp/" is created. "balooctl
config show excludeFolders" will show that this is evaluated to
/home/user//tmp/
(note the double "/" after HOME)
This is because "$HOME" already contains a trailing slash
Baloo will index files in ~/tmp
Manually changing the option in baloofilerc to "exclude
folders[$e]=${HOME}tmp/" works as expected.
EXPECTED RESULT
Baloo should not index files in ~/tmp, the entry should be
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 413875] New: Excludes do not work
https://bugs.kde.org/show_bug.cgi?id=413875 Bug ID: 413875 Summary: Excludes do not work Product: frameworks-baloo Version: 5.63.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: k...@mockies.de Target Milestone: --- I configured Baloo using the KDE system settings. I added a folder that should be excluded from file indexing. Using "balooctl monitor", I can see that the folder gets indexed nonetheless. STEPS TO REPRODUCE 1. activate index based file search 2. add a folder (in home directory) to excludes 3. save settings and start indexing OBSERVED RESULT files in excluded folder get indexed EXPECTED RESULT files in excluded folder should be skipped (recursively) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION When adding the exclude list, it appears as "foldername" in the list. After closing and reopening the settings dialogue it will then be shown as "/foldername". This might indicate that the folder is expected to be in the file system root. Actually, it is a sub-folder of my $HOME folder -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412959] New: Distinguish between exFAT and FAT32
https://bugs.kde.org/show_bug.cgi?id=412959 Bug ID: 412959 Summary: Distinguish between exFAT and FAT32 Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: k...@mockies.de Target Milestone: --- When creating a FAT32 partition with partition manager, actually an exFAT partition will be created (partition type 0x07 instead of 0x0b). This is a problem when creating bootable SD-cards for devices using AM335x ARM Cortex-A8 processor (e.g. BeagleBone boards). The processor is not able to load exFAT partitions. IMHO partitionmanager should distinguish between FAT32 and exFAT (currently, exFAT is not an available file system option in the list). At least the current entry "fat32" should be renamed to "exFAT" as this is actually what is created. STEPS TO REPRODUCE 1. create a FAT32 partition OBSERVED RESULT the partition type is set to 0x07 (exFAT) (can be checked with e.g. fdisk) EXPECTED RESULT the partition type should be 0x0b (FAT32) -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #13 from Christoph Vogtländer --- Created attachment 122811 --> https://bugs.kde.org/attachment.cgi?id=122811=edit Patch1 Patch which creates/selects the default account when the value for "account" column in CSV file is empty -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #12 from Christoph Vogtländer --- I was able to track down this issue. The problem is that my bank exports the field "Konto-Nr." (account number) without actually setting any value (see the sample CSV file). When importing with LANG=de_DE.UTF-8 the default regular expression for detecting the account per line is "^Konto" which matches the exported field at column 4 in the header data. The bool "noAccountColumn" (skgimportplugincsv.cpp:447) is false in this case and no default account will be created/selected. When processing the "account" column, "val" is an empty string and no account will be created/set either (as "val != defAccount.getName()" in skgimportplugincsv.cpp:618 is true). Setting the parent account will fail, then. Starting skrooge with LANG=C will change the default regular expression to "^account" which then does not match anything in the CSV. "noAccountColumn" is true and a default account will be created before the import gets started. The import succeeds in this case. IMHO this should be handled more gracefully as it is nearly impossible to understand the problem from the users perspective. Either the importer should show a more meaningful error message or, even better, should fall back to the default account (like when "noAccountColumn" is true) for lines with an empty "Account" value. I will provide a patch for the latter case. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #10 from Christoph Vogtländer --- I can see that in skgoperationobject.cpp:153 the value of "newAccount" is "0" with LANG=de_DE.UTF-8 and "1" with LANG=C. Unfortunately I cannot see what is happening inside "importFile()" because skrooge loads the plug-ins from /usr/lib/qt/plugins (no debug information there of course) rather than from my shadow directory used when compiling. I can see that KServiceTypeTrader is used to locate plug-ins. I'm not experienced with KDE API and a quick search did not reveal anything useful. How can I instruct skrooge to load plug-ins from a custom directory? If possible I would like to avoid to install my compiled binaries into the system. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #9 from Christoph Vogtländer --- The import also fails when importing into a completely new (empty) file. How can I help? I think I am able to compile skrooge myself in debug mode. If you can give me some hints where to set some break points it would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #7 from Christoph Vogtländer --- Hi, yes, I'm sure that the file is not empty -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #6 from Christoph Vogtländer --- Created attachment 122700 --> https://bugs.kde.org/attachment.cgi?id=122700=edit Traces.txt As requested -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #4 from Christoph Vogtländer --- Sorry. My default LANG is "de_DE.UTF-8". I can confirm that it works with LANG=DE but not with LANG=de_DE.UTF-8 I start skrooge for my test with: $ LANG=de_DE.UTF-8 skrooge -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #2 from Christoph Vogtländer --- Created attachment 122679 --> https://bugs.kde.org/attachment.cgi?id=122679=edit Smaple CSV file Required import settings: Date: ^Buchungstag Payee: ^payee|^tiers|^.*Zahlungspflichtiger Comment: ^comment|^libell?|^d?tail|^info|^Vorgang.* Amount: ^value|^amount|^valeur|^montant|^credit|^debit|^Umsatz Sign: ^sign|^sens Unit: ^Währung Debit values of "sign" column: ^S The other regular expressions are still on their default value (and IMHO not relevant for this case) -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] New: Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 Bug ID: 411958 Summary: Import fails with LANG=DE Product: skrooge Version: 2.19.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: k...@mockies.de CC: steph...@mankowski.fr Target Milestone: --- SUMMARY Importing a CSV file fails when LANG=DE (my default LANG) is set. When starting skrooge with LANG=C the import works as expected. The CSV file is encoded in ISO8859-15 STEPS TO REPRODUCE 1. Import a ISO8859-15 encoded CSV file wile LNAG=DE is set OBSERVED RESULT [ERR-5]: Das Importieren der Datei „file:///.../account.csv“ ist fehlgeschlagen. [ERR-5]: „SKGOperationObject::setParentAccount“ ist fehlgeschlagen, da das verknüpfte Objekt noch nicht in der Datenbank gespeichert wurde. Freely translated: [ERR-5]: Import of file ... failed [ERR-5]: „SKGOperationObject::setParentAccount“ failed because the linked object has not been saved in the database EXPECTED RESULT Import should work independently from the currently set locale SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 Skrooge: 2.20.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409782] New: Akonadi server crashed on boot
https://bugs.kde.org/show_bug.cgi?id=409782 Bug ID: 409782 Summary: Akonadi server crashed on boot Product: Akonadi Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: k...@mockies.de Target Milestone: --- Application: akonadiserver (5.11.3) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.2.0-arch2-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Newly started the system. After first log-in, Akonadi server is not able to start up cleanly when Kontact starts (Kontact is in my autostart list) Starting Akonadi using the provided "Start" button in Kontact does not work either. There seems to be no crash in this case, at least Dr. Konqui does not detect anything. Pressing "Details..." button in Kontact does not work (there is no visible action). Closing and restarting Kontact does not solve the problem either. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd628e7f400 (LWP 1064))] Thread 38 (Thread 0x7fd5ef7fe700 (LWP 2465)): #0 0x7fd62c85c77c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd62d47350c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fd62d473659 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fd62d470b0b in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fd62d46d520 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd62c85657f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd62d0e20e3 in clone () from /usr/lib/libc.so.6 Thread 37 (Thread 0x7fd618df4700 (LWP 2464)): #0 0x7fd62c85c77c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd62d47350c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fd62d473659 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fd62d470b0b in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fd62d46d520 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd62c85657f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd62d0e20e3 in clone () from /usr/lib/libc.so.6 Thread 36 (Thread 0x7fd6195f5700 (LWP 2463)): #0 0x7fd62c85c77c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd62d47350c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fd62d473659 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fd62d470b0b in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fd62d46d520 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd62c85657f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd62d0e20e3 in clone () from /usr/lib/libc.so.6 Thread 35 (Thread 0x7fd5eeffd700 (LWP 2462)): #0 0x7fd62c85c77c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd62d47350c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fd62d473659 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fd62d470b0b in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fd62d46d520 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd62c85657f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd62d0e20e3 in clone () from /usr/lib/libc.so.6 Thread 34 (Thread 0x7fd5e700 (LWP 2461)): #0 0x7fd62c85c77c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd62d47350c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fd62d473659 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fd62d470b0b in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fd62d46d520 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd62c85657f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd62d0e20e3 in clone () from /usr/lib/libc.so.6 Thread 33 (Thread 0x7fd5977fe700 (LWP 1839)): #0 0x7fd62b986479 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7fd62b9d3a87 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #2 0x7fd62b9d5b11 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fd62b9d5b51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fd62d6929bc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fd62d6395ec in QEventLoop::exec(QFlags) () from
[skrooge] [Bug 408138] Date of imported transactions not recognised
https://bugs.kde.org/show_bug.cgi?id=408138 --- Comment #3 from Christoph Vogtländer --- I confirm that the workaround in org.kde.skrooge-import-backend-aqbanking.desktop fixes the problem. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 408138] New: Date of imported transactions not recognised
https://bugs.kde.org/show_bug.cgi?id=408138 Bug ID: 408138 Summary: Date of imported transactions not recognised Product: skrooge Version: 2.19.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: k...@mockies.de CC: steph...@mankowski.fr Target Milestone: --- The date of imported transactions is always set to the current date. I'm using the aqbanking (SABB) backend. Using skrooge-sabb.py directly (e.g. "./skrooge-sabb.py bulkdownload --output_folder ~/tmp/") shows that the format in the resulting CSV files is "/MM/DD". This format is not listed as a possible format in the Skrooge import settings. So it might be that Skrooge simply is not able to recognise the used date format any longer. It seems that the format is provided by the bank? Or is it possible to configure the format in AqBanking somehow? The import worked without problems in earlier versions of Skrooge/AqBanking. Unfortunately I do not know exactly when I did the last successful import (I think it was around Februrary 19). STEPS TO REPRODUCE 1. import with aqbanking backend OBSERVED RESULT The date of all imported transactions is the current date EXPECTED RESULT The date should be the actual date of the transaction SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 403636] Media Pause button doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=403636 Christoph Vogtländer changed: What|Removed |Added CC||k...@mockies.de -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 --- Comment #6 from Christoph Vogtländer --- I launched my favorite debugger and found the problem: mainwindow.cpp:1006: QLatin1String fsName = QLatin1String(rePartition.captured(4).toLatin1()); >From the Qt documentation: QLatin1String::QLatin1String(const QByteArray ) Constructs a QLatin1String object that stores str. **The string data is not copied. The caller must be able to guarantee that str will not be deleted or modified as long as the QLatin1String object exists.** So it is a mistake to construct a QLatin1String from a temporary. As "fsType" is required to be a QString later anyway, a possible fix would be to simply create a QString: QString fsName = rePartition.captured(4); I tested this and it works. But, this has explicitly changed in 4b4198c34a9f4880546242de330138cc11da8359 together with the creation of "fs*". The latter was reverted in 24237a6120e31f1051a07499f04c7391b877552c -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 --- Comment #4 from Christoph Vogtländer --- To me it looks like a race condition during import. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 --- Comment #2 from Christoph Vogtländer --- I can confirm that this happens by simply "export -> import" without applying operations. The steps I run: 1. start partitionmanager 2. select device 3. Device -> Export Partition Table: save file 4. Device -> Import Partition Table: load file --> partition type of the partitions is loaded as "unknown" Sometimes, only the second partition (ext4) is loaded as "unknown" but the first partition (fat32) is loaded correctly -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401878] Password denied in 2.16.2, works fine in 2.15.0
https://bugs.kde.org/show_bug.cgi?id=401878 --- Comment #12 from Christoph Vogtländer --- The patch works. Tested with arch linux community testing package skrooge-2.17.0-2 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401878] Password denied in 2.16.2, works fine in 2.15.0
https://bugs.kde.org/show_bug.cgi?id=401878 --- Comment #9 from Christoph Vogtländer --- As a side note: Skrooge 2.17.0 is able to open a newly created files, with or without password. Don't know if this helps to track this down. My old file, even if I clean up everything (deleted all transactions, accounts, etc), is still about 47MB. It's too big to add to the bugtracker. You can download it from here: https://lunik.synology.me:1443/nextcloud/index.php/s/sPNYKX9A9TY6E2s PWD is "test" -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401878] Password denied in 2.16.2, works fine in 2.15.0
https://bugs.kde.org/show_bug.cgi?id=401878 --- Comment #8 from Christoph Vogtländer --- Created attachment 117019 --> https://bugs.kde.org/attachment.cgi?id=117019=edit trace created with SKGTRACE=10 and SKGTRACESQL=1 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401878] Password denied in 2.16.2, works fine in 2.15.0
https://bugs.kde.org/show_bug.cgi?id=401878 Christoph Vogtländer changed: What|Removed |Added Version|2.16.0 |2.17.0 Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Christoph Vogtländer --- The error still persists in 2.17.0 see also https://bugs.archlinux.org/task/60989 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401878] Password denied in 2.16.2, works fine in 2.15.0
https://bugs.kde.org/show_bug.cgi?id=401878 --- Comment #3 from Christoph Vogtländer --- For Arch Linux see https://bugs.archlinux.org/task/60989?project=5=skrooge -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401878] Password denied in 2.16.2, works fine in 2.15.0
https://bugs.kde.org/show_bug.cgi?id=401878 --- Comment #1 from Christoph Vogtländer --- Even after removing the password using 2.15.0 the file will not open with 2.16.2. While 2.15.0 opens the file without prompting for a password as expected, 2.16.2 still comes up with the password dialogue. Clicking "OK" will again show "Wrong password" (well, this might be some follow up error as the file is not protected at all and trying to decode will fail even with an empty password) -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401878] New: Password denied in 2.16.2, works fine in 2.15.0
https://bugs.kde.org/show_bug.cgi?id=401878 Bug ID: 401878 Summary: Password denied in 2.16.2, works fine in 2.15.0 Product: skrooge Version: 2.16.0 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: k...@mockies.de CC: steph...@mankowski.fr Target Milestone: --- SUMMARY Opening my encrypted skg-file with Skrooge 2.16.2 prompts for the password as normal. But, the file won't open: "Wrong password. This file seems to be protected. Please enter the password." Using Skrooge 2.15.0 (AppImage) the file opens just fine so I'm pretty sure the password is correct. STEPS TO REPRODUCE Open attached file with Skrooge 2.16.2 OBSERVED RESULT Skrooge does not open the file EXPECTED RESULT Skrooge should open the file (and version 2.15.0 does) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION The password for the attached file is "test". The file is a stripped down and anonymized version of my working file. I used the 2.15.0 AppImage to change the password and anonymize the data. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 400532] New: Copy to clipboard on host terminates session
https://bugs.kde.org/show_bug.cgi?id=400532 Bug ID: 400532 Summary: Copy to clipboard on host terminates session Product: krdc Version: 18.08 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: k...@mockies.de Target Milestone: --- Copying text to clipboard (Ctrl+c or Ctrl+x) on the host will terminate the active RDP session. The text is not actually placed into the clipboard (which could lead to data loss in case Ctrl+x was used and the text field does not support "undo"). Copying text on the client into clipbaord is available on the host as expected. Clipboard text copied before the session gets opened will be available in a newly opened session. STEPS TO REPRODUCE 1. open a RDP session (to Windows 7 in my case) 2. copy text to clipbaord on the host OBSERVED RESULT The RDP session gets terminated. Text is not copied to clipboard at all. EXPECTED RESULT Text should be available in the clipboard of the host as well as in the client session. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION I'm using Plasma clipboard applet, after copying text and the remote session terminates the applet will show an empty entry. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400331] New: partition flags are not imported
https://bugs.kde.org/show_bug.cgi?id=400331 Bug ID: 400331 Summary: partition flags are not imported Product: partitionmanager Version: 3.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stiko...@kde.org Reporter: k...@mockies.de Target Milestone: --- Importing an exported partition table will not set "flag" attributes. STEPS TO REPRODUCE 1. Device -> Export Partition Table: save file 2. Device -> Import Partition Table: load file (might fail completely due to Bug 400330) OBSERVED RESULT only the partition table, partition type, label and size are imported. "Flags" (like "boot") are not present. EXPECTED RESULT Flags should be restored SOFTWARE VERSIONS (available in About System) partitionmanager: 3.3.1 KPMcore: 3.3.0 KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Content of my exported partition table file (8GB SD-card): ##|v1|## partition table of /dev/sdd # on Wednesday, 10 October 2018 11:06:58 CEST type: "msdos" align: "sector" # number start end type roles label flags 1;2048;1050623;fat32;primary;"";"boot" 2;1050624;15325183;ext4;primary;"";"" -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] New: Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 Bug ID: 400330 Summary: Filesystem type unknown after partition table import Product: partitionmanager Version: 3.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stiko...@kde.org Reporter: k...@mockies.de Target Milestone: --- Importing an exported partition table will fail to restore the filesystem type. All partitions are created with type "unknown". Sometimes importing works as expected, but fails on a second import. STEPS TO REPRODUCE 1. Device -> Export Partition Table: save file 2. Device -> Import Partition Table: load file 3. If this worked: Undo all changes 4. Device -> Import Partition Table: load file OBSERVED RESULT Filesystem type is "unknown" EXPECTED RESULT Filesystem type should be restored as e.g. "fat32" or "ext4" SOFTWARE VERSIONS (available in About System) partitionmanager: 3.3.1 KPMcore: 3.3.0 KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Content of my exported partition table file (8GB SD-card): ##|v1|## partition table of /dev/sdd # on Wednesday, 10 October 2018 11:06:58 CEST type: "msdos" align: "sector" # number start end type roles label flags 1;2048;1050623;fat32;primary;"";"boot" 2;1050624;15325183;ext4;primary;"";"" -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 395522] Amazon Music not supported
https://bugs.kde.org/show_bug.cgi?id=395522 Christoph Vogtländer changed: What|Removed |Added CC||k...@mockies.de -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 375875] New: Changing password does not work
https://bugs.kde.org/show_bug.cgi?id=375875
Bug ID: 375875
Summary: Changing password does not work
Product: skrooge
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: guillaume.deb...@gmail.com
Reporter: kdebugzi...@mockies.de
CC: steph...@mankowski.fr
Target Milestone: ---
After upgrading to skrooge 2.7.0 I get a warning that a security hole has been
detected in an earlier version and upgrading the password is strongly advised.
Trying to change the password will result in the following error (sorry, some
messages in German even if starting skrooge with LANG=en):
[ERR-5]: Failed to change password.
[ERR-5]: Creation failed. The object already exists.
[ERR-10019]: Das Objekt kann nicht eingefügt werden (doctransaction wird von
doctransactionmsg verwendet).
Name der Einschränkung:
fki_doctransactionmsg_doctransaction_rd_doctransaction_id_id Der Datensatz
konnte nicht abgeholt werden
[ERR-10019]: INSERT INTO doctransactionmsg
('t_message','rd_doctransaction_id','t_type') VALUES ('The document password
has been modified.','22532','P')
Changing something and trying to save will result in:
[ERR-5]: Cannot save file
[ERR-10026]: file is encrypted or is not a database Der Datensatz konnte nicht
abgeholt werden
[ERR-10026]: update doctransaction set t_savestep='Y' where id in (select A.id
from doctransaction A where NOT EXISTS(select 1 from doctransaction B where
B.i_parent=A.id) and A.t_mode='U')
--
You are receiving this mail because:
You are watching all bug changes.
[skrooge] [Bug 369090] Transfers sub operation created by template has wrong date
https://bugs.kde.org/show_bug.cgi?id=369090 --- Comment #2 from Christoph Vogtländer <kdebugzi...@mockies.de> --- Created attachment 101193 --> https://bugs.kde.org/attachment.cgi?id=101193=edit screenshot showing wrong date -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 369090] Transfers sub operation created by template has wrong date
https://bugs.kde.org/show_bug.cgi?id=369090 --- Comment #1 from Christoph Vogtländer <kdebugzi...@mockies.de> --- Created attachment 101192 --> https://bugs.kde.org/attachment.cgi?id=101192=edit test file demonstrating the issue -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 369090] New: Transfers sub operation created by template has wrong date
https://bugs.kde.org/show_bug.cgi?id=369090 Bug ID: 369090 Summary: Transfers sub operation created by template has wrong date Product: skrooge Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: kdebugzi...@mockies.de CC: steph...@mankowski.fr Creating a transfer between two accounts from a template will set (or at least shows) the date of one sub operation to the date when the template was created, not the actual date. This breaks the report when "Transfers" is checked and the wrong date is outside the report date bounds. As only one part of the transfer is processed by the report the result is not as expected. Reproducible: Always Steps to Reproduce: 1. create two accounts 2. create a template to transfer money from one account to another 3. set the date of the template to e.g. 1.1.1979 4. double click the template to create a operation 5. double click on on part of the transfer to get to the suboperation group view Actual Results: after step 4: date is shown correctly on the normal operations page after step5: the date of one part of the operation is not the actual date but the date of the template Expected Results: the date should always be the actual date of the operation, not the date of the template -- You are receiving this mail because: You are watching all bug changes.
