[Discover] [Bug 485613] Discover crashes when you search into all apps
https://bugs.kde.org/show_bug.cgi?id=485613 Jon Intxaurbe changed: What|Removed |Added Status|CONFIRMED |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485613] Discover crashes when you search into all apps
https://bugs.kde.org/show_bug.cgi?id=485613 Jon Intxaurbe changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|BACKTRACE |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 485765] New: Pasting text from Chrome to Krita rich text editor changes font styling
https://bugs.kde.org/show_bug.cgi?id=485765 Bug ID: 485765 Summary: Pasting text from Chrome to Krita rich text editor changes font styling Classification: Applications Product: krita Version: 5.2.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: j...@moeller.io Target Milestone: --- SUMMARY STEPS TO REPRODUCE 0. Be in dark mode 1. Open an image file in Krita 2. Click the text tool 3. create a text box on the canvas by clicking and dragging 4. Paste some text from a webpage with a white background 5. Observe that text is now black on white OBSERVED RESULT text is now black on white EXPECTED RESULT My expectation is that a rich text editor also has a "paste without formatting" option, but I could not find one in the dialog. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485613] Discover crashes when you search into all apps
https://bugs.kde.org/show_bug.cgi?id=485613 --- Comment #5 from Jon Intxaurbe --- (In reply to Harald Sitter from comment #2) > and make sure your system is up to date. Yes, my system is up to date. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485613] Discover crashes when you search into all apps
https://bugs.kde.org/show_bug.cgi?id=485613 --- Comment #4 from Jon Intxaurbe --- (Second part) -- Stack trace of thread 3410: #0 0x7d486da91117 __futex_abstimed_wait_common64 (libc.so.6 + 0x91117) #1 0x7d486da93a41 __pthread_cond_wait_common (libc.so.6 + 0x93a41) #2 0x7d486431952d n/a (iris_dri.so + 0x11952d) #3 0x7d48642c98bb n/a (iris_dri.so + 0xc98bb) #4 0x7d486431945b n/a (iris_dri.so + 0x11945b) #5 0x7d486da94ac3 start_thread (libc.so.6 + 0x94ac3) #6 0x7d486db26850 __clone3 (libc.so.6 + 0x126850) Stack trace of thread 3416: #0 0x7d486da91117 __futex_abstimed_wait_common64 (libc.so.6 + 0x91117) #1 0x7d486da93e9b __pthread_cond_wait_common (libc.so.6 + 0x93e9b) #2 0x7d486e589647 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x389647) #3 0x7d486e58660a n/a (libQt6Core.so.6 + 0x38660a) #4 0x7d486e583c9d n/a (libQt6Core.so.6 + 0x383c9d) #5 0x7d486da94ac3 start_thread (libc.so.6 + 0x94ac3) #6 0x7d486db26850 __clone3 (libc.so.6 + 0x126850) Stack trace of thread 3365: #0 0x7d486da91117 __futex_abstimed_wait_common64 (libc.so.6 + 0x91117) #1 0x7d486da93a41 __pthread_cond_wait_common (libc.so.6 + 0x93a41) #2 0x7d486431952d n/a (iris_dri.so + 0x11952d) #3 0x7d48642c98bb n/a (iris_dri.so + 0xc98bb) #4 0x7d486431945b n/a (iris_dri.so + 0x11945b) #5 0x7d486da94ac3 start_thread (libc.so.6 + 0x94ac3) #6 0x7d486db26850 __clone3 (libc.so.6 + 0x126850) Stack trace of thread 3552: #0 0x7d486da91117 __futex_abstimed_wait_common64 (libc.so.6 + 0x91117) #1 0x7d486da93e9b __pthread_cond_wait_common (libc.so.6 + 0x93e9b) #2 0x7d486e589647 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x389647) #3 0x7d486e58660a n/a (libQt6Core.so.6 + 0x38660a) #4 0x7d486e583c9d n/a (libQt6Core.so.6 + 0x383c9d) #5 0x7d486da94ac3 start_thread (libc.so.6 + 0x94ac3) #6 0x7d486db26850 __clone3 (libc.so.6 + 0x126850) Stack trace of thread 3569: #0 0x7d486db18bcf __GI___poll (libc.so.6 + 0x118bcf) #1 0x7d486d5711f6 n/a (libglib-2.0.so.0 + 0xab1f6) #2 0x7d486d5193e3 g_main_context_iteration (libglib-2.0.so.0 + 0x533e3) #3 0x7d486e476570 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x276570) #4 0x7d486e6a3e3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4a3e3b) #5 0x7d486e5bcf48 _ZN7QThread4execEv (libQt6Core.so.6 + 0x3bcf48) #6 0x7d486e583c9d n/a (libQt6Core.so.6 + 0x383c9d) #7 0x7d486da94ac3 start_thread (libc.so.6 + 0x94ac3) #8 0x7d486db26850 __clone3 (libc.so.6 + 0x126850) Stack trace of thread 3414: #0 0x7d486da91117 __futex_abstimed_wait_common64 (libc.so.6 + 0x91117) #1 0x7d486da93e9b __pthread_cond_wait_common (libc.so.6 + 0x93e9b) #2 0x7d486e589647 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x389647) #3 0x7d486e58660a n/a (libQt6Core.so.6 + 0x38660a) #4 0x7d486e583c9d n/a (libQt6Core.so.6 + 0x383c9d) #5 0x7d486da94ac3 start_thread (libc.so.6 + 0x94ac3) #6 0x7d486db26850 __clone3 (libc.so.6 + 0x126850) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485613] Discover crashes when you search into all apps
https://bugs.kde.org/show_bug.cgi?id=485613 --- Comment #3 from Jon Intxaurbe --- I'll try to provide backtrace. I hope to be helpful. I've replace my real user with "my_user". The only change I've done. I have splitted in two pieces, because of the limit of characters in one comment. Thank you very much. The back trace (via System/drkonqi-coredump): - PID: 3347 (plasma-discover) UID: 1000 (my_user) GID: 1000 (my_user) Signal: 11 (SEGV) Timestamp: Tue 2024-04-16 12:50:31 CEST (13s ago) Command Line: /usr/bin/plasma-discover Executable: /usr/bin/plasma-discover Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover-454620afbf4a4d4db7f74ce5338f8e9d.scope Unit: user@1000.service User Unit: app-org.kde.discover-454620afbf4a4d4db7f74ce5338f8e9d.scope Slice: user-1000.slice Owner UID: 1000 (my_user) Boot ID: b953983ffb16408fb4a50a012ab668e9 Machine ID: 78824f2b8db741628c1d79ad8d3dc53b Hostname: Nere-essential14 Storage: /var/lib/systemd/coredump/core.plasma-discover.1000.b953983ffb16408fb4a50a012ab668e9.3347.171326463100.zst (present) Disk Size: 82.7M Message: Process 3347 (plasma-discover) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: 24544dfc4a0fd9fa84a623515c92f78febfb440b Found module libaccounts-glib.so.0 with build-id: 6991a9e950212220b0c336dbf2ea01209996d5d9 Found module libsignon-qt6.so.1 with build-id: 2ecddc38eb194e135a62b24d170f51e2dea30842 Found module libQt6QuickWidgets.so.6 with build-id: e31ab27ce0ee944bbf0364b65bc2427264a47f2b Found module libaccounts-qt6.so.1 with build-id: 3f8ccada17b5262487a1b8b15dd28d46ff6ea7bb Found module libkaccounts6.so.2 with build-id: 0b3f651e3746a944ba2e1cb8c411f5193599e7e2 Found module libKF6KCMUtils.so.6 with build-id: 8b017ebdfd1c261c8008e0bce5d9a413c37a9a35 Found module attica_kde.so with build-id: cd0a00868daebb2e8e9c04fbc133684fc021023c Found module libqcertonlybackend.so with build-id: 2ee804d2be642f4c7d1c508ae4838580863dfa72 Found module libqopensslbackend.so with build-id: cc410c51590af0115261030e89062911dd9cb8da Found module kimg_eps.so with build-id: 5fe4131994991b1392cf5654a4e6bcd66d3f8d02 Found module kimg_rgb.so with build-id: d48c10d89b6349ce5d005d36a650d385e03cbb6a Found module libqico.so with build-id: a5952cc5ec6fe8e0b3f40ffd23653252028cc1fc Found module kimg_qoi.so with build-id: 25a0ee253435ea94d2c772b9fdc6129f9648753e Found module libraw.so.20 with build-id: 13b7683911b1d8cf0644fbf1e90affa547c7bc53 Found module kimg_raw.so with build-id: 4dce46f2214bff0c6d760b3dc516ea5dfc0ba95f Found module libqtiff.so with build-id: 670400532c2e085946d47bbc2891fad0036918e2 Found module kimg_ras.so with build-id: c97ff7b095065c337aa43c84e39c112ebe3915a4 Found module kimg_pcx.so with build-id: 7f302b54e69fa53b6184cb990143273ca8ebce80 Found module libqicns.so with build-id: 18e7ba1d93a9600e64f61ecb94bb8f73010153c9 Found module libnuma.so.1 with build-id: 92e1c5de1d74216d8cd25a4cba6ea2dcbd531897 Found module libx265.so.199 with build-id: 724cf0e53c8c791c6baa015a6a8f8e83b1be6e5b Found module libde265.so.0 with build-id: 9c5304e54beb55c96f3c932a7e3c726cf7529793 Found module libheif.so.1 with build-id: 0c513158613d441555edeefe8c6b1fec9d63ddf4 Found module kimg_heif.so with build-id: 428b4adf8e668f7c187baf9e01af07949ccb4cb8 Found module libqwebp.so with build-id: 000b8cefef4581b94ce391daebc214eab7c9319c Found module libqgif.so with build-id: 215bea65c3c361f74f3d29e2616caf4daa145cc5 Found module libIlmThread-3_1.so.30 with build-id: 695eca9e28afcfd35527883793e655c6f79e2e7f Found module libIex-3_1.so.30 with build-id: dc383ad90d315fafb1cfde5a9efbafe77e71fb2c Found module libImath-3_1.so.29 with build-id: 979ba9b5e2166dd8fd08ee8061e28e0507cef23f Found module libOpenEXR-3_1.so.30 with build-id: 76ffa88e076d4f7adb16f0571d7317ab6ea96e1c Found module kimg_exr.so with build-id: 3296125d4b5da998f45c4a8782159f112e075f21 Found module libQt6Pdf.so.6 with build-id: dd3065a7b088a415e74cc1cc6d93c9ef207ca22a Found module libqpdf.so with build-id: 73dc9edf3e9a213cbc5784ebb1b88ad1a9d7fd69 Found module libmng.so.2 with build-id: 90c62f543f25f43a5c847842d927a5d6cf9ac4d1 Found module libqmng.so with build-id: a7091824e6ed6eff84a8b1e45027f67b3da4056a Found module kimg_kra.so wit
[Discover] [Bug 485613] Discover crashes when you search into all apps
https://bugs.kde.org/show_bug.cgi?id=485613 Jon Intxaurbe changed: What|Removed |Added CC||join...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485613] New: Discover crashes when you search into all apps
https://bugs.kde.org/show_bug.cgi?id=485613 Bug ID: 485613 Summary: Discover crashes when you search into all apps Classification: Applications Product: Discover Version: 6.0.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: join...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY when you open Discover and you select something to search (for example, Thunderbird) the search is completed, but after a few seconds, Discover crashes. Not error's report is shown. I don't know how debug, I'm sorry. However, if you chose some category and search something, it doesn't crash. STEPS TO REPRODUCE 1. Open Discover 2. Search something (something which could be in the database. F.i. Thunderbird). Curiously, with some terms, it doesn't crashes. I think that if the search is for an app's complete name, it's when Discover crashes. 3. After show the results, wait 5 seconds more or less for crashing. SOFTWARE/OS VERSIONS KDE Neon, updated to Plasma 6 from Plasma 5 Linux/KDE Plasma: 6.5.0-27-generic (64-bit) (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION wayland -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 483868] New: Error message when saving multiple tabs with unsaved changes
https://bugs.kde.org/show_bug.cgi?id=483868 Bug ID: 483868 Summary: Error message when saving multiple tabs with unsaved changes Classification: Applications Product: KEXI Version: 3.2.0 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kexi-b...@kde.org Reporter: j_hi6...@icloud.com CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- Created attachment 167389 --> https://bugs.kde.org/attachment.cgi?id=167389=edit Please see attached video for demonstration of bug. SUMMARY If user has performed design changes on a form, and then performs changes on a table it's using, Kexi will warn user that the form changes are unsaved, and present an option to save them before continuing. When this option is accepted, though, Kexi presents user with an error message saying that it could not save the form object. STEPS TO REPRODUCE 1. Create new blank database. 2. Create a new table, give it a primary key, and fill another field with some data. Save but do not close. 3. Create a new form. It should be in its own tab next to the tab for the table. 4. Set form's Data Source to the table you just made. 5. Drop a text box into the form's design. Set its widget data source to a field in your table. 6. Save form. 7. Make any change to the form's design, so that an asterisk appears next to the object name in its tab. 8. Without saving the form, go back to the table tab. 9. Make any change to the table, such as a field's datatype, or to one of the fields' properties. 10. Click Save. 11. Click Close Windows & Save. 12. Click Save. OBSERVED RESULT Error message received saying "Saving '[object name]' object failed." EXPECTED RESULT Successful save of both open tabs/objects, or, if the table change is not allowed, a message describing steps to take. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Studio 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Please see attached video for demonstration of bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #31 from Jon --- Yifan's fix is included in kwin 6.0.2, tested from arch kde-unstable repo and it fixes this issue for me. Thanks Yifan! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483029] Firefox On Plasma 6 Wayland Dragging and Rearranging A Bookmark Auto Opens A Bookmark Above It
https://bugs.kde.org/show_bug.cgi?id=483029 Jon changed: What|Removed |Added CC||jonste...@gmail.com --- Comment #5 from Jon --- Related to / duplicate of: https://bugs.kde.org/show_bug.cgi?id=482687 maybe? FWIW I see all cursor interaction with Firefox being 30-ish pixels off, but only on one computer, and only when I snap firefox to left or right half of the screen. If I maximize then snap left or right all my cursor interactions are correct. Looks like this MR might have fixed it: https://invent.kde.org/plasma/kwin/-/merge_requests/5382 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483361] New: In Python API, fromXML does not generate valid ManagedColor when called with output of toXML
https://bugs.kde.org/show_bug.cgi?id=483361
Bug ID: 483361
Summary: In Python API, fromXML does not generate valid
ManagedColor when called with output of toXML
Classification: Applications
Product: krita
Version: 5.1.5
Platform: NixOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: jon.bosque.herna...@gmail.com
Target Milestone: ---
SUMMARY
```
view = Application.activeWindow().activeView()
qDebug(f"{color.fromXML(color.toXML()).toXML()}")
```
OBSERVED RESULT
Always generates None
EXPECTED RESULT
The same color that generated the XML is returned
SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: NixOS 24.05
(available in About System)
KDE Plasma Version: -
KDE Frameworks Version: -
Qt Version: -
ADDITIONAL INFORMATION
Krita
Version: 5.1.5
Hidpi: true
Qt
Version (compiled): 5.15.11
Version (loaded): 5.15.11
OS Information
Build ABI: x86_64-little_endian-lp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: linux
Kernel Version: 6.6.2
Pretty Productname: NixOS 24.05 (Uakari)
Product Type: nixos
Product Version: 24.05
Desktop: none+i3
Locale
Languages: en_US, en, en_Latn_US
C locale:
LC_CTYPE=en_US.UTF-8;LC_NUMERIC=es_ES.UTF-8;LC_TIME=es_ES.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=es_ES.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=es_ES.UTF-8;LC_NAME=es_ES.UTF-8;LC_ADDRESS=es_ES.UTF-8;LC_TELEPHONE=es_ES.UTF-8;LC_MEASUREMENT=es_ES.UTF-8;LC_IDENTIFICATION=es_ES.UTF-8
QLocale current: en
QLocale system: en
QTextCodec for locale: UTF-8
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 482743] New: Mouse position incorrect on Firefox when window snapped left or right
https://bugs.kde.org/show_bug.cgi?id=482743 Bug ID: 482743 Summary: Mouse position incorrect on Firefox when window snapped left or right Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jonste...@gmail.com Target Milestone: --- Created attachment 166611 --> https://bugs.kde.org/attachment.cgi?id=166611=edit example SUMMARY When I snap Firefox to the left or right side of the screen, mouse interactions happen at the wrong location. I have to place the mouse about 30 pixels below the thing I want to click/interact with, clicking on the target does nothing, or clicks the thing 30 pixels above. Cursor changes based on the incorrect location also. This happens mainly when I launch Firefox and snap it left or right with Meta+L|R hotkey, also when I drag window to either side. I can 'fix' this by maximizing the window, then snapping left or right. That seems to fix the issue until I close and relaunch STEPS TO REPRODUCE 1. Launch Firefox 2. Snap left or right 3. Move mouse into Firefox window, notice mouse position seems to report incorrectly, cursors change for item 30 pixels above mouse cursor, clicking interacts with that point also OBSERVED RESULT Mouse position / interactions happen 30ish pixels above cursor EXPECTED RESULT Mouse position is right SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch - plasma-meta 6.0-2 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This was an upgrade from KDE Plasma 5.X, I tried resetting Firefox profile, renamed plasma-org.kde.plasma.desktop-appletsrc, 100% scaling display, X11. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 477751] Inline Text property not saved unless using the Properties pane
https://bugs.kde.org/show_bug.cgi?id=477751 --- Comment #3 from Jon --- I didn't catch those. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 477751] Label's Text property not saved unless using the Properties pane
https://bugs.kde.org/show_bug.cgi?id=477751 Jon changed: What|Removed |Added Version|3.2.1 |3.2.0 -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 477751] New: Label's Text property not saved unless using the Properties pane
https://bugs.kde.org/show_bug.cgi?id=477751 Bug ID: 477751 Summary: Label's Text property not saved unless using the Properties pane Classification: Applications Product: KEXI Version: 3.2.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Forms Assignee: kexi-b...@kde.org Reporter: j_hi6...@icloud.com CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- Created attachment 163636 --> https://bugs.kde.org/attachment.cgi?id=163636=edit video of me demonstrating the bug I am describing SUMMARY When creating a label for a widget on a form in Kexi, text entered directly into the label doesn't seem to get retained when saved. It reverts back to its original, default Text property value (e.g., "Label", "Label 2", etc.). STEPS TO REPRODUCE 1. Open Kexi. 2. Select "New...", "Blank Database"; "File" [storage method]; fill out name and destination directory. 3. Under Create tab, select Form. 4. In Form Design tab, select Label. 5. Click and drag to create a new label in the form design area. 6. Type in desired label text (program defaults to letting you type into the label itself, not the Properties pane). 7. Click somewhere outside of label to lock its contents into place. 8. Save the form. 9. Close form. 10. Reopen form. OBSERVED RESULT Desired label text that was typed in before saving form was not retained after saving, closing, and reopening form. EXPECTED RESULT When reopening saved form, text would be what had been originally typed directly into the label upon its creation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: Ubuntu Studio 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-89-lowlatency (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 540 @ 2.53GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics ADDITIONAL INFORMATION A workaround seems to be just typing the desired label text into the Text property in the Properties pane (see attached video). I am new to Kexi, but I looked through existing bug reports and did not see one related to this. Thank you -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466554] [Usability] Autocomplete a persons name in the text box when tagging people
https://bugs.kde.org/show_bug.cgi?id=466554 Jon changed: What|Removed |Added Platform|Other |Microsoft Windows OS|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466554] New: [Usability] Autocomplete a persons name in the text box when tagging people
https://bugs.kde.org/show_bug.cgi?id=466554 Bug ID: 466554 Summary: [Usability] Autocomplete a persons name in the text box when tagging people Classification: Applications Product: digikam Version: 7.10.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jsh121...@hotmail.com Target Milestone: --- The current workflow for me is: 1. Hover over a face to tag 2. Type in 2 or 3 letters 3. Arrow down to select the persons name 4. Hit enter I would rather have the first persons name autocomplete in the text box without having to arrow through the list. This would allow me to skip step 3, and simply hit enter if the first person is the person I want. I would do it similar to a google search where the part I type is not highlighted, and the part autocompleted is highlighted. This way I can just hit backspace to stop/remove the autocomplete if I didn't need it for that tag. Thanks, Jon -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460570] Face Recognition fails (process stuck at 0%)
https://bugs.kde.org/show_bug.cgi?id=460570 Jon changed: What|Removed |Added CC||jsh121...@hotmail.com --- Comment #15 from Jon --- I'm experiencing this same issue. I think it's due to the first run of detect faces using multiple cpu cores. If I do a first run with 1 core, then the subsequent runs with multiple cores works. I think this has to happen after every startup of the digikam. My simple repro: 1. Open digikam 2. Detect faces with multiple cpu cores ENABLED 3. Progress hung at 0% 4. App is hung, so kill app. Workaround: 1. Open digikam 2. Detect faces on a small album with multiple cpu cores DISABLED 3. ENABLE multiple cpu cores 4. Detect faces on a large album -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464279] it won't let me cut and paste images doesn't work
https://bugs.kde.org/show_bug.cgi?id=464279 --- Comment #2 from jon --- I put copy image and when I paste it, it automatically goes to brush and does not paste anything and does not cut the images either. El sáb., 14 ene. 2023 15:55, wolthera escribió: > https://bugs.kde.org/show_bug.cgi?id=464279 > > wolthera changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||griffinval...@gmail.com > > --- Comment #1 from wolthera --- > Hi, > > This is too little information for a Bug Report, I can't tell what you are > trying to copy paste, how you are copy-pasting, which various ways to > copy-paste you have tried, whether you have a selection, and what kind of > image > you are working on. If you intended to file a Bug Report, I will need a > list of > steps to reproduce. > > If you just wanted help and not file a Bug Report, we recommend using > Krita-Artists.org instead. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464279] New: it won't let me cut and paste images doesn't work
https://bugs.kde.org/show_bug.cgi?id=464279 Bug ID: 464279 Summary: it won't let me cut and paste images doesn't work Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tanhause...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** it won't let me cut and paste images doesn't work STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396301] Investment Performance by Account YTD Return on Investment result different between version 4.8 and 5.01
https://bugs.kde.org/show_bug.cgi?id=396301 Jon changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Jon --- Thanks for advising that I neglected to mark my previous comment (Comment 4) as “Reported”. Please refer to that comment for other details if necessary. The first issue with the Investment Performance reports is that the Return on Investment is only calculated correctly when the Date Range selected is either All Dates or a Date Range that begins with or earlier than the first Buy transaction. All other Date Ranges calculate an incorrect Return on Investment. The reason for the incorrect result is that the Starting Balance for these other Date Ranges is calculated by KMyMoney as the number of shares held on the report’s beginning date multiplied by the share price on that date. The correct value for the Starting Balance should be the original Buy Value of those shares, not the Buy Value +/- any gain/loss in share price as of the beginning date. The second issue with the Investment Performance reports is that the Dividends Reinvestment value is being calculated as if it were a Buy Value, which results in an incorrect Return on Investment. Buy Value is the amount of cash that an investor uses to purchase new shares. Shares added to the investor’s account by the mutual fund in a Dividend or Capital Gain distribution are not a purchase made by the shareholder. The value of shares added in a reinvestment is correctly accounted for as a part of the total number the shareholder owns. The Dividends Reinvested value should not be used in any additional way in calculating Return on Investment. Dividends Paid Out are cash in the investor’s hand and this value is correctly calculated by KMyMoney as a gain in the Investment Performance reports. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396301] Investment Performance by Account YTD Return on Investment result different between version 4.8 and 5.01
https://bugs.kde.org/show_bug.cgi?id=396301 --- Comment #4 from Jon --- To answer you question, the 3.5 shares not sold are the $350 in the Ending Balance. I reviewed the information on ROI calculation in the Investopedia link you provided. As an investor, I have used this calculation many times. KMyMoney does not have the functionality to correctly make this ROI calculation. KmyMoney Handbook has the following statement about ROI in the Investment section: “Unimplemented Features There are some features that are normally associated with investments which are not yet implemented in KMyMoney. These include, but are not limited to derivatives, options, and futures. In addition, when you sell a security, KMyMoney does not know which specific shares you are selling, i.e., the oldest or the most recently purchased, so it cannot calculate return on investment. Finally, it has no direct knowledge about any country's specific tax reporting requirements, but these can usually be handled by marking as Tax related all the categories you use for transactions which might have tax consequences.” After reading this, I was curious how KMyMoney was able to do the ROI calculation for the Investment Capital Gains reports. I created another KMyMoney file with one investment account and put in several Buy and Sell transactions using made up numbers to see if I could figure out how the program was determining the buy value for each time shares were sold. It appears that the program is using a First In/First Out method (first shares bought are the first shares sold). Lacking the ability to identify the specific shares sold, this a reasonable but not accurate way to estimate capital gains. The gain is accurate only for the situation where the report date range includes all of the transaction dates and also all shares have been sold. The KMyMoney file I created included only Buy transactions for 2021. For 2022 I included one Buy transactions and two Sell transactions that sold all shares. Total Buy value for 2021 was $1295 and another $210 for 2022, for a grand total of $1505. The total Sell value was $1340. The ROI calculation is therefore ($1340 – $1505) / $1505 = a 10.96% loss. The Capital Gains report in KMyMoney matches this result. When I ran the Investment Performance report with a date range of All Dates, I see Beginning Balance $0, Buy Value $1505, Sell Value $1340, Ending Balance $0 and ROI of 10.96% loss, matching the Capital Gains report. However, a different result happens when I use the default report date range of Year to Date. In that case I see Beginning Balance of $1500, Buy Value $210, Sell Value $1340, Ending Balance $0 and ROI of 21.64% loss. Since all shares that were bought were sold, this is obviously an incorrect result. The problem is that the shares bought in 2021 had an increase in share price by the end of the year bringing the ending value of the shares to $1500. The Beginning Balance for 2022 should have been the ending Buy Value for 2021 of $1295, not the Investment Value based on the year end share price. There are two types of investment gains. When shares are sold we have “realized” gains as above. If not all shares are sold we also have “unrealized” gains. Unrealized gains are calculated as the increase or decrease in share value based on the current share price minus the buy value of the shares. Unrealized gains vary from day to day as share prices change due to market activity. Unrealized gains are part of the performance of an investment. The Investment Performance report does not use the unrealized gain value as the Ending Balance. Instead, it uses the full value of the shares at the ending price. This is wrong. The report calculates the ROI by adding the Ending Balance to the Sell Value. The Ending Balance needs to be the unrealized gain amount, not the ending shares value. A better title for Ending Balance would be Unrealized Gain/Loss. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396301] Investment Performance by Account YTD Return on Investment result different between version 4.8 and 5.01
https://bugs.kde.org/show_bug.cgi?id=396301 Jon changed: What|Removed |Added Status|NEEDSINFO |REPORTED Version|5.0.1 |5.1.2 Resolution|WAITINGFORINFO |--- --- Comment #2 from Jon --- I am currently using KmyMoney version 5.1.2 running on Linux Mint version 21. The Investment Performance By Account report continues to miscalculate the Return on Investment for those investments that have some or all Dividends Reinvested. The report correctly calculates Return on Investment for all other situations, including when all Dividends are Paid Out. Using the column headings on the report, I believe that Return on Investment should be calculated as follows: (Ending Balance + Dividends Paid Out + Sell Value) – (Starting Balance + Buy Value) = Return The % Return is then calculated by: 100 * Return / (Starting Balance + Buy Value) Dividends Reinvested are not an item included in the return calculation because the value of the shares from the reinvestment is already part of the Ending Balance. I created a KmyMoney file with only 4 transactions as a test. The share price for all transactions is set to $100 so that price changes could be ruled out of the issue. For the Dividends Paid Out situation: Starting Balance transaction – 12/31/21 buy 8 shares at $100/share = $800 Buy Value transaction – 3/22/22 buy 4 shares at $100/share = $400 Dividends Paid Out transaction – 6/30/22 = $150 Sell Value transaction – 12/2/22 sell 10 shares at $100/share = $1,000 Ending Balance = $200 ($200 + $150 + $1,000) - ($800 + $400) = $150 Return $150 / ($800 + $400) = 0.125 * 100 = 12.5% The The Investment Performance By Account report agrees with this result. For the Dividends Reinvested situation: Starting Balance transaction – 12/31/21 buy 8 shares at $100/share = $800 Buy Value transaction – 3/22/22 buy 4 shares at $100/share = $400 Dividends Reinvested transaction – 6/30/22 = 1.5 shares added at $100/share Sell Value transaction – 12/2/22 sell 10 shares at $100/share = $1,000 Ending Balance = $350 ($350 + $0 + $1,000) - ($800 + $400) = $150 Return $150 / ($800 + $400) = 0.125 * 100 = 12.5% For this case the The Investment Performance By Account report shows an incorrect 0% return and strangely, a 15.51% Annualized Return. How can a zero return also have a greater than zero annualized return? I only invest in mutual funds so do not know whether the calculation is different for individual stocks or bonds. When a mutual fund does a dividend reinvestment they simply add the number of shares that match the dividend value at the current price. This is not a Buy transaction. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 421909] Konqueror crash on reboot
https://bugs.kde.org/show_bug.cgi?id=421909 Jon Fincher changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #3 from Jon Fincher --- It hasn't repro'd with the latest version, so I think this can be closed as such. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458773] New: Scheduler Prevents Meridian Flip
https://bugs.kde.org/show_bug.cgi?id=458773 Bug ID: 458773 Summary: Scheduler Prevents Meridian Flip Product: kstars Version: 3.6.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jbry...@comcast.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** While acquiring dark frames Kstars attempted a meridian flip and failed with the following log entries: 2022-09-05T23:03:54 Meridian flip completed. 2022-09-05T23:03:54 meridian flip failed, retrying in 4 minutes 2022-09-05T23:03:53 Meridian flip slew started... 2022-09-05T23:03:53 Meridian flip started. 2022-09-05T23:03:32 Meridian flip waiting. I stopped the Scheduler and after the four minutes had elapsed the meridian flip was successful, at which point I restarted the Scheduler. I'm guiding with PHD2, but was not guiding at the time because I was taking dark frames. I've consistently had the same failure while guiding. This was the first time that I thought to stop the Scheduler. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458729] New: After Dark Frames Kstars Doesn't ask for cover to be removed
https://bugs.kde.org/show_bug.cgi?id=458729 Bug ID: 458729 Summary: After Dark Frames Kstars Doesn't ask for cover to be removed Product: kstars Version: 3.6.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jbry...@comcast.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After taking dark frames the Scheduler immediately moves to the next job and starts trying to plate solve. After I scamper outside and take off the cover, it solves and slews to the target, THEN it asks me to remove the cover. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451687] Attempted Meridian Flip causes great confusion
https://bugs.kde.org/show_bug.cgi?id=451687 --- Comment #2 from Jon Bryan --- I just haven’t had any success with flips lately, so I’ve been scheduling around them. It fails without ever moving the mount. I think there must be something basic that I’m missing. We’ve had a very unusual couple of months of cloudy nights, but the monsoon flow up from Baja has shifted now and I’ve gotten a couple of good nights in. I’ll get back around to it eventually, but I’m having other problems with Kstars (3.6.0) failing in various ways after I go to bed. I really want to like it, but it’s not very reliable for me. -Jon > On Sep 4, 2022, at 6:07 AM, Wolfgang Reissenberger > wrote: > > https://bugs.kde.org/show_bug.cgi?id=451687 > > Wolfgang Reissenberger changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > CC||wreis...@gmx.de > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Wolfgang Reissenberger --- > Sorry for the late response. Do you have the logs available? If not, could you > reproduce the same with the latest KStars version? > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458640] PHD2 Timing Out, INDI and Kstars/PHD2 don't agree
https://bugs.kde.org/show_bug.cgi?id=458640 --- Comment #2 from Jon Bryan --- It’s happened a number of times, but this was the first time I got it going again without restarting Kstars on both ends. There may be some issue with my Xfinity router, because I’ve had several occasions when images were coming across really slow and I “fixed” it by rebooting the router, but that doesn’t seem to be related to this problem with it timing out and exposure time getting out of sync. I’ll certainly let you know if I figure out a way to reproduce it. -Jon > On Sep 3, 2022, at 10:03 AM, Rob wrote: > > https://bugs.kde.org/show_bug.cgi?id=458640 > > --- Comment #1 from Rob --- > I'm sorry this happened to you. The first question is really which thing is > causing the problem. From what you said, it could possibly be KStars, or > INDI, > or PHD2, something with the network, or something with the camera. Is this > problem easily reproducible? Maybe try playing with it in the daytime and see > if you can repeat it? If you can reproduce it, then we can narrow down what > could be causing the problem by eliminating variables. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458640] New: PHD2 Timing Out, INDI and Kstars/PHD2 don't agree
https://bugs.kde.org/show_bug.cgi?id=458640 Bug ID: 458640 Summary: PHD2 Timing Out, INDI and Kstars/PHD2 don't agree Product: kstars Version: 3.6.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jbry...@comcast.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I am running 3.6.0 on my MacBook connected to my rig, and 3.6.0 on my iMac in the house to control it remotely. I had a problem (again) last night with PHD2 timing out while trying to download from my ASI120MM guide camera. After trying multiple times, restarting INDI, restarting Kstars on the iMac, I went into the INDI camera settings and discovered that the exposure time was set to a very small value, even though I'm sure that Kstars and PHD2 both thought it was at 2 seconds. I set it to 2 in the INDI camera configuration and tried again, and it worked! Now I have to moan a little. I started up my sequence and went to bed, since it was 2:30 by that point. Then when I got up and checked at 6:30 I discovered that it had taken six exposures and crashed hard out of Kstars. Really disappointing, since the seeing was first-rate for the first time in weeks, and my little mount was consistently guiding better than an arc-second as long as the wind wasn't blowing. I could really love Kstars if it didn't do these things to me. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 457425] Cmd-F Crashes Every Time
https://bugs.kde.org/show_bug.cgi?id=457425 --- Comment #6 from Jon Bryan --- Oops. I didn't. Last night was a bust, windy and then clouds rolled in, and I didn’t take the cue that it was a new 3.6.0. I don’t have everything fully up and running PHD2/remote MacBook/scope, but it didn’t crash when I tried it just now, so that’s promising. -Jon > On Aug 29, 2022, at 4:38 AM, Rob wrote: > > https://bugs.kde.org/show_bug.cgi?id=457425 > > --- Comment #5 from Rob --- > Are you trying the latest dmg that I posted here? > > https://edu.kde.org/kstars/#download > > Because it definitely was doing what you described, but a more recent commit > fixed the issue and put into the stable 3.6.0 and then I rebuilt the dmg and > replaced the former file. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 457425] Cmd-F Crashes Every Time
https://bugs.kde.org/show_bug.cgi?id=457425 --- Comment #4 from Jon Bryan --- Oh, and it crashes no matter where it tries to search from, including the Scheduler. -Jon > On Aug 26, 2022, at 11:09 PM, Rob wrote: > > https://bugs.kde.org/show_bug.cgi?id=457425 > > --- Comment #2 from Rob --- > It has taken me some time to work through several issues, but I think the > 3.6.0 > is now a pretty good one. Please check to see if it is improved. Based on > what you said here, I think you were having the issue with opening the Find > Dialog which had been changed to load asynchronously in 3.6.0. There was an > issue in that code, so it was modified yesterday to no longer load items > asynchronously. The fix is now in both the current DMG on the Kstars kde > website and the nightly releases. So please check and I hope it is all better > now. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 457425] Cmd-F Crashes Every Time
https://bugs.kde.org/show_bug.cgi?id=457425 --- Comment #3 from Jon Bryan --- Well, I finally caught a break after six weeks of cloudy nights, and the problem persists on my 27” iMac. Trying to find something instantly crashes completely out of Kstars in 3.6.0. I fought with 3.5.9 for three hours, after it suddenly decided it wouldn’t connect to my guide camera through PHD2 any more, before deciding to try 3.6.0 again. At least I can click on things, but trying to find something results in an instant crash every time. -Jon > On Aug 26, 2022, at 11:09 PM, Rob wrote: > > https://bugs.kde.org/show_bug.cgi?id=457425 > > --- Comment #2 from Rob --- > It has taken me some time to work through several issues, but I think the > 3.6.0 > is now a pretty good one. Please check to see if it is improved. Based on > what you said here, I think you were having the issue with opening the Find > Dialog which had been changed to load asynchronously in 3.6.0. There was an > issue in that code, so it was modified yesterday to no longer load items > asynchronously. The fix is now in both the current DMG on the Kstars kde > website and the nightly releases. So please check and I hope it is all better > now. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 457425] New: Cmd-F Crashes Every Time
https://bugs.kde.org/show_bug.cgi?id=457425 Bug ID: 457425 Summary: Cmd-F Crashes Every Time Product: kstars Version: 3.6.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jbry...@comcast.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Cmd-F crashes straight out. I reverted to 3.5.9. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453767] New: SailfishOS sailfish connect app and iPad cant see each other
https://bugs.kde.org/show_bug.cgi?id=453767 Bug ID: 453767 Summary: SailfishOS sailfish connect app and iPad cant see each other Product: kdeconnect Version: unspecified Platform: Other OS: iOS Status: REPORTED Severity: normal Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: j...@proverb2.co.uk Target Milestone: --- Tried discovery and also via IP address but neither device appears on the other SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451850] Multiline Title No Shadow
https://bugs.kde.org/show_bug.cgi?id=451850 jon changed: What|Removed |Added Flags|low_hanging+|low_hanging? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451850] Multiline Title No Shadow
https://bugs.kde.org/show_bug.cgi?id=451850 jon changed: What|Removed |Added Flags||corner_case+, low_hanging+, ||Usability? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451850] Multiline Title No Shadow
https://bugs.kde.org/show_bug.cgi?id=451850 --- Comment #9 from jon --- (In reply to emohr from comment #8) > Now I get your point. Right click in the project bin -> Add Template Title > -> put text into the left window -> click OK. Only the template text itself > gets applied! > > It's that what you mean? If so, that’s a bug and should definitely not > happen. It should take over the text format from the template to the new > entered text. Yes, thats it. (Except the left window says Apply for me, not OK) Well, it takes over the text format perfectly for the first line and the text color seems to remain on all lines, but the text shadow only gets taken over in the first line and then there is no more shadow. (Haven't tried other effects) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451850] Multiline Title No Shadow
https://bugs.kde.org/show_bug.cgi?id=451850 --- Comment #7 from jon --- (In reply to emohr from comment #6) > Do you edit the title in the clip properties? This doesn't work. You have to > click on Edit Clip in the clip properties to make your change direct in the > titler. Then the shadow should appear. Yes I do that. (would like to do that) Isn't this the whole concept of a Template-Title? Pull in the Template, change the text and be done with it. If I have to open the titler than why even use the Template-Title? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451850] Multiline Title No Shadow
https://bugs.kde.org/show_bug.cgi?id=451850 --- Comment #5 from jon --- (In reply to emohr from comment #3) > We made some title update lately. I tested with the latest nightly build and > I guess it's fixed. I took a template with shadow text and create a new line > by pressing enter and the text in the new line still has shadow. > > Here you can download the latest nigthly build for testing: > https://binary-factory.kde.org/job/Kdenlive_Nightly_mingw64/ > lastSuccessfulBuild/artifact/ Unfortunately still broken for me in Version 22.07.70 (rev. 891c109c3), shown in attachment. (Unfortunately botched putting reply and attachment in sthe same comment.) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451850] Multiline Title No Shadow
https://bugs.kde.org/show_bug.cgi?id=451850 --- Comment #4 from jon --- Created attachment 148404 --> https://bugs.kde.org/attachment.cgi?id=148404=edit still_broken -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451850] Multiline Title No Shadow
https://bugs.kde.org/show_bug.cgi?id=451850 jon changed: What|Removed |Added CC||jofom98...@wowcg.com --- Comment #2 from jon --- (In reply to emohr from comment #1) > How do you have created the screenshot with the text "Multiline, Text"? > > The shadow gets only applied to the same "text box". Shadow is not a general > title setting. If you create a new text within the title no shadow is > applied. Not OP but just rant into the same bug. I guess the screenshot was created by just using a template title. (Personally I used this tutorial to achieve this: https://docs.kdenlive.org/en/effects_and_compositions/titles.html#template-titles-user-defined) As soon as you press "enter" when using the template to create a linebreak the observed effect happens. (The shadow gets "forgotten" in the new line, despite being in the same textbox) -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452116] New: Prompts don't get focus
https://bugs.kde.org/show_bug.cgi?id=452116 Bug ID: 452116 Summary: Prompts don't get focus Product: kstars Version: 3.5.8 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jbry...@comcast.net Target Milestone: --- SUMMARY *** Pop-up prompts come up behind the Ekos window. Hard to respond to something you can't see. It happens for everything, including submitting this bug report. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451687] Attempted Meridian Flip causes great confusion
https://bugs.kde.org/show_bug.cgi?id=451687 Jon Bryan changed: What|Removed |Added CC||jbry...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451687] New: Attempted Meridian Flip causes great confusion
https://bugs.kde.org/show_bug.cgi?id=451687 Bug ID: 451687 Summary: Attempted Meridian Flip causes great confusion Product: kstars Version: 3.5.7 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jbry...@comcast.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Running KStars/Ekos remotely on a MacBook Pro, controlling with an iMac in the house. Using PHD2 to guide. I had split the job into a pre-meridian sequence, darks, and post-meridian, imaging M 106. At the conclusion of the dark acquisition, the mount was reporting only about three minutes to the flip. I paused the Scheduler, leaving the mount tracking and PHD2 guiding. When it came time for the flip, it reported failure, and said it would try again in three-something minutes. I noticed that the mount was offset somewhat from the target. I tried to capture and slew to it, but the mount wouldn't move. I selected a number of other objects in the vicinity and had no problem solving and centering them. No matter what I tried, it would no longer solve and center M 106 in the reticle. I eventually realized that PHD2 was interfering somehow (though no longer guiding), and killed and restarted it. I was then able to capture, solve and slew to M 106. I deleted the pre-meridian and dark jobs in the scheduler, re-started it and completed the post-meridian job. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 11.6.4 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.
[frameworks-solid] [Bug 355024] No device appears after after plug-in Nikon camera to USB
https://bugs.kde.org/show_bug.cgi?id=355024 --- Comment #9 from Jon --- (In reply to postix from comment #8) > wiew...@gmail.com, do you still see no notification with the latest > frameworks? > > (In reply to Jon from comment #7) > > Works fine here. > I guess this can otherwise be closed then or marked as a dup of #206120 The device notifier now offers me 3 choicesfor my camera: Download w/ digicam view w/ FileManager Download w/ Gwenview Currently I am using kernel 5.3.18-150300.59.49-default #1 SMP Mon Feb 7 14:40:20 UTC 2022 (77d9d02) x86_64 x86_64 x86_64 GNU/Linux Yes, please close this ticket Thanks for fixing this issue. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 450808] New: Hour Angle Limit sometimes causes aborted moves when Parking and Polar Aligning
https://bugs.kde.org/show_bug.cgi?id=450808 Bug ID: 450808 Summary: Hour Angle Limit sometimes causes aborted moves when Parking and Polar Aligning Product: kstars Version: 3.5.6 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jbry...@comcast.net Target Milestone: --- SUMMARY *** Turning off the HA Limit seems to have "cured" it. I don't know if this would be considered a bug or a feature, but it doesn't seem right. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 355024] No device appears after after plug-in Nikon camera to USB
https://bugs.kde.org/show_bug.cgi?id=355024 --- Comment #7 from Jon --- (In reply to Graham Perrin from comment #6) > Please: with the most recent software, is this still an issue? re: comment #3, 2015-11-18 01:17:50 UTC Works fine here. openSuse Leap 15.3, kernel 5.3.18-59.37 KDE Plasma 5.18.6, KDE Frameworks 5.76.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446936] git master - Cursor appears dark/corrupted with RDNA2 gpu under Wayland
https://bugs.kde.org/show_bug.cgi?id=446936 --- Comment #1 from Jon Voss --- As suspected, reverting these commits in kwin made the cursor appear normal again: 3fb14035 backends/drm: only use atomic gamma size with AMS 4206046f Re-enable proper gamma ramps with AMS I mispoke on the MR - the correct MR is: https://invent.kde.org/plasma/kwin/-/merge_requests/1472 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446936] New: git master - Cursor appears dark/corrupted with RDNA2 gpu under Wayland
https://bugs.kde.org/show_bug.cgi?id=446936 Bug ID: 446936 Summary: git master - Cursor appears dark/corrupted with RDNA2 gpu under Wayland Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: jonv...@outlook.com Target Milestone: --- SUMMARY Running the latest git master build of Plasma Wayland on a Radeon 6700XT, the cursor appears darker than it should be. Sort of a "corrupted" state. I believe this is related to the gamma changes in MR https://invent.kde.org/plasma/kwin/-/merge_requests/1335 - using the full gamma ramp from the kernel driver causes an issue with the coloring of the cursor. This happens under X11 as well, and not just with Plasma. Under X11, the issue can be mitigated by using the modesetting driver and disabling the UseGammaLUT option. It looks like this is an issue with amdgpu, there has been an open issue over for quite a while: https://gitlab.freedesktop.org/drm/amd/-/issues/1513 I would grab a screenshot, but it doesn't show up well. The best example is in the issue above. Submitting this for awareness and tracking. SOFTWARE/OS VERSIONS Operating System: Arch Linux Kernel Version: 5.15.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 --- Comment #19 from Jon Voss --- I was able to compile git master and it appears this may be fixed there. I haven't tested extensively, but a couple of reboots didn't hang. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 --- Comment #11 from Jon Voss --- Reporting back that 5.23.4 does not fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444510] Mouse cursor acts weird with flat acceleration profile in plasma-wayland
https://bugs.kde.org/show_bug.cgi?id=444510 --- Comment #2 from Jon Voss --- Just updated to 5.23.4. Issue still exists. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444510] Mouse cursor acts weird with flat acceleration profile in plasma-wayland
https://bugs.kde.org/show_bug.cgi?id=444510 Jon Voss changed: What|Removed |Added CC||jonv...@outlook.com --- Comment #1 from Jon Voss --- I also have this issue. Moving the mouse in a very specific direction in-game (center to top left) seems to drop input. My profile is set to flat as well. Doesn’t seem to be as bad at higher DPI levels, but very noticeable at 800dpi. Happens on Wayland only, no issue on X. Mouse is running at a 1000hz polling rate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 --- Comment #10 from Jon Voss --- (In reply to Aleix Pol from comment #6) > Would you be able to test git master there? > f377696bff39e35ae0f7ae6104d8732b3856744e could help address this issue. > > Otherwise, could you try enabling systemd boot for Plasma and see if it > addresses the problem for you? > https://invent.kde.org/plasma/plasma-workspace/-/wikis/Plasma-and-the- > systemd-boot Using systemd boot for the session doesn't fix. Will that MR be included in 5.23.4? If so, I will let you know if it resolves when it hits the repo next week. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 --- Comment #3 from Jon Voss --- (In reply to Schlaefer from comment #2) > > SUMMARY > > When issuing a shutdown or restart from within a Plasma Wayland session, > > there is a 1 min. 30 sec. delay while waiting for systemd to stop Simple > > Desktop Display Manager. This times out and forces a SIGKILL to sddm and > > associated processes. > > Same here. > > The issue started using the 15.15 kernel. Check with 5.10-LTS seems fine. > Confirmed. I downgraded to kernel 5.14.16 and the issue went away. Shutdown is immediate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 --- Comment #1 from Jon Voss --- Created attachment 143524 --> https://bugs.kde.org/attachment.cgi?id=143524=edit tail of journal where issue occurred -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] New: Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 Bug ID: 445449 Summary: Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM Product: kwin Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jonv...@outlook.com Target Milestone: --- Created attachment 143523 --> https://bugs.kde.org/attachment.cgi?id=143523=edit picture of issue SUMMARY When issuing a shutdown or restart from within a Plasma Wayland session, there is a 1 min. 30 sec. delay while waiting for systemd to stop Simple Desktop Display Manager. This times out and forces a SIGKILL to sddm and associated processes. If I log out of my session and shutdown/reboot directly from sddm, this issue does not occur. Shutdown is instantaneous. I cannot reproduce in the X11 session. It only occurs in Wayland. It also did not occur prior to 5.23.3. A relevant portion of my shutdown log is attached. Not much to see, unfortunately. Let me know if I can help in any way. STEPS TO REPRODUCE 1. Log in to Plasma Wayland 2. Applcation Launcher -> Shutdown (or Restart) OBSERVED RESULT Shutdown hangs on SDDM. EXPECTED RESULT Shutdown should be instantaneous. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT ADDITIONAL INFORMATION Does this fix? https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1177 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 443430] New: Kontact crashes when starts
https://bugs.kde.org/show_bug.cgi?id=443430 Bug ID: 443430 Summary: Kontact crashes when starts Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: join...@gmail.com Target Milestone: --- Application: kontact (5.18.1 (21.08.1)) Qt Version: 5.15.3 Frameworks Version: 5.86.0 Operating System: Linux 4.15.0-134-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: -Start application. I have pushed in the application (kontact) starter and kontact has crashed. But some seconds later, kontact has started without doing nothing. It has happened several times The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [New LWP 25057] [New LWP 25058] [New LWP 25059] [New LWP 25060] [New LWP 25061] [New LWP 25116] [New LWP 25118] [New LWP 25124] [New LWP 25125] [New LWP 25126] [New LWP 25131] [New LWP 25133] [New LWP 25153] [New LWP 25155] [New LWP 25210] [New LWP 25211] [New LWP 25214] [New LWP 25215] [New LWP 25218] [New LWP 25602] [New LWP 25621] [New LWP 26071] [New LWP 26078] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f245b8a6aff in __GI___poll (fds=0x7ffe43ba6278, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f2446d8b200 (LWP 25054))] Thread 24 (Thread 0x7f241a7fc700 (LWP 26078)): #0 0x7f2451b7f48e in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f245be765eb in QEventDispatcherGlib::processEvents (this=0x7f240c0683e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #2 0x7f245be1a87b in QEventLoop::exec (this=this@entry=0x7f241a7fb3a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #3 0x7f245bc34292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #4 0x7f245bc3542c in QThreadPrivate::start (arg=0x564799e60f90) at thread/qthread_unix.cpp:329 #5 0x7f24526f1609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f245b8b3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f23e8fe8700 (LWP 26071)): #0 0x7ffe43bc3b62 in clock_gettime () #1 0x7f245b871235 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f23e8fe7110) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38 #2 0x7f245be75eb5 in qt_clock_gettime (ts=0x7f23e8fe7110, clock=1) at kernel/qelapsedtimer_unix.cpp:175 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f245be7474d in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f2400021ff0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f245be74d29 in QTimerInfoList::timerWait (this=0x7f2400021ff0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f245be76346 in timerSourcePrepareHelper (timeout=0x7f23e8fe71d4, src=) at kernel/qeventdispatcher_glib.cpp:162 #8 timerSourcePrepare (source=, timeout=0x7f23e8fe71d4) at kernel/qeventdispatcher_glib.cpp:166 #9 0x7f2451b7e8ef in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f2451b7f29b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f2451b7f4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f245be765eb in QEventDispatcherGlib::processEvents (this=0x7f2400022060, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7f245be1a87b in QEventLoop::exec (this=this@entry=0x7f23e8fe73a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #14 0x7f245bc34292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #15 0x7f245bc3542c in QThreadPrivate::start (arg=0x56479b1bd320) at thread/qthread_unix.cpp:329 #16 0x7f24526f1609 in start_thread (arg=) at pthread_create.c:477 #17 0x7f245b8b3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f23dc750700 (LWP 25621)): #0 0x7f245b8a6aff in __GI___poll (fds=0x7f24400663d0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f23f659b1d6 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f23f658c841 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f23f658cec3 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f23f658cf70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f23f659b11d in ??
[systemsettings] [Bug 438684] New: System Setting crashes when switching between entries
https://bugs.kde.org/show_bug.cgi?id=438684 Bug ID: 438684 Summary: System Setting crashes when switching between entries Product: systemsettings Version: 5.21.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jfinche...@gmail.com Target Milestone: --- Application: systemsettings5 (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.9-1-MANJARO x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Manjaro Linux -- Information about the crash: - What I was doing when the application crashed: Switching from Display setting to Power settings and back quickly The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7fa154007875 in QObjectPrivate::addConnection(int, QObjectPrivate::Connection*) () at /usr/lib/libQt5Core.so.5 #5 0x7fa15400c35c in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () at /usr/lib/libQt5Core.so.5 #6 0x7fa15400c836 in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () at /usr/lib/libQt5Core.so.5 #7 0x7fa111fa2d17 in () at /usr/lib/qt/qml/org/kde/kirigami.2/libkirigamiplugin.so #8 0x7fa1530c3456 in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib/libQt5Qml.so.5 #9 0x7fa1530c656a in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () at /usr/lib/libQt5Qml.so.5 #10 0x7fa1530c6b10 in QQmlObjectCreator::setupBindings(bool) () at /usr/lib/libQt5Qml.so.5 #11 0x7fa1530c29c4 in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () at /usr/lib/libQt5Qml.so.5 #12 0x7fa1530c39e5 in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib/libQt5Qml.so.5 #13 0x7fa1530c4676 in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () at /usr/lib/libQt5Qml.so.5 #14 0x7fa1530c3dff in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib/libQt5Qml.so.5 #15 0x7fa1530c656a in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () at /usr/lib/libQt5Qml.so.5 #16 0x7fa1530c6b10 in QQmlObjectCreator::setupBindings(bool) () at /usr/lib/libQt5Qml.so.5 #17 0x7fa1530c29c4 in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () at /usr/lib/libQt5Qml.so.5 #18 0x7fa1530c39e5 in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib/libQt5Qml.so.5 #19 0x7fa1530c4676 in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () at /usr/lib/libQt5Qml.so.5 #20 0x7fa1530c3dff in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib/libQt5Qml.so.5 #21 0x7fa1530c4676 in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () at /usr/lib/libQt5Qml.so.5 #22 0x7fa15304ffa5 in QQmlComponentPrivate::beginCreate(QQmlContextData*) () at /usr/lib/libQt5Qml.so.5 #23 0x7fa1530509fb in QQmlComponent::create(QQmlContext*) () at /usr/lib/libQt5Qml.so.5 #24 0x7fa1557ce8c1 in () at /usr/lib/libKF5KCMUtils.so.5 #25 0x7fa1557cb836 in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () at /usr/lib/libKF5KCMUtils.so.5 #26 0x7fa1557d4298 in () at /usr/lib/libKF5KCMUtils.so.5 #27 0x7fa1557d4b6b in KCModuleProxy::realModule() const () at /usr/lib/libKF5KCMUtils.so.5 #28 0x7fa1557d52b4 in KCModuleProxy::showEvent(QShowEvent*) () at /usr/lib/libKF5KCMUtils.so.5 #29 0x7fa154bf10be in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x7fa154badd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #31 0x7fa153fde00a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #32 0x7fa154bed8a8 in QWidgetPrivate::show_helper() () at /usr/lib/libQt5Widgets.so.5 #33 0x7fa154bed7fa in QWidgetPrivate::showChildren(bool) () at /usr/lib/libQt5Widgets.so.5 #34 0x7fa154bed882 in QWidgetPrivate::show_helper() () at /usr/lib/libQt5Widgets.so.5 #35 0x7fa154bf0bbd in QWidgetPrivate::setVisible(bool) () at /usr/lib/libQt5Widgets.so.5 #36 0x7fa154bed7db in QWidgetPrivate::showChildren(bool) () at /usr/lib/libQt5Widgets.so.5 #37 0x7fa154bed882 in QWidgetPrivate::show_helper() () at /usr/lib/libQt5Widgets.so.5 #38 0x7fa154bf0bbd in QWidgetPrivate::setVisible(bool) () at
[kmymoney] [Bug 437757] Add ability to enter splits when scheduling a payment
https://bugs.kde.org/show_bug.cgi?id=437757 --- Comment #2 from Jon Albright --- You're correct. I looked for that and obviously had a brain fart. Jon On May 27, 2021, 3:36 PM -1000, Jeremy Whiting , wrote: > https://bugs.kde.org/show_bug.cgi?id=437757 > > Jeremy Whiting changed: > > What |Removed |Added > > CC| |jpwhit...@kde.org > > --- Comment #1 from Jeremy Whiting --- > I think that's already possible. At least I'm able to here on a 6 month old > build by clicking the button to the right of the dropdown "Transfer to:" Just > to the left of "Next due date:" label. Clicking that opens the split editor > and > allows adding whatever splits are needed. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 437757] New: Add ability to enter splits when scheduling a payment
https://bugs.kde.org/show_bug.cgi?id=437757 Bug ID: 437757 Summary: Add ability to enter splits when scheduling a payment Product: kmymoney Version: 5.1.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jon.albri...@outlook.com Target Milestone: --- SUMMARY The schedules I am running have to be edited once they have run in order to split apart a payment from the interest charge. Having the ability to enter a split for the transaction would be so much appreciated. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 437726] New: Add specific day of a week for Scheduler to run
https://bugs.kde.org/show_bug.cgi?id=437726 Bug ID: 437726 Summary: Add specific day of a week for Scheduler to run Product: kmymoney Version: 5.1.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jon.albri...@outlook.com Target Milestone: --- SUMMARY I have a need that may fit with a lot of others. i have payments due on the first friday of every month along with others due on the last friday of every month. i cannot find a way with the current scheduler to accomplish this. Is there a way that this feature can be added to KMYmoney? I do hope this is correct place to make feature requests. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 professional 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.
[kmymoney] [Bug 333093] Enhanced Scheduling needed
https://bugs.kde.org/show_bug.cgi?id=333093 Jon Albright changed: What|Removed |Added CC||jon.albri...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434128] Plasma crashes while trying to move a desktop file to the trash using the delete key in Show Desktop mode
https://bugs.kde.org/show_bug.cgi?id=434128 Jon changed: What|Removed |Added CC||levyjon1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 431238] autostart with tray on, doesn't appear when application is closed
https://bugs.kde.org/show_bug.cgi?id=431238 Jon Severinsson changed: What|Removed |Added CC||j...@severinsson.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 418227] Screens scaling 150%: bad font rendering when moving konsole from laptop screen to extern 4k monitor
https://bugs.kde.org/show_bug.cgi?id=418227 Jon Severinsson changed: What|Removed |Added CC||j...@severinsson.net --- Comment #4 from Jon Severinsson --- I'm seeing the same / a very similar issue on my desktop with two displays, one 32" 4k display with a scaling factor of 2, and one rotated 24" 1920x1200 display with a scaling factor of 1.5: $ xrandr | grep " connected " DisplayPort-0 connected primary 3840x2160+1200+0 (normal left inverted right x axis y axis) 697mm x 392mm DVI-D-0 connected 1200x1920+0+0 left (normal left inverted right x axis y axis) 518mm x 324mm $ env | grep SCALE_FACTOR QT_SCREEN_SCALE_FACTORS=DisplayPort-0=2;DVI-D-0=1.5 QT_AUTO_SCREEN_SCALE_FACTOR=0 If I start a new Konsole tab on my big display, it looks good. If I start one on my small display, the text is distorted. Zooming in or out using ctrl and the scroll wheel fixes the text for that tab, but then the text gets distorted if I move the window to my big screen, unless I zoom in or out again. SOFTWARE/OS VERSIONS Operating System: Debian testing Konsole Version: 20.12.3 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 434483] New: "Disabled" translated to Swedish as "Aktiverad" in the KDE Plasma Desktop system-tray configuration window
https://bugs.kde.org/show_bug.cgi?id=434483 Bug ID: 434483 Summary: "Disabled" translated to Swedish as "Aktiverad" in the KDE Plasma Desktop system-tray configuration window Product: i18n Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sv Assignee: stefan.asserh...@comhem.se Reporter: j...@severinsson.net Target Milestone: --- The original en_US word "Disabled" in the system-tray configuration window is translated to Swedish as "Aktiverad" (lit. activated) rather than "Deaktiverad" (lit. deactivated) or "Inaktiverad" (lit. inactivated). I have checked that this mistranslation is still present in both SVN stable and SVN trunk (filename: .../l10n-kf5/sv/messages/plasma-workspace/plasma_applet_org.kde.plasma.private.systemtray.po) SOFTWARE/OS VERSIONS Debian: testing KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 432392] Dont started spectacle
https://bugs.kde.org/show_bug.cgi?id=432392 Jon changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Jon --- Fixed with system update. Update on last version kde-spectacle 20.12.1-0xneon+20.04+focal+build16 worked ok with libkColorPicker.so.0.1.5. Mark as resolved. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432392] Dont started spectacle
https://bugs.kde.org/show_bug.cgi?id=432392 Jon changed: What|Removed |Added Version|unspecified |20.12.1 Product|neon|Spectacle Component|Packages User Edition |General --- Comment #1 from Jon --- Bug on libkColorPicker.so version: 0.1.5-0xneon+20.04+focal+build2 Spectacle worked again if downgrade libkColorPicker.so version to: libkColorPicker.so version: 0.1.4-1+20.04+focal -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432392] Dont started spectacle
https://bugs.kde.org/show_bug.cgi?id=432392 Jon changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432392] New: Dont started spectacle
https://bugs.kde.org/show_bug.cgi?id=432392 Bug ID: 432392 Summary: Dont started spectacle Product: Spectacle Version: 20.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: termina...@yandex.ru CC: k...@david-redondo.de Target Milestone: --- SUMMARY Dont started spectacle In log jopurnal: /usr/bin/spectacle: error while loading shared libraries: libkColorPicker.so.0.1.4: cannot open shared object file: No such file or directory 20.12.1-0xneon+20.04+focal+build14 STEPS TO REPRODUCE 1. $ spectacle spectacle: error while loading shared libraries: libkColorPicker.so.0.1.4: cannot open shared object file: No such file or directory OBSERVED RESULT spectacle window dont opened EXPECTED RESULT spectacle window is opened SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.5 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION OS 64-bit KDE.neon -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432090] New: Dolphin crashes remapping fish:// path in preferences
https://bugs.kde.org/show_bug.cgi?id=432090 Bug ID: 432090 Summary: Dolphin crashes remapping fish:// path in preferences Product: dolphin Version: 20.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jonjonj...@westnet.com.au CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.1) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.4.0-62-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I had mapped to a local machine using fish:// and wanted to change the path from /"user"/home (I think it was /home) to /snap Tried twice and the same crash occurred, Tried to also map just to fish://ipaddress/ and it also crashed, I haven't used fish:// before and mapping to root or another directory is probably outside the protocol? Anyway I don't consider this to be a critical bug - at least not in my use case. - Custom settings of the application: .None that i can think of - vanilla dolphin installation etc The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 720676] [New LWP 720678] [New LWP 720679] [New LWP 720680] [New LWP 720681] [New LWP 720682] [New LWP 720687] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f016766aaff in __GI___poll (fds=0x7ffe2d42c168, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f016070c8c0 (LWP 720674))] Thread 8 (Thread 0x7f013b7fe700 (LWP 720687)): #0 0x7f016315d33d in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f01631102ce in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f01653a2fbb in QEventDispatcherGlib::processEvents (this=0x7f012c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f01653471ab in QEventLoop::exec (this=this@entry=0x7f013b7fdce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #4 0x7f0165161a12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #5 0x7f0165162bac in QThreadPrivate::start (arg=0x564b907e4420) at thread/qthread_unix.cpp:329 #6 0x7f0163adf609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f0167677293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f01561ba700 (LWP 720682)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564b90560198) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564b90560148, cond=0x564b90560170) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564b90560170, mutex=0x564b90560148) at pthread_cond_wait.c:638 #3 0x7f0157717e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f0157717a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f0163adf609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0167677293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f01569bb700 (LWP 720681)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564b90560198) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564b90560148, cond=0x564b90560170) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564b90560170, mutex=0x564b90560148) at pthread_cond_wait.c:638 #3 0x7f0157717e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f0157717a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f0163adf609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0167677293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f01571bc700 (LWP 720680)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564b90560198) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564b90560148, cond=0x564b90560170) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564b90560170, mutex=0x564b90560148) at pthread_cond_wait.c:638 #3 0x7f0157717e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f0157717a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f0163adf609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0167677293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f015c876700 (LWP 720679)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564b90560198) at
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 --- Comment #34 from Jon Intxaurbe --- (In reply to Jon Intxaurbe from comment #33) > ... > > I'm a simple KDE user. I don't have so much technical knowledge. Excuse me. I've again read my post and I've seen a hard post. I wasn't angry but tired. On the other hand, my English level doesn't help. I'm sorry. Thank you very much -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 --- Comment #33 from Jon Intxaurbe --- (In reply to Alex from comment #32) ...> I believe that you don't absolutely need admin privileges to change your own > data ... I'm a simple KDE user. I don't have so much technical knowledge. Tough in my system at least: user@Host:/var/lib/AccountsService$ ls -l guztira 8 drwxrwxr-x 2 root root 4096 abe 5 21:28 icons drwx-- 2 root root 4096 abe 5 21:28 users Users don’t have permission to write in that directory. And, of course, I haven't changed permissions. I’ve checked to change my own icon in system settings again. And password is asked for the change as you can see in these images: • https://i.postimg.cc/Pq2pHBhF/User-System-Settings-202012231.png • https://i.postimg.cc/B6zjLHjT/User-System-Settings-202012232.png • https://i.postimg.cc/3RNyxnxr/User-System-Settings-202012233.png • https://i.postimg.cc/cJsgVsqn/User-System-Settings-202012234.png • https://i.postimg.cc/D0b8q0Gt/User-System-Settings-202012235.png It’s strange than in System Settings the icon has changed at the ende, but not in /var/lib/AccountsService/icons nor in kickoff nor in SDDM too. My Operating System: KDE neon 5.20 (base Ubuntu 20.04) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 But it isn’t a new installation. It comes from KDE NEON ¿5.16? based in Ubuntu 18.04 and upgraded later. I don't want have an argument, of course, not even discuss about it I've related my experience. :-) Thank you very much for your time and effort. :-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 Jon Intxaurbe changed: What|Removed |Added CC||join...@gmail.com --- Comment #28 from Jon Intxaurbe --- Is reasonable asking for an administrator's password to change my OWN avatar? Perhaps it can be because this confirmed bug but I have thought I should tell you about this. BTW, confirmed too in my system, Operating System: KDE neon 5.20, KDE Plasma Version: 5.20.4, KDE Frameworks Version: 5.76.0, Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412018] Nightly build of KDEConnect on Windows crashes following pairing
https://bugs.kde.org/show_bug.cgi?id=412018 Jon Spriggs changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Jon Spriggs --- Wow, yes, this is a fantastic step up. I'm resolving this issue as it's all working fine! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427503] Whenever I "Create a Blank Frame", the programme crashes and closes. I have tried reset everything and the issue still persists. On the Loading Screen, it says I'm using Krita 4.3
https://bugs.kde.org/show_bug.cgi?id=427503 Jon changed: What|Removed |Added Version|unspecified |4.3.0 --- Comment #1 from Jon --- Also, I have plenty of space on my computer -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427503] New: Whenever I "Create a Blank Frame", the programme crashes and closes. I have tried reset everything and the issue still persists. On the Loading Screen, it says I'm using Krit
https://bugs.kde.org/show_bug.cgi?id=427503 Bug ID: 427503 Summary: Whenever I "Create a Blank Frame", the programme crashes and closes. I have tried reset everything and the issue still persists. On the Loading Screen, it says I'm using Krita 4.3.0 Product: krita Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: jshe...@gmail.com Target Milestone: --- SUMMARY Whenever I "Create a Blank Frame", the programme crashes and closes. I have tried reset everything and the issue still persists. On the Loading Screen, it says I'm using Krita 4.3.0 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 421194] Yakuake sometimes crashes when closing a session
https://bugs.kde.org/show_bug.cgi?id=421194 Jon changed: What|Removed |Added CC||joncook...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422099] New: Display setting crashed when discarding resolution changes.
https://bugs.kde.org/show_bug.cgi?id=422099 Bug ID: 422099 Summary: Display setting crashed when discarding resolution changes. Product: systemsettings Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jfinche...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-31-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: Changing display resolution on laptop screen with secondary monitor attached. Decided to discard resolution changes, crash when discarding. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f92ec076800 (LWP 18873))] Thread 10 (Thread 0x7f92af0e4700 (LWP 18896)): #0 __GI___libc_read (nbytes=10, buf=0x7f92af0e3bde, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=22, buf=0x7f92af0e3bde, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f92b8802955 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f92b8884416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f92b8884eb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f92b8884f70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f92b889311d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f92b883157c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f92eeb43609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f92eff96103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f92d58b5700 (LWP 18883)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:56 #1 0x7f92eff89957 in __GI___poll (fds=0x7f92c00029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7f92ee25f1ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f92ee25f2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f92f0525583 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f92f04cc4db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f92f0304785 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f92ef5b71a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f92f03059d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f92eeb43609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f92eff96103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f92d75af700 (LWP 18882)): #0 0x7f92ee26ef10 in g_poll () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f92ee25f1ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f92ee25f2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f92f0525583 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f92f04cc4db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f92f0304785 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f92ef5b71a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f92f03059d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f92eeb43609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f92eff96103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f92d7db0700 (LWP 18880)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561131382148) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5611313820f8, cond=0x561131382120) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561131382120, mutex=0x5611313820f8) at pthread_cond_wait.c:638 #3 0x7f92e266c3db in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f92e266bfeb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f92eeb43609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f92eff96103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f92e0f48700 (LWP 18879)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561131382148) at ../sysdeps/nptl/futex-internal.h:183 #1
[plasmashell] [Bug 376676] thumbnail.so causes high CPU load
https://bugs.kde.org/show_bug.cgi?id=376676 Jon changed: What|Removed |Added CC||jareyoh...@whowlft.com --- Comment #5 from Jon --- This bug is still relevant! Manifests itself, when Dolphin had a folder open where there is a file that's being modified continuously. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 421909] New: Konqueror crash on reboot
https://bugs.kde.org/show_bug.cgi?id=421909 Bug ID: 421909 Summary: Konqueror crash on reboot Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: jfinche...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 5.3.2-050302-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: Rebooting my machine. I had performed an apt upgrade the evening before, and rebooted my machine. It was sitting at the login screen, and my machien went to sleep overnight. I woke it this morning, logged in, and saw the Konqueror failed message. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f005ec78840 (LWP 6687))] Thread 22 (Thread 0x7effd9ffb700 (LWP 7020)): #0 0x7f0053c309f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5585a693ea28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0053c309f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5585a693e9d8, cond=0x5585a693ea00) at pthread_cond_wait.c:502 #2 0x7f0053c309f3 in __pthread_cond_wait (cond=0x5585a693ea00, mutex=0x5585a693e9d8) at pthread_cond_wait.c:655 #3 0x7f0028c38c95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0028c39177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0028c39f11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0028c365eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0053c2a6db in start_thread (arg=0x7effd9ffb700) at pthread_create.c:463 #8 0x7f005e4e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7effda7fc700 (LWP 7016)): #0 0x7f005e4f16ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f005e4f3474 in ___fprintf_chk (fp=0x7f005e7ae8b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f0026b176a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f0026aff9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f0026affb44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f0026b0146c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f0026af7114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f0028c09b0d in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0028c05da8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0028c2277b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0028c3a4d6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f0028c365eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7f0053c2a6db in start_thread (arg=0x7effda7fc700) at pthread_create.c:463 #12 0x7f005e4e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7effdaffd700 (LWP 7015)): #0 0x7f0053c309f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7effdaffca78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0053c309f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7effdaffca28, cond=0x7effdaffca50) at pthread_cond_wait.c:502 #2 0x7f0053c309f3 in __pthread_cond_wait (cond=0x7effdaffca50, mutex=0x7effdaffca28) at pthread_cond_wait.c:655 #3 0x7f0028c2e999 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0028c2e9c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0028c094db in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0028c05da8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0028c2277b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0028c3a4d6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0028c365eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f0053c2a6db in start_thread (arg=0x7effdaffd700) at pthread_create.c:463 #11 0x7f005e4e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7effdb7fe700 (LWP 7014)): #0 0x7f0053c309f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5585a693ea28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0053c309f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5585a693e9d8, cond=0x5585a693ea00) at pthread_cond_wait.c:502 #2 0x7f0053c309f3 in __pthread_cond_wait (cond=0x5585a693ea00, mutex=0x5585a693e9d8) at
[rust-qt-binding-generator] [Bug 419854] New: Using dates/times for properties and function arguments
https://bugs.kde.org/show_bug.cgi?id=419854 Bug ID: 419854 Summary: Using dates/times for properties and function arguments Product: rust-qt-binding-generator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: j...@vandenoever.info Reporter: jon.pache...@gmail.com Target Milestone: --- Hi, I was looking into using this project for a side-project of mine, and was wondering how to use dates/times for properties and function arguments. For the Rust side of the interface code, could the DateTime structs from the `chrono` crate be used? i.e. the Qt type -> `chrono` type mappings would be: - QDate -> NaiveDate - QTime -> NaiveTime - QDateTime -> DateTime (since QDateTime is timezone aware) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418209] New: Unable to set kcm_nightsettings start time after midnight
https://bugs.kde.org/show_bug.cgi?id=418209 Bug ID: 418209 Summary: Unable to set kcm_nightsettings start time after midnight Product: systemsettings Version: 5.18.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: clarj...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- Created attachment 126416 --> https://bugs.kde.org/attachment.cgi?id=126416=edit Image showing the error SUMMARY My sleep schedule has my wind down time starting after midnight locally. Hoping to be able to set my screen darkening during my wind down time, I was greeted by the error: "Error: Morning is before evening" I'm not sure why this would be a check, as folks sleep schedules should determine when this setting is configured, not what time morning is. STEPS TO REPRODUCE 1. Set activation time setting to "Custom time", 2. Set Turn On at: to 01:00 3. Set Turn Off at: to 11:00 OBSERVED RESULT In italics, the text "Error: Morning is before evening" appears, and dimming does not happen. EXPECTED RESULT The dimming should happen at the times the user specifies. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.5.5-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416058] Permission denied saving into "bin" folder
https://bugs.kde.org/show_bug.cgi?id=416058 --- Comment #4 from Jon --- (In reply to Jon from comment #3) > Permissions are 755: > ME@COMPUTER:~$ ls -l |grep bin > drwxr-xr-x 2 ME ME 4096 Jan 10 09:41 bin > > Then I set the permissions to 777 and the error still persisted: > ME@COMPUTER:~$ chmod -R a+w bin/ > ME@COMPUTER:~$ ls -l |grep bin > drwxrwxrwx 2 ME ME 4096 Jan 10 09:41 bin > > And finally the stats: > ME@COMPUTER:~$ stat ~/bin > File: /home/ME/bin > Size: 4096 Blocks: 8 IO Block: 4096 directory > Device: fd01h/64769d Inode: 5642408 Links: 2 > Access: (0777/drwxrwxrwx) Uid: ( 1000/s1964740) Gid: ( 1000/ME) > Access: 2020-01-10 15:28:27.033651233 + > Modify: 2020-01-10 09:41:15.266793179 + > Change: 2020-01-10 15:28:27.033651233 + > Birth: - -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416058] Permission denied saving into "bin" folder
https://bugs.kde.org/show_bug.cgi?id=416058 --- Comment #3 from Jon --- Permissions are 755: ME@COMPUTER:~$ ls -l |grep bin drwxr-xr-x 2 ME ME 4096 Jan 10 09:41 bin Then I set the permissions to 777 and the error still persisted: ME@COMPUTER:~$ chmod -R a+w bin/ ME@COMPUTER:~$ ls -l |grep bin drwxrwxrwx 2 ME ME 4096 Jan 10 09:41 bin And finally the stats: ME@COMPUTER:~$ stat ~/bin File: /home/ME/bin Size: 4096Blocks: 8 IO Block: 4096 directory Device: fd01h/64769dInode: 5642408 Links: 2 Access: (0777/drwxrwxrwx) Uid: ( 1000/s1964740) Gid: ( 1000/ME) Access: 2020-01-10 15:28:27.033651233 + Modify: 2020-01-10 09:41:15.266793179 + Change: 2020-01-10 15:28:27.033651233 + Birth: - -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416058] New: Permission denied saving into "bin" folder
https://bugs.kde.org/show_bug.cgi?id=416058 Bug ID: 416058 Summary: Permission denied saving into "bin" folder Product: okular Version: 1.7.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: j.eugs...@sms.ed.ac.uk Target Milestone: --- Ocular cannot save PDF's inside a folder that's called "bin" which lies in the home directory. Does not apply to folders with that name somewhere else in the system tree. STEPS TO REPRODUCE 1. cd ~ 2. mkdir ./bin 3. Open any PDF, edit it and save it to "~/bin" or any subfolder thereof Error message: File could not be saved in 'file:///home/USERNAME/bin/test.pdf'. Error: 'Access denied. Could not write to /home/USERNAME/bin/test.pdf.part.'. Try to save it to another location. EXPECTED RESULT This restriction seems to be put in artificially and should not be there. (Or at most there should be a warning, "Cautious bin-folders are important") SOFTWARE/OS VERSIONS Linux (x86_64) release 5.0.0-37-generic -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412018] Nightly build of KDEConnect on Windows crashes following pairing
https://bugs.kde.org/show_bug.cgi?id=412018
--- Comment #1 from Jon Spriggs ---
Last few lines from kdeconnectd run in a command prompt:
Command Line: SnoreToast.exe -t "KDE Connect Daemon" -m "Pairing request from
Personal phone" -p
C:/Users/Jon/AppData/Local/Temp/kdeconnect.daemon-jopAxT/0.png -appID
kdeconnect.daemon -pid 3916 -id 0 -pipename \\.\pipe\1580314081 -b
Accept;Reject
discarding unsupported packet "kdeconnect.runcommand.request" for "Personal
phone"
discarding unsupported packet "kdeconnect.mpris" for "Personal phone"
Notifications are disabled
Reason: DisabledForUser Please make sure that the app id is set correctly.
Command Line: SnoreToast.exe -t Slack -m "SomeText" -p
C:/Users/Jon/AppData/Local/Temp/kdeconnect.daemon-jopAxT/1.png -appID
kdeconnect.daemon -pid 3916 -id 1 -pipename \\.\pipe\1580314081 -b Reply
Notifications are disabled
Reason: DisabledForUser Please make sure that the app id is set correctly.
Command Line: SnoreToast.exe -t Slack -m "SomeText" -p
C:/Users/Jon/AppData/Local/Temp/kdeconnect.daemon-jopAxT/-2.png -appID
kdeconnect.daemon -pid 3916 -id -2 -pipename \\.\pipe\1580314081 -b Reply
Application then stops.
I noted that notifications were disabled on my system. Enabling the
notifications and restarting kdeconnectd now has a slightly longer lifespan:
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket successfully established an SSL connection
kdeconnect.core: It is a known device "Personal phone"
kdeconnect.core: Not loading plugin "kdeconnect_remotesystemvolume" because
device doesn't support it
kdeconnect.core: Not loading plugin "kdeconnect_remotecommands" because device
doesn't support it
kdeconnect.core: Not loading plugin "kdeconnect_lockdevice" because device
doesn't support it
kdeconnect.core: creating pairing handler for "someid"
kdeconnect.core: Unpair request
kdeconnect.plugin.notification: Destroying NotificationsPlugin
kdeconnect.core: Unpair request
kdeconnect.core: Unpair request
kdeconnect.core: Unpair request
kdeconnect.core: Unpair request
kdeconnect.core: Pair request
kdeconnect.plugin.battery: Deleting stale BatteryDbusInterface for "Personal
phone"
discarding unsupported packet "kdeconnect.runcommand.request" for "Personal
phone"
discarding unsupported packet "kdeconnect.mpris" for "Personal phone"
kdeconnect.core: FileTransferJob Downloading payload to
QUrl("file:///C:/Users/Jon/AppData/Local/Temp/kdeconnect_Jon/someid") size:
14430
QMetaObject::invokeMethod: No such method
KIO::StoredTransferJob::slotDataReqFromDevice()
kdeconnect.core: Finished transfer
QUrl("file:///C:/Users/Jon/AppData/Local/Temp/kdeconnect_Jon/someid")
And then, crash again.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 412018] New: Nightly build of KDEConnect on Windows crashes following pairing
https://bugs.kde.org/show_bug.cgi?id=412018 Bug ID: 412018 Summary: Nightly build of KDEConnect on Windows crashes following pairing Product: kdeconnect Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: j...@sprig.gs Target Milestone: --- SUMMARY Desktop application crashes, replacing machine name with "Failed to execute program org.kde.kdeconnect: The system cannot" in the desktop application. Service stops responding from phone application STEPS TO REPRODUCE 1. Download nightly build from https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/kdeconnect-kde-master-146-windows-msvc2017_64-cl.exe and install 2. Pair with device (either initiated Windows -> Phone or Phone -> Windows) 3. Ping device Windows -> Phone 4. Crash OBSERVED RESULT Replaced machine name with "Failed to execute program org.kde.kdeconnect: The system cannot" in the desktop application. Service stops responding, disconnecting connected devices. EXPECTED RESULT Ping on Phone or Ping on Desktop application SOFTWARE/OS VERSIONS Windows: Windows 10 Enterprise 1703 Android: 1.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409870] KDE Connect v1.12.93 problem exporting phone file system
https://bugs.kde.org/show_bug.cgi?id=409870 --- Comment #3 from Jon --- Addendum: when I tested 18.04, I used the install .iso for testing. Since then, I've upgraded my machine to the 18.04.2 release of Kubuntu and tried using kdeconnect. It gave a message of Root>run>user> [phone id ] > primary does not exist (using the 1.12.93 version of the Android app freshly installed from the Google Play Store). After trial of many things, I found that I had to go to the vertical "..." in the top right, choose "Plugin settings", "Filesystem expose", select "primary/primary:" by holding it for a few seconds, then delete it using the garbage can in the top right. I then chose "Add storage location" and added SanDisk SD card, which again gave "primary/primary:" and again paired with the laptop and the "primary" directory was now populated with subdirectories that could be browsed. It's not clear why this extra configuration is necessary---it might be deleting leftover configuration from previous trials. Still, I'm documenting this in case someone else has a similar issue. This problem persists and requires the same actions across an uninstall and re-install of the Android app from the store. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409870] KDE Connect v1.12.93 problem exporting phone file system
https://bugs.kde.org/show_bug.cgi?id=409870 --- Comment #2 from Jon --- I've verified that this is a "feature" rather than a bug. Sometime between the release of the Android KDE Connect app version 1.8.4, circa May 2018 and the 1.10 version circa November 2018, the software was updated to use the Android "Storage Access Framework", and "using /storage/emulated/0 directly is no longer allowed", according to reddit user /u/albertvaka. So, the bottom line is that if one is using Ubuntu 16.04 or earlier, they must use the 1.8.4 Android app. If using Ubuntu 18.04 or later, they may use any version after 10.1, including the current version at the Google Play Store (1.12.93). If using a 17.x release, you're on your own to figure out which works---I wasn't able to find reliable releases to download and test. I would suggest to the Android KDE Connect app folks that it would have been nice to detect being connected to an incompatible version of the desktop software and give a warning---that would have saved me some considerable time trying to figure out what was going on here. The message "/primary does not exist." in the file browser isn't very helpful in suggesting incompatible desktop vs. app software. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409870] New: KDE Connect v1.12.93 problem exporting phone file system
https://bugs.kde.org/show_bug.cgi?id=409870 Bug ID: 409870 Summary: KDE Connect v1.12.93 problem exporting phone file system Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: jfbcommerc...@gmail.com Target Milestone: --- SUMMARY I'm running KDE Connect 1.12.93 (newly installed from Google Play Store) and trying to export its file system to a Linux machine running Kubuntu 16.04.6 LTS. The phone is a Moto G7 Play, with all apps on an SD Card. When I go to "Filesystem expose" and go to the top of the tree, it shows "SanDisk SD card", which I "Select", and it gives me a box "Add storage location" with grayed out box "Storage location" containing "primary:" and "Display name" "primary". If I start a Dolphin file browser and select "motorola", I see "primary" under it, but opening that gives an error "/home//.config/kdeconnect//kdeconnect_sftp//primary does not exist." In an older version of kdeconnect (1.8.2, I believe) I was able to export "/storage/emulated/0" and everything worked correctly. I am not given a keyboard when selecting "Storage location", so I can't input "/storage/emulated/0" directly. Exporting any of the subdirectories (such as DCIM) are all referenced relative to "primary:", which, again, doesn't exist. My set-up can't be all that unique, so I'm baffled that I don't seem to be able to find many references to it when searching for it. I've tried to find references to a configuration that resolves the issue, but the only thing that seems to work is to go back to version 1.8.2. For obvious reasons, I'd like to stay current and get everything to work with the current release. Any suggestions would be much appreciated. STEPS TO REPRODUCE 1. Install kdeconnect to Kubuntu system (16.04.6 LTS) 2. Install kdeconnect v1.12.93 app to phone from Google Play Store 3. Pair to laptop 4. Test connection (Ring my phone successful). 5. Export file system (...->Plugin settings->Filesystem expose->Add storage location->Click to select 6. Browse to SanDisk SD card 7. Select 8. Storage location "primary:" (grayed out, can't be modified via keyboard) 9. OK 10. On laptop, click kdeconnect icon, select "Browse this device". 11. When browser opens, select "primary". OBSERVED RESULT Error message /home//.config/kdeconnect//kdeconnect_sftp//primary does not exist. EXPECTED RESULT Older versions (1.8.4, I believe) permitted the expose of /storage/emulated/0/, which opened correctly in the browser. It's not clear whether the failure is due to configuration of this particular phone where "primary:" should be set up in some way. SOFTWARE/OS VERSIONS Windows: no way! macOS: no Linux/KDE Plasma: 16.04.6 LTS (available in About System) KDE Plasma Version: 5.8.9 KDE Frameworks Version: 5.36.0 Qt Version: 5.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 406374] New: Show rpm scripts in properties
https://bugs.kde.org/show_bug.cgi?id=406374 Bug ID: 406374 Summary: Show rpm scripts in properties Product: ark Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: j...@moozaad.co.uk CC: rthoms...@gmail.com Target Milestone: --- There isn't a GUI app out there to examine rpms easily and I often examine the file structure of rpms when packaging or providing tech support in ark as it's super convenient. Would it be possible to add the rpm meta data into properties or somewhere else? GUI equivalent of `rpm -q --scripts` Thanks for your consideration :) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 330225] Unexpected crash of Konqueror
https://bugs.kde.org/show_bug.cgi?id=330225 --- Comment #3 from Jon Ahlquist --- After trying KDE briefly at the time that Konqueror crashed for me, I have gone back to Gnome, so I no longer have a computer with KDE to check the status of this bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356966] crash in QXcbWindow::setParent() due to NULL xcbScreen()
https://bugs.kde.org/show_bug.cgi?id=356966 Jon Burgess changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Jon Burgess --- Yes, 3 years is a long time ago. I think QT finally fixed all the NULL screen pointer issues I was seeing with X11. The only bad thing is that there seem to be similar problems handling screens disappearing in Wayland which has made me stick with X11 for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384654] found kded module "touchpad" by prepending 'kded_' to the library path, please fix your metadata
https://bugs.kde.org/show_bug.cgi?id=384654 Jon Burgess changed: What|Removed |Added CC||jburgess...@googlemail.com --- Comment #2 from Jon Burgess --- it looks like this was fixed here: https://cgit.kde.org/plasma-desktop.git/commit/?id=b10fe56678cf20688c90f15ca76c6917d830c7b5 -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 397633] kf5.kded: found kded module "colord" by prepending 'kded_' to the library path
https://bugs.kde.org/show_bug.cgi?id=397633 --- Comment #2 from Jon Burgess --- (In reply to Christoph Feck from comment #1) > So does changing the desktop file in this way fix the issue? Yes. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 397633] New: kf5.kded: found kded module "colord" by prepending 'kded_' to the library path
https://bugs.kde.org/show_bug.cgi?id=397633 Bug ID: 397633 Summary: kf5.kded: found kded module "colord" by prepending 'kded_' to the library path Product: colord-kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Daemon Module (KDED) Assignee: dantt...@gmail.com Reporter: jburgess...@googlemail.com Target Milestone: --- When I login and look at the system log messages I see the message above $ journalctl --since today | grep colord Aug 19 14:47:51 localhost.localdomain kdeinit5[837034]: kf5.kded: found kded module "colord" by prepending 'kded_' to the library path, please fix your metadata. I'm guessing that it wants this change in the desktop file: diff --git a/colord-kded/colord.desktop b/colord-kded/colord.desktop index c1086be..c07d82f 100644 --- a/colord-kded/colord.desktop +++ b/colord-kded/colord.desktop @@ -2,7 +2,7 @@ Type=Service X-KDE-ServiceTypes=KDEDModule -X-KDE-Library=colord +X-KDE-Library=kded_colord X-KDE-DBus-ModuleName=colord X-KDE-Kded-autoload=true X-KDE-Kded-phase=1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396301] New: Investment Performance by Account YTD Return on Investment result different between version 4.8 and 5.01
https://bugs.kde.org/show_bug.cgi?id=396301 Bug ID: 396301 Summary: Investment Performance by Account YTD Return on Investment result different between version 4.8 and 5.01 Product: kmymoney Version: 5.0.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: clouddrive...@gmail.com Target Milestone: --- I have been using KMyMoney version 4.8 for several years in Linux Mint 18.3. I upgraded a few days ago to Linux Mint 19 and installed KMyMoney 5.0.1 using the Software Manager. When I ran the Investment by Account YTD report I see that version 5.0.1 provides different values for Return on Investment than those provided by version 4.8. I believe (but am not certain) that version 4.8 provides the correct results. For example, I have a mutual fund bond account that pays a monthly dividend that is reinvested to buy additional shares. There have been no Buy or Sell activities this year. Version 4.8 calculates the difference between the Beginning Balance and Ending Balance and divides the result by the beginning balance then multiplies the result by 100 to convert it into the Return on Investment percentage. Version 5.0.1 gives a different answer that I have been able to duplicate by subtracting the Beginning Balance AND the Dividends Reinvested from the Ending Balance and dividing a result that again is multiplied by 100 to convert to a percentage. Because the Dividends Reinvested were used to purchase new shares that are included in the Ending Balance I see no reason to subtract the Dividends Reinvested value from the Ending Balance when calculating Return on Investment. I have another mutual fund account from which we take monthly dividends in cash (no reinvestment). There has been no Buy or Sell activity this year. Both version 4.8 and 5.0.1 calculate the same (that I believe correct) Return on Investment percentage by adding the Dividends Paid Out to the Ending Balance, subtracting the Beginning Balance and then dividing the result by the Beginning Balance and converting to a percentage. I have a third mutual fund that has quarterly Reinvested Dividends and Buy activity but no Sell activity this year. Version 4.8 calculates Return on Investment for this fund by subtracting both the Beginning Balance and Buy Value from the Ending Balance, then dividing the result by the sum of the Beginning Balance and Buy Value. The Dividends Reinvested amount is not a part of the calculation. Version 5.0.1 comes up with a lower Return on Investment that I have been unable to duplicate in any way. I have a fourth mutual fund that has quarterly Reinvested Dividends and Sell activity but no Buy activity this year. Version 4.8 calculates Return on Investment for this fund by subtracting the Sell Value from the Beginning Balance and then subtracting the result from the Ending Balance. Dividing this result by the Beginning Balance minus the Sell Value gives the Return on Investment. The Dividends Reinvested amount is not a part of the calculation. Version 5.0.1 comes up with a lower Return on Investment that I have been unable to duplicate in any way. The Annualized Return percentages for all of my individual investments are the same for both version 4.8 and 5.0.1 and also match what I calculate using the Excel XIRR function. I'm not sure about the new Annualized Return Account totals in version 5.0.1 as I haven't tried to match them in Excel as yet. Thank you in advance for any assistance in resolving the differences between version 4.8 and 5.0.1. Jon -- You are receiving this mail because: You are watching all bug changes.
