[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #12 from Mykola Krachkovsky --- > In EVERY case where krdc fails with either the blue screen and never > displaying the desktop or where krdc core dumps, I can run xfreerdp to make > the connection and it works WITHOUT ANY issue. > > It is my understanding, that krdc is at least partially using freerdp behind > the scenes so clearly something in krdc is the source of the problem since > xfreerdp works. It's not for RDP only, I can't connect to VNC as well (neither AppleVNC nor KRFB) and my bugreport was closed as duplicate of this one. So basically KRDC is unusable for now. > How can we escalate this so that it such a critical component gets some > priority ? Yes it is strange it was broken but has not fixed yet. I'd assume there is no one really maintaining it, or maybe maintainers are busy. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484608] KRDC 24.02 doesn't connect to MacOS via VNC anymore
https://bugs.kde.org/show_bug.cgi?id=484608 --- Comment #3 from Mykola Krachkovsky --- (In reply to pablo from comment #1) > Have you tried any other VNC viewer? > > My current work-around is to use TigerVNC to reach a Linux remote. I'm > curious if it's the same for you. I'm also on Tumbleweed. > > For reference, here's the Tumbleweed bug reference - > https://bugzilla.opensuse.org/show_bug.cgi?id=1222019 TigerVNC doesn't support MacOS security type (it's not standard) so doesn't connect. My workaround to use older version of KRDC from this repo: https://build.opensuse.org/project/show/home:wolfi323:branches:KDE:Frameworks5 It's installed into /opt, so could be installed at the same time as newer KRDC and works fine. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484608] New: KRDC 24.02 doesn't connect to MacOS via VNC anymore
https://bugs.kde.org/show_bug.cgi?id=484608 Bug ID: 484608 Summary: KRDC 24.02 doesn't connect to MacOS via VNC anymore Classification: Applications Product: krdc Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VNC Assignee: uwol...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- SUMMARY KRDC 24.02.1 (as was 24.02.0) doesn't connect to MacOS Apple VNC Server. MacOS Monterey 12.6.6, MacMini late 2014. KRDC 23.08.4 connects just fine. 24.02.1 built with Qt6. 23.08.4 built with Qt5. STEPS TO REPRODUCE 1. Open connection to MacOS. 2. Wait. Nothing happens. 3. If disconnect is pressed, window UI is hanged too. OBSERVED RESULT Connection hangs — neither connected nor timeouted. EXPECTED RESULT Connection expected to be successful as on v.23.08.4. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240325. (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION KRD 23.08.4 is installed in parallel (/opt) after unsuccessful connection to MacOS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479668] Software cursor image may left on last position on screen when moved to other
https://bugs.kde.org/show_bug.cgi?id=479668 --- Comment #5 from Mykola Krachkovsky --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479668] Software cursor image may left on last position on screen when moved to other
https://bugs.kde.org/show_bug.cgi?id=479668 Mykola Krachkovsky changed: What|Removed |Added Keywords||qt6, wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 --- Comment #10 from Mykola Krachkovsky --- (In reply to fanzhuyifan from comment #9) > That sounds like a separate issue. Could you open a separate bug report for > it? Thanks! Done. https://bugs.kde.org/show_bug.cgi?id=479668 > I have had similar issues with the cursor being left on the external monitor > on a dual-gpu system with intel iGPU and nvidia dGPU, but haven't been > seeing that recently. I have NVidia GPU but it's powered off (hardware LED confirms that) and no nvidia modules loaded (`lsmod | grep nv` shows only nvme modules). So I don't think it affects this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479668] New: Software cursor image may left on last position on screen when moved to other
https://bugs.kde.org/show_bug.cgi?id=479668 Bug ID: 479668 Summary: Software cursor image may left on last position on screen when moved to other Classification: Plasma Product: kwin Version: 5.92.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- SUMMARY When software cursor (Intel GPU) moved from one screen (A) to another (B) its image may be left on screen A where it was before moving to screen B. If cursor area touches screen A even slightly in different screen region, old image disappears. It simpler to reproduce this bug when cursor moves fast from A to B. STEPS TO REPRODUCE 1. Software cursor enabled. 2. Move cursor back and forth between two screens. OBSERVED RESULT Cursor image leftover. EXPECTED RESULT Only one cursor should be present. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240109 (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 KWin: 5.91.90git.20240111T181004~36222adb-78.1 ADDITIONAL INFORMATION Sometimes its hard to see second cursor. I think some windows may affect it, it easier for me to reproduce it without any windows opened. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 --- Comment #8 from Mykola Krachkovsky --- Small glitch — when cursor moved fast between screens it may be left on last position on other screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 --- Comment #7 from Mykola Krachkovsky --- Thank you, works fine now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #15 from Mykola Krachkovsky --- Thank you, it looks fine now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #12 from Mykola Krachkovsky --- Created attachment 164811 --> https://bugs.kde.org/attachment.cgi?id=164811=edit Bibata Amber cursors -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #10 from Mykola Krachkovsky --- (In reply to Vlad Zahorodnii from comment #6) > or can attach a zip archive with the cursor theme? Should I add it? It's about 1.7MiB. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #9 from Mykola Krachkovsky --- (In reply to Vlad Zahorodnii from comment #7) > also have you enabled color management? No, ICC is not set, gamma at 1.00, night colors not active yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #8 from Mykola Krachkovsky --- Created attachment 164810 --> https://bugs.kde.org/attachment.cgi?id=164810=edit Breeze software (In reply to Vlad Zahorodnii from comment #5) > > I'm using older version of Bibata Cursors (prefer pointie ones, not modern > > rounded): > > https://build.opensuse.org/package/show/home:NickLion:res/bibata-cursors > > Is the issue reproducible with breeze cursor theme? Yes. Here it is. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479634] Invisible mouse cursor on internal laptop screen while visible on external
https://bugs.kde.org/show_bug.cgi?id=479634 --- Comment #2 from Mykola Krachkovsky --- I've made a separate bug for cursor artifacts: https://bugs.kde.org/show_bug.cgi?id=479637 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #4 from Mykola Krachkovsky --- I've added photos (sorry, but screenshot has no artifacts that are present on real screen) how cursor looks like when SW and HW. I'm using older version of Bibata Cursors (prefer pointie ones, not modern rounded): https://build.opensuse.org/package/show/home:NickLion:res/bibata-cursors -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #3 from Mykola Krachkovsky --- Created attachment 164808 --> https://bugs.kde.org/attachment.cgi?id=164808=edit Bibata Amber cursor screenshot (doesn't depend on sw/hw) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #2 from Mykola Krachkovsky --- Created attachment 164807 --> https://bugs.kde.org/attachment.cgi?id=164807=edit Bibata Amber hardware cursor photo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 --- Comment #1 from Mykola Krachkovsky --- Created attachment 164806 --> https://bugs.kde.org/attachment.cgi?id=164806=edit Bibata Amber software cursor photo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479637] New: Software cursor has artifacts while hardware looks fine (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=479637 Bug ID: 479637 Summary: Software cursor has artifacts while hardware looks fine (Intel GPU) Classification: Plasma Product: kwin Version: 5.92.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- SUMMARY Commit https://invent.kde.org/plasma/kwin/-/commit/b214251f81cbacacf3ef483081a7cef15343fa7f forces software cursors on Intel GPU's. But they have visual artifacts. STEPS TO REPRODUCE 1. Activate software cursors with `KWIN_FORCE_SW_CURSOR=1` 2. Check how cursor is rendered. 3. Disable software cursors with `KWIN_FORCE_SW_CURSOR=0` 4. Compare rendering. OBSERVED RESULT HW cursors have smooth shadow outside. SW cursors have artifacts instead of shadow. EXPECTED RESULT SW should look similar to HW ones. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE 20240109 (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479634] Invisible mouse cursor on internal laptop screen while visible on external
https://bugs.kde.org/show_bug.cgi?id=479634 --- Comment #1 from Mykola Krachkovsky --- Additonal information: 1. Cursor visible when external screen is not plugged or switched off in settings, but disappears again on plug in (switch on). 2. Cursor looks fine (no artifacts & visible) on screenshots. 3. I've tried to set 100% scaling and it seems doesn't affect, these bugs still present. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479634] Invisible mouse cursor on internal laptop screen while visible on external
https://bugs.kde.org/show_bug.cgi?id=479634 Mykola Krachkovsky changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479634] Invisible mouse cursor on internal laptop screen while visible on external
https://bugs.kde.org/show_bug.cgi?id=479634 Mykola Krachkovsky changed: What|Removed |Added Keywords||qt6, wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479634] New: Invisible mouse cursor on internal laptop screen while visible on external
https://bugs.kde.org/show_bug.cgi?id=479634 Bug ID: 479634 Summary: Invisible mouse cursor on internal laptop screen while visible on external Classification: Plasma Product: kwin Version: 5.92.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- Created attachment 164805 --> https://bugs.kde.org/attachment.cgi?id=164805=edit KScreen setup SUMMARY After update of kwin6 to 5.91.90git.20240111T012852~e427ad73-77.1 (openSUSE Tumbleweed KDE Unstable repository) mouse cursor disappeared on internal screen for any application or plasma shell. Even when cursor is near the edge of external screen and part of it should be visible on internal — that part became invisible. Also cursor has artifacts on the edge, btw I'm using older version of Bibata Amber cursors, not sure if this true for native Breeze, but these artifacts weren't present before on kwin6. I suspect this is a software cursors problem, as I have an Intel GPU on laptop. I think this commit: https://invent.kde.org/plasma/kwin/-/commit/b214251f81cbacacf3ef483081a7cef15343fa7f discovered this bug. If I add `export KWIN_FORCE_SW_CURSOR=0` to `~/.config/plasma-workspace/env/` folder to revert to hardware cursors, then both these problems go away — cursor is visible everywhere and no visual artifacts. Also maybe this is important, I'm using fractional scaling, 1.25 on external screen & 1.5 on internal. I think artifacts related to this, but whu they aren't present with HW cursor? Different resampling algorithm? Details in kscreen-doctor output in attachment. STEPS TO REPRODUCE 1. Use laptop with Intel GPU. 2. Setup internal & external screens. 3. Move mouse cursor between external & internal screens. OBSERVED RESULT Cursor is invisible on internal screen. EXPECTED RESULT Cursor should be visible on both screens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE 20240109 (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477678] Crispy text in various pieces of Qt6 software when using fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=477678 --- Comment #11 from Mykola Krachkovsky --- (In reply to Robby Engelmann from comment #10) > Indeed, this workaround solves the issue. For the time being, I export it on > session start. > Is this bug now resolved -> upstream? Well, I'm not sure about this: (In reply to Robby Engelmann from comment #5) > Created attachment 163602 [details] > crispy in panel This one uses AFAIK QtQuick, so shouldn't be affected by WebEngine bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477678] Crispy text in various pieces of Qt6 software when using fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=477678 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com --- Comment #9 from Mykola Krachkovsky --- (In reply to Robby Engelmann from comment #1) > Created attachment 163573 [details] > crispy text reading akregator feed I think this one is due Qt6 QtWebEngine bug: https://bugreports.qt.io/browse/QTBUG-113574 For Falkon I use `QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor` workaround. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 468495] KTextEditor (Kate, KWrite, KPart) new line on line start may eat text after tabs
https://bugs.kde.org/show_bug.cgi?id=468495 --- Comment #10 from Mykola Krachkovsky --- (In reply to Mykola Krachkovsky from comment #9) > (In reply to Waqar Ahmed from comment #7) > > will work from a quick look. (patches not accepted here though) > > I've created the merge request: > https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/541 > > I'm not insisting on merging it, change is subtle, though code looks cleaner > to me. revoked it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 468495] KTextEditor (Kate, KWrite, KPart) new line on line start may eat text after tabs
https://bugs.kde.org/show_bug.cgi?id=468495 --- Comment #9 from Mykola Krachkovsky --- (In reply to Waqar Ahmed from comment #7) > will work from a quick look. (patches not accepted here though) I've created the merge request: https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/541 I'm not insisting on merging it, change is subtle, though code looks cleaner to me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 468495] KTextEditor (Kate, KWrite, KPart) new line on line start may eat text after tabs
https://bugs.kde.org/show_bug.cgi?id=468495 --- Comment #6 from Mykola Krachkovsky --- Created attachment 158111 --> https://bugs.kde.org/attachment.cgi?id=158111=edit Patch without removing extra spaces Like this patch? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 468495] KTextEditor (Kate, KWrite, KPart) new line on line start may eat text after tabs
https://bugs.kde.org/show_bug.cgi?id=468495 --- Comment #5 from Mykola Krachkovsky --- (In reply to Waqar Ahmed from comment #4) > Git commit 89bf2451f4aeef3d787ff70eec531b9276d8b139 by Waqar Ahmed. > Committed on 14/04/2023 at 19:57. > Pushed by waqar into branch 'master'. > > Fix indenting removes characters if line has tabs at start > > M +26 -0autotests/src/katedocument_test.cpp > M +1-0autotests/src/katedocument_test.h > M +1-1src/utils/kateautoindent.cpp > > https://invent.kde.org/frameworks/ktexteditor/commit/ > 89bf2451f4aeef3d787ff70eec531b9276d8b139 I've tried patch similar to that and it worked. But maybe it's better to not remove those spaces in the first place? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 468495] KTextEditor (Kate, KWrite, KPart) new line on line start may eat text after tabs
https://bugs.kde.org/show_bug.cgi?id=468495 --- Comment #3 from Mykola Krachkovsky --- I think this commit made this behaviour: (kf5) https://invent.kde.org/frameworks/ktexteditor/-/commit/f6e70dd237ff184097102c10be3a1dcde0c3ab76 (master) https://invent.kde.org/frameworks/ktexteditor/-/commit/431bdf7b40ffc385a6e52c884f8b2aa113901dde This line looks suspicious: `doc->editRemoveText(line, 0, indentDepth);` before it was: `doc->editRemoveText(line, 0, currentWhitespace.length());` If indentDepth calculates tabs as tab width, then it removes all tabs and extra chars from line, explains why (tab count) * (tab width - 1), -1 — tab char itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 468495] New: KTextEditor (Kate, KWrite, KPart) new line on line start may eat text after tabs
https://bugs.kde.org/show_bug.cgi?id=468495 Bug ID: 468495 Summary: KTextEditor (Kate, KWrite, KPart) new line on line start may eat text after tabs Classification: Frameworks and Libraries Product: frameworks-ktexteditor Version: 5.105.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- Created attachment 158098 --> https://bugs.kde.org/attachment.cgi?id=158098=edit Example file where bug manifests on 2nd&3rd lines SUMMARY If line has tab indentation (work code styling) then pressing enter on line start (before tabs) may eat some characters from meaningful part of the line (after tabs). I haven't discovered why it sometimes eats, sometimes keeps it fine. How much characters would be eaten depends on tab count and tab width, loos like: (tab count) * (tab width - 1). STEPS TO REPRODUCE 1. Create new file. 2. Add some text (2 lines is enough). 1-2. Or open file from attachment. 3. Place text cursor onto start of 2nd or 3rd line (1st isn't affected). 4. Press enter. OBSERVED RESULT New line without indentation is created and next line with indentation but meaningful part is corrupted — starting characters are dropped. EXPECTED RESULT New line without indentation and old line with indentation same as previous one. All meaningful characters preserved. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20230412 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8+kde185 ADDITIONAL INFORMATION All indentation modes are affected, but line has to start with tabs. Seems doesn't depend on programming language (noticed in javascript file, but regular text files affected too): 'Tools' → 'Indentation' → 'Normal'/'C Style' — were checked, both affected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465385] With Wayland menu keyboard navigation (left/right keys) closes all menu
https://bugs.kde.org/show_bug.cgi?id=465385 --- Comment #5 from Mykola Krachkovsky --- Created attachment 156095 --> https://bugs.kde.org/attachment.cgi?id=156095=edit Window menu Also with regular menu, pressing Left or Right also closes menu instead of moving to previous/next item. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465385] With Wayland menu keyboard navigation (left/right keys) closes all menu
https://bugs.kde.org/show_bug.cgi?id=465385 --- Comment #4 from Mykola Krachkovsky --- Created attachment 156094 --> https://bugs.kde.org/attachment.cgi?id=156094=edit Opened submenu If at this point you'll push left button to go back to upper menu, whole menu will be closed, not just submenu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465385] With Wayland menu keyboard navigation (left/right keys) closes all menu
https://bugs.kde.org/show_bug.cgi?id=465385 --- Comment #3 from Mykola Krachkovsky --- (In reply to Vlad Zahorodnii from comment #1) > > Open context/hamburger menu > > Can you be more specific please? Basically any context/hamburger menu in Qt5 Widget application, e.g. Dolphin hamburger menu menu, Falkon context menu, Krusader bookmarks menu, etc. As a test you can open Dolphin hamburger menu, then with keyboard navigate to Create (New?) submenu, and then press left go up level. And whole menu is closed not just submenu. I'll add a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465385] New: With Wayland menu keyboard navigation (left/right keys) closes all menu
https://bugs.kde.org/show_bug.cgi?id=465385 Bug ID: 465385 Summary: With Wayland menu keyboard navigation (left/right keys) closes all menu Classification: Plasma Product: kwin Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- SUMMARY When open menu (window menu, context or hamburger) when pressing left or right key whole menu is close, instead of moving to previous/next menu (in window menu) or returning to upper level menu (submenu in context/hamburger). STEPS TO REPRODUCE For context/hamburger 1. Open context/hamburger menu. 2. Navigate to submenu (keyboard or mouse — doesn't matter at this step). 3. Press Left key to return to upper menu. For window menu 1. Open window menu (with Alt+letter or using a mouse). 2. Press Left or Right key to go to previous or next item. OBSERVED RESULT Whole menu is closed. EXPECTED RESULT Only submenu should be closed, or next/previous item selected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20230204 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8+kde160 ADDITIONAL INFORMATION In Qt Creator (build with Qt6) context menu works fine. Maybe it's a Qt bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464842] Maximized windows on one screen take one pixel on other (fractional scaling)
https://bugs.kde.org/show_bug.cgi?id=464842 --- Comment #1 from Mykola Krachkovsky --- Created attachment 155656 --> https://bugs.kde.org/attachment.cgi?id=155656=edit screenshot with noticeable step between panel and extent of window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464842] New: Maximized windows on one screen take one pixel on other (fractional scaling)
https://bugs.kde.org/show_bug.cgi?id=464842
Bug ID: 464842
Summary: Maximized windows on one screen take one pixel on
other (fractional scaling)
Classification: Plasma
Product: kwin
Version: 5.26.90
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: w01dn...@gmail.com
Target Milestone: ---
Created attachment 155655
--> https://bugs.kde.org/attachment.cgi?id=155655=edit
Affected 1.25 + 1.5 screen layout
SUMMARY
With kwin_wayland 5.26.90 (bug wasn't present on kwin_wayland 5.26.5) maximized
windows take also one pixel on other screen. I use fractional scaling,
top-bottom screen arrangements (left-right wasn't tested). Bug reproduced with
top×1.25 + bottom×1.5 and top×1 + bottom×1.5 screen layouts. One extra pixel is
not kscreen problem, screens do not overlap (it is hidden by right panel on
bottom screen and active maximized window on bottom screen).
STEPS TO REPRODUCE
1. Setup layout with two screens, bottom one has scaling 1.5, top could be any
(reproduced at least with 1 and 1.25).
2. Maximize window on top screen (for easier noticing, contrast window and
wallpaper may be used).
3. (Optional) Maximize some window on bottom screen.
OBSERVED RESULT
One pixel line overhang on on bottom screen from top max window.
With step 3 you could switch between windows and see how that extra line
appears and hides.
EXPECTED RESULT
Maximized windows should not extend beyond their screen.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20230124 with KDE Plasma 5.27 beta
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8+kde160
ADDITIONAL INFORMATION
This bug looks like some sort of opposite to
https://bugs.kde.org/show_bug.cgi?id=459373
Unlike that bug it doesn't depend on XWayland (native Wayland clients are used)
and it wasn't present before 5.27 beta.
example of affected layout (full in attachment)
`kscreen-doctor -j | jq '[.outputs[] | { name: .name, pos: .pos, size: .size,
scale: .scale }]'`
```
[
{
"name": "eDP-1",
"pos": {
"x": 385,
"y": 1152
},
"size": {
"height": 1080,
"width": 1920
},
"scale": 1.5
},
{
"name": "DP-1",
"pos": {
"x": 0,
"y": 0
},
"size": {
"height": 1440,
"width": 2560
},
"scale": 1.25
}
]
```
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 449138] Pinning KRunner doesn't keep it open when clicking entries
https://bugs.kde.org/show_bug.cgi?id=449138 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com --- Comment #5 from Mykola Krachkovsky --- Hmm. I kinda loved previous behaviour. When activity goes to other window, it keeps active, but when Enter pressed it hides as no longer needed. Right now both not pinned and pinned aren't what I like. In first case I can't keep calculations always visible, in second after running apps it still opened and cover app, so I need to switch to it and press Esc. I'd like to add option for that, would it be welcomed or not (as extra option somewhere)? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448936] "Replace all" replaces only one instance when newline character in replacement string
https://bugs.kde.org/show_bug.cgi?id=448936 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com --- Comment #2 from Mykola Krachkovsky --- I think this bug should be solved with Commit 863f606b, see bug https://bugs.kde.org/show_bug.cgi?id=447972. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 --- Comment #33 from Mykola Krachkovsky --- Created attachment 144489 --> https://bugs.kde.org/attachment.cgi?id=144489=edit widget broken layout (not sure is related) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 --- Comment #32 from Mykola Krachkovsky --- These lines are logged before crash, maybe they are up to something: ``` file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:158:5: Unable to assign [undefined] to QString kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/drives/ST2000LM007_1R8174_ZDZ64EF7”" kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/drives/ST2000LM007_1R8174_ZDZ64EF7”" ``` (I've added `deviceItem.message.error || ""` in subtitle, not sure if that would have any effect on the first log line). btw, seems like some race condition, cause with normal running I got crash in about 15-25% of times, while under gdb it happens more often (though it may be just random fluctuations). Another possibly interesting information, one frame earlier in `QQmlVMEMetaObjectEndpoint::tryConnect` — `connect(target, pd->notifyIndex(), ctxt->engine);` `p pd->name(target)` returns basically string `inVisibleLayout` so, if I understood correctly (not sure) crash is on getting this bool (pd->m_propType == 1) property. Searching for it gives only two files: ``` /usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/CurrentItemHighLight.qml /usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/AbstractItem.qml ``` Also widget has broken layout, maybe due to this problem or unrelated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 --- Comment #30 from Mykola Krachkovsky --- Well, I use the same device, USB HDD with two partitions, one of which (ext4) is configured to mount on connect, second (ntfs) isn't mounted. I'll try to check thumb drives or other hdd, usually using just this one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 --- Comment #31 from Mykola Krachkovsky --- (In reply to Fushan Wen from comment #27) > I can only think of a possible cause: duplicate udi This could lead to null engine? I don't know that code, `QQmlEngine* engine=0x0` looks strange to me, but I don't know what can cause that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945
--- Comment #26 from Mykola Krachkovsky ---
(In reply to David Edmundson from comment #25)
> Print that first QObject's object->metaObject()->className()
```
(gdb) frame 4
#4 QQmlNotifierEndpoint::connect (this=this@entry=0x57c46da0,
source=0x7fffec02a500, sourceSignal=47, engine=0x0,
doNotify=doNotify@entry=true)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.2.x86_64/src/qml/qml/qqmlnotifier.cpp:122
122
QObjectPrivate::get(engine)->threadData.loadRelaxed()->threadId.loadRelaxed())
{
(gdb) p source->metaObject()->className()
$3 = 0x57149a30 "PlasmoidItem_QMLTYPE_796"
```
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 Mykola Krachkovsky changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #17 from Mykola Krachkovsky --- Still happens to me on 5.23.2, details in previous comment from DrKonqi. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 --- Comment #16 from Mykola Krachkovsky --- Created attachment 143185 --> https://bugs.kde.org/attachment.cgi?id=143185=edit New crash information added by DrKonqi plasmashell (5.23.2) using Qt 5.15.2 Still happens to me on 5.23.2 - What I was doing when the application crashed: Pressed safely remove on the mounted partition of external HDD. -- Backtrace (Reduced): #6 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/11/bits/atomic_base.h:836 #7 std::atomic::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/11/atomic:570 #8 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #9 QBasicAtomicPointer::loadRelaxed() const (this=) at /usr/include/qt5/QtCore/qbasicatomic.h:248 #10 QQmlNotifierEndpoint::connect(QObject*, int, QQmlEngine*, bool) (this=this@entry=0x55d9c7841410, source=0x55d9c5fd3de0, sourceSignal=46, engine=0x0, doNotify=doNotify@entry=true) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/qml/qml/qqmlnotifier.cpp:122 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 --- Comment #13 from Mykola Krachkovsky --- Created attachment 142969 --> https://bugs.kde.org/attachment.cgi?id=142969=edit New crash information added by DrKonqi plasmashell (5.23.1) using Qt 5.15.2 - What I was doing when the application crashed: 1. Pressed safely remove on the mounted partition of external HDD. -- Backtrace (Reduced): #6 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/11/bits/atomic_base.h:836 #7 std::atomic::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/11/atomic:570 #8 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #9 QBasicAtomicPointer::loadRelaxed() const (this=) at /usr/include/qt5/QtCore/qbasicatomic.h:248 #10 QQmlNotifierEndpoint::connect(QObject*, int, QQmlEngine*, bool) (this=this@entry=0x55c6395e0f10, source=0x55c63a385d80, sourceSignal=46, engine=0x0, doNotify=doNotify@entry=true) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.5.x86_64/src/qml/qml/qqmlnotifier.cpp:122 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive
https://bugs.kde.org/show_bug.cgi?id=427945 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 444421] Kontact crashes on attachment save
https://bugs.kde.org/show_bug.cgi?id=21 --- Comment #1 from Mykola Krachkovsky --- Tried to reproduce it again, and everything was fine, no crash. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 444421] New: Kontact crashes on attachment save
https://bugs.kde.org/show_bug.cgi?id=21
Bug ID: 21
Summary: Kontact crashes on attachment save
Product: kontact
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: w01dn...@gmail.com
Target Milestone: ---
Application: kontact (5.18.2 (21.08.2))
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.11-2-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.0 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
1. Opened first email with attachment.
2. Pressed on attachment and then "save" button, approved in save window.
Everything was fine here.
3. Opened second email with attachment (attachment has the same name, though it
differs, maybe it would be important, idk).
4. Pressed on atachment.
5. Pressed on "save" and got a crash.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6 0x7fba706b1639 in KMime::Content::headerByType
(this=this@entry=0x560c21075310, type=0x7fba706ca020 "Content-Disposition") at
/usr/src/debug/kmime-21.08.2-1.1.x86_64/src/kmime_content.cpp:615
#7 0x7fba706b3919 in
KMime::Content::header (create=true,
this=0x560c21075310) at
/usr/src/debug/kmime-21.08.2-1.1.x86_64/src/kmime_content.h:681
#8 KMime::Content::contentDisposition (this=this@entry=0x560c21075310,
create=create@entry=true) at
/usr/src/debug/kmime-21.08.2-1.1.x86_64/src/kmime_content.cpp:872
#9 0x7fba42408c1f in MimeTreeParser::NodeHelper::fileName
(node=0x560c21075310) at
/usr/src/debug/messagelib-21.08.2-1.1.x86_64/mimetreeparser/src/nodehelper.cpp:620
#10 0x7fba425f9257 in MessageViewer::Util::saveContents
(parent=0x560c203c0e80, contents=..., urlList=...) at
/usr/src/debug/messagelib-21.08.2-1.1.x86_64/messageviewer/src/utils/messageviewerutil.cpp:226
#11 0x7fba425c2445 in MessageViewer::ViewerPrivate::openAttachment
(this=0x560c2027b770, node=, url=...) at
/usr/src/debug/messagelib-21.08.2-1.1.x86_64/messageviewer/src/viewer/viewer_p.cpp:322
#12 0x7fba425ceb59 in MessageViewer::AttachmentURLHandler::handleClick
(this=, url=..., w=0x560c2027b770) at
/usr/src/debug/messagelib-21.08.2-1.1.x86_64/messageviewer/src/viewer/urlhandlermanager.cpp:660
#13 0x7fba425c9870 in MessageViewer::URLHandlerManager::handleClick
(w=0x560c2027b770, url=..., this=) at
/usr/src/debug/messagelib-21.08.2-1.1.x86_64/messageviewer/src/viewer/urlhandlermanager.cpp:284
#14 MessageViewer::ViewerPrivate::slotUrlOpen (this=0x560c2027b770, url=...) at
/usr/src/debug/messagelib-21.08.2-1.1.x86_64/messageviewer/src/viewer/viewer_p.cpp:1901
#15 0x7fbac6e25fbe in QObject::event (this=0x560c2027b770,
e=0x560c23e13030) at kernel/qobject.cpp:1314
#16 0x7fbac79f7a7f in QApplicationPrivate::notify_helper (this=, receiver=0x560c2027b770, e=0x560c23e13030) at
kernel/qapplication.cpp:3632
#17 0x7fbac6df99ca in QCoreApplication::notifyInternal2
(receiver=0x560c2027b770, event=0x560c23e13030) at
kernel/qcoreapplication.cpp:1064
#18 0x7fbac6dfca17 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x560c1fc22920) at
kernel/qcoreapplication.cpp:1821
#19 0x7fbac6e51823 in postEventSourceDispatch (s=s@entry=0x560c1fd8b270) at
kernel/qeventdispatcher_glib.cpp:277
#20 0x7fbabd63cd5f in g_main_dispatch (context=0x7fbaac005000) at
../glib/gmain.c:3381
#21 g_main_context_dispatch (context=0x7fbaac005000) at ../glib/gmain.c:4099
#22 0x7fbabd63d0e8 in g_main_context_iterate
(context=context@entry=0x7fbaac005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#23 0x7fbabd63d19f in g_main_context_iteration (context=0x7fbaac005000,
may_block=1) at ../glib/gmain.c:4240
#24 0x7fbac6e50ea4 in QEventDispatcherGlib::processEvents
(this=0x560c1fd87110, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#25 0x7fbac6df83cb in QEventLoop::exec (this=this@entry=0x7fff689d8710,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#26 0x7fbac6e006b0 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#27 0x7fbac729919c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#28 0x7fbac79f79f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#29 0x560c1e189f52 in main (argc=, argv=) at
/usr/src/debug/kontact-21.08.2-1.1.x86_64/src/main.cpp:216
[Inferior 1 (process 4570) detached]
Possible duplicates by query: bug 426432, bug 421501, bug 393391, bug
[krunner] [Bug 432377] KRunner calculator wrongly interpret hex numbers starting with digit as multiplication
https://bugs.kde.org/show_bug.cgi?id=432377 --- Comment #2 from Mykola Krachkovsky --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 432377] New: KRunner calculator wrongly interpret hex numbers starting with digit as multiplication
https://bugs.kde.org/show_bug.cgi?id=432377 Bug ID: 432377 Summary: KRunner calculator wrongly interpret hex numbers starting with digit as multiplication Product: krunner Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calculator Assignee: alexander.loh...@gmx.de Reporter: w01dn...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY KRunner's calculator seems interpret hex numbers starting with digit as a multiplication leading to zero result. STEPS TO REPRODUCE 1. Open KRunner 2. Type `=0x20` OBSERVED RESULT 0 EXPECTED RESULT 32 SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210130 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit ADDITIONAL INFORMATION It seems krunner's calculator may interpret `x` as multiplication, e.g. `=4x5`->`20`. If this is needed for anyone, still `0x4` as multiplication is pointless, so IMHO, it's better to keep `0x` prefix just for hex numbers and interpret `x` as multiplication only when there is non-zero value before `x`. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421949] Battery Applet in Systray Missing
https://bugs.kde.org/show_bug.cgi?id=421949 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com --- Comment #4 from Mykola Krachkovsky --- https://bugs.kde.org/show_bug.cgi?id=422111 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410582] Konsole with two tabs crashes when you press ctrl+d
https://bugs.kde.org/show_bug.cgi?id=410582 --- Comment #9 from Mykola Krachkovsky --- Application: konsole (20.04.0) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.11-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Closing tabs one by one with Ctrl+D. There were no "read only" tabs. Some tabs were SSH tabs (Konsole profile with ssh command). I'm not sure, maybe mouse was over some of the opened/closing tabs. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f50149fd800 (LWP 2382))] Thread 7 (Thread 0x7f5008ec6700 (LWP 2488)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f50096c7700 (LWP 2487)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f5009ec8700 (LWP 2486)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f500a6c9700 (LWP 2485)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f5010968700 (LWP 2447)): #0 0x7f5018642acf in poll () from /lib64/libc.so.6 #1 0x7f50153a69de in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f50153a6aff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5016e64beb in QEventDispatcherGlib::processEvents (this=0x7f5004000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5016e0cb7b in QEventLoop::exec (this=this@entry=0x7f5010967d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f5016c375ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f501644c507 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f5016c38698 in QThreadPrivate::start (arg=0x7f50164ceda0) at thread/qthread_unix.cpp:342 #8 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #9 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5012904700 (LWP 2403)): #0 0x7f5018642acf in poll () from /lib64/libc.so.6 #1 0x7f5015db2772 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f5015db343a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f5012ae9ab0 in QXcbEventQueue::run (this=0x55c7cb427cd0) at qxcbeventqueue.cpp:228 #4 0x7f5016c38698 in QThreadPrivate::start (arg=0x55c7cb427cd0) at thread/qthread_unix.cpp:342 #5 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #6 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f50149fd800 (LWP 2382)): [KCrash Handler] #6 QWidget::testAttribute (attribute=, this=) at kernel/qwidget.h:883 #7 QWidget::isEnabled (this=0x0) at kernel/qwidget.h:780 #8 QWidget::setFocus (this=0x0, reason=Qt::OtherFocusReason) at kernel/qwidget.cpp:6295 #9 0x7f5016e429de in QtPrivate::QSlotObjectBase::call (a=0x7ffea7ecc3a0, r=0x55c7cb9387c0, this=0x55c7cb97aa70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 doActivate (sender=0x7f50040142c0, signal_index=15, argv=0x7ffea7ecc3a0) at kernel/qobject.cpp:3870 #11 0x7f5016e3d19f in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffea7ecc3a0) at kernel/qobject.cpp:3930 #12 0x7f50184fa422 in Konsole::TabbedViewContainer::activeViewChanged (this=, _t1=) at /usr/src/debug/konsole-20.04.0-1.1.x86_64/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_ViewContainer.cpp:273 #13 0x7f501846d739 in Konsole::TabbedViewContainer::currentTabChanged (index=4, this=0x7f50040142c0) at /usr/src/debug/konsole-20.04.0-1.1.x86_64/src/ViewContainer.cpp:517 #14 Konsole::TabbedVi
[konsole] [Bug 410582] Konsole with two tabs crashes when you press ctrl+d
https://bugs.kde.org/show_bug.cgi?id=410582 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 418459] New: Two display configuration with one above other has one pixel shift
https://bugs.kde.org/show_bug.cgi?id=418459 Bug ID: 418459 Summary: Two display configuration with one above other has one pixel shift Product: KScreen Version: 5.18.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: kscreen-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- Created attachment 126589 --> https://bugs.kde.org/attachment.cgi?id=126589=edit KScreen Config JSON SUMMARY Two displays (same size each — 1920x1080) when configured one above other can't be placed perfectly matching left/right edge. Sticking makes the display you're moving 1px to the left of other. Placing them horizontally has no such threshold. STEPS TO REPRODUCE 1. Two identical size display (I'm not sure they has to be identical) place vertically one above other, they'll stick together. 2. Apply configuration. (3. Long press (without moving) on both screens to detect their positions.) OBSERVED RESULT Display that was moved is placed at x=0, while other at x=1. You may notice this by: 1. Mouse moving at edge stuck at that 1px threshold. 2. Long press shows coordinates like (0,0) and (1,1080) if top screen was moved or (1,0) and (0,1080) if bottom was moved. 3. `kscreen-console outputs | grep -E '^(Pos|Size)'` ``` Pos: QPoint(1,1080) Size: QSize(1920, 1080) Pos: QPoint(0,0) Size: QSize(1920, 1080) ``` EXPECTED RESULT Sticking should place screens at the same x=0 coordinate without threshold. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200229, x86_64 KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION JSON configuration in attachment. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 416844] Media with audio does no play (after update to Qt 5.14?)
https://bugs.kde.org/show_bug.cgi?id=416844 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com --- Comment #3 from Mykola Krachkovsky --- Same here, though I had impression (maybe wrong), that breakage was after update to 5.14.1, not 5.14.0. And this is not Falkon specific, any QtWebEngine is affected on my system. So I think this is either some openSUSE Tumbleweed problem or Qt upstream. I've created openSUSE Tumbleweed bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1163744 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405220] Kontact crashes on opening attachment when mail becomes inactive
https://bugs.kde.org/show_bug.cgi?id=405220 Mykola Krachkovsky changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Mykola Krachkovsky --- Looks like fixed. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405122] Kontact(KMail) crashes after switching away if some loading process is going on
https://bugs.kde.org/show_bug.cgi?id=405122 Mykola Krachkovsky changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Mykola Krachkovsky --- Isn't present anymore. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection
https://bugs.kde.org/show_bug.cgi?id=392594 Mykola Krachkovsky changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME --- Comment #12 from Mykola Krachkovsky --- So, my old phone is broken and I don't use it anymore. Closing as not actual, as KDE Connect works fine on newer Androids. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407084] Changed behavior of profile shortcuts in Konsole
https://bugs.kde.org/show_bug.cgi?id=407084 --- Comment #12 from Mykola Krachkovsky --- Created attachment 119867 --> https://bugs.kde.org/attachment.cgi?id=119867=edit Current not finished patch Question is about literals in profileShortcutGroupName -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407084] Changed behavior of profile shortcuts in Konsole
https://bugs.kde.org/show_bug.cgi?id=407084 --- Comment #10 from Mykola Krachkovsky --- So, I'm trying to implement this feature, currently in the middle of solving this problem. But there is one easy for implementing but principal decision should be made — konsolerc file before and currently has one section [Profile Shortcuts], I'm introducing another, but which variant should be accepted: 1. [Profile Shortcuts] is used for new tab (as before 19.04). [Apply Profile Shortcuts] is introduced to apply profile. pros: no breakage for people who will update from 18.xx to future 19.xx, just new feature. cons: double breakage for people with rolling updates. 2. [Profile Shortcuts] is used to apply profile (as in 19.04). [Profile New Tab Shortcuts] is introduced to create new tab with profile. I'm personally for the 1st variant, but it's not very important to me as it's easily fixable (just rename group in config file). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407084] Changed behavior of profile shortcuts in Konsole
https://bugs.kde.org/show_bug.cgi?id=407084 --- Comment #8 from Mykola Krachkovsky --- But why this was introduced as replacement of old behaviour? IMHO, this have broken not just my workflow, as profile in Konsole much more powerful than just visual style. So basically we need to revert/rework https://cgit.kde.org/konsole.git/commit/?id=d689ba5403ceb998013fc99de6758976f8509e98 Right? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407121] New: Konsole profile shortcut behaviour change brakes usage
https://bugs.kde.org/show_bug.cgi?id=407121 Bug ID: 407121 Summary: Konsole profile shortcut behaviour change brakes usage Product: konsole Version: 19.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- SUMMARY Before Konsole 19.04 profile shortcut created new tab, but with 19.04 was introduced new behaviour ( https://cgit.kde.org/konsole.git/commit/?id=d689ba5403ceb998013fc99de6758976f8509e98 ) and it completely brakes my workflow. Shortcut becomes unusable for me. I have profiles for different servers and profiles not just visual style, but also a different starting command (ssh to specific server). So after this change I have to use mouse to create new tab with specific profile (which is very inconvenient). STEPS TO REPRODUCE 1. Update to 19.04. 2. Use shortcut for profile to specific server. OBSERVED RESULT Current tab just changed visual style. EXPECTED RESULT New tab created with specified command and visual style. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed x86_64 (snapshot 20190428) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION IMHO, both shortcuts for creating profile new tab and changing current tab profile are useful so both should be supported. So IMHO, instead of replacing new tab it's better to introduce new column profiles settings. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 352868] Folding for all nodes (not just top-level) and/or siblings to current
https://bugs.kde.org/show_bug.cgi?id=352868 Mykola Krachkovsky changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #14 from Mykola Krachkovsky --- Oh, I've missed there is new action. Then everything should be fine. I'm closing it and thanks again! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 352868] Folding for all nodes (not just top-level) and/or siblings to current
https://bugs.kde.org/show_bug.cgi?id=352868 --- Comment #12 from Mykola Krachkovsky --- (In reply to Lothar from comment #11) > Hi! A little hard for me to follow here. Will... > https://phabricator.kde.org/D20606 > ...fix this too, so we can close it? Maybe but: 1) this hasn't landed into master yet, is it? 2) imho, it's not very obvious to use LMR clicks for this task, and no hotkey support. it looks like some hidden knowledge. Anyway thanks for your work! It'll good to have this feature. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405224] KMail/Kontact mail list refreshed on (de)activation
https://bugs.kde.org/show_bug.cgi?id=405224 Mykola Krachkovsky changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Mykola Krachkovsky --- This looks like solved with 5.10.3. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405224] New: KMail/Kontact mail list refreshed on (de)activation
https://bugs.kde.org/show_bug.cgi?id=405224 Bug ID: 405224 Summary: KMail/Kontact mail list refreshed on (de)activation Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- SUMMARY Each time main KMail/Kontact window is activated or deactivated its mail list is refreshed and currently selected mail is lost. STEPS TO REPRODUCE 1. Open some mail directory (and keep in mind which mail was selected). 2. Select one or other mail (not the same which was selected on directory switch). 3. Switch to another app, for example Alt+F2 (Alt+Space) to run KRunner, that doesn't matter. OBSERVED RESULT I. Current directory content list is refreshed. II. Selected mail switches back to that from step 1. (NB Selected mail is kept on switching mail directory) EXPECTED RESULT I. I can't see a reason to refresh list on activation/deactivation, though maybe I'm wrong and there is some reason. But flashing to empty and showing list again doesn't look good. II. At least selected mail should be kept on deactivation/activation. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (snapshot 20190305). KDE Plasma Version: 5.15.2 KDE Applications Version: 18.12.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 KMail/Kontact Version: 5.10.2 (XCB, not wayland) ADDITIONAL INFORMATION This strange behaviour might be (might be not) a trigger for next bugs: https://bugs.kde.org/show_bug.cgi?id=405122 https://bugs.kde.org/show_bug.cgi?id=405220 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 388641] Kontact crashed trying to open attachment
https://bugs.kde.org/show_bug.cgi?id=388641 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com --- Comment #1 from Mykola Krachkovsky --- I've experiencing similar bug: https://bugs.kde.org/show_bug.cgi?id=405220 Maybe they are the same bug, but this bug description lacks details (at least for me) to confirm that. Please, check it to confirm they are the same or not. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405220] Kontact crashes on opening attachment when mail becomes inactive
https://bugs.kde.org/show_bug.cgi?id=405220 --- Comment #1 from Mykola Krachkovsky --- PS It's mandatory to have newly selected mail on step 1, as if currently opened mail doesn't change all goes ok and as expected. PS2 I'm usually using Kontact, but this behaviour is reproduced on pure KMail as well. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405220] New: Kontact crashes on opening attachment when mail becomes inactive
https://bugs.kde.org/show_bug.cgi?id=405220 Bug ID: 405220 Summary: Kontact crashes on opening attachment when mail becomes inactive Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- Application: kontact (5.10.2) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.20.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: 1. Select new mail with attachment. 2. Click on attachment (I was using PDF) and select to open it in program (Okular in my case). 3. After that deactivation of main Kontact window makes list to reload and previous mail is activated. 4. Kontact crashes. - Custom settings of the application: IMAP GMail account, keeping all mail local copy is unkchecked. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff3af784a40 (LWP 8861))] Thread 24 (Thread 0x7ff37dffb700 (LWP 10249)): #0 0x7ff3bd627428 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff3b71d0c57 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7ff3b71d15aa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7ff3b71d1692 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7ff3b718f131 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7ff3b7191c67 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7ff3b7192254 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7ff3b71d37b1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7ff3bd620fab in start_thread () from /lib64/libpthread.so.0 #9 0x7ff3be5f569f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7ff38bfff700 (LWP 10248)): #0 0x7ff3bd627428 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff3b71d0c57 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7ff3b71d15aa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7ff3b71d1692 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7ff3b718f131 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7ff3b7191f96 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7ff3b7192254 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7ff3b71d37b1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7ff3bd620fab in start_thread () from /lib64/libpthread.so.0 #9 0x7ff3be5f569f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7ff29a313700 (LWP 8947)): #0 0x7ff3be5eaad9 in poll () from /lib64/libc.so.6 #1 0x7ff3bcc38156 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff3bcc3827c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff3beb3bc5b in QEventDispatcherGlib::processEvents (this=0x7ff28c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7ff3beae64fb in QEventLoop::exec (this=this@entry=0x7ff29a312b60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7ff3be930396 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7ff3be9316e2 in QThreadPrivate::start (arg=0x556e77bb1e80) at thread/qthread_unix.cpp:361 #7 0x7ff3bd620fab in start_thread () from /lib64/libpthread.so.0 #8 0x7ff3be5f569f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7ff2b0e83700 (LWP 8913)): #0 0x7ff3bcc37690 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7ff3bcc3808b in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff3bcc3827c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff3beb3bc5b in QEventDispatcherGlib::processEvents (this=0x7ff2ab20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7ff3beae64fb in QEventLoop::exec (this=this@entry=0x7ff2b0e82b60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7ff3be930396 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7ff3be9316e2 in QThreadPrivate::start (arg=0x556e719c2000) at thread/qthread_unix.cpp:361 #7 0x7ff3bd620fab in start_thread () from /lib64/libpthread.so.0 #8 0x7ff3be5f569f in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7ff2b17af700 (LWP 8905)): #0 0x7ff3be5eaad9 in poll () from /lib64/libc.so.6 #1 0x7ff3bcc38156 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff3bcc3827c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3
[kontact] [Bug 405122] New: Kontact(KMail) crashes after switching away if some loading process is going on
https://bugs.kde.org/show_bug.cgi?id=405122 Bug ID: 405122 Summary: Kontact(KMail) crashes after switching away if some loading process is going on Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- Application: kontact (5.10.2) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.20.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: 1. I have IMAP GMail acount with a lot of labels/directories. 2. IMAP directory refreshing was in process. 3. Select some letter, which is loading but not loaded yet. 4. Switch away to another desktop. 5. Immediately (almost?) Kontact crashed. This doesn't happen everytime, but have happened several times, so I've installed symbols to provide more information, hope it would be helpful enough. I'm not sure steps 2 & 3 are mandatory to reproduce this bug. But all crashes happened on switching to other desktop (usually I'm using hotkey, Super+arrow_key to navigate 3x3 desktops). The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9d86412a40 (LWP 24653))] Thread 23 (Thread 0x7f9c6b02d700 (LWP 22179)): #0 0x7f9d942bb428 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9d8de5ec57 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f9d8de5f5aa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f9d8de5f692 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f9d8de1d131 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f9d8de1ff96 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f9d8de20254 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f9d8de617b1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f9d942b4fab in start_thread () from /lib64/libpthread.so.0 #9 0x7f9d9528969f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f9c6bfff700 (LWP 24767)): #0 0x7f9d9527ead9 in poll () from /lib64/libc.so.6 #1 0x7f9d938c6156 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9d938c627c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9d957cfc5b in QEventDispatcherGlib::processEvents (this=0x7f9c6b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f9d9577a4fb in QEventLoop::exec (this=this@entry=0x7f9c6bffeb60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f9d955c4396 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f9d955c56e2 in QThreadPrivate::start (arg=0x55a9af86d960) at thread/qthread_unix.cpp:361 #7 0x7f9d942b4fab in start_thread () from /lib64/libpthread.so.0 #8 0x7f9d9528969f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f9c7f7fe700 (LWP 24705)): #0 0x7f9d9527ead9 in poll () from /lib64/libc.so.6 #1 0x7f9d938c6156 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9d938c627c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9d957cfc5b in QEventDispatcherGlib::processEvents (this=0x7f9c6c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f9d9577a4fb in QEventLoop::exec (this=this@entry=0x7f9c7f7fdb60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f9d955c4396 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f9d955c56e2 in QThreadPrivate::start (arg=0x55a9a9600350) at thread/qthread_unix.cpp:361 #7 0x7f9d942b4fab in start_thread () from /lib64/libpthread.so.0 #8 0x7f9d9528969f in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f9c7700 (LWP 24697)): #0 0x7f9d9527a6b4 in read () from /lib64/libc.so.6 #1 0x7f9d9390bc70 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9d938c5c2f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9d938c6100 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f9d938c627c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f9d957cfc5b in QEventDispatcherGlib::processEvents (this=0x7f9c74000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f9d9577a4fb in QEventLoop::exec (this=this@entry=0x7f9c7fffeb60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f9d955c4396 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8
[okular] [Bug 306417] opened new tab becomes active though not visible
https://bugs.kde.org/show_bug.cgi?id=306417 Mykola Krachkovsky changed: What|Removed |Added Resolution|FIXED |INTENTIONAL --- Comment #30 from Mykola Krachkovsky --- (In reply to Luigi Toscano from comment #29) > I would not close as FIXED, then. Maybe INTENTIONAL. Ok. I've tried to search something like "too old/not relevant" but failed :) UNMAINTAINED doesn't look fine. So, let it be INTENTIONAL. > But Konqueror still opens PDF in tabs, if you have the kpart installed. Well, I have `/usr/lib64/qt5/plugins/okularpart.so` but when I click with middle button on PDF link Konqueror opens new tab and shows dialog what to do with file (maybe some misconfiguration). When entering URL manually, pdf is opened inside of Konqueror, so kpart itself working. But anyway, I'm not using Konqueror anymore (moved to QupZilla->Falkon). And Konqueror is almost deprecated, am I wrong? Is anybody working on it? So if this bug would be relevant again anyone could reopen it, or open new for newer version. PS looked https://cgit.kde.org/konqueror.git/log/ and was surprised to see a lot of commits this month (unlike previous year). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 306417] opened new tab becomes active though not visible
https://bugs.kde.org/show_bug.cgi?id=306417 Mykola Krachkovsky changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #28 from Mykola Krachkovsky --- I can't see a reason to keep this open. Konqueror 5 doesn't open PDF in tabs (kinda fixed) and anyway it's effectively dead, isn't it? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399379] Mouse scroll doesn't work in UI comboboxes drop-down list
https://bugs.kde.org/show_bug.cgi?id=399379 --- Comment #21 from Mykola Krachkovsky --- (In reply to Boudewijn Rempt from comment #20) > Aw... We can either ifdef around it, or up the minimum Qt to 5.9. I'm fine > with either, 5.9 is the current LTS in any case. There is no need, just use `transientParent()` (present in 5.6) instead of `parent(QWindow::IncludeTransients)`. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399379] Mouse scroll doesn't work in UI comboboxes drop-down list
https://bugs.kde.org/show_bug.cgi?id=399379 --- Comment #15 from Mykola Krachkovsky --- Adding `QGuiApplication::modalWindow() != window->parent(QWindow::IncludeTransients)` fixed problem for me: https://build.opensuse.org/package/view_file/home:NickLion:kf5/krita/krita-no-window-check.patch Maybe using just transientParent() is better, I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399379] Mouse scroll doesn't work in UI comboboxes drop-down list
https://bugs.kde.org/show_bug.cgi?id=399379 --- Comment #14 from Mykola Krachkovsky --- I've looked through commit eccae890400cfac7805c3b89d042d223ea9f5360 and thought that one place looks suspiciously as drop-down is in fact separate window, I've tried to comment out check if current window is a modal window and scroll works. This 'if': https://cgit.kde.org/krita.git/tree/libs/ui/input/wintab/qxcbconnection.cpp#n778 So I believe, condition should be slightly more complex. Adding just "QGuiApplication::modalWindow() != window->parent()" didn't work for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399379] Mouse scroll doesn't work in UI comboboxes drop-down list
https://bugs.kde.org/show_bug.cgi?id=399379 --- Comment #12 from Mykola Krachkovsky --- (In reply to Boudewijn Rempt from comment #10) > Please test https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ > build 250 when it's done. Sorry, forgot to comment. Scroll in combos drop-downs works with build 250 appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399379] Mouse scroll doesn't work in UI comboboxes drop-down list
https://bugs.kde.org/show_bug.cgi?id=399379 --- Comment #6 from Mykola Krachkovsky --- (In reply to Boudewijn Rempt from comment #1) > While there certainly are places where the scrollwheel doesn't seem to work Anyway, good to know it's reproduced. > Those dropdowns do not have enough items to have a scrollbar, > and without a scrollbar, there will be no scrolling. Well, I have 17 items in standard image size list and about 80-90 items in color profiles, so there is scroll bar. And I have a lot of fonts. Maybe that depends on installation. (In reply to Boudewijn Rempt from comment #2) > Notably, the scroll wheel should work in the brush preset docker Yes, it works, sorry, haven't checked, as I usually use favorites without actual scroll there. > and on those items you mention when the combobox isn't dropped down. Yes, I've mentioned that ;) (In reply to Boudewijn Rempt from comment #4) > Okay, this actually has been fixed before, in > commit eccae890400cfac7805c3b89d042d223ea9f5360 > ... > But it's broken again. It's not totally broken though, T1272 says about canvas zoom/scrolling, which works fine for me. Just combobox drop-down lists broken. Maybe this case was not fixed with that commit? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399379] New: Mouse scroll doesn't work in UI comboboxes drop-down list
https://bugs.kde.org/show_bug.cgi?id=399379 Bug ID: 399379 Summary: Mouse scroll doesn't work in UI comboboxes drop-down list Product: krita Version: 4.1.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- Mouse wheel vertical scroll doesn't work in UI comboboxes drop-down lists. I'm not sure about every combo, but at least, every I've tried. Mouse scroll on closed combobox works as expected. STEPS TO REPRODUCE 1. Open "Create new document" window. 2. Click on standard image size combo or color profile combo. 3. Try to use mouse scroll on dropped-down list. OBSERVED RESULT Nothing happens, list doesn't actually scroll. EXPECTED RESULT List should scroll as in other Qt/KDE programs. SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Other checked comboboxes: font face/style/size in text window, color profile combos in Krita setings. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 398574] KIO SFTP doesn't connect to some (ecdsa-sha2-nistp256 key) hosts with libssh 0.8
https://bugs.kde.org/show_bug.cgi?id=398574 --- Comment #6 from Mykola Krachkovsky --- (In reply to Andreas Schneider from comment #5) > Oh sorry, this is about known_hosts. However in libssh 0.8 the known_hosts > API has been rewritten but kio_sftp is not using that yet. This will be > fixed soon. > > My WIP branch is: > https://gitlab.com/cryptomilk/kio-extras/commits/asn/master-sftp > > > I will finish it once libssh 0.8.3 is out. Just curious. I've noticed that `knownhosts.c` was added which should replace old `known_hosts.c`, right? And functions like `ssh_is_server_known` were deprecated. But moving from `ssh_is_server_known` to `ssh_session_is_known_server` means loosing compatibility with libssh < 0.8? Is it ok? Well, that's not problem for openSUSE Tumbleweed, which I use, but KDE Neon still uses older packages, am I right? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 398574] KIO SFTP doesn't connect to some (ecdsa-sha2-nistp256 key) hosts with libssh 0.8
https://bugs.kde.org/show_bug.cgi?id=398574 --- Comment #2 from Mykola Krachkovsky --- (In reply to Nate Graham from comment #1) > does this work if you delete the entry for the affected server in your > .known_hosts file? Oh, sorry, forgot to say, after `ssh-keygen -R ...` kio sftp connects fine and adds `ssh-ed25519` keys to known hosts. > Since it seems like you've identified the relevant piece of code, would you > like to try your hand at submitting a patch? The process is pretty simple, > and it's well documented here: > https://community.kde.org/Infrastructure/Phabricator Ok, I'll try. I've used Phabricator already, just haven't worked with libssh directly before. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 398574] New: KIO SFTP doesn't connect to some (ecdsa-sha2-nistp256 key) hosts with libssh 0.8
https://bugs.kde.org/show_bug.cgi?id=398574 Bug ID: 398574 Summary: KIO SFTP doesn't connect to some (ecdsa-sha2-nistp256 key) hosts with libssh 0.8 Product: kio-extras Version: 18.08.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: SFTP Assignee: plasma-b...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- After update of libssh to 0.8.2 KIO SFTP stopped to connect to hosts with known ecdsa-sha2-nistp256 keys, while `ssh` and KIO FISH work fine. KIO SFTP fails with error "The host key for this server was not found, but another type of key exists. An attacker might change the default server key to confuse your client into thinking the key does not exist. Please contact your system administrator." One of servers has ecdsa-sha2-nistp256 key but still works. I've looked into code and found that kio_sftp in sftpProtocol::openConnection() calls ``` rc = ssh_get_publickey_hash(srv_pubkey, SSH_PUBLICKEY_HASH_SHA1, , ); ``` I think that worked fine with 0.7.5 which had only SSH_PUBLICKEY_HASH_SHA1 and SSH_PUBLICKEY_HASH_MD5 cases in switch. But 0.8.2 also has SSH_PUBLICKEY_HASH_SHA256. BTW, called after that ssh_is_server_known is deprecated. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396081] New: Show more certificate information on SSL Certificate Error
https://bugs.kde.org/show_bug.cgi?id=396081 Bug ID: 396081 Summary: Show more certificate information on SSL Certificate Error Product: Falkon Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: w01dn...@gmail.com Target Milestone: --- On opening some sites, e.g. https://www.eqtpartners.com/About-EQT/ I've got an "SSL Certificate Error!" window with message that certificate isn't trustworthy. But there is no any information about the reason, why it is treated in such way. Especially while both Chromium and Firefox open this site without question. The reason would be quite useful for making decision for allowing certificate. This is slightly related to https://bugs.kde.org/show_bug.cgi?id=387210 but has different user case. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394259] Elisa has empty albums and artists folders
https://bugs.kde.org/show_bug.cgi?id=394259 --- Comment #7 from Mykola Krachkovsky <w01dn...@gmail.com> --- (In reply to Matthieu Gallien from comment #6) > Do you have a KDE developper account ? > If not, one Elisa developper can lend your patch. Let us know. Well, I'm registered in phabricator… and that's all. Alexander Stippich have written at https://phabricator.kde.org/D12889 about landing, but I don't think I can do that, am I wrong? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394259] Elisa has empty albums and artists folders
https://bugs.kde.org/show_bug.cgi?id=394259 --- Comment #5 from Mykola Krachkovsky <w01dn...@gmail.com> --- (In reply to Quiralta from comment #4) > I notice this behavior happening without Elisa updating, thus I'm thinking > something in Plasma has changed that render Elisa album view empty? > > Archlinux/Plasma here. same error reported in phabricator. I think it's a Qt + SQLite bug, which maybe fixed in [1], but it isn't in 5.11.0. So removing second parameter usage is simplest solution to remove problems, IMHO. I just didn't understand what next I should do in phabricator. [1] http://code.qt.io/cgit/qt/qtbase.git/commit/src/plugins/sqldrivers/sqlite/qsql_sqlite.cpp?id=b0f3cc1594308ed3f3977bdcd451e8cf0eb0478d -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394259] Elisa has empty albums and artists folders
https://bugs.kde.org/show_bug.cgi?id=394259 --- Comment #2 from Mykola Krachkovsky <w01dn...@gmail.com> --- Phabricator is working finally: https://phabricator.kde.org/D12889 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394259] New: Elisa has empty albums and artists folders
https://bugs.kde.org/show_bug.cgi?id=394259
Bug ID: 394259
Summary: Elisa has empty albums and artists folders
Product: elisa
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: w01dn...@gmail.com
Target Milestone: ---
Created attachment 112654
--> https://bugs.kde.org/attachment.cgi?id=112654=edit
removing of SQL parameter second usage
When launching Elisa it scans for tracks and shows them in Tracks section, but
in Albums or Artists sections every folder appears to be empty. I've found a
lot of errors (two distinct, but repeated a lot), when Elisa is launched from
terminal:
DatabaseInterface::updateTracksCount QSqlError("", "Parameter count mismatch",
"")
DatabaseInterface::fetchTracks QSqlError("", "Parameter count mismatch", "")
There are also SQL expression and bind map. All looks quite fine, the only I've
noted parameter :albumId is mentioned twice in that expression. I've tried to
rewrite SQL to use that parameter only once and it seems working fine after
that.
I'm not sure this is exactly an Elisa error or somewhere between Qt and SQLite.
Haven't found any statement that parameters should be used only once.
Qt: 5.10.0
SQLite: 3.23.1
Should I move patch to phabricator?
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 391438] Zoom preferences not remembered
https://bugs.kde.org/show_bug.cgi?id=391438 --- Comment #8 from Mykola Krachkovsky <w01dn...@gmail.com> --- (In reply to Theo from comment #7) > Nah, it's better to be consistent with other browsers and the needs of the > majority[citation needed]. My reason: "temporary" zoom change is more frequent operation, while setting site zoom is usually single for a long time. > Of course there is also an obvious solution to > this disagreement: make the keyboard shortcuts configurable as it is common > in KDE applications. True. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391438] Zoom preferences not remembered
https://bugs.kde.org/show_bug.cgi?id=391438 --- Comment #6 from Mykola Krachkovsky <w01dn...@gmail.com> --- (In reply to Theo from comment #5) > As a solution to this dilemma there could be two different sets of keyboard > shortcuts, for instance Ctrl+± for remembered zoom levels and Ctrl+Shift+± > for temporary zoom levels. IMHO, better to keep Ctrl+± as "per tab" (temporary) zoom control and add "per site" (persistent) default zoom to site settings. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391438] Zoom preferences not remembered
https://bugs.kde.org/show_bug.cgi?id=391438 --- Comment #3 from Mykola Krachkovsky <w01dn...@gmail.com> --- (In reply to lyr3 from comment #2) > Same here. Its tottally annoying! It's not clear what is exactly annoying. As for me Chromium common scale for all tabs of site is very annoying. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection
https://bugs.kde.org/show_bug.cgi?id=392594 --- Comment #11 from Mykola Krachkovsky <w01dn...@gmail.com> --- And still, that's not a full solution. When KDE Connect GUI isn't started and connection made from background thread it still crashes until GUI is opened. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393004] ImageFinder QupZilla plugin is absent in Falkon
https://bugs.kde.org/show_bug.cgi?id=393004 --- Comment #2 from Mykola Krachkovsky <w01dn...@gmail.com> --- Oh, I see. The problem is it needs PySide2 and not every distro has it as it still in development. Ok, I'll try to do something about it… -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393004] New: ImageFinder QupZilla plugin is absent in Falkon
https://bugs.kde.org/show_bug.cgi?id=393004 Bug ID: 393004 Summary: ImageFinder QupZilla plugin is absent in Falkon Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: w01dn...@gmail.com Target Milestone: --- QupZilla had simple but useful plugin ImageFinder, which is absent in Falkon. What is the reason for this? Are there any plans to return it back? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection
https://bugs.kde.org/show_bug.cgi?id=392594 --- Comment #10 from Mykola Krachkovsky <w01dn...@gmail.com> --- Opps, missed this from my logs, static initializer, clinit: E/AndroidRuntime(12161):at android.inputmethodservice.InputMethodService.(InputMethodService.java:315) And call to InputMethodService.BACK_DISPOSITION_DEFAULT (I suppose) was just optimized out, as that's a final static field. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #9 from Mykola Krachkovsky <w01dn...@gmail.com> ---
Ok, so what I've found, problem seems is in calling of some of static
initializers of RemoteKeyboardService or its super classes
(InputMethodService?). This static initializer works fine if first access to
class is made from gui thread (and fails when from non-gui). Adding nothing
doing log to MainActivity:
Log.d("MainActivity", "Current RemoteKeyboardPlugin instance: " +
RemoteKeyboardService.instance);
Fixes future call and everything seems works fine after that.
Sounds crazy. It looks like some bug of Android 4.4 to me. I'm not sure how to
fix it properly, calling log looks too hacky.
I've tried to access InputMethodService.BACK_DISPOSITION_DEFAULT but that
hadn't effect.
I'm not sure about static initializers, but couldn't find anything else.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection
https://bugs.kde.org/show_bug.cgi?id=392594 --- Comment #7 from Mykola Krachkovsky <w01dn...@gmail.com> --- Exception looks similar: E/AndroidRuntime(12161): FATAL EXCEPTION: Thread-22405 E/AndroidRuntime(12161): Process: org.kde.kdeconnect_tp, PID: 12161 E/AndroidRuntime(12161): java.lang.ExceptionInInitializerError E/AndroidRuntime(12161):at org.kde.kdeconnect.Plugins.RemoteKeyboardPlugin.RemoteKeyboardPlugin.onCreate(RemoteKeyboardPlugin.java:123) E/AndroidRuntime(12161):at org.kde.kdeconnect.Device.addPlugin(Device.java:741) E/AndroidRuntime(12161):at org.kde.kdeconnect.Device.reloadPluginsFromSettings(Device.java:830) E/AndroidRuntime(12161):at org.kde.kdeconnect.Device.addLink(Device.java:516) E/AndroidRuntime(12161):at org.kde.kdeconnect.BackgroundService$5.onConnectionReceived(BackgroundService.java:192) E/AndroidRuntime(12161):at org.kde.kdeconnect.Backends.BaseLinkProvider.connectionAccepted(BaseLinkProvider.java:48) E/AndroidRuntime(12161):at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.addLink(LanLinkProvider.java:315) E/AndroidRuntime(12161):at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.access$100(LanLinkProvider.java:70) E/AndroidRuntime(12161):at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$3.handshakeCompleted(LanLinkProvider.java:247) E/AndroidRuntime(12161):at com.android.org.conscrypt.OpenSSLSocketImpl.notifyHandshakeCompletedListeners(OpenSSLSocketImpl.java:582) E/AndroidRuntime(12161):at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:444) E/AndroidRuntime(12161):at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$4.run(LanLinkProvider.java:267) E/AndroidRuntime(12161):at java.lang.Thread.run(Thread.java:841) E/AndroidRuntime(12161): Caused by: java.lang.RuntimeException: Can't create handler inside thread that has not called Looper.prepare() E/AndroidRuntime(12161):at android.os.Handler.(Handler.java:200) E/AndroidRuntime(12161):at android.os.Handler.(Handler.java:114) E/AndroidRuntime(12161):at android.inputmethodservice.InputMethodService.(InputMethodService.java:315) E/AndroidRuntime(12161):... 13 more As you can't reproduce, I'll try to debug it on my side. Are sources [1] and Android Studio are enough for build/debug? [1] https://cgit.kde.org/kdeconnect-android.git/ -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection
https://bugs.kde.org/show_bug.cgi?id=392594 --- Comment #6 from Mykola Krachkovsky <w01dn...@gmail.com> --- Hmm. Crashes anyway, I'll try to see logcat later. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection
https://bugs.kde.org/show_bug.cgi?id=392594 Mykola Krachkovsky <w01dn...@gmail.com> changed: What|Removed |Added Resolution|BACKTRACE |--- Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED --- Comment #4 from Mykola Krachkovsky <w01dn...@gmail.com> --- I should've changed status to reopened, right? -- You are receiving this mail because: You are watching all bug changes.
