[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #3 from Michail Vourlakos --- (In reply to Jeff Hodd from comment #1) > I can confirm that latte-dock v0.10.0 is broken. It's not functioning > properly when started via KDE/Plasma Autostart. On login, the bottom half of > the screen is blacked out and blocks any desktop functionality from > mid-screen down. If you open a terminal and kill the latte-dock process, all > desktop functionality returns. You can then start latte-dock from the system > menu, and it starts and functions as expected. I have tried clearing the > qmlcache, rebuilding the package in my build environment, building the > master version from github, autostarting from xdg and attempted to start it > from session restore. None of these approaches fix the problem. I have not > found any evidence that the latte-dock process has crashed, it's simply > interfering with the normal desktop startup. I have checked the logs for any > sign of crashes - I haven't found any. I did note that my build of the > master code did produce a drkonqi process which I have never been able to > access. for the autostart issues: 1. You must make sure that the auto start desktop file used is updated properly 2. Remove all latte desktop files from: ~/.config/autostart/ 3. Add in ~/.config/autostart/ the new desktop file provided from Latte The crash comes when the system tries to autostart Latte more than two times. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/latte-dock/commit/a67e3c |ma/latte-dock/commit/66ddda |050f1bf79d6e9687cfd66c8733b |956b299bfe8c6c001f15b016498 |3d4bdd0 |0d70dad --- Comment #12 from Michail Vourlakos --- Git commit 66ddda956b299bfe8c6c001f15b0164980d70dad by Michail Vourlakos. Committed on 12/08/2021 at 05:08. Pushed by mvourlakos into branch 'master'. fix build with Fedora requirements --simplify warnings and add formalt security checks M +8-1CMakeLists.txt https://invent.kde.org/plasma/latte-dock/commit/66ddda956b299bfe8c6c001f15b0164980d70dad -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/latte-dock/commit/a67e3c ||050f1bf79d6e9687cfd66c8733b ||3d4bdd0 --- Comment #11 from Michail Vourlakos --- Git commit a67e3c050f1bf79d6e9687cfd66c8733b3d4bdd0 by Michail Vourlakos. Committed on 12/08/2021 at 05:04. Pushed by mvourlakos into branch 'v0.10'. fix build with Fedora requirements --simplify warnings and add formalt security checks M +8-1CMakeLists.txt https://invent.kde.org/plasma/latte-dock/commit/a67e3c050f1bf79d6e9687cfd66c8733b3d4bdd0 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Michail Vourlakos --- In the crash topic this is fixed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428687] 11pt text object is shown as 10pt in editor
https://bugs.kde.org/show_bug.cgi?id=428687 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 388312] Timeline today always shows an old file & not properly updated
https://bugs.kde.org/show_bug.cgi?id=388312 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439712] Plasma Wayland crashed after turning hdmi monitor off
https://bugs.kde.org/show_bug.cgi?id=439712 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 440329] CPU usage shown, not the same of other task managers
https://bugs.kde.org/show_bug.cgi?id=440329 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439014] Appearance Settings always crashes
https://bugs.kde.org/show_bug.cgi?id=439014 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439071] Okular print: cannot stretch smaller pages to bigger paper format
https://bugs.kde.org/show_bug.cgi?id=439071 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438949] Latte dock crash after "desktop effects restart"
https://bugs.kde.org/show_bug.cgi?id=438949 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438909] Multinegation in “Inhibit automatic sleep and screen locking” checkbox confuses me.
https://bugs.kde.org/show_bug.cgi?id=438909 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 435704] TextEdit corners not displaying correctly
https://bugs.kde.org/show_bug.cgi?id=435704 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440885] Edit Current Profile opens the editing of a new profile when attempting to edit the Default profile
https://bugs.kde.org/show_bug.cgi?id=440885 Javier O. Cordero Pérez (Cuperino) changed: What|Removed |Added CC||jav...@imaginary.tech -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440885] New: Edit Current Profile opens the editing of a new profile when attempting to edit the Default profile
https://bugs.kde.org/show_bug.cgi?id=440885
Bug ID: 440885
Summary: Edit Current Profile opens the editing of a new
profile when attempting to edit the Default profile
Product: konsole
Version: master
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kpart
Assignee: konsole-de...@kde.org
Reporter: jav...@imaginary.tech
Target Milestone: ---
SUMMARY
When "Default" profile is selected "Edit Current Profile..." opens the Edit
Profile window set to create a new profile instead of allowing to edit
"Default" profile.
STEPS TO REPRODUCE
1. Make sure "Default" is the currently active profile.
2. Right click on the terminal emulator and choose "Edit Current Profile...".
OBSERVED RESULT
Edit Profile window opens, but it is set to edit a new (non-existent) profile.
Attempting to name this profile like any pre-existing profile, including
"Default", results in the following error:
`A profile with the name "{{profile_name}}" already exists.`
EXPECTED RESULT
Edit Profile window opens set to edit "Default" profile.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon Testing Edition
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
Similar to bug 396808 from 2018. This may be a regression.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 429249] Sending SMS doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=429249 Charis Mitsakis changed: What|Removed |Added CC||cmitsakis@protonmail.co ||m --- Comment #11 from Charis Mitsakis --- I have the same issue. Sending SMS via kdeconnect-cli fails silently. Below you can find the output of adb logcat. I also tried programmatically via dbus and also tried qdbus and d-feet with the same result. > Then run the command "adb logcat" from a terminal window That was very helpful. If you have any suggestion how I can investigate this further let me know. KDE Connect version 21.04.3 OS: Arch Linux Phone: Xiaomi Redmi Note 4 KDE Connect Android app version 1.17 08-12 05:38:38.586 24410 29993 W Sending message: Unable to get outgoing address for sub ID -1 using null 08-12 05:38:38.609 2078 3442 W ContentProvider: Normalized content://telephony/carriers//preferapn/subId/-1 to content://telephony/carriers/preferapn/subId/-1 to avoid possible security issues 08-12 05:38:38.657 2078 3442 D TelephonyProvider: subIdString = -1 subId = -1 08-12 05:38:38.657 2078 3442 D TelephonyProvider: getPreferredApnIdFromApn: for subId -1 08-12 05:38:38.690 24410 29993 E Sending message: Exception 08-12 05:38:38.690 24410 29993 E Sending message: java.lang.NullPointerException: Attempt to read from field 'java.lang.String org.kde.kdeconnect.Helpers.TelephonyHelper$LocalPhoneNumber.number' on a null object reference 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Plugins.SMSPlugin.SmsMmsUtils.sendMessage(SmsMmsUtils.java:158) 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin.java:413) 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Device.onPacketReceived(Device.java:570) 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Backends.BaseLink.packageReceived(BaseLink.java:70) 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.receivedNetworkPacket(LanLink.java:249) 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0(LanLink.java:97) 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0$LanLink(LanLink.java) 08-12 05:38:38.690 24410 29993 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.-$$Lambda$LanLink$u8LWlVA_uGoxlkxdXMbWulE13kY.run(lambda) 08-12 05:38:38.690 24410 29993 E Sending message: at java.lang.Thread.run(Thread.java:760) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425832] TIFFTAG_ORIENTATION ignored on import
https://bugs.kde.org/show_bug.cgi?id=425832 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/997 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399302] Random OpenGL freeze causes KWin to disable compositing
https://bugs.kde.org/show_bug.cgi?id=399302 tildearrow changed: What|Removed |Added CC||tildear...@protonmail.com --- Comment #1 from tildearrow --- Just reproduced this today. Seems like it is a 5% chance, and requires an HDD or slow storage medium to increase probability of reproduction. It could be that the compositor indeed freezes because everything else is loading at the same time and it strains the disk that it causes KWin to issue a false-positive and disable compositing... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440884] New: dolphin slow launch on wayland
https://bugs.kde.org/show_bug.cgi?id=440884 Bug ID: 440884 Summary: dolphin slow launch on wayland Product: dolphin Version: 21.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: i...@mikelpr.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY dolphin takes a lot of time to open on wayland STEPS TO REPRODUCE 1. launch dolphin 2. wait for the main window to appear OBSERVED RESULT the window takes about 30 seconds to appear. the following is printed on the terminal: kf.xmlgui: KActionCollection::setComponentName does not work on a KActionCollection containing actions! "dolphin" (takes its ~30 seconds here with no output) kf.dbusaddons: 'kdeinit5' is taking more than 30 seconds to start. (dolphin window appears) EXPECTED RESULT instant dolphin window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440493] Add an option for whether to enable or disable Bluetooth adapters at session start
https://bugs.kde.org/show_bug.cgi?id=440493 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #10 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/bluedevil/-/merge_requests/44 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 440883] New: xwayland apps blurry even on integer scales
https://bugs.kde.org/show_bug.cgi?id=440883 Bug ID: 440883 Summary: xwayland apps blurry even on integer scales Product: KScreen Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: i...@mikelpr.com Target Milestone: --- SUMMARY apps running on Xwayland are blurry always. at 200% STEPS TO REPRODUCE 1. open any X11 app (any electron app) OBSERVED RESULT blurry rendering EXPECTED RESULT perfect rendering SOFTWARE/OS VERSIONS Linux: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I saw bug #412088 refering to blurry rendering on non integer scales. This is for integer scales (200%) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440872] digikam dies at 'Checking the ICC repository...'
https://bugs.kde.org/show_bug.cgi?id=440872 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |ColorManagement -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440872] digikam dies at 'Checking the ICC repository...'
https://bugs.kde.org/show_bug.cgi?id=440872 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||7.4.0 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440882] Screen Energy Saving does not respect SimulateUserActivity in XWayland sessions
https://bugs.kde.org/show_bug.cgi?id=440882 Forest changed: What|Removed |Added Summary|Screen Energy Saving does |Screen Energy Saving does |not respect |not respect |SimulateUserActivity when |SimulateUserActivity in |XWayland is used|XWayland sessions -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440882] New: Screen Energy Saving does not respect SimulateUserActivity when XWayland is used
https://bugs.kde.org/show_bug.cgi?id=440882 Bug ID: 440882 Summary: Screen Energy Saving does not respect SimulateUserActivity when XWayland is used Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fores...@sonic.net Target Milestone: --- SUMMARY The org.freedesktop.ScreenSaver SimulateUserActivity dbus method is supposed to reset screen blanking timeouts. It works for both the screen locker and the Screen Energy Saving feature when used in X.Org desktop sessions. However, in XWayland sessions, it works only for the screen locker: The Screen Energy Saving feature ignores SimulateUserActivity on XWayland, and the screen therefore powers off when it should not. STEPS TO REPRODUCE 1. Start a KDE Plasma 5 XWayland desktop session. (I used KUbuntu 21.04 in my test.) 2. In KDE Settings: Screen Energy Saving, enable the feature and set "Switch off after" to 1 minute. (Note: You might need real hardware, not a VM, for the option to appear.) 3. Start a shell script that runs the following command every few seconds: qdbus org.freedesktop.ScreenSaver /ScreenSaver SimulateUserActivity 4. Sit back for a minute waiting for the energy saving mode to activate. OBSERVED RESULT The screen powers off, ignoring the SimulateUserActivity calls. EXPECTED RESULT The screen should not power off. It should respect the SimulateUserActivity calls, just as it does in an X.Org session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Problem exists with XWayland sessions, but not X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 Jeff Hodd changed: What|Removed |Added CC||jgh...@gmail.com --- Comment #1 from Jeff Hodd --- I can confirm that latte-dock v0.10.0 is broken. It's not functioning properly when started via KDE/Plasma Autostart. On login, the bottom half of the screen is blacked out and blocks any desktop functionality from mid-screen down. If you open a terminal and kill the latte-dock process, all desktop functionality returns. You can then start latte-dock from the system menu, and it starts and functions as expected. I have tried clearing the qmlcache, rebuilding the package in my build environment, building the master version from github, autostarting from xdg and attempted to start it from session restore. None of these approaches fix the problem. I have not found any evidence that the latte-dock process has crashed, it's simply interfering with the normal desktop startup. I have checked the logs for any sign of crashes - I haven't found any. I did note that my build of the master code did produce a drkonqi process which I have never been able to access. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 440881] New: Add a timezone code option to the clock
https://bugs.kde.org/show_bug.cgi?id=440881 Bug ID: 440881 Summary: Add a timezone code option to the clock Product: kdeplasma-addons Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: timer Assignee: plasma-b...@kde.org Reporter: antti.s...@gmail.com Target Milestone: --- SUMMARY Would it be possible to have an option to display the timezone code in timezone list and search? The current city based notation of the clock is of zero use to me since most event start announcements on the internet are displayed as a code. Usually people put PST/EST/GMT/JST as their start time. It would also be easier to search for. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 433054] Code errors in the lock screen theme (1st party or 3rd-party) can block screen unlocking
https://bugs.kde.org/show_bug.cgi?id=433054 --- Comment #62 from David Edmundson --- >2. Long-term: remove all code from lock screen themes--like Plasma themes, for >example. Then 3rd-party themes can's break screen unlock by shipping faulty >code (only we can do that lol). Personally I would very happily support this. We still have the plasma theme and wallpaper loaded from plugins, so it's just about being able to change the layout of some text fields. It's not like we make the kwallet prompt configurable! If people do really want to overwrite things, they can always mod the original files, we're just removing it from being supported. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439610] Autoscroll using middle click
https://bugs.kde.org/show_bug.cgi?id=439610 Axle changed: What|Removed |Added CC||axl...@gmail.com --- Comment #5 from Axle --- I Think adding autoscrolling support across all application i.e.(discord, document viewer, web browser.) would be great. I really don't like having to do hacky code just to get this feature. I don't know if x11 can support it, but I think wayland is the future, and can probably be implemented in the wayland kwin compositor. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 433054] Code errors in the lock screen theme (1st party or 3rd-party) can block screen unlocking
https://bugs.kde.org/show_bug.cgi?id=433054 --- Comment #61 from David Edmundson --- WRT this bug, ithere is (supposedly) a fallback path in kscreenlocker itself. It does check if a root item gets created or not. Problem is all our UI code is in a Loader for an attempted startup optimisation, which is why it doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 433054] Code errors in the lock screen theme (1st party or 3rd-party) can block screen unlocking
https://bugs.kde.org/show_bug.cgi?id=433054 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Priority|VHI |NOR --- Comment #60 from David Edmundson --- Removing from VHI, if something only affects modders with 3rd party addons it is not that big of a priority no matter the impact. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #36 from Jaroslav Skarvada --- digiKam PR: https://invent.kde.org/graphics/digikam/-/merge_requests/136 Unofficial unsupported build for testing (it's built from the v7.3.0 tag): https://jskarvad.fedorapeople.org/digiKam/digiKam-7.3.0-Win64.exe -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #35 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/digikam/-/merge_requests/136 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440880] New: sound borked after resume
https://bugs.kde.org/show_bug.cgi?id=440880 Bug ID: 440880 Summary: sound borked after resume Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dav1dblunk...@hotmail.com Target Milestone: --- After sleep and resume my audio is borked. I need to restart pulseaudio using pulseaudio -k and restart any applications that use sound. Sometimes I also need to restart plasmashell to permit the mixer to operate the volume controls. This problem seems to wax and wane with updates (ubuntu 20.04) but never goes away. Sometimes it resumes with sound (around 1 in 20 times). It's quite irritating. lunesta 5.4.0-80-generic Ubuntu 20.04.2 LTS KDE Frameworks 5.68.0 Qt 5.12.8 (built against 5.12.8) The xcb windowing system digital HDMI output nvidia graphics -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 440879] Feature request: search by artist name
https://bugs.kde.org/show_bug.cgi?id=440879 Neel patel changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 440879] Feature request: search by artist name
https://bugs.kde.org/show_bug.cgi?id=440879 --- Comment #1 from Smeha Pillay --- The following issue is resolved: ISSUE DESCRIPTION: The feature of searching an album by searching by the name of an artist is not working. STEPS TO REPRODUCE THE REPORTED BUG 1. Open the app. 2. Click on the search button. 3. Type in a name of the artist. 4. Click on search. RESOLUTION STEPS: The configuration of search engine is modified. We have added "artist" as a parameter in the search query. ACTAUL RESULT The application shows a list of albums by that artist. EXPECTED RESULT The application shows a list of albums by that artist. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (Available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 440879] Feature request: search by artist name
https://bugs.kde.org/show_bug.cgi?id=440879 Neel patel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392877] balooctl index command with large number of files corrupts db
https://bugs.kde.org/show_bug.cgi?id=392877 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #4 from tagwer...@innerjoin.org --- (In reply to Nate Graham from comment #3) > Is this 100% fixed now? Or is there still anything left to do? Checked, on an index of 2,000,000 files (recorded Go games), the balooctl option to clear the entries for 1 files: balooctl clear 2016-01* and reindex them balooctl index 2016-01* in one transaction. Done on a system with constrained RAM so that transaction filled the RAM and extended into swap. It completed; the index was seemingly OK. Can never be sure, but good enough? -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 440879] Feature request: search by artist name
https://bugs.kde.org/show_bug.cgi?id=440879 Neel patel changed: What|Removed |Added Assignee|jbb.m...@gmx.de |snehapilla...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440785] Menu broken
https://bugs.kde.org/show_bug.cgi?id=440785 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #4 from Albert Astals Cid --- Do you think you'd be able to reproduce the problem by trying to do the same editing of the toolbars? If we could reproduce the problem it'd be much easier to fix -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 440879] Feature request: search by artist name
https://bugs.kde.org/show_bug.cgi?id=440879 Neel patel changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 440879] Feature request: search by artist name
https://bugs.kde.org/show_bug.cgi?id=440879 Neel patel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 440879] New: Feature request: search by artist name
https://bugs.kde.org/show_bug.cgi?id=440879 Bug ID: 440879 Summary: Feature request: search by artist name Product: audiotube Version: unspecified Platform: Homebrew (macOS) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: jbb.m...@gmx.de Reporter: nine091...@gmail.com Target Milestone: --- SUMMARY The feature of searching an album by searching by the name of an artist is not working. STEPS TO Test 1. Open the app. 2. Click on the search button. 3. Type in a name of the artist. 4. Click on search. OBSERVED RESULT The application does not allow you to search for the albums by that artist. EXPECTED RESULT The application shows a list of albums by that artistt. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439628] Feature request: change volume (and ringtone) for ring my phone/find device feature
https://bugs.kde.org/show_bug.cgi?id=439628 Neel patel changed: What|Removed |Added CC||nine091...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 59060] Feature Request: Ability to have a "not read for X time" based filter paramater in addition to existing ones
https://bugs.kde.org/show_bug.cgi?id=59060 Neel patel changed: What|Removed |Added CC||nine091...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440878] New: Tabbar title format with session number behaves weird
https://bugs.kde.org/show_bug.cgi?id=440878 Bug ID: 440878 Summary: Tabbar title format with session number behaves weird Product: konsole Version: 21.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: ose...@gmail.com Target Milestone: --- Created attachment 140658 --> https://bugs.kde.org/attachment.cgi?id=140658=edit Tab title session number ss My daily workflow requires to interact with many servers for configuration and management. For that, i am using custom tab/remote tab title format and i add session number place holder for new tabs to interact easly with alt+ shortcut. What annoys me is, if i close a tab and open new one after that, tab number gets incremented number, not last closed one which confuses me for keyboard shortcut. For instance; i have 3 tabs open and their tab titles are 1,2,3. if i close tab number three and open new one, tab titles become 1,2,4. At the end of the day my tab titles appearence is 1,3,8,11 etc which is annoying. To reproduce, edit your profile -> tabs -> Tab Titles. Insert session number place holder for your tab titles. Then open and close tabs. You will see numbers become weird and hard to navigate with shortcut. In short, new tab sesion number must continue where it leaved off. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440877] New: Discovery app crashes. Crash report states the crash was during a cancelation of flatpak install. it was not cancelled!
https://bugs.kde.org/show_bug.cgi?id=440877 Bug ID: 440877 Summary: Discovery app crashes. Crash report states the crash was during a cancelation of flatpak install. it was not cancelled! Product: Discover Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: d_boot...@hotmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.8-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: Installing flatpak app (two at the same time). Suddenly the app creashed without me interfering - Custom settings of the application: added flathub The crash does not seem to be reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f5f91c159c0 (LWP 7410))] [KCrash Handler] #6 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x556842b35300, fundamental_type=fundamental_type@entry=80) at ../gobject/gtype.c:4082 #7 0x7f5f92d829c5 in g_object_unref (_object=0x556842b35300) at ../gobject/gobject.c:3421 #8 0x7f5f683077be in FlatpakTransactionThread::~FlatpakTransactionThread (this=, this=) at /usr/src/debug/discover-5.22.4-1.1.x86_64/libdiscover/backends/FlatpakBackend/FlatpakTransactionThread.cpp:77 #9 FlatpakTransactionThread::~FlatpakTransactionThread (this=, this=) at /usr/src/debug/discover-5.22.4-1.1.x86_64/libdiscover/backends/FlatpakBackend/FlatpakTransactionThread.cpp:79 #10 FlatpakJobTransaction::~FlatpakJobTransaction (this=, this=) at /usr/src/debug/discover-5.22.4-1.1.x86_64/libdiscover/backends/FlatpakBackend/FlatpakJobTransaction.cpp:30 #11 0x7f5f68307879 in FlatpakJobTransaction::~FlatpakJobTransaction (this=, this=) at /usr/src/debug/discover-5.22.4-1.1.x86_64/libdiscover/backends/FlatpakBackend/FlatpakJobTransaction.cpp:31 #12 0x7f5f9505fcff in QObject::event (this=0x7f5f4c017b30, e=0x556844d729c0) at kernel/qobject.cpp:1301 #13 0x7f5f96119a7f in QApplicationPrivate::notify_helper (this=, receiver=0x7f5f4c017b30, e=0x556844d729c0) at kernel/qapplication.cpp:3632 #14 0x7f5f9503396a in QCoreApplication::notifyInternal2 (receiver=0x7f5f4c017b30, event=0x556844d729c0) at kernel/qcoreapplication.cpp:1064 #15 0x7f5f950369b7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5568421a5780) at kernel/qcoreapplication.cpp:1821 #16 0x7f5f9508b7d3 in postEventSourceDispatch (s=s@entry=0x556842277e80) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7f5f9343f80f in g_main_dispatch (context=0x7f5f88005000) at ../glib/gmain.c:3337 #18 g_main_context_dispatch (context=0x7f5f88005000) at ../glib/gmain.c:4055 #19 0x7f5f9343fb98 in g_main_context_iterate (context=context@entry=0x7f5f88005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #20 0x7f5f9343fc4f in g_main_context_iteration (context=0x7f5f88005000, may_block=1) at ../glib/gmain.c:4196 #21 0x7f5f9508ae54 in QEventDispatcherGlib::processEvents (this=0x556842283280, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f5f9503236b in QEventLoop::exec (this=this@entry=0x7ffdcea570e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f5f9503a650 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x7f5f9547e1dc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #25 0x7f5f961199f5 in QApplication::exec () at kernel/qapplication.cpp:2824 #26 0x556841532f90 in main (argc=, argv=) at /usr/src/debug/discover-5.22.4-1.1.x86_64/discover/main.cpp:196 [Inferior 1 (process 7410) detached] Possible duplicates by query: bug 439668. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440870] Krita 5 git 08ccd37: When I converted colorized mask layers to paint layer, the converted layers jump on top of the line art layer (the layer I use for drawing line art)
https://bugs.kde.org/show_bug.cgi?id=440870 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from tomtomtomreportin...@gmail.com --- This should have been fixed with https://invent.kde.org/graphics/krita/-/commit/672de3752b156d933d4be8829b8a24a1834e1fb5 . Also see https://bugs.kde.org/show_bug.cgi?id=438397 . Does the issue still happen for you on the latest master? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 440856] Option to show wifi QR code is not very discoverable
https://bugs.kde.org/show_bug.cgi?id=440856 --- Comment #5 from Rolf Eike Beer --- Ok, indeed, I have never seen this before. I looked for it in the network details, especially the security page. I would like to be able to show the QR code even for a network that is not in range as that was my usecase today: take the connection data for a Wifi with me that I knew I had not connected to with the new phone. Showing it directly in the applet the same way as the clipboard tray has it would be great. The big "disconnect network" button could be replaced by something smaller with only an icon (I'm on 5.18.5, so this maybe already is resolved). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kunitconversion] [Bug 428464] Missing currencies in the converter of Krunner
https://bugs.kde.org/show_bug.cgi?id=428464 --- Comment #10 from Alexander Lohnau --- Thanks for the research. I will look into the options you presented. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 403153] ComboBox entry popup is not resized to delegate width
https://bugs.kde.org/show_bug.cgi?id=403153 --- Comment #19 from Patrick Silva --- at least duplicates bug 432829 and bug 421746 are still reproducible on neon unstable, -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440808] "Run as" does not work using Wayland
https://bugs.kde.org/show_bug.cgi?id=440808 --- Comment #2 from Andreas Hartmann --- "One cannot run apps as another user on wayland." You are joking, aren't you? Even Windows is able to run programs as different users. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440201] Windows appear detached from titlebars in Present Windows and Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=440201 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #3 from Alexandre Pereira --- nice ! this also fixed "firefox wayland" "window opening" when using the "scale effect". ( it used to look like the window was divided into 4 parts all growing ) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759
--- Comment #10 from Gerald Cox ---
(In reply to Michail Vourlakos from comment #9)
> I made a test. Please change the two lines you mentioned in CMakeLists file
> with:
>
> #hide warnings
> string(REPLACE "-Wall" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
> string(REPLACE "-Wdeprecated-declarations" "" CMAKE_CXX_FLAGS
> ${CMAKE_CXX_FLAGS})
> string(REPLACE "-Wreorder" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
> string(REPLACE "-Wunused-variable" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
> string(REPLACE "-Wunused-parameter" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
>
> #add format security check
> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wformat -Werror=format-security")
>
>
> 1. I enforced the Fedora rule to check what errors are happening
> 2. Does it build in Fedora in that case?
> 3. In my system it with above changes it builds just fine. If it doesnt
> build in Fedora what warnings are considered errors and it is not built?
Yes, that builds fine! Thanks for fixing!
I also ran with the trace option, the error is:
cc1plus: error: '-Wformat-security' ignored without '-Wformat'
[-Werror=format-security]
so that seems to imply that the errors are from removing the -Wformat and
Fedora adding the Werror=format-security. Which would explain why when I also
removing it via the string REPLACE gets around the issue.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 421098] Speed control of brush properties has an impractically large 'Fast' value.
https://bugs.kde.org/show_bug.cgi?id=421098 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/996 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440876] New: an even easier way to test new Plasma versions
https://bugs.kde.org/show_bug.cgi?id=440876 Bug ID: 440876 Summary: an even easier way to test new Plasma versions Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_updates Assignee: plasma-b...@kde.org Reporter: aron...@gmail.com Target Milestone: --- I think it would help with making Plasma more stable if there was an option to install Plasma Beta releases and a new ex. Alpha-version that updates to master every couple of weeks from the 'updates' settings. sort of like kdesrc-build without the build and with a GUI. or sort of like Windows Insider, but with the option to switch between stable and alpha at the login screen. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #50 from medin --- I solved my problem by removing "~/.local/share/kxmlgui5/okular/shell.rc" file then Okular showed the correct menu entries, but that removed file is never recreated again. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440785] Menu broken
https://bugs.kde.org/show_bug.cgi?id=440785 --- Comment #3 from medin --- > Did you configure the toolbars before this problem occured? Yes I modified toolbar items to add more buttons, it seems removing shell.rc solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440875] New: System Settings crash when apply after removing virtual desktops
https://bugs.kde.org/show_bug.cgi?id=440875 Bug ID: 440875 Summary: System Settings crash when apply after removing virtual desktops Product: systemsettings Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: g4rg4n...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.13.9-200.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.4 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: 1) System Settings -> Workspace Behaviour -> Virtual Desktops 2) Remove Desktop 3) Apply 4) Crash The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f91a74b2f37 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #6 0x7f91a749f419 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #7 0x7f91a74bb7c3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #8 0x7f91a4e1cc04 in ffi_call_unix64 () from /lib64/libffi.so.6 #9 0x7f91a4e1c107 in ffi_call () from /lib64/libffi.so.6 #10 0x7f91a740cd10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #11 0x7f91a740d42b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #12 0x7f91a740d61c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #13 0x7f91a74977a3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #14 0x7f91a9aadce0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f91a9ab043a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #16 0x7f91a9ab0c53 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f91aa646423 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7f91a9a7a098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f91a9acc11f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7f91a78024cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7f91a78564e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #22 0x7f91a77ffc03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7f91a9acb698 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f91a9a78ab2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7f91a9a80fe4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x55a99ef7158c in main () [Inferior 1 (process 5431) detached] Possible duplicates by query: bug 440860, bug 440660, bug 440643, bug 440616, bug 440460. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440201] Windows appear detached from titlebars in Present Windows and Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=440201 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/4912c7cfa2e5 ||4c2f5ad491f868aaae43135ca17 ||2 --- Comment #2 from Vlad Zahorodnii --- Git commit 4912c7cfa2e54c2f5ad491f868aaae43135ca172 by Vlad Zahorodnii. Committed on 11/08/2021 at 16:43. Pushed by vladz into branch 'master'. scenes/opengl: Calculate item transforms differently Currently, a vertex coordinate is transformed first, then mapped to the global screen coordinates. This causes a problem if a transform is applied to the top-most item and child items are not at (0, 0). For example, scaled windows may have popping out sub-surfaces, etc. With this change, the item transforms will be computed differently. For example, if the parent item is transformed, a child's transform will look as follows [Parent's translation][Parent's transform][Child's translation] instead of [Parent's translation][Child's translation][Parent's transform] In the future, I'd like to get rid of the Item::setTransform() call in OpenGLWindow::performPaint() and have either AnimationEffect or libkwineffects call Item::setTransform(). M +10 -0src/item.cpp M +4-0src/item.h M +43 -32 src/plugins/scenes/opengl/scene_opengl.cpp M +1-1src/plugins/scenes/opengl/scene_opengl.h https://invent.kde.org/plasma/kwin/commit/4912c7cfa2e54c2f5ad491f868aaae43135ca172 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 387797] Scrollviews automatically scroll up or down when you hover over a partially-visible list item
https://bugs.kde.org/show_bug.cgi?id=387797 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437155 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=437155| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 437155] Scroll views scroll themselves up when completely scrolled down with touchpad
https://bugs.kde.org/show_bug.cgi?id=437155 Nate Graham changed: What|Removed |Added Target Milestone|1.0 |--- Component|Widget Explorer |components Summary|[Wayland] Widgets list |Scroll views scroll |scrolls itself up when |themselves up when |completely scrolled down|completely scrolled down |with touchpad |with touchpad See Also|https://bugs.kde.org/show_b |https://bugs.kde.org/show_b |ug.cgi?id=440874|ug.cgi?id=387797 Version|5.21.90 |5.84.0 CC||plasma-b...@kde.org Product|plasmashell |frameworks-plasma Assignee|plasma-b...@kde.org |notm...@gmail.com --- Comment #7 from Nate Graham --- Still reproducible, that's unrelated. It's a general problem in the Plasma scroll area. Possibly a different manifestation of Bug 387797. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437155 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437155] [Wayland] Widgets list scrolls itself up when completely scrolled down with touchpad
https://bugs.kde.org/show_bug.cgi?id=437155 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=440874 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437155] [Wayland] Widgets list scrolls itself up when completely scrolled down with touchpad
https://bugs.kde.org/show_bug.cgi?id=437155 --- Comment #6 from Dennis Schridde --- (In reply to Dennis Schridde from comment #2) > I noticed something similar when dragging an email in KMail from the mail > list into the folder list. As soon as my mouse cursor is over the folder > list, the folders will start scrolling up, until it reaches the top. > Sometimes this stops happening after several attempts, but most of the time > there it just keeps doing that on every try. Is that related or a different > bug? I created bug #440874 for this. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440874] New: Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Bug ID: 440874 Summary: Folder list scrolls up when trying to drag message into folder Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- SUMMARY When trying to drag a message from the message list of one folder into another folder (by moving it over a folder in the folder list), the folder list starts to scroll up to the top, moving the folders under the mouse and scrolling the intended folder out of view. A workaround to be able to drag and drop messages into the target folder is to collapse all folders in the list, so that it cannot scroll further up. This only works, if the target folder is visible when the list is fully scrolled up. STEPS TO REPRODUCE 1. Expand some folders in the folder list 2. Open a folder so that its messages are shown in the message list 3. Drag a message from the message list over the folder list OBSERVED RESULT The folder list starts scrolling up once the mouse is moved over it. It will keep moving even when the mouse is still. EXPECTED RESULT The folder list does not move on its own. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.8 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon™ Vega 11 Graphics ADDITIONAL INFORMATION KMail 5.17.3 Under some circumstances, very seldomly, this magic scrolling does not happen. I was however so far unable to reproduce that. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759
--- Comment #9 from Michail Vourlakos ---
I made a test. Please change the two lines you mentioned in CMakeLists file
with:
#hide warnings
string(REPLACE "-Wall" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
string(REPLACE "-Wdeprecated-declarations" "" CMAKE_CXX_FLAGS
${CMAKE_CXX_FLAGS})
string(REPLACE "-Wreorder" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
string(REPLACE "-Wunused-variable" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
string(REPLACE "-Wunused-parameter" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS})
#add format security check
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wformat -Werror=format-security")
1. I enforced the Fedora rule to check what errors are happening
2. Does it build in Fedora in that case?
3. In my system it with above changes it builds just fine. If it doesnt build
in Fedora what warnings are considered errors and it is not built?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 437155] [Wayland] Widgets list scrolls itself up when completely scrolled down with touchpad
https://bugs.kde.org/show_bug.cgi?id=437155 --- Comment #5 from Patrick Silva --- it's still reproducible on neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437155] [Wayland] Widgets list scrolls itself up when completely scrolled down with touchpad
https://bugs.kde.org/show_bug.cgi?id=437155 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #4 from Méven Car --- I couldn't reproduce this with latest master (future plasma 5.23). I suspect https://invent.kde.org/frameworks/kirigami/-/commit/537e213292cfadb6892a10987cdd9b21df158770 fixed the issue. I would welcome confirmation that this has been. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #34 from Jaroslav Skarvada --- I got it working even for non-admin user. I also tried the libusb-win32 driver, but it's crashing during download of the photos. The WinUSB driver seems to work the most reliable way. Steps how to install it: - logon as admin - download Zadig (https://zadig.akeo.ie/) and run it - click Options->List All Devices - connect camera and switch it on - locate it in the Zadig device list, check whether the USB VID/PID matches - select the WInUSB driver (I used WinUSB v6.1.7600.16385) - click Install Driver - wait several minutes (this can take really long time, because it's usually creating restore point) - when the driver is installed, disconnect and reconnect the camera - logon as normal user If you want to restore the original driver to be able to do the native PTP from the explorer: - logon as admin - open device manager - connect camera and switch it on - the camera should appear in the device manager - right click it and select uninstall, check remove installation files - disconnect and reconnect the camera -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 439920] DragArea requires press-and-hold with a touchscreen, which is unintuitive and undiscoverable
https://bugs.kde.org/show_bug.cgi?id=439920 --- Comment #6 from Thiago Sueto --- (In reply to Nate Graham from comment #5) > Huh, touch-and-hold-and-drag works fine for me on both Wayland and X11. I'm > starting to suspect that there is something generally wrong with your > touchscreen drivers or something. :) It doesn't seem to be the case, because once I tap and hold for what seems to be half a second the widget drawer darkens accordingly, and when I drag my finger outwards and release it goes back to its original state, so it seems the actual gestures are recognized properly, it's just not doing what it's supposed to do. Is there some way to test for such issues? I don't think that's it, but it's true that my current distro (openSUSE Krypton) is the only one where I experience lack of screen rotation in iio-sensor-proxy[1], so perhaps there is something happening there and I should test this hardware with another distro. Although I remember this happening on Arch, Fedora and Kubuntu Impish. [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1188224 In any case, seems like something that should be in a different bug report or still needs confirmation from other reporters. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759 --- Comment #8 from Gerald Cox --- Thanks again for your quick replies. I don't believe anyone is talking about banning anything. I counted 15 errors when the compile failed. I'll see if I can figure out a way to get more information to narrow that down. I'm still a bit confused about why removing those lines made the problem disappear in Fedora. IMO, it shouldn't have. Additionally, when this change was approved by Fedora, they said that other distributions had already implemented, and that was 7 years ago. So if that is indeed the case then that to me would imply they are also bypassing the check. I had asked the question in the maintainer forum, if I don't get an answer there I'll open a ticket with the build infrastructure team. I'll let you know what I find. Thanks again for your quick responses. latte-dock is a great package and also thanks for the .10 update. I'm running it now on my laptop and it's working with no issues! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440872] digikam dies at 'Checking the ICC repository...'
https://bugs.kde.org/show_bug.cgi?id=440872 miguel.life changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from miguel.life --- 1250 albumbs, 273509 images OK, it might be because of that. But there are fewer files than last week, and until yesterday it was working fine. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #33 from Jaroslav Skarvada --- (In reply to caulier.gilles from comment #32) > To implement a Windows native support in digiKam import tool, this interface > must be re-implemented : > > https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/ > backend/dkcamera.h > > As it's already done for Gphoto2 backend : > > https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/ > backend/gpcamera.h > > ...and USB Mass Storage backend : > > https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/ > backend/umscamera.h > > Typically, the UMS implementation is a good start to port to Windows native. > > Gilles Caulier OK, just keeping this idea for somebody else as an RFE. Unfortunately, at the moment, I am out of time to implement this myself :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440493] Add an option for whether to enable or disable Bluetooth adapters at session start
https://bugs.kde.org/show_bug.cgi?id=440493 --- Comment #9 from Nate Graham --- Hmm, looks like the code already has the ability to save and resume enablement state before and after suspend. I guess we just need to wire that up to login and logout too, in conjunction with this new UI to control what happens. However the save/restore stuff does not seem to be working for me. Need to debug that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440872] digikam dies at 'Checking the ICC repository...'
https://bugs.kde.org/show_bug.cgi?id=440872 --- Comment #2 from Maik Qualmann --- The log shows no abnormalities. How long did you wait? This is also the point at which the albums are read. How many albums and images are in the collection? Have you ever tested the AppImage? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440872] digikam dies at 'Checking the ICC repository...'
https://bugs.kde.org/show_bug.cgi?id=440872 Maik Qualmann changed: What|Removed |Added Severity|critical|grave CC||metzping...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440828] Pinned icons inappropriately shrink when any are opened while there is not much space on the panel
https://bugs.kde.org/show_bug.cgi?id=440828 --- Comment #6 from Oleksii Zolotarevskyi --- (In reply to Nate Graham from comment #5) > There's not much room in your panel. The Task Manager is reacting by > shrinking elements as needed. In this case, the calculation seems to be > getting it somewhat wrong. :) You're right. Thanks for putting more concise title! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440849] Titlebar disappears in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=440849 --- Comment #5 from Nate Graham --- Interesting, thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440872] digikam dies at 'Checking the ICC repository...'
https://bugs.kde.org/show_bug.cgi?id=440872
--- Comment #1 from miguel.life ---
[miguel@tpx240 ~]$ export QT_LOGGING_RULES="digikam*=true"
[miguel@tpx240 ~]$ digikam
digikam.widgets: Use installed icons
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QSQLITE"
DB Core Name: "/home/miguel/.local/digiKam/digikam4.db"
DB Thumbs Name:
"/home/miguel/.local/digiKam/thumbnails-digikam.db"
DB Face Name: "/home/miguel/.local/digiKam/recognition.db"
DB Similarity Name:"/home/miguel/.local/digiKam/similarity.db"
Connect Options: ""
Host Name: ""
Host port: -1
Internal Server: false
Internal Server Path: ""
Internal Server Admin Cmd: ""
Internal Server Serv Cmd: ""
Internal Server Init Cmd: ""
Username: ""
Password: ""
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 13
digikam.coredb: Core database: makeUpdates 13 to 13
digikam.database: Creating new Location "/Fotos y vídeos" uuid
"volumeid:?uuid=ff38c186-20c7-49d0-a746-73b9a027a632"
digikam.database: location for "/run/media/miguel/TOSHIBA2TB/Fotos y vídeos"
is available true
digikam.general: KMemoryInfo: Platform identified : "LINUX"
digikam.general: KMemoryInfo: TotalRam: 8215134208
digikam.general: Allowing a cache size of 391 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
digikam.thumbsdb: Thumbs database: have a structure version "3"
digikam.general: Thumbnails database ready for use
digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
digikam.similaritydb: Similarity database: have a structure version "1"
digikam.similaritydb: Similarity database ready for use
digikam.dimg: ("/usr/share/color/icc")
digikam.general: Does not contain "Caption" Namespace
digikam.dimg: No X.org XICC profile installed for screen 1
digikam.general: Camera XML data:
"/home/miguel/.local/share/digikam/cameras.xml"
digikam.general: Starting to load external tools.
digikam.general: Parsing plugins from ("/usr/lib/qt/plugins/digikam/")
digikam.general: Plugins found: 134
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_Texture_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_CurvesAdjust_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_Rotate_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_ConvertToTIFF_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_UserScript_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_Invert_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_ColorFX_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_ChannelMixer_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_Flip_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_Border_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_WaterMark_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_ColorBalance_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_Convert8To16_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_ConvertToHEIF_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_AntiVignetting_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_BcgCorrection_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_NoiseReduction_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_FilmGrain_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
"/usr/lib/qt/plugins/digikam/bqm/Bqm_Crop_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginBqm loaded from
[Mangonel] [Bug 440871] Opening the Application Menu causes the Plasma Wayland session to crash
https://bugs.kde.org/show_bug.cgi?id=440871 --- Comment #2 from krpis...@protonmail.com --- Created attachment 140657 --> https://bugs.kde.org/attachment.cgi?id=140657=edit Log from redirecting stderr into a file. This is the best I can do right now. It's kind of short, because I only started a session and triggered the crash manually by locking, signing in, and then opening the application menu a few times. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440849] Titlebar disappears in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=440849 --- Comment #4 from Troy Dawson --- It is fairly interactive. You can right click on it, and get the normal right click selections. If I click around I can eventually hit some buttons, but they seems to be out of place. But it does seem to be "invisible" versus "gone". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #32 from caulier.gil...@gmail.com --- To implement a Windows native support in digiKam import tool, this interface must be re-implemented : https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/backend/dkcamera.h As it's already done for Gphoto2 backend : https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/backend/gpcamera.h ...and USB Mass Storage backend : https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/backend/umscamera.h Typically, the UMS implementation is a good start to port to Windows native. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759 --- Comment #7 from Michail Vourlakos --- An update, reading Fedora article then Fedora is pretty clear why it is adding that specific check. Its argument is pretty understandable. First of all removing the check that Fedora adds is not good practice that could make Latte banned from Fedora because is not following its rules. Secondly in order for Latte to be accepted in Fedora the only way is Latte to become compatible with this. Latte v0.10 is being developed for two years, these two years none came and reguested that compliance. Unfortunately making v0.10 compliant I have no idea how much work is needed and also if it is also possible to not break translations. To make things even more anxious, v0.10 is scheduled to stay around for many years around. I have no idea if I will ever release a v0.11 or if someone will step in to continue development. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 440856] Option to show wifi QR code is not very discoverable
https://bugs.kde.org/show_bug.cgi?id=440856 --- Comment #4 from Nate Graham --- Generally we have an expanded view that shows extra actions, which would take care of this. But in the case of the networks applet, the expanded view is used to two custom views instead. Not sure where we could put the action. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 440802] High ram consumption (1GB) when idle
https://bugs.kde.org/show_bug.cgi?id=440802 --- Comment #1 from tagwer...@innerjoin.org --- (In reply to irchaika from comment #0) > It consumes nearly a gigabyte of ram despite being idle, the problem > persists across reboots (though I haven't checked how long it takes for the > process to reappear and take that amount of ram) I've seen this when I've tried indexing many files (2 million), that gives a big index. Each time you log on, baloo cross-checks your files on disc against the files in the index to see if anything has changed. In this case baloo is just reading most of the information, it gets pulled off disc and stays in RAM in case it is needed again. If "balooctl status" says idle, then baloo is not actively using the memory, I would expect that as soon as another process needs memory, the amount used by baloo will drop. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 440856] Option to show wifi QR code is not very discoverable
https://bugs.kde.org/show_bug.cgi?id=440856 Nate Graham changed: What|Removed |Added Summary|add option to show wifi QR |Option to show wifi QR code |code|is not very discoverable Keywords||usability CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Severity|wishlist|normal --- Comment #3 from Nate Graham --- Yup. The fact that you didn't know this suggests that it's not discoverable enough, though. In general right-click-only user interfaces are bad for precisely this reason. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440828] Pinned icons inappropriately shrink when any are opened while there is not much space on the panel
https://bugs.kde.org/show_bug.cgi?id=440828 Nate Graham changed: What|Removed |Added Summary|Icons in Icons-only Task|Pinned icons |Manager change size when|inappropriately shrink when |opening windows |any are opened while there ||is not much space on the ||panel Status|REOPENED|CONFIRMED CC||n...@kde.org --- Comment #5 from Nate Graham --- There's not much room in your panel. The Task Manager is reacting by shrinking elements as needed. In this case, the calculation seems to be getting it somewhat wrong. :) -- You are receiving this mail because: You are watching all bug changes.
[Mangonel] [Bug 440871] Opening the Application Menu causes the Plasma Wayland session to crash
https://bugs.kde.org/show_bug.cgi?id=440871 --- Comment #1 from krpis...@protonmail.com --- NOTE: I have two displays, and it only happens, if I use it on my primary one. May have something to do with the two displays having different refresh rates. (One is 75Hz, the other one, on which it doesn't happen, is 60Hz) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414920] Plasma crashes in RunnerModel::matchesChanged() while searching
https://bugs.kde.org/show_bug.cgi?id=414920 Nate Graham changed: What|Removed |Added CC||berni.bo...@gmx.at --- Comment #37 from Nate Graham --- *** Bug 440850 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440850] Plasma crash while typing in search
https://bugs.kde.org/show_bug.cgi?id=440850 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 414920 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 440843] Popup sometimes cuts off contents wider than itself
https://bugs.kde.org/show_bug.cgi?id=440843 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Summary|Popup cuts off contents |Popup sometimes cuts off |wider than itself |contents wider than itself --- Comment #2 from Nate Graham --- Can sometimes reproduce. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759 --- Comment #6 from Gerald Cox --- (In reply to Michail Vourlakos from comment #5) > Other distros are already providing latest versions. You can leave it open > and see how it goes. No idea when and if i will add it. Thanks, I've also submitted a question within the project to see if someone can explain what exactly is happening and why. I'll let you know when I get a response. It could be that fedora is at a more recent version of the software and/or that the other distros just patched CMakeList.txt without letting you know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440849] Titlebar disappears in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=440849 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- Is it invisible but still interactive or just gone? If it's gone, does this mean that clicks in the area where it should be actually get passed down to whatever is underneath the titlebar-less window? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440873] Scrolling issue prevents viewing the first and some of the last Clipboard entries
https://bugs.kde.org/show_bug.cgi?id=440873 --- Comment #1 from Lyubomir --- Only happens with touchpad scroll -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440852] Black or vertically mirrored window with some XWayland apps on nvidia 470+ drivers
https://bugs.kde.org/show_bug.cgi?id=440852 Nate Graham changed: What|Removed |Added Summary|Black or upside down window |Black or vertically |with some XWayland apps on |mirrored window with some |nvidia 470+ drivers |XWayland apps on nvidia ||470+ drivers CC||n...@kde.org, ||xaver.h...@gmail.com --- Comment #3 from Nate Graham --- yikes! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440854] Ambiguous shortcut Ctrl+Alt+I
https://bugs.kde.org/show_bug.cgi?id=440854 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- I was briefly seeing this last month too, but now it's gone. It seems to have been fixed either in the latest unreleased version of Kate or frameworks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #31 from Jaroslav Skarvada --- Also probably dupes (maybe there are more): https://bugs.kde.org/show_bug.cgi?id=398061 https://bugs.kde.org/show_bug.cgi?id=379970 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440759] Version 0.10.0 or git (master) fails on build, previous version builds fine
https://bugs.kde.org/show_bug.cgi?id=440759 --- Comment #5 from Michail Vourlakos --- Other distros are already providing latest versions. You can leave it open and see how it goes. No idea when and if i will add it. -- You are receiving this mail because: You are watching all bug changes.
