[Skanlite] [Bug 444987] silent crash while searching for scanners
https://bugs.kde.org/show_bug.cgi?id=444987 András Manţia changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/libr ||aries/ksanecore/-/commit/ee ||34096fefa78887d102fa65f2492 ||aa4cb215f37 Resolution|--- |FIXED --- Comment #11 from András Manţia --- Git commit ee34096fefa78887d102fa65f2492aa4cb215f37 by Andras Mantia, on behalf of Andras Mantia. Committed on 30/05/2024 at 12:25. Pushed by amantia into branch 'master'. Don't crash scanner apps (skanlite, skanpage) when searching for scanners This is triggered eg. with network scanners where scanning takes longer time. As comment says: this defeats the idea of using a scanner thread, but the proper fix would be more elaborate (ie. do the rest of initialization only when the thread is finished). Still makes sense to have this hotfix, especially as this is an old bug... Related: bug 468053 M +7-0src/interface_p.cpp https://invent.kde.org/libraries/ksanecore/-/commit/ee34096fefa78887d102fa65f2492aa4cb215f37 -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 468053] Skanlite and Skanpage crash when using a network scanner that is already the default in the app's state file
https://bugs.kde.org/show_bug.cgi?id=468053 András Manţia changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/libr ||aries/ksanecore/-/commit/ee ||34096fefa78887d102fa65f2492 ||aa4cb215f37 Resolution|--- |FIXED --- Comment #6 from András Manţia --- Git commit ee34096fefa78887d102fa65f2492aa4cb215f37 by Andras Mantia, on behalf of Andras Mantia. Committed on 30/05/2024 at 12:25. Pushed by amantia into branch 'master'. Don't crash scanner apps (skanlite, skanpage) when searching for scanners This is triggered eg. with network scanners where scanning takes longer time. As comment says: this defeats the idea of using a scanner thread, but the proper fix would be more elaborate (ie. do the rest of initialization only when the thread is finished). Still makes sense to have this hotfix, especially as this is an old bug... Related: bug 444987 M +7-0src/interface_p.cpp https://invent.kde.org/libraries/ksanecore/-/commit/ee34096fefa78887d102fa65f2492aa4cb215f37 -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 468053] Skanlite and Skanpage crash when using a network scanner that is already the default in the app's state file
https://bugs.kde.org/show_bug.cgi?id=468053 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #5 from András Manţia --- Looks like a duplicate of https://bugs.kde.org/show_bug.cgi?id=444987 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 444987] silent crash while searching for scanners
https://bugs.kde.org/show_bug.cgi?id=444987 --- Comment #9 from András Manţia --- Thread 10 "KSaneCore::Find" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffc0fff700 (LWP 24953)] 0x7fffef615631 in sane_net_get_devices (device_list=0x7fffc0ffe930, local_only=) at net.c:1302 1302 for (num_devs = 0; reply.device_list[num_devs]; ++num_devs); (gdb) bt #0 0x7fffef615631 in sane_net_get_devices (device_list=0x7fffc0ffe930, local_only=) at net.c:1302 #1 0x744c95da in sane_dll_get_devices (device_list=0x7fffc0ffe990, local_only=0) at dll.c:1098 #2 0x7518c833 in KSaneCore::FindSaneDevicesThread::run (this=0x557146d0) at /usr/src/debug/ksanecore-24.05.0-kf.50.1.x86_64/src/finddevicesthread.cpp:80 #3 0x7624e7f9 in ?? () from /usr/lib64/libQt6Core.so.6 #4 0x75d036ea in start_thread () from /lib64/libpthread.so.0 #5 0x75c1a58f in clone () from /lib64/libc.so.6 As the bt is the same for skanlite and skanpage, it looks the problem is in KSaneCore. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 444987] silent crash while searching for scanners
https://bugs.kde.org/show_bug.cgi?id=444987 András Manţia changed: What|Removed |Added Ever confirmed|0 |1 CC||aman...@kde.org Status|REPORTED|CONFIRMED --- Comment #8 from András Manţia --- Confirmed with a canon scanner connected over the network. Passing "-d net" explicitly makes skanlite to not crash. (skanpage still crashes though with that option). skanlite 24.05.0, libsane 1.3.1. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472356] Okular crashes when configuring certificates with SafeNet Client
https://bugs.kde.org/show_bug.cgi?id=472356 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #7 from András Manţia --- I can confirm this on X11, Okular 24.0.2, Qt 6.7.0. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483722] kscreenlocker_greet locks up since Plasma 6 upgrade
https://bugs.kde.org/show_bug.cgi?id=483722 --- Comment #3 from András Manţia --- I experience this on X11 though. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483722] kscreenlocker_greet locks up since Plasma 6 upgrade
https://bugs.kde.org/show_bug.cgi?id=483722 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #2 from András Manţia --- This seems to happen if you move the mouse to cancel the lock when it was not fully locked. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483976] KOrganizer forgets the enabled calendars
https://bugs.kde.org/show_bug.cgi?id=483976 --- Comment #1 from András Manţia --- https://bugs.kde.org/show_bug.cgi?id=456717 looks related -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483976] New: KOrganizer forgets the enabled calendars
https://bugs.kde.org/show_bug.cgi?id=483976 Bug ID: 483976 Summary: KOrganizer forgets the enabled calendars Classification: Applications Product: korganizer Version: 6.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: aman...@kde.org Target Milestone: --- SUMMARY KOrganizer regularly forget what calendar was enabled and all calendars remain unchecked. STEPS TO REPRODUCE Hard to reproduce, but I suspect this happens when KOrganizer crashes for whatever reason. That is what happened just now: some calendars were enable, removed an event. While Kontact was in the background, it crashed. After restarting no calendars were enabled. This bug is not recent, it is around for a very long time. OBSERVED RESULT All calendars are unchecked. EXPECTED RESULT It should keep the state the user selected. SOFTWARE/OS VERSIONS KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 akonadiserver 6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482136] File copy/move progress does not appear in the notifications with Plasma 6.
https://bugs.kde.org/show_bug.cgi?id=482136 András Manţia changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from András Manţia --- Let's close for now, I didn't see recently. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 483412] When search field has focus, End key goes to the last entry in the results view, not the end of the search field
https://bugs.kde.org/show_bug.cgi?id=483412
--- Comment #5 from András Manţia ---
Here is a proposed patch (couldn't test as right now I have some config issues
to build plasma-workspace):
diff --git a/krunner/qml/RunCommand.qml b/krunner/qml/RunCommand.qml
index d7f174d938..48843057f4 100644
--- a/krunner/qml/RunCommand.qml
+++ b/krunner/qml/RunCommand.qml
@@ -228,16 +228,17 @@ ColumnLayout {
event.accepted = true;
}
}
+
+var inCompletionMode = runnerWindow.historyBehavior ===
HistoryBehavior.CompletionSuggestion
+&& fadedTextCompletion.text.length > 0;
// We only need to handle the Key_End case, the first item is
focused by default
-if (event.key === Qt.Key_End && results.count > 0 &&
cursorPosition === text.length) {
+if (event.key === Qt.Key_End && results.count > 0 &&
cursorPosition === text.length && !inCompletionMode) {
results.currentIndex = results.count - 1
event.accepted = true;
focusCurrentListView()
}
-if (runnerWindow.historyBehavior ===
HistoryBehavior.CompletionSuggestion
-&& fadedTextCompletion.text.length > 0
-&& cursorPosition === text.length
-&& event.key === Qt.Key_Right
+if (inCompletionMode && cursorPosition === text.length
+&& (event.key === Qt.Key_Right || event.key == Qt.Key_End)
) {
queryField.text = fadedTextCompletion.text
fadedTextCompletion.text = ""
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 483412] End key goes to the last entry, not the end of the lineedit
https://bugs.kde.org/show_bug.cgi?id=483412 András Manţia changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INTENTIONAL |--- --- Comment #3 from András Manţia --- Sorry, but you are wrong. As the description says, this happens when you type in the lineedit. That implies the lineedit has the focus. In any other lineedit pressing end goes to the end of the text, not somewhere else. Just try it. Or try what you have suggested: press CTRL-F and End. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 483412] New: End key goes to the last entry, not the end of the lineedit
https://bugs.kde.org/show_bug.cgi?id=483412 Bug ID: 483412 Summary: End key goes to the last entry, not the end of the lineedit Classification: Plasma Product: krunner Version: 6.0.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aman...@kde.org CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY As opposed to KRunner 5, the End key doesn't go to the end of the command lineedit, but instead jumps to the end of the list which is very annoying behavior change. STEPS TO REPRODUCE 1. Start to type something that is already in the command history of Krunner 2. After a few chars the rest appears in greyed out color 3. Press End key OBSERVED RESULT The last entry from the dropdown is selected which can be completely different from what you want, eg. a contact or such. EXPECTED RESULT The cursors jumps to the end of the lineedit as you would have typed the whole command from history. SOFTWARE/OS VERSIONS Linux/KDE Plasma: X11 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] KRunner not horizontally centered on X11
https://bugs.kde.org/show_bug.cgi?id=482666 --- Comment #11 from András Manţia --- Exactly. I removed kcmutils-imports, kcmutils-devel and after restarting krunner it appears where it should. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 --- Comment #5 from András Manţia --- Meantime I deinstalled some kf5 kcmutils related packages (but kept the library) and works now. Even more, bug https://bugs.kde.org/show_bug.cgi?id=482666 too. Thanks for the hint! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 András Manţia changed: What|Removed |Added Resolution|DOWNSTREAM |FIXED --- Comment #4 from András Manţia --- Yes, I have both KF5 and KF6 kcmutils, the KF5 version is needed for some apps -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 András Manţia changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from András Manţia --- Mar 10 20:30:22 stein.andtib krunner[5664]: kf.kio.gui: Could not find an executable named: "kcmshell5" Mar 10 20:30:22 stein.andtib krunner[5664]: QObject::connect(KProcessRunner, KJob): invalid nullptr parameter Mar 10 20:30:22 stein.andtib krunner[5664]: QObject::connect(KProcessRunner, KJob): invalid nullptr parameter Why does it try to start kcmshell5? andris@stein: ~ > krunner -v krunner 6.0.0 andris@stein: ~ > ps uax | grep krunner andris5664 0.0 0.4 6824540 288388 ? Ssl Feb29 3:42 /usr/bin/krunner andris 25957 0.0 0.0 8216 816 pts/16 S+ 20:31 0:00 grep --color=auto krunner andris@stein: ~ > which krunner /usr/bin/krunner andris@stein: ~ > ls /usr/bin/kcmshell* /usr/bin/kcmshell6 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] KRunner doesn't appear in the middle and does not remember its position
https://bugs.kde.org/show_bug.cgi?id=482666 --- Comment #8 from András Manţia --- I use 3 monitors with X11, scaling is 150%. The relative position is the same on all screens. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] KRunner doesn't appear in the middle and does not remember its position
https://bugs.kde.org/show_bug.cgi?id=482666 --- Comment #7 from András Manţia --- Created attachment 166694 --> https://bugs.kde.org/attachment.cgi?id=166694=edit Krunner in Center -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] KRunner doesn't appear in the middle and does not remember its position
https://bugs.kde.org/show_bug.cgi?id=482666 --- Comment #6 from András Manţia --- Created attachment 166693 --> https://bugs.kde.org/attachment.cgi?id=166693=edit KRunner on Top -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] New: Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 Bug ID: 482831 Summary: Krunner settings do not show up Classification: Plasma Product: krunner Version: 6.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aman...@kde.org CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY KRunner settings button does nothing STEPS TO REPRODUCE 1. Alt-F2 2. Click on settings button that is on the left OBSERVED RESULT Nothing happens. EXPECTED RESULT Settings should show. SOFTWARE/OS VERSIONS Tested X11 ADDITIONAL INFORMATION Settings can be reached via System Settings. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] KRunner doesn't appear in the middle and does not remember its position
https://bugs.kde.org/show_bug.cgi?id=482666 András Manţia changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED --- Comment #3 from András Manţia --- By testing more: - if set to appear on Top, it appears as in my screenshot. On top, but not horizontally centered - if set to appear in the Center it appears somewhere on the screen, definitely not in the center. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] KRunner doesn't appear in the middle and does not remember its position
https://bugs.kde.org/show_bug.cgi?id=482666 --- Comment #2 from András Manţia --- The main bug is that it doesn't appear in the middle as it used to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482670] Move To Desktop -> All Desktops does not work
https://bugs.kde.org/show_bug.cgi?id=482670 --- Comment #3 from András Manţia --- I am on X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482670] New: Move To Desktop -> All Desktops does not work
https://bugs.kde.org/show_bug.cgi?id=482670 Bug ID: 482670 Summary: Move To Desktop -> All Desktops does not work Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: aman...@kde.org CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY Move To Desktop -> All Desktops does not move the window to all desktops. STEPS TO REPRODUCE 1. Set up two desktops 2. Switch to Desktop 2 3. Start an app 4. In the taskbar right click to it and select Move To Desktop -> All Desktops OBSERVED RESULT The app remains only on Desktop 2 EXPECTED RESULT The app should be on all desktops ADDITIONAL INFORMATION Move to -> Desktop 1 still works. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] New: KRunner doesn't appear in the middle and does not remember its position
https://bugs.kde.org/show_bug.cgi?id=482666 Bug ID: 482666 Summary: KRunner doesn't appear in the middle and does not remember its position Classification: Plasma Product: krunner Version: 6.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aman...@kde.org CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Alt-F2 shows Krunner slightly to the left on the top and even if moved to the middle the position is not remembered. STEPS TO REPRODUCE 1. Alt-F2 2. See screenshot: it is not in the middle of the screen 3. Move with Alt+drag 4. Close 5. Open again: it is in the same position as in 2. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 480901] "Configure Okular" window under "Settings" menu is slow to open
https://bugs.kde.org/show_bug.cgi?id=480901 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #4 from András Manţia --- Same for me in other apps too, i don't have Screen reader enabled and don't have ~/.config/speech-dispatcher/speechd.conf at all. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #5 from András Manţia --- This bug is even more annoying than I thought: the shortcut keeps resetting itself to F10 from time to time (I don't know yet when it happens) despite changing it to "None". Configure Keyboard Shortucts Dialog also shown the Open Menu entry twice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] Plasma 6 panel has larger end margins compared to Plasma 5
https://bugs.kde.org/show_bug.cgi?id=482121 --- Comment #10 from András Manţia --- Created attachment 166391 --> https://bugs.kde.org/attachment.cgi?id=166391=edit Whole width panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] Plasma 6 panel has larger end margins compared to Plasma 5
https://bugs.kde.org/show_bug.cgi?id=482121 --- Comment #9 from András Manţia --- it is your decision of course, but right now if you look at the panel as a whole, it is unbalanced. See attachment. 27px on the left, 22px on the right. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #3 from András Manţia --- In my opinion Konsole is special and should be conservative in what shortcuts it steals from the applications running in the terminal. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482149] New: F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 Bug ID: 482149 Summary: F10 as menu shortcut steals it from applications Classification: Applications Product: konsole Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: aman...@kde.org Target Milestone: --- SUMMARY konsole in 24.0.2 has a default shortcut for F10 to open the menu, which conflicts with applications run in the terminal. STEPS TO REPRODUCE 1. Run konsole 2. Run mc (or mcedit) in the konsole 3. Press F10 to quit the app OBSERVED RESULT F10 will focus the Konsole's menu instead of quitting the app run in the terminal. EXPECTED RESULT Konsole should use as little as possible shortcuts, especially common ones. Otherwise terminal apps will not behave as expected. See also the very old issue https://bugs.kde.org/show_bug.cgi?id=162209 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] Plasma 6 panel has borders on sides
https://bugs.kde.org/show_bug.cgi?id=482121 András Manţia changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] Plasma 6 panel has borders on sides
https://bugs.kde.org/show_bug.cgi?id=482121 --- Comment #5 from András Manţia --- Created attachment 166247 --> https://bugs.kde.org/attachment.cgi?id=166247=edit Extra border on left Maybe this shows better: - gap between the panel edge and the app icon on the left is 33px - gap between the icons and the next item (desktop selection) is 24px -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] Plasma 6 panel has borders on sides
https://bugs.kde.org/show_bug.cgi?id=482121 --- Comment #4 from András Manţia --- Created attachment 166246 --> https://bugs.kde.org/attachment.cgi?id=166246=edit Plasma5 vs 6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] Plasma 6 panel has borders on sides
https://bugs.kde.org/show_bug.cgi?id=482121 --- Comment #3 from András Manţia --- Created attachment 166245 --> https://bugs.kde.org/attachment.cgi?id=166245=edit Inner is plasma5 in a remote machine, outer is plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] Plasma 6 panel has borders on sides
https://bugs.kde.org/show_bug.cgi?id=482121 --- Comment #2 from András Manţia --- In plasma 5 the menu icon was all the way to the left side. In plasma 6 there is a gap. The screenshot shows the left side of the panel all the way to the screen edge. I will add another screenshot with plasma5 vs 6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482136] New: File copy/move progress does not appear in the notifications with Plasma 6.
https://bugs.kde.org/show_bug.cgi?id=482136 Bug ID: 482136 Summary: File copy/move progress does not appear in the notifications with Plasma 6. Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: aman...@kde.org CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY File copy/move progress does not appear in the notifications with Plasma 6. STEPS TO REPRODUCE 1. Start to copy or move a large file (like 1-2 GB so it takes some time) 2. A dialog appears 2a. Cancel the move OBSERVED RESULT 1) The progress is not integrated into the systray notifications as with Plasma 5. 2) After the move is canceled the copy operation still goes on. EXPECTED RESULT 1) You can anytime check the progress in systray 2) Move is cancelled immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: plasmashell 6.0.0 dolphin 24.02.0 KDE Frameworks 6.0.0 Qt 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 479367] Cancelling move operation for kio-mtp results in data loss
https://bugs.kde.org/show_bug.cgi?id=479367 András Manţia changed: What|Removed |Added OS|Other |Linux Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 479367] Cancelling move operation for kio-mtp results in data loss
https://bugs.kde.org/show_bug.cgi?id=479367 --- Comment #3 from András Manţia --- With 24.0.2 I cannot reproduce, but that has other issues, like move cannot be cancelled at all. Using Cancel keeps copying the file until the end, but it will at least not delete the original. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 479367] Cancelling move operation for kio-mtp results in data loss
https://bugs.kde.org/show_bug.cgi?id=479367 --- Comment #2 from András Manţia --- OpenSuse Leap 15.5, the "official" KDE repositories , 23.08. Reproducing was as I wrote: plug the phone, move the files, cancel the operation. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #64 from András Manţia --- Works fine in 24.02.0, thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482121] New: Plasma 6 panel has borders on sides
https://bugs.kde.org/show_bug.cgi?id=482121 Bug ID: 482121 Summary: Plasma 6 panel has borders on sides Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: aman...@kde.org CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 166236 --> https://bugs.kde.org/attachment.cgi?id=166236=edit Space before the menu In Plasma 6.0.0 the widgets on the panel do not go all the way to the sides and you have borders there. I use full-width , non-floating panel. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 479367] New: Cancelling move operation for kio-mtp results in data loss
https://bugs.kde.org/show_bug.cgi?id=479367 Bug ID: 479367 Summary: Cancelling move operation for kio-mtp results in data loss Classification: Frameworks and Libraries Product: kio-extras Version: 23.08.4 Platform: Other OS: Other Status: REPORTED Severity: grave Priority: NOR Component: MTP Assignee: unassigned-b...@kde.org Reporter: aman...@kde.org CC: elvis.angelac...@kde.org Target Milestone: --- I d some files in Dolphin from the android phone (via MTP) and by mistake selected Move operation instead of copy, so I stopped the operation in the progress notification popup. This resulted in 0 byte files on the PC while the files from the phone were deleted with no (easy or at all) way to recover them. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478632] Print preview doesn't show the actual printout layout
https://bugs.kde.org/show_bug.cgi?id=478632 --- Comment #1 from András Manţia --- Created attachment 164243 --> https://bugs.kde.org/attachment.cgi?id=164243=edit Print preview even with scaling to full page area turned on -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478632] New: Print preview doesn't show the actual printout layout
https://bugs.kde.org/show_bug.cgi?id=478632 Bug ID: 478632 Summary: Print preview doesn't show the actual printout layout Classification: Applications Product: okular Version: 23.08.3 Platform: openSUSE OS: Other Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: aman...@kde.org Target Milestone: --- Created attachment 164242 --> https://bugs.kde.org/attachment.cgi?id=164242=edit Test pdf In Print settings (File->Print->PDF Options) set the Scale mode to "Fit to printable area". Go to File->Print Preview: the preview does not scale the content, which is confusing. Attached is the PDF I used and the screenshot of the preview. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478631] New: Printing settings are ignored
https://bugs.kde.org/show_bug.cgi?id=478631 Bug ID: 478631 Summary: Printing settings are ignored Classification: Applications Product: okular Version: 23.08.3 Platform: openSUSE OS: Other Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: aman...@kde.org Target Milestone: --- I have a color printer and the default printing is set to grayscale. If I try to print one pdf in color from okular and change the printing to color, it is ignored and i still get a greyscale print. Steps: 1) open the pdf 2)File->Print 3) Properties (for the printer) 4) Change the option of Color Mode in the Advanced tab) 5) OK 6) Print Result: grayscale print . -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 476943] New: Kontact frequently crashes when switching to the Calendar
https://bugs.kde.org/show_bug.cgi?id=476943 Bug ID: 476943 Summary: Kontact frequently crashes when switching to the Calendar Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: aman...@kde.org Target Milestone: --- Application: kontact (5.24.2 (23.08.2)) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 5.14.21-150500.55.31-default x86_64 Windowing System: X11 Distribution: openSUSE Leap 15.5 DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: Many times just switching to calendar causes the crash. Sometimes immediately after Kontact startup, sometimes happens at a later time but it is frequent enough. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 QVector::size() const (this=0x40002) at ../../include/QtCore/../../src/corelib/tools/qvector.h:88 #5 QSortFilterProxyModelPrivate::proxy_to_source(QModelIndex const&) const (this=0x55dd2e10fba0, proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:572 #6 0x7f794c258046 in QSortFilterProxyModel::mapToSource(QModelIndex const&) const (proxyIndex=..., this=0x55dd2e00abe0) at itemmodels/qsortfilterproxymodel.cpp:3179 #7 QSortFilterProxyModelPrivate::store_persistent_indexes() const (this=this@entry=0x55dd2e10fba0) at itemmodels/qsortfilterproxymodel.cpp:1248 #8 0x7f794c25dab8 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=0x55dd2e10fba0, source_top_left=, source_bottom_right=, roles=...) at itemmodels/qsortfilterproxymodel.cpp:1503 #9 0x7f794c25fd98 in QSortFilterProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at .moc/moc_qsortfilterproxymodel.cpp:275 #10 0x7f794c2ccba5 in doActivate(QObject*, int, void**) (sender=0x55dd2e05fae0, signal_index=3, argv=0x7fffae21a770) at kernel/qobject.cpp:3937 #11 0x7f794c2c61f2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55dd2e05fae0, m=m@entry=0x7f794c578ce0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffae21a770) at kernel/qobject.cpp:3985 #12 0x7f794c22a3ec in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=this@entry=0x55dd2e05fae0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #13 0x7f794c25d9d5 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=0x55dd2e066430, source_top_left=, source_bottom_right=, roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539 #14 0x7f794c25fd98 in QSortFilterProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at .moc/moc_qsortfilterproxymodel.cpp:275 #15 0x7f794c2ccba5 in doActivate(QObject*, int, void**) (sender=0x55dd2e354240, signal_index=3, argv=0x7fffae21aa80) at kernel/qobject.cpp:3937 #16 0x7f794c2c61f2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f794c578ce0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffae21aa80) at kernel/qobject.cpp:3985 #17 0x7f794c22a3ec in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=, _t1=, _t2=, _t3=) at .moc/moc_qabstractitemmodel.cpp:557 #18 0x7f78e052c3fc in () at /usr/lib64/libKPim5AkonadiCore.so.5 #19 0x7f794c2cce2b in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffae21ac40, r=0x55dd2e354240, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate(QObject*, int, void**) (sender=0x55dd2e12a8b0, signal_index=3, argv=0x7fffae21ac40) at kernel/qobject.cpp:3925 #21 0x7f794c2c61f2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55dd2e12a8b0, m=m@entry=0x7f794c578ce0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffae21ac40) at kernel/qobject.cpp:3985 #22 0x7f794c22a3ec in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=this@entry=0x55dd2e12a8b0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #23 0x7f794c25d9d5 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=0x55dd2e1f9320, source_top_left=, source_bottom_right=, roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539 #24 0x7f794c25fd98 in QSortFilterProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at
[kwin] [Bug 475868] New: Missing close button with cloned monitor setup
https://bugs.kde.org/show_bug.cgi?id=475868 Bug ID: 475868 Summary: Missing close button with cloned monitor setup Classification: Plasma Product: kwin Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: aman...@kde.org Target Milestone: --- The red close button overlay is not drawn above windows if you have overlapping (cloning) monitors enabled. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377399] kontact loses imap connections constantly
https://bugs.kde.org/show_bug.cgi?id=377399 András Manţia changed: What|Removed |Added CC||aman...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413051] Changes to "Unified Mailboxes" not permanent and not reflected in underlying Inboxes
https://bugs.kde.org/show_bug.cgi?id=413051 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #1 from András Manţia --- Still the same with 5.23.0. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413051] Changes to "Unified Mailboxes" not permanent and not reflected in underlying Inboxes
https://bugs.kde.org/show_bug.cgi?id=413051 András Manţia changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467855] On X11, Rectangular Region captures the wrong area with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=467855 --- Comment #9 from András Manţia --- This is a different layout. I have 3 monitors (two 4K, one smaller). Main one is the middle one. QT_SCREEN_SCALE_FACTORS=DisplayPort-0=1.5;DisplayPort-1=1.5;DisplayPort-2=1.5;HDMI-A-0=1.5; DisplayPort-0 is the middle one, DisplayPort-1 is the leftmost, DisplayPort-2 is the rightmost (smaller). HDMI was not turned on when I did the test. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467855] On X11, Rectangular Region captures the wrong area with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=467855 --- Comment #7 from András Manţia --- Yes, it still happens with 23.03.90 too -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467855] On X11, Rectangular Region captures the wrong area with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=467855 --- Comment #5 from András Manţia --- Created attachment 157883 --> https://bugs.kde.org/attachment.cgi?id=157883=edit Screen layout -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467855] Rectangular Region captures the wrong area with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=467855 --- Comment #3 from András Manţia --- Version 21.12.3 does not have the problem. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467855] Rectangular Region captures the wrong area with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=467855 --- Comment #2 from András Manţia --- I use X11 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467855] New: Rectangular Region captures the wrong area with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=467855 Bug ID: 467855 Summary: Rectangular Region captures the wrong area with multiple monitors Classification: Applications Product: Spectacle Version: 23.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: aman...@kde.org CC: k...@david-redondo.de Target Milestone: --- On a multi-monitor setup screenshoting a rectangle captures the wrong screen area: On the first (leftmost) monitor it is correct. On the second monitor the captured area is much to the right from the selected rectangle. On the third monitor it captured the full desktop (3 monitors) instead of the selection. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 226950] Creating an event for multiple days could be easier
https://bugs.kde.org/show_bug.cgi?id=226950 --- Comment #12 from András Manţia --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 226950] Creating an event for multiple days could be easier
https://bugs.kde.org/show_bug.cgi?id=226950 --- Comment #8 from András Manţia --- 13 years later the situation is the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #12 from András Manţia --- With my current config (first monitor scaled down from 4K with xrandr) it is even worse, the restored window appears partially on the first monitor, partially on the second, no matter where it was when it was closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #11 from András Manţia --- Still present with X11/Nvidia drivers Plasma 5.26.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 458138] New: Crash when adding new items to the Batch Queue Manager
https://bugs.kde.org/show_bug.cgi?id=458138 Bug ID: 458138 Summary: Crash when adding new items to the Batch Queue Manager Product: digikam Version: 7.7.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: aman...@kde.org Target Milestone: --- Application: digikam (7.7.0) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.14.21-150400.24.18-default x86_64 Windowing System: X11 Distribution: openSUSE Leap 15.4 DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: After drag & dropping the second file into the Batcj Queue Manager, digikam crashes. It is always reproducible. The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 0x7fcb19048c83 in QModelIndex::parent() const (this=0x559b3535f1d0) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443 #5 QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const (this=0x559b366be1b0, painter=0x7ffcc6f3b6d8, option=..., index=...) at itemviews/qtreeview.cpp:1610 #6 0x7fcb1b965b9f in () at /usr/lib64/libdigikamgui.so.7.7.0 #7 0x7fcb1904ede1 in QTreeView::drawTree(QPainter*, QRegion const&) const (this=this@entry=0x559b366be1b0, painter=painter@entry=0x7ffcc6f3b6d8, region=...) at itemviews/qtreeview.cpp:1504 #8 0x7fcb19052ef5 in QTreeView::paintEvent(QPaintEvent*) (this=0x559b366be1b0, event=0x7ffcc6f3bcd0) at itemviews/qtreeview.cpp:1332 #9 0x7fcb18dc1c38 in QWidget::event(QEvent*) (this=this@entry=0x559b366be1b0, event=event@entry=0x7ffcc6f3bcd0) at kernel/qwidget.cpp:9033 #10 0x7fcb18e690ce in QFrame::event(QEvent*) (this=0x559b366be1b0, e=0x7ffcc6f3bcd0) at widgets/qframe.cpp:550 #11 0x7fcb18fe98a3 in QAbstractItemView::viewportEvent(QEvent*) (this=this@entry=0x559b366be1b0, event=event@entry=0x7ffcc6f3bcd0) at itemviews/qabstractitemview.cpp:1746 #12 0x7fcb19053e1c in QTreeView::viewportEvent(QEvent*) (this=0x559b366be1b0, event=0x7ffcc6f3bcd0) at itemviews/qtreeview.cpp:1314 #13 0x7fcb17dcef40 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (receiver=receiver@entry=0x559b366be4f0, event=event@entry=0x7ffcc6f3bcd0) at kernel/qcoreapplication.cpp:1190 #14 0x7fcb18d81452 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x559b32d19890, receiver=receiver@entry=0x559b366be4f0, e=e@entry=0x7ffcc6f3bcd0) at kernel/qapplication.cpp:3631 #15 0x7fcb18d8823f in QApplication::notify(QObject*, QEvent*) (this=, receiver=0x559b366be4f0, e=0x7ffcc6f3bcd0) at kernel/qapplication.cpp:3161 #16 0x7fcb17dcf1b3 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x559b366be4f0, event=0x7ffcc6f3bcd0) at kernel/qcoreapplication.cpp:1064 #17 0x7fcb17dcf39e in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (receiver=receiver@entry=0x559b366be4f0, event=event@entry=0x7ffcc6f3bcd0) at kernel/qcoreapplication.cpp:1474 #18 0x7fcb18dba135 in QWidgetPrivate::sendPaintEvent(QRegion const&) (this=this@entry=0x559b366c00c0, toBePainted=...) at kernel/qwidget.cpp:5467 #19 0x7fcb18dbad1e in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=this@entry=0x559b366c00c0, pdev=pdev@entry=0x559b3667e860, rgn=..., offset=..., flags=flags@entry=..., sharedPainter=sharedPainter@entry=0x0, repaintManager=) at kernel/qwidget.cpp:5417 #20 0x7fcb18dbbbe0 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=this@entry=0x559b366bfc10, pdev=pdev@entry=0x559b3667e860, siblings=, index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x559b37d8bf10) at kernel/qwidget.cpp:5598 #21 0x7fcb18dbbd69 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=this@entry=0x559b366bfc10, pdev=pdev@entry=0x559b3667e860, siblings=, index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x559b37d8bf10) at kernel/qwidget.cpp:5584 #22 0x7fcb18dbbd69 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=this@entry=0x559b366bfc10, pdev=pdev@entry=0x559b3667e860, siblings=, index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x559b37d8bf10) at kernel/qwidget.cpp:5584 #23 0x7fcb18dbbd69 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*,
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 András Manţia changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #9 from András Manţia --- If that would be that simple... :) No, just using Plasma (Wayland) in the login screen does not work, as with this system (for whatever reason, I never debugged so far) it doesn't work, I get back to the login screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #7 from András Manţia --- FTR, Charm is a Qt only app. And I tested with Teamviewer, which is again not a KDE app, that works fine too. So the problem seems to be related to KDE applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #6 from András Manţia --- Here is an example how it goes (test case app Ruqola): - open it on screen 1 - minimize to tray (close the window) - click on the tray icon: it is shown on screen 1. - move to screen 2 - close the window (minimize to tray) - click the tray icon: it is shown again on screen 1 Now move to screen 2, but minimize the window, don't close. Click the tray icon: it is shown where it was on screen 2. Same can be reproduced with KMail or Amarok when tray icon is enabled, but I cannot reproduce e.g with Charm (charmtimetracker). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #5 from András Manţia --- No, that setting doesn't change the behavior. As for Wayland cannot say, I use X11 since forever and never tried to set up wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #3 from András Manţia --- X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451607] New: Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 Bug ID: 451607 Summary: Application are not restored where they were when clicking on the systray icon Product: plasmashell Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: aman...@kde.org CC: mate...@gmail.com Target Milestone: 1.0 In a multi-monitor setup clicking on a system icon of an application bring up the window on the screen that last had the focus. This is very annoying when you want to see applications always on a certain screen, and no, making kwin to put on that is not a solution, as you might want to move the app to a different screen for a while and expect to pop up where it was left last time. Reproducible with any app that can be minimized to systray. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450020] Dolphin sometime renames the wrong file
https://bugs.kde.org/show_bug.cgi?id=450020 András Manţia changed: What|Removed |Added Platform|Other |openSUSE RPMs Severity|normal |major Version|unspecified |21.12.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450020] New: Dolphin sometime renames the wrong file
https://bugs.kde.org/show_bug.cgi?id=450020 Bug ID: 450020 Summary: Dolphin sometime renames the wrong file Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: aman...@kde.org CC: kfm-de...@kde.org Target Milestone: --- Created attachment 146585 --> https://bugs.kde.org/attachment.cgi?id=146585=edit Video showing the bug SUMMARY If you have more files than it fits in the view, renaming the last file will rename the file that starts with the first typed letter. STEPS TO REPRODUCE 1. Create a few files in a folder, the first let's start with an A, like "Another file" 2. Shrink the view vertically so the scrollbar appears 3. Go to the last file and select it (with keyboard or right click) 4. Press F2 or select rename from the menu 5. start to type "Ano" and press enter 6. Selection jumps to the first file and renames to "no" See also the attached video. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 --- Comment #34 from András Manţia --- The reason could be the change in 5.12.2 per https://bugreports.qt.io/browse/QTBUG-72260 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 András Manţia changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #33 from András Manţia --- Sigh. Seems to be back again. Don't have time to debug it now, but will keep on my radar. I see on openSuse, Akregator 5.10.80 beta1, KF5 5.56.0, Qt 5.12.2. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 --- Comment #26 from András Manţia --- Do you see a crash of aKregator as well? From your description it seems that is something else, not what was fixed. If you have a debug build (or you can install the debug symbols on Arch), try to run akregator in gdb and provide a backtrace. Still I think this is a different problem and should be reported in a separate report. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401804] Connecting external display shows wrong placement of displays
https://bugs.kde.org/show_bug.cgi?id=401804 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #4 from András Manţia --- If I understood the bug and as I see https://phabricator.kde.org/D18101 should mitigate the problem, although it doesn't seem to completely fix it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 400302] Contents of 'Displays' system settings module isn't updating upon resizing after pressing its Default button
https://bugs.kde.org/show_bug.cgi?id=400302 András Manţia changed: What|Removed |Added Assignee|se...@kde.org |aman...@kde.org --- Comment #3 from András Manţia --- Fixed in Plasma 5.12, 5.14 and master branches. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 400302] Contents of 'Displays' system settings module isn't updating upon resizing after pressing its Default button
https://bugs.kde.org/show_bug.cgi?id=400302 András Manţia changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ksc ||reen/3e90b446c121acf3252de6 ||7247573253f5d15aee --- Comment #2 from András Manţia --- Git commit 3e90b446c121acf3252de67247573253f5d15aee by Andras Mantia. Committed on 09/01/2019 at 13:25. Pushed by amantia into branch 'Plasma/5.12'. Don't lose the widget layout after Default is pressed Summary: BUG: 400302 Reviewers: dvratil, #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D18121 M +2-0kcm/src/kcm_kscreen.cpp https://commits.kde.org/kscreen/3e90b446c121acf3252de67247573253f5d15aee -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 400302] Contents of 'Displays' system settings module isn't updating upon resizing after pressing its Default button
https://bugs.kde.org/show_bug.cgi?id=400302 András Manţia changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||aman...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 348126] Very poor use of space in display settings window
https://bugs.kde.org/show_bug.cgi?id=348126 András Manţia changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||aman...@kde.org --- Comment #4 from András Manţia --- With Plasma 5.14 is better, but not good enough, especially inside the System Settings. Outside it (kcmshell5 kcm_screen) it looks quite OK. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 319815] embedded video not playable, must open article in new tab to play
https://bugs.kde.org/show_bug.cgi?id=319815 András Manţia changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||aman...@kde.org --- Comment #4 from András Manţia --- Fixed by https://phabricator.kde.org/D17638 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 379016] Cookies only remembered for each Tab
https://bugs.kde.org/show_bug.cgi?id=379016 András Manţia changed: What|Removed |Added CC||aman...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from András Manţia --- https://phabricator.kde.org/D17638 might have fixed it, please text with the netx major release (akregator 5.11) and reopen if still present. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 121298] open link in external firefox
https://bugs.kde.org/show_bug.cgi?id=121298 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #6 from András Manţia --- Should we keep this open? I'd close with wontfix, as nowadays Konqui is well, less usable as a default browser anyway, so people usually have one fixed main browser, as Open in External Browser works fine in that case. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 401901] Lockup Crash
https://bugs.kde.org/show_bug.cgi?id=401901 András Manţia changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||aman...@kde.org --- Comment #1 from András Manţia --- I'd say this is fixed with https://phabricator.kde.org/D17563 Please reopen if you see with 18.12.1 or newer. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 399701] Closing tab to youtube gives crash [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=399701 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #1 from András Manţia --- Can you provide some newer link/feed? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 377437] clicking a link does not open the page
https://bugs.kde.org/show_bug.cgi?id=377437 András Manţia changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||aman...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 369500] Links in Feed are not opened in external browser anymore
https://bugs.kde.org/show_bug.cgi?id=369500 András Manţia changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||aman...@kde.org --- Comment #1 from András Manţia --- This seems to work with 5.10 (from KDE apps 18.12). If you still see, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 374692] Javascript does not work
https://bugs.kde.org/show_bug.cgi?id=374692 András Manţia changed: What|Removed |Added CC||aman...@kde.org --- Comment #2 from András Manţia --- Can you provide an example feed/article? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 190369] (usability) asking confirmation when activating slow keys
https://bugs.kde.org/show_bug.cgi?id=190369 András Manţia changed: What|Removed |Added Assignee|aman...@kde.org |unassigned-b...@kde.org --- Comment #5 from András Manţia --- https://phabricator.kde.org/D17533 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 András Manţia changed: What|Removed |Added Assignee|kdepim-b...@kde.org |aman...@kde.org Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #22 from András Manţia --- Fixed, will be in the next release (18.12.1 +) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 --- Comment #21 from András Manţia --- Theoretically anything related to opening and closing webpages in Akregator is a duplicate in the sense that even if the exact reproducing method is not the same, the patch should fix it. I just found out though, that there are other webengine instances, outside of Akregator in Kontact, so probably not all kontact crashes (eg. Kontact crash on close) are fixed by it. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 400494] Kontact crashes - clicking other news-feed URL in Akregator while internal webview is opened
https://bugs.kde.org/show_bug.cgi?id=400494 András Manţia changed: What|Removed |Added CC||aman...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from András Manţia --- *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 András Manţia changed: What|Removed |Added CC||p...@gmx.net --- Comment #18 from András Manţia --- *** Bug 400494 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 András Manţia changed: What|Removed |Added CC||o...@iki.fi --- Comment #17 from András Manţia --- *** Bug 401905 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 401905] Akregator crashes when HTTP request times out
https://bugs.kde.org/show_bug.cgi?id=401905 András Manţia changed: What|Removed |Added CC||aman...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from András Manţia --- Most probably a duplicate of 371511, so let's track there, as it will be soon fixed. *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 András Manţia changed: What|Removed |Added CC||gianni_2...@hotmail.it --- Comment #16 from András Manţia --- *** Bug 397866 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397866] akregator crashes when closing the rightmost tab
https://bugs.kde.org/show_bug.cgi?id=397866 András Manţia changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||aman...@kde.org --- Comment #14 from András Manţia --- *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 401638] Segmentation fault (version 5.9.3) when closing the full article
https://bugs.kde.org/show_bug.cgi?id=401638 András Manţia changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #14 from András Manţia --- Let's track this in 371511, as it is older and is the same issue. *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 András Manţia changed: What|Removed |Added CC||vokalashniko...@gmail.com --- Comment #15 from András Manţia --- *** Bug 401638 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
