[frameworks-knotifications] [Bug 451192] New: Connecting to KNotification::activated before doing setActions does not work
https://bugs.kde.org/show_bug.cgi?id=451192 Bug ID: 451192 Summary: Connecting to KNotification::activated before doing setActions does not work Product: frameworks-knotifications Version: 5.91.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: bhus...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY If you do connection to activated before doing setActions, slot does not trigger, I verified using dbus-monitor that related dbus signal is emitted but not the lambda slot. See https://invent.kde.org/plasma-mobile/plasma-dialer/-/merge_requests/85 Question is, if is it expected? If so it should be possibly documented? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449810] KWin scripts can't be configured in Plasma 5.24
https://bugs.kde.org/show_bug.cgi?id=449810 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 437879] Segfault in Card::sources on 1.3 on Pinephone
https://bugs.kde.org/show_bug.cgi?id=437879 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma-mobile/plasma-dialer/com ||mit/0c10171436a1dac0a4735fa ||1b03409aac670b786 Status|ASSIGNED|RESOLVED --- Comment #5 from Bhushan Shah --- Git commit 0c10171436a1dac0a4735fa1b03409aac670b786 by Bhushan Shah. Committed on 31/05/2021 at 10:24. Pushed by bshah into branch 'master'. Fix crash if used with wrong UCM Wrong/old UCM does not have some proper namings, which means it will not find earpiece/speaker and mic ports and m_voiceCallCard will never be set. While this means audio will not work, at least guard against the crasher. M +5-0src/callaudio.cpp https://invent.kde.org/plasma-mobile/plasma-dialer/commit/0c10171436a1dac0a4735fa1b03409aac670b786 -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 437879] Segfault in Card::sources on 1.3 on Pinephone
https://bugs.kde.org/show_bug.cgi?id=437879 --- Comment #3 from Bhushan Shah --- Also, can you upload full output of the plasma-dialer? -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 437879] Segfault in Card::sources on 1.3 on Pinephone
https://bugs.kde.org/show_bug.cgi?id=437879 --- Comment #2 from Bhushan Shah --- Latest version with which it is tested is, https://gitlab.com/pine64-org/pine64-alsa-ucm (/usr/share/alsa/ucm2/PinePhone/) -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 437879] Segfault in Card::sources on 1.3 on Pinephone
https://bugs.kde.org/show_bug.cgi?id=437879 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #1 from Bhushan Shah --- Did you also update UCM to newer version? -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 437344] Missing icon for Angelfish
https://bugs.kde.org/show_bug.cgi?id=437344 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma-mobile/angelfish/commit/ ||c67ca900bb014cc9e4c165c1c3b ||808a28c0fb121 --- Comment #1 from Bhushan Shah --- Git commit c67ca900bb014cc9e4c165c1c3b808a28c0fb121 by Bhushan Shah. Committed on 19/05/2021 at 09:29. Pushed by bshah into branch 'master'. Fix icon name in desktop file M +1-1org.kde.angelfish.desktop https://invent.kde.org/plasma-mobile/angelfish/commit/c67ca900bb014cc9e4c165c1c3b808a28c0fb121 -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 437156] Logging into opendesktop account says that I will be sharing my information with Bhushan Shah
https://bugs.kde.org/show_bug.cgi?id=437156 Bhushan Shah changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Bhushan Shah --- This should be fixed. Apologies, when doing initial testing client associated with the API key was registered as Bhushan Shah on backend side. We have updated client name now. (Despite my name being there, I *do not* have access to your personal data FWIW) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #10 from Bhushan Shah --- Git commit d5186701e27ad6f09f3944809cec2a25c5328026 by Bhushan Shah, on behalf of Vlad Zahorodnii. Committed on 11/05/2021 at 06:56. Pushed by apol into branch 'kde/5.15'. Client: Announce an output after receiving more complete state Output initialization is not atomic, meaning that the compositor may process a wl_output bind request in one event loop cycle, and the xdg_output_manager.get_xdg_output in another event loop cycle. This means that xdg_output properties may arrive in another wl_output done frame. Prior to xdg-output v3, that wasn't an issue because the compositor is required to send an xdg_output.done event after sending xdg_output properties. Starting with v3, the compositor may choose not to send an xdg_output.done event after sending xdg_output properties. Therefore, as is, QtWayland may announce an output with bad logical geometry or even worse without name assigned by the compositor. Unfortunately, that breaks applications such as plasmashell. Plasma uses output names as a criterion to determine what kind of contents should be displayed on a particular output. In order to fix the initialization sequence, this change makes every QWaylandScreen track processed events. After all required events have been received, the screen can be announced to the rest of Qt. Change-Id: If5da747edd7af277ec1364cbea105c6994f47402 Reviewed-by: David Edmundson (cherry picked from commit 69ea480f2e53ad4a5bbca78cde044eb8d4c48896) Original Ticket: https://codereview.qt-project.org/c/qt/qtwayland/+/347774 M +23 -9src/client/qwaylandscreen.cpp M +8-2src/client/qwaylandscreen_p.h https://invent.kde.org/qt/qt/qtwayland/commit/d5186701e27ad6f09f3944809cec2a25c5328026 -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 436862] Ability to release multiple things using at once
https://bugs.kde.org/show_bug.cgi?id=436862 --- Comment #2 from Bhushan Shah --- (In reply to Harald Sitter from comment #1) > don't you then still need a script to remember which $foo is part of > $productset? Well sure, but then this can be as simple as the simple yml file or text file with list of repositories I want releaseme to act on for starter. > https://invent.kde.org/sysadmin/repo-metadata/-/issues/3 might be what we > want? I agree with need for this though. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 436862] New: Ability to release multiple things using at once
https://bugs.kde.org/show_bug.cgi?id=436862 Bug ID: 436862 Summary: Ability to release multiple things using at once Product: releaseme Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bhus...@gmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY When doing release for PlaMo gear, I created some wrapper scripts to wrap around tarme/tagme/branchme etc Similary there exists some scripts for Plasma in repo. But this is not practical STEPS TO REPRODUCE 1. Want to release > 1 thigns OBSERVED RESULT You will need multiple wrapper scripts for this EXPECTED RESULT You can do something like, ./tarme.rb --origin trunk --version 21.05 plasma-phonebook,plasma-dialer,spacebarxyz and it would create a tars without needing explicit loop/wrapper script similar goes for tagme and branchme. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 436703] choqok no longer runs after upgrade to kde-frameworks 5.81
https://bugs.kde.org/show_bug.cgi?id=436703 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #3 from Bhushan Shah --- I can not reproduce this on my local setup, Do you have some more information on crash? like if some window appears before it is crashing? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435467] KWIN_DRM_DEVICE no longer supported
https://bugs.kde.org/show_bug.cgi?id=435467 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 Bhushan Shah changed: What|Removed |Added Priority|NOR |VHI --- Comment #8 from Bhushan Shah --- I am starting to get more and more reports about this, so I am up-ing the severity of this bug report to VHI. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #7 from Bhushan Shah --- This also might be potential duplicate of bug 427861, Although personally I doubt it because that bug report is mostly about user where screenId is not assigned correctly and config is not removed completely, assigning correct screenID fixes it for them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 Bhushan Shah changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #6 from Bhushan Shah --- I am marking this as confirmed since I get reports about this at least twice a week in plasma mobile as well as pinephone channel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #5 from Bhushan Shah --- And for same user as comment #5 config file before reset was this, [Containments][14] AppOrder=org.kde.phone.dialer.desktop,telegramdesktop.desktop-0,org.postmarketos.Megapixels.desktop-0,org.kde.mobile.angelfish.desktop DesktopItems= Favorites=org.kde.phone.dialer.desktop,telegramdesktop.desktop-0,org.postmarketos.Megapixels.desktop-0,org.kde.mobile.angelfish.desktop ItemGeometriesVertical=Applet-15:0,0,360,113,0; MaxFavoriteCount=4 activityId=a8a6782c-c5aa-45b3-80b2-6b02da0d82c1 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.phone.homescreen wallpaperplugin=org.kde.image [Containments][14][Applets][15] immutability=1 plugin=org.kde.phone.krunner [Containments][14][ConfigDialog] DialogHeight=666 DialogWidth=360 [Containments][14][General] AppOrder=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop,org.kde.mobile.camera.desktop [Containments][14][Wallpaper][org.kde.image][General] Image=file:///home/lukasz/Downloads/Other stuff/backgroundphone.png [Containments][3] activityId= formfactor=2 immutability=1 lastScreen=0 location=3 plugin=org.kde.phone.panel wallpaperplugin=org.kde.image [Containments][3][Applets][4] immutability=1 plugin=org.kde.plasma.notifications [Containments][3][Applets][4][Configuration] PreloadWeight=100 [Containments][3][Applets][5] immutability=1 plugin=org.kde.plasma.mediacontroller [Containments][3][Applets][5][Configuration] PreloadWeight=100 [Containments][6] activityId= formfactor=2 immutability=1 lastScreen=0 location=4 plugin=org.kde.phone.taskpanel wallpaperplugin=org.kde.image -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #4 from Bhushan Shah --- >From another affected user's config what I noticed is, there is bunch of empty containment with no activityId assigned to it. This is after config was reset [Containments][16] AppOrder=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop DesktopItems= Favorites=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop MaxFavoriteCount=4 activityId=a8a6782c-c5aa-45b3-80b2-6b02da0d82c1 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.phone.homescreen wallpaperplugin=org.kde.image [Containments][16][General] AppOrder=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop,org.kde.mobile.camera.desktop [Containments][16][Wallpaper][org.kde.image][General] Image=file:///usr/share/wallpapers/Next/contents/images/720x1440.png [Containments][3] activityId= formfactor=2 immutability=1 lastScreen=0 location=3 plugin=org.kde.phone.panel wallpaperplugin=org.kde.image [Containments][3][Applets][4] immutability=1 plugin=org.kde.plasma.notifications [Containments][3][Applets][4][Configuration] PreloadWeight=100 [Containments][3][Applets][5] immutability=1 plugin=org.kde.plasma.mediacontroller [Containments][3][Applets][5][Configuration] PreloadWeight=100 [Containments][6] activityId= formfactor=2 immutability=1 lastScreen=0 location=4 plugin=org.kde.phone.taskpanel wallpaperplugin=org.kde.image -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #3 from Bhushan Shah --- Running on Plasma 5.21 based image, we see following in log, org.kde.plasma.phoneshell/contents/views/Desktop.qml:78: TypeError: Cannot read property 'availableScreenRect' of null which DavidE thought is interesting and that was "fixed" in, https://invent.kde.org/plasma/plasma-phone-components/-/commit/59297a25f316d772f0e7e18ee7ce29c703cd58c5 But according to DavidE, containment never should be null(?). This is pending investigation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #2 from Bhushan Shah --- Config after bug happens [Containments][25] AppOrder=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop DesktopItems= Favorites=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop MaxFavoriteCount=4 activityId=1bb207c6-7b0f-4d53-849e-2a5c359dc0b9 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.phone.homescreen wallpaperplugin=org.kde.image [Containments][25][General] AppOrder=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop,org.kde.mobile.camera.desktop [Containments][25][Wallpaper][org.kde.image][General] Image=file:///usr/share/wallpapers/Next/contents/images/720x1440.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 --- Comment #1 from Bhushan Shah --- Example config before bug happens [Containments][23] Favorites=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop,org.kde.mobile.qmlkonsole.desktop-0 ItemGeometriesVertical=Applet-24:0,0,360,113,0; MaxFavoriteCount=4 activityId=1bb207c6-7b0f-4d53-849e-2a5c359dc0b9 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.phone.homescreen wallpaperplugin=org.kde.image [Containments][23][Applets][24] immutability=1 plugin=org.kde.phone.krunner [Containments][23][ConfigDialog] DialogHeight=666 DialogWidth=360 [Containments][23][General] AppOrder=org.kde.phone.dialer.desktop,org.kde.phonebook.desktop,org.kde.mobile.angelfish.desktop,org.kde.mobile.qmlkonsole.desktop-0 [Containments][23][Wallpaper][org.kde.image][General] Image=file:///usr/share/wallpapers/logo_dark.jpg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435124] New: plasmashell config reset when using mobile shell
https://bugs.kde.org/show_bug.cgi?id=435124 Bug ID: 435124 Summary: plasmashell config reset when using mobile shell Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bhus...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On Plasma Mobile after few restarts plasmashell resets it's own configuration, adds new containment and looses the old containment. STEPS TO REPRODUCE 1. Start plasma mobile on pinephone, change wallpaper for example 2. Restart phone multiple times OBSERVED RESULT 3. Eventually the config will go in wrong state and wallpaper will be reset as well as launcher/shortcuts EXPECTED RESULT 3. Nothing happens to config, and launchers stay as-is -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434088] Removing user with auto-login enabled causes failure to show SDDM on reboot
https://bugs.kde.org/show_bug.cgi?id=434088 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433983] Widget explorer does not list some widgets despite being in formfactor
https://bugs.kde.org/show_bug.cgi?id=433983 Bhushan Shah changed: What|Removed |Added Version|5.20.90 |5.21.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433983] New: Widget explorer does not list some widgets despite being in formfactor
https://bugs.kde.org/show_bug.cgi?id=433983 Bug ID: 433983 Summary: Widget explorer does not list some widgets despite being in formfactor Product: plasmashell Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: bhus...@gmail.com Target Milestone: 1.0 SUMMARY On phone some widgets are not listed, despite having matching formfactor entries STEPS TO REPRODUCE 1. export PLASMA_PLATFORM=phone:handheld 2. plasmashell 3. Open widget explorer OBSERVED RESULT 4. Notice that analog clock is not listed EXPECTED RESULT Analog clock should be listed, given it have handset in X-KDE-FormFactors key -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 433849] Windows resizing themselves when a translation is used
https://bugs.kde.org/show_bug.cgi?id=433849 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #2 from Bhushan Shah --- More like both bugs have same root cause. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432724] New: Allow to pre-configure/pre-seed scaling values
https://bugs.kde.org/show_bug.cgi?id=432724 Bug ID: 432724 Summary: Allow to pre-configure/pre-seed scaling values Product: KScreen Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kded Assignee: kscreen-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY Currently scaling for screen is decided by the kscreen on fly, which means, if you are starting wayland session for first time, briefly, kwin and plasma would have a "wrong" scaling until kded starts, and for some reason if kscreen kded is delayed, it will get stuck on wrong scaling randomly. This is very visible when starting session with the --lockscreen option on mobile session. Now there's two solution to this, 1) we pre-seed values for the kscreen configuration or kwin scaling configuration. This in theory is possible but quite hard given this config format uses the UUIDs and there's no way of knowing that and pre-setting this values using /etc/xdg or something like that. So only way right now is to let kscreen figure out correct scaling value and set it, in some cases this is too late and provides very in-consistent experience. 2) We evaluate kscreen scaling configuration before starting anything including lockscreen. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 432723] Spotify shows up as a three different players
https://bugs.kde.org/show_bug.cgi?id=432723 --- Comment #1 from Bhushan Shah --- Created attachment 13 --> https://bugs.kde.org/attachment.cgi?id=13&action=edit and tab where metadata is set correctly -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 432723] New: Spotify shows up as a three different players
https://bugs.kde.org/show_bug.cgi?id=432723 Bug ID: 432723 Summary: Spotify shows up as a three different players Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: bhus...@gmail.com Target Milestone: --- Created attachment 135554 --> https://bugs.kde.org/attachment.cgi?id=135554&action=edit one of 3 items where metadata is not set correctly SUMMARY STEPS TO REPRODUCE 1. Play music in spotify OBSERVED RESULT 1. Notice that media player applet shows 3 tabs 2. Only one of them have a proper artwork/metadata. EXPECTED RESULT 1. It shows up as only one instance. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Plasma 5.20.90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431977] New: Restore scroll to switch timezone option
https://bugs.kde.org/show_bug.cgi?id=431977 Bug ID: 431977 Summary: Restore scroll to switch timezone option Product: plasmashell Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: bhus...@gmail.com Target Milestone: 1.0 SUMMARY Commit in https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/414 removed the option to switch timezone using wheel. I was a great fan of this feature and in my opinion while it fixed original bug 428096, this introduced a massive regression for me (and others who were using these option). I work with colleagues who are in 3 different timezones, so some meetings as well as events are generally scheduled in different timezones, and accordingly I decide what clock to show at a time. For example, During work hours, I set clock to Berlin time, if I have some event (Recent Wayland goal meeting for example) then I set it to UTC. New option of the switching timezone by the Clock settings is simply not initiative. It requires me to go through 5 different steps where I could previously do this with simple mouse scroll. - Right click on digital clock - Digital clock settings - Timezone - Select option - Apply This is just needless extra work and yes I can see the time in the tooltip, but I much prefer it to be visible in panel rather then it showing up only when I hover mouse over it. This may seem super insignificant for people who are mostly interacting with 1 timezone but for others this makes it much much annoying. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431569] Complete removal of Dolphin from KDE required
https://bugs.kde.org/show_bug.cgi?id=431569 Bhushan Shah changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431569] Complete removal of Dolphin from KDE required
https://bugs.kde.org/show_bug.cgi?id=431569 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Bhushan Shah --- If you have any specific bugs you want to report instead of unproductive rant, feel free to create separate actionable bug reports. I'm closing this again just similar to other bug report. If you continue reporting bugs like this it will result in ban. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431567] Complete removal of Dolphin from KDE required
https://bugs.kde.org/show_bug.cgi?id=431567 Bhushan Shah changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431567] Complete removal of Dolphin from KDE required
https://bugs.kde.org/show_bug.cgi?id=431567 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429622] Re-enable “reveal password” button on login screen
https://bugs.kde.org/show_bug.cgi?id=429622 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429353] Lockscreen doesn't resize to full screen after rotation of screen
https://bugs.kde.org/show_bug.cgi?id=429353 --- Comment #1 from Bhushan Shah --- Created attachment 133460 --> https://bugs.kde.org/attachment.cgi?id=133460&action=edit broken lockscreen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429353] New: Lockscreen doesn't resize to full screen after rotation of screen
https://bugs.kde.org/show_bug.cgi?id=429353 Bug ID: 429353 Summary: Lockscreen doesn't resize to full screen after rotation of screen Product: kwin Version: git master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY This seems to happen on the phone, where rotating phone lockscreen doesn't properly resize. STEPS TO REPRODUCE 1. Start PlaMo session 2. Lock 3. Rotate phone OBSERVED RESULT You got broken UI EXPECTED RESULT Lockscreen resizes in any orientation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428859] OSDs are maximized when using Maximized window placement policy
https://bugs.kde.org/show_bug.cgi?id=428859 --- Comment #6 from Bhushan Shah --- Created attachment 133163 --> https://bugs.kde.org/attachment.cgi?id=133163&action=edit plasmashell wl debug WAYLAND_DEBUG of plasma-shell, I show OSD, it is displayed correctly, it auto hides, and then is shown again which is not showed correctly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428859] OSDs are maximized when using Maximized window placement policy
https://bugs.kde.org/show_bug.cgi?id=428859 Bhushan Shah changed: What|Removed |Added Ever confirmed|0 |1 CC||bhus...@gmail.com Status|REPORTED|CONFIRMED --- Comment #3 from Bhushan Shah --- Mind you this bug happens on second invocation of the OSD and not the initial one. I can confirm this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343577] Panel size config should be separated by shell package name
https://bugs.kde.org/show_bug.cgi?id=343577 Bhushan Shah changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Bhushan Shah --- Yes it is still issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428039] Holding a key does not repeat it like it should [Wayland][kwin][kwayland-server]
https://bugs.kde.org/show_bug.cgi?id=428039 --- Comment #5 from Bhushan Shah --- (In reply to Nate Graham from comment #3) > Is it appropriate to backport this to 5.20? No, the regression was from master branch, so only needed for master branch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428039] Holding a key does not repeat it like it should [Wayland][kwin][kwayland-server]
https://bugs.kde.org/show_bug.cgi?id=428039 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/733692f4391e ||bf82f0f9a44c1a9aadab95240e4 ||3 Status|ASSIGNED|RESOLVED --- Comment #2 from Bhushan Shah --- Git commit 733692f4391ebf82f0f9a44c1a9aadab95240e43 by Bhushan Shah. Committed on 21/10/2020 at 10:31. Pushed by bshah into branch 'master'. input: reconfigure after setting up the libinput Previously seat interface was keeping track of the repeat information, but now it is taken care by KeyboardInterface, which is created only if the setHasKeyboard is set to true. So, since we are setting up various capabilities on seat in libinput, re-parse configuration here, so that various information like key repeat is notified to kwayland-server M +1-1input.cpp https://invent.kde.org/plasma/kwin/commit/733692f4391ebf82f0f9a44c1a9aadab95240e43 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428039] Holding a key does not repeat it like it should [Wayland][kwin][kwayland-server]
https://bugs.kde.org/show_bug.cgi?id=428039 Bhushan Shah changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||bhus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428039] Holding a key does not repeat it like it should [Wayland][kwin][kwayland-server]
https://bugs.kde.org/show_bug.cgi?id=428039 Bhushan Shah changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428017] Cannot assign Super+tab shortcut
https://bugs.kde.org/show_bug.cgi?id=428017 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 423045] New: Test bug
https://bugs.kde.org/show_bug.cgi?id=423045 Bug ID: 423045 Summary: Test bug Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY Testy bug STEPS TO REPRODUCE 1. Check if gitlab integration works 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418977] After rotation mouse cursor is visible on touch device
https://bugs.kde.org/show_bug.cgi?id=418977 Bhushan Shah changed: What|Removed |Added Version Fixed In||5.19.0 Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/b2df11bf7e59 ||d57240afcdf88b352d49799d992 ||2 Resolution|--- |FIXED --- Comment #1 from Bhushan Shah --- Git commit b2df11bf7e59d57240afcdf88b352d49799d9922 by Bhushan Shah. Committed on 21/05/2020 at 07:08. Pushed by bshah into branch 'Plasma/5.19'. [platforms/drm] show cursor only when it is enabled In previous code we used to update/show cursor even when the pointer device was present, e.g mobile device. Guard it behind the cursor enabled check. FIXED-IN: 5.19.0 M +4-0plugins/platforms/drm/drm_backend.h M +11 -6plugins/platforms/drm/drm_output.cpp https://invent.kde.org/plasma/kwin/commit/b2df11bf7e59d57240afcdf88b352d49799d9922 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418977] New: After rotation mouse cursor is visible on touch device
https://bugs.kde.org/show_bug.cgi?id=418977 Bug ID: 418977 Summary: After rotation mouse cursor is visible on touch device Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY On mobile devices cursor should not be visible at all, but it appears after rotating device once using orientation sensor. STEPS TO REPRODUCE 1. Have a Mobile/Tablet device without any cursor 2. Rotate it OBSERVED RESULT Cursor is visible EXPECTED RESULT Cursor should not be visible since no mouse is attached. KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 418739] New: tablet mode value is wrong in kded
https://bugs.kde.org/show_bug.cgi?id=418739 Bug ID: 418739 Summary: tablet mode value is wrong in kded Product: KScreen Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kded Assignee: kscreen-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- As mentioned on IRC, for some reason tablet mode value is in wrong state in the kded for config, which prevents auto-rotation from working. I've tried debugging this without much of luck. But basically, - wayland backend sets value to true - on rotation event it tries to read value from monitored config - which doesn't take value set by wayland backend and defaults to false - as a result TopUp rotation is only thing available (all git master, FTR: kwin had tablet mode reporting broken, https://cgit.kde.org/kwin.git/commit/?id=7c5c7b5a1eba81c1df119993ac0b4bebfd7f2fcc fixes it, so make sure you have it before testing it) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414926] Enter key doesn't work for entering password.
https://bugs.kde.org/show_bug.cgi?id=414926 Bhushan Shah changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Bhushan Shah --- *** This bug has been marked as a duplicate of bug 414875 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414875] After entering the password, SDDM doesn't respond to pressing "Enter", you need to click on the ">" button to it's right
https://bugs.kde.org/show_bug.cgi?id=414875 Bhushan Shah changed: What|Removed |Added CC||tnb...@gmail.com --- Comment #5 from Bhushan Shah --- *** Bug 414926 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414126] DPMS doesn't work in drm backend
https://bugs.kde.org/show_bug.cgi?id=414126 Bhushan Shah changed: What|Removed |Added Version|unspecified |5.17.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414126] New: DPMS doesn't work in drm backend
https://bugs.kde.org/show_bug.cgi?id=414126 Bug ID: 414126 Summary: DPMS doesn't work in drm backend Product: kwin Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY On Pinephone device when I try to configure powerdevil so that the power button turns off the screen, it seems to just reset itself instead of shutting down. If I press power button twice quickly it seems to work, but not in single press. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.17.x release and also git master ADDITIONAL INFORMATION https://kde.modular.im/_matrix/media/v1/download/kde.org/wpmIsGiDXuTcmjrfsOgaWKss -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412069] Appstream integration no longer works
https://bugs.kde.org/show_bug.cgi?id=412069 --- Comment #2 from Bhushan Shah --- Do you want new tar of plasma-workspace created with this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412069] Appstream integration no longer works
https://bugs.kde.org/show_bug.cgi?id=412069 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-workspace/5115071bf3ed5 ||108a25069116dad138b68fa64f8 Status|REPORTED|RESOLVED --- Comment #1 from Bhushan Shah --- Git commit 5115071bf3ed5108a25069116dad138b68fa64f8 by Bhushan Shah. Committed on 19/09/2019 at 17:57. Pushed by bshah into branch 'Plasma/5.17'. Fix the appstream qt detection in cmake Missed that part during move of kicker plugin to plasma-workspace M +3-0CMakeLists.txt https://commits.kde.org/plasma-workspace/5115071bf3ed5108a25069116dad138b68fa64f8 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409885] New: Request for icon: timezone and set time automatically
https://bugs.kde.org/show_bug.cgi?id=409885 Bug ID: 409885 Summary: Request for icon: timezone and set time automatically Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: bhus...@gmail.com CC: kain...@gmail.com Target Milestone: --- Created attachment 121572 --> https://bugs.kde.org/attachment.cgi?id=121572&action=edit Screenshot of mobile time settings SUMMARY To be used in Plasma Mobile time settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #13 from Bhushan Shah --- Can you also upload ~/.config/kdegloabls? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409640] Hide virtual keyboard SNI on mobile/touchscreen only device.
https://bugs.kde.org/show_bug.cgi?id=409640 --- Comment #2 from Bhushan Shah --- KWin have information about input systems available (i.e touchscreen or tablet or keyboard0, so in my opinion it would make sense from KWin side to dynamically hide/show SNI. Beside filtering out this specific SNI from for example system tray would require very specific code from what I understand. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 --- Comment #4 from Bhushan Shah --- can you also pastebin ~/.config/fontconfig/fonts.conf? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #2 from Bhushan Shah --- Can you provide ~/.config/kdeglobals and ~/.config/kcmfontrc files? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409640] New: Hide virtual keyboard SNI on mobile/touchscreen only device.
https://bugs.kde.org/show_bug.cgi?id=409640 Bug ID: 409640 Summary: Hide virtual keyboard SNI on mobile/touchscreen only device. Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY It kinda becomes problem when on touchscreen only device if by accident you disable virtual keyboard. It makes no sense to enable/disable virtual-keyboard on phone/tablet devices. you always want virtual keyboard Linux/KDE Plasma: git master -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386393] No virtual keyboard when used without Xwayland
https://bugs.kde.org/show_bug.cgi?id=386393 Bhushan Shah changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #6 from Bhushan Shah --- Can not reproduce this anymore. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes
https://bugs.kde.org/show_bug.cgi?id=374890 Bhushan Shah changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #4 from Bhushan Shah --- This bug was not NEEDSINFO -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 375001] Mouse doesn't scroll in KDE applications
https://bugs.kde.org/show_bug.cgi?id=375001 Bhushan Shah changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #3 from Bhushan Shah --- Don't close bugs marked as reported! Bug policy clearly states this needs to be done for needsinfo bugs. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405091] Subpixel rendering gets disabled when changing fonts
https://bugs.kde.org/show_bug.cgi?id=405091 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #2 from Bhushan Shah --- Can you check if this is still reproducible with git master/ Neon dev unstable? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400834] Changing anti-aliasing settings doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=400834 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #3 from Bhushan Shah --- Vendor Default option has been removed from Plasma git master (to be released as Plasma 5.17). If possible can you check with git master or for example Neon dev unstable edition and see if you can still reproduce this? or is this bug even valid? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 270079] KDE should update XftSubpixel setting when using "System Settings" for font and fontconfig settings is changed
https://bugs.kde.org/show_bug.cgi?id=270079 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #3 from Bhushan Shah --- Is this still reproducible with git master? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 154471] antialiasing settings -- provide explicit options
https://bugs.kde.org/show_bug.cgi?id=154471 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED CC||bhus...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Bhushan Shah --- I think this has been sorted, as Fonts KCM have a single page instead of the multiple dialogs/pages. Please re-open if you think this is still valid for Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 244857] kcm_fonts: choosing "System Settings" for anti-alias does not revert the previous change made to user-level fonts.conf
https://bugs.kde.org/show_bug.cgi?id=244857 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/08ec9a036bf5b3e ||e102938ad332f624adc1060b9 --- Comment #4 from Bhushan Shah --- Git commit 08ec9a036bf5b3ee102938ad332f624adc1060b9 by Bhushan Shah. Committed on 12/06/2019 at 07:00. Pushed by bshah into branch 'Plasma/5.16'. Replace the excludeRange mode setting when already available Summary: Instead of appending a new entry. Related: bug 408415 Test Plan: - remove fonts.conf - start fonts kcm - enable exclude range - save - see config is added only once - modify config - save - see config is replaced and not added again - disable exclude range - save - see config is totally removed. Reviewers: fvogt Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D21748 M +5-1kcms/fonts/kxftconfig.cpp https://commits.kde.org/plasma-desktop/08ec9a036bf5b3ee102938ad332f624adc1060b9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408415] kcm_fonts unable to change previous exclude range
https://bugs.kde.org/show_bug.cgi?id=408415 Bhushan Shah changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/08ec9a036bf5b3e ||e102938ad332f624adc1060b9 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Bhushan Shah --- Git commit 08ec9a036bf5b3ee102938ad332f624adc1060b9 by Bhushan Shah. Committed on 12/06/2019 at 07:00. Pushed by bshah into branch 'Plasma/5.16'. Replace the excludeRange mode setting when already available Summary: Instead of appending a new entry. Related: bug 244857 Test Plan: - remove fonts.conf - start fonts kcm - enable exclude range - save - see config is added only once - modify config - save - see config is replaced and not added again - disable exclude range - save - see config is totally removed. Reviewers: fvogt Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D21748 M +5-1kcms/fonts/kxftconfig.cpp https://commits.kde.org/plasma-desktop/08ec9a036bf5b3ee102938ad332f624adc1060b9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408415] kcm_fonts unable to change previous exclude range
https://bugs.kde.org/show_bug.cgi?id=408415 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386566] Use Anti-Aliasing Language Change
https://bugs.kde.org/show_bug.cgi?id=386566 --- Comment #8 from Bhushan Shah --- Git commit 39c6facc51a807acc418a2e0dad6fda37d53071f by Bhushan Shah, on behalf of Julian Wolff. Committed on 27/05/2019 at 09:06. Pushed by bshah into branch 'master'. Parse global config files. Remove 'Vendor default' option. Fix changes not recognized. The fonts kcm did only parse a local config file. Global and default settings were not recognized. With this patch, all global config files are parsed before the local file is parsed. This allows us to drop the "Vendor default" option. This patch also fixes some changes not recognized (apply button disabled). Test Plan: Delete `~/.config/fontconfig/fonts.conf` and `~/.config/kcmfonts` . Run `kcmshell5 fonts`. The default/global settings should be displayed. Change some settings. The apply button should be enabled. Save. A new config file should be created. Follow up of the D12925 M +146 -81 kcms/fonts/fonts.cpp M +28 -16 kcms/fonts/fonts.h M +209 -95 kcms/fonts/kxftconfig.cpp M +11 -0kcms/fonts/kxftconfig.h M +13 -19 kcms/fonts/package/contents/ui/main.qml M +9-6kcms/fonts/previewimageprovider.cpp https://commits.kde.org/plasma-desktop/39c6facc51a807acc418a2e0dad6fda37d53071f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407754] StartKDE script writes into config files
https://bugs.kde.org/show_bug.cgi?id=407754 --- Comment #6 from Bhushan Shah --- Git commit 873cbc1da8f3f2b589f9f2722a4e15a8fcbfe4e5 by Bhushan Shah. Committed on 27/05/2019 at 09:06. Pushed by bshah into branch 'master'. Set defaults for anti-aliasing using the krdb We used to write a configuration for the anti-aliasing using the startkde script, startkde script would write to kdeglobals and then read this configuration in the krdb. This had un-intended side-effect of $XDG_CONFIG_DIRS/kdeglobals settings or settings set by ~/.config/fontconfig/fonts.conf not being used. D21335 fixes this by not writing to kdeglobals anymore, this transfers the defaults used by startkde here. Related: bug 389598 M +16 -25 kcms/krdb/krdb.cpp https://commits.kde.org/plasma-desktop/873cbc1da8f3f2b589f9f2722a4e15a8fcbfe4e5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 --- Comment #10 from Bhushan Shah --- Git commit 873cbc1da8f3f2b589f9f2722a4e15a8fcbfe4e5 by Bhushan Shah. Committed on 27/05/2019 at 09:06. Pushed by bshah into branch 'master'. Set defaults for anti-aliasing using the krdb We used to write a configuration for the anti-aliasing using the startkde script, startkde script would write to kdeglobals and then read this configuration in the krdb. This had un-intended side-effect of $XDG_CONFIG_DIRS/kdeglobals settings or settings set by ~/.config/fontconfig/fonts.conf not being used. D21335 fixes this by not writing to kdeglobals anymore, this transfers the defaults used by startkde here. Related: bug 407754 M +16 -25 kcms/krdb/krdb.cpp https://commits.kde.org/plasma-desktop/873cbc1da8f3f2b589f9f2722a4e15a8fcbfe4e5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-desktop/a24867873952378 |sma-desktop/1958f1ca1e4fcfa |4aa55279ba67b5949a394cc66 |cade554e4b196daaa0d7425f0 --- Comment #9 from Bhushan Shah --- Git commit 1958f1ca1e4fcfacade554e4b196daaa0d7425f0 by Bhushan Shah. Committed on 27/05/2019 at 09:06. Pushed by bshah into branch 'master'. Make slight/rgb the default option Medium hinting and None subpixel rendering was default options added when we used Oxygen fonts, however freetype recommends slight hinting as seen in this blog post from 2015 [1]. Also RGB hinting is most-recommended over the None. See linked bug report as well. [1] https://www.freetype.org/freetype2/docs/text-rendering-general.html M +4-4kcms/fonts/fonts.cpp M +2-2kcms/krdb/krdb.cpp https://commits.kde.org/plasma-desktop/1958f1ca1e4fcfacade554e4b196daaa0d7425f0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407754] StartKDE script writes into config files
https://bugs.kde.org/show_bug.cgi?id=407754 Bhushan Shah changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-workspace/1af4680ea8464 ||e0f6f444c103d49887fe219ee27 --- Comment #5 from Bhushan Shah --- Git commit 1af4680ea8464e0f6f444c103d49887fe219ee27 by Bhushan Shah. Committed on 27/05/2019 at 09:07. Pushed by bshah into branch 'master'. Don't write a anti-aliasing settings from startkde Summary: Writing a config files in $HOME at start-up is wrong way of setting defaults, If defaults needs to be set, they should be set by krdb instead of the startkde. Another side-effect of writing config file is that this breaks the distribution/vendor configuration, who might want to configure this value by shipping kdeglobals in either /etc/xdg or $XDG_CONFIG_DIRS. Related: bug 389598 Reviewers: #plasma, ngraham, apol, davidedmundson Reviewed By: #plasma, ngraham, apol, davidedmundson Subscribers: apol, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D21335 M +0-11 startkde/startkde.cmake M +0-11 startkde/startplasmacompositor.cmake https://commits.kde.org/plasma-workspace/1af4680ea8464e0f6f444c103d49887fe219ee27 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 --- Comment #8 from Bhushan Shah --- Git commit 1af4680ea8464e0f6f444c103d49887fe219ee27 by Bhushan Shah. Committed on 27/05/2019 at 09:07. Pushed by bshah into branch 'master'. Don't write a anti-aliasing settings from startkde Summary: Writing a config files in $HOME at start-up is wrong way of setting defaults, If defaults needs to be set, they should be set by krdb instead of the startkde. Another side-effect of writing config file is that this breaks the distribution/vendor configuration, who might want to configure this value by shipping kdeglobals in either /etc/xdg or $XDG_CONFIG_DIRS. Related: bug 407754 Reviewers: #plasma, ngraham, apol, davidedmundson Reviewed By: #plasma, ngraham, apol, davidedmundson Subscribers: apol, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D21335 M +0-11 startkde/startkde.cmake M +0-11 startkde/startplasmacompositor.cmake https://commits.kde.org/plasma-workspace/1af4680ea8464e0f6f444c103d49887fe219ee27 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386566] Use Anti-Aliasing Language Change
https://bugs.kde.org/show_bug.cgi?id=386566 --- Comment #7 from Bhushan Shah --- Git commit 0dfeb1d61bddde7b721b1bb188692715f7c630fa by Bhushan Shah, on behalf of Julian Wolff. Committed on 23/05/2019 at 08:40. Pushed by bshah into branch 'bshah/fixup-fonts'. Parse global config files. Remove 'Vendor default' option. Fix changes not recognized. The fonts kcm did only parse a local config file. Global and default settings were not recognized. With this patch, all global config files are parsed before the local file is parsed. This allows us to drop the "Vendor default" option. This patch also fixes some changes not recognized (apply button disabled). Test Plan: Delete `~/.config/fontconfig/fonts.conf` and `~/.config/kcmfonts` . Run `kcmshell5 fonts`. The default/global settings should be displayed. Change some settings. The apply button should be enabled. Save. A new config file should be created. Follow up of the D12925 M +147 -82 kcms/fonts/fonts.cpp M +28 -16 kcms/fonts/fonts.h M +218 -102 kcms/fonts/kxftconfig.cpp M +11 -0kcms/fonts/kxftconfig.h M +13 -19 kcms/fonts/package/contents/ui/main.qml M +9-6kcms/fonts/previewimageprovider.cpp https://commits.kde.org/plasma-desktop/0dfeb1d61bddde7b721b1bb188692715f7c630fa -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 Bhushan Shah changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #7 from Bhushan Shah --- Reopening... it was feature branch... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/a24867873952378 ||4aa55279ba67b5949a394cc66 Status|REOPENED|RESOLVED --- Comment #5 from Bhushan Shah --- Git commit a248678739523784aa55279ba67b5949a394cc66 by Bhushan Shah. Committed on 23/05/2019 at 08:42. Pushed by bshah into branch 'bshah/fixup-fonts'. Make slight/rgb the default option Medium hinting and None subpixel rendering was default options added when we used Oxygen fonts, however freetype recommends slight hinting as seen in this blog post from 2015 [1]. Also RGB hinting is most-recommended over the None. See linked bug report as well. [1] https://www.freetype.org/freetype2/docs/text-rendering-general.html M +4-4kcms/fonts/fonts.cpp M +2-2kcms/krdb/krdb.cpp https://commits.kde.org/plasma-desktop/a248678739523784aa55279ba67b5949a394cc66 --- Comment #6 from Bhushan Shah --- Git commit bbe55f7580b52524fd324bb684a71204efe2854d by Bhushan Shah. Committed on 23/05/2019 at 08:42. Pushed by bshah into branch 'bshah/fixup-fonts'. Set defaults for anti-aliasing using the krdb We used to write a configuration for the anti-aliasing using the startkde script, startkde script would write to kdeglobals and then read this configuration in the krdb. This had un-intended side-effect of $XDG_CONFIG_DIRS/kdeglobals settings or settings set by ~/.config/fontconfig/fonts.conf not being used. D21335 fixes this by not writing to kdeglobals anymore, this transfers the defaults used by startkde here. Related: bug 407754 M +16 -25 kcms/krdb/krdb.cpp https://commits.kde.org/plasma-desktop/bbe55f7580b52524fd324bb684a71204efe2854d -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/a24867873952378 ||4aa55279ba67b5949a394cc66 Status|REOPENED|RESOLVED --- Comment #5 from Bhushan Shah --- Git commit a248678739523784aa55279ba67b5949a394cc66 by Bhushan Shah. Committed on 23/05/2019 at 08:42. Pushed by bshah into branch 'bshah/fixup-fonts'. Make slight/rgb the default option Medium hinting and None subpixel rendering was default options added when we used Oxygen fonts, however freetype recommends slight hinting as seen in this blog post from 2015 [1]. Also RGB hinting is most-recommended over the None. See linked bug report as well. [1] https://www.freetype.org/freetype2/docs/text-rendering-general.html M +4-4kcms/fonts/fonts.cpp M +2-2kcms/krdb/krdb.cpp https://commits.kde.org/plasma-desktop/a248678739523784aa55279ba67b5949a394cc66 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407754] StartKDE script writes into config files
https://bugs.kde.org/show_bug.cgi?id=407754 --- Comment #4 from Bhushan Shah --- Git commit bbe55f7580b52524fd324bb684a71204efe2854d by Bhushan Shah. Committed on 23/05/2019 at 08:42. Pushed by bshah into branch 'bshah/fixup-fonts'. Set defaults for anti-aliasing using the krdb We used to write a configuration for the anti-aliasing using the startkde script, startkde script would write to kdeglobals and then read this configuration in the krdb. This had un-intended side-effect of $XDG_CONFIG_DIRS/kdeglobals settings or settings set by ~/.config/fontconfig/fonts.conf not being used. D21335 fixes this by not writing to kdeglobals anymore, this transfers the defaults used by startkde here. Related: bug 389598 M +16 -25 kcms/krdb/krdb.cpp https://commits.kde.org/plasma-desktop/bbe55f7580b52524fd324bb684a71204efe2854d -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #4 from Bhushan Shah --- This bug is not duplicate of the referenced bug, whatever default is set by startkde needs to be set by krdb, somewhere else, and those needs to be changed. Re-opening. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389598] Use better defaults for AA instead of relying on the system or distro to have decent default settings
https://bugs.kde.org/show_bug.cgi?id=389598 Bhushan Shah changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 407721] Brightness keys no longer work with Plasma 5.16
https://bugs.kde.org/show_bug.cgi?id=407721 --- Comment #8 from Bhushan Shah --- Commit above will fix it for other users, unfortunately for beta testers, they will still have broken "powerdevil" entry, which will conflict with the org_kde_powerdevil. Beta testers will need to cleanup the "[powerdevil]" section in ~/.config/kglobalshortcutsrc -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 407721] Brightness keys no longer work with Plasma 5.16
https://bugs.kde.org/show_bug.cgi?id=407721 Bhushan Shah changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pow ||erdevil/90839c802ebc30c1fd4 ||6b54bc04a75fe1e7c3a47 Status|CONFIRMED |RESOLVED --- Comment #7 from Bhushan Shah --- Git commit 90839c802ebc30c1fd46b54bc04a75fe1e7c3a47 by Bhushan Shah. Committed on 20/05/2019 at 12:35. Pushed by bshah into branch 'Plasma/5.16'. Set application name to org_kde_powerdevil Summary: Previously application component name without any KAboutData was org_kde_powerdevil (executable name), although, 972eb26d0558d commit changed the component name to powerdevil, which had side-effects that powerdevil would write shortcuts to powerdevil component and it would conflict with old org_kde_powerdevil shortcuts, and ultimately none would work. In theory we can do migration of the shortcuts to powerdevil component using kconf_update but that doesn't work, as kglobalaccel is already started before powerdevil, resulting in kconf_update changes having no effect, more on this in commit 4ae36ae which introduces the PowerDevilApp::migratePre512KeyboardShortcuts() function, while in theory PowerDevilApp::migratePre516KeyboardShortcuts can be introduced, we can simply avoid this hassle by re-assigning old component name. Reviewers: davidedmundson, romangg Reviewed By: davidedmundson Subscribers: fvogt, arojas, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D21303 M +2-1daemon/powerdevilapp.cpp https://commits.kde.org/powerdevil/90839c802ebc30c1fd46b54bc04a75fe1e7c3a47 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 407721] Brightness keys no longer work with Plasma 5.16
https://bugs.kde.org/show_bug.cgi?id=407721 --- Comment #6 from Bhushan Shah --- https://phabricator.kde.org/D21303 modifies the regression introducing code. Unfortunately kconf_update script is not useful for migrating shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404235] Flatpak backend doesn't do error reporting or handling
https://bugs.kde.org/show_bug.cgi?id=404235 --- Comment #3 from Bhushan Shah --- It's most generic way to explain bug I have :P While installing flatpak on phone it had hit 4-5 different problems, 1) bubblewrap being broken 2) space full on disk 3) internet not connected at all 4) flathub timing out in middle of download 5) one other bit I can't remember right now But in all cases flatpak CLI correctly reported issue but not discover, so oh well. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404235] Flatpak backend doesn't do error reporting or handling
https://bugs.kde.org/show_bug.cgi?id=404235 Bhushan Shah changed: What|Removed |Added Summary|Discover doesn't report any |Flatpak backend doesn't do |error when network |error reporting or handling |connection is disconnected | |in the middle of a Flatpak | |app installation| -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404235] Discover doesn't report any error when network connection is disconnected in the middle of a Flatpak app installation
https://bugs.kde.org/show_bug.cgi?id=404235 --- Comment #1 from Bhushan Shah --- Title is changed incorrectly. It doesn't do any error reporting, Internet connection was just example. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404235] New: Flatpak backend doesn't do error reporting or handling
https://bugs.kde.org/show_bug.cgi?id=404235 Bug ID: 404235 Summary: Flatpak backend doesn't do error reporting or handling Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: bhus...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start discover 2. Start installing flatpak 3. Disconnect internet (best way to produce error I found) OBSERVED RESULT Discover quietly finishes operation without any kind of notice. EXPECTED RESULT Expect that Discover will show some error message SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403336] Test bug
https://bugs.kde.org/show_bug.cgi?id=403336 Bhushan Shah changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403336] Test bug
https://bugs.kde.org/show_bug.cgi?id=403336 --- Comment #2 from Bhushan Shah --- Les test -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403336] Test bug
https://bugs.kde.org/show_bug.cgi?id=403336 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #1 from Bhushan Shah --- Test! More test! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #5 from Bhushan Shah --- *hardware -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 Bhushan Shah changed: What|Removed |Added Ever confirmed|0 |1 CC||bhus...@gmail.com Status|REPORTED|CONFIRMED --- Comment #4 from Bhushan Shah --- I can reproduce this issue, at a time that I thought this would be hard are issue. I don't exactly know pattern to reproduce this but yes this is annoying. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 400879] New: New icon request: torch on/off (monochrome)
https://bugs.kde.org/show_bug.cgi?id=400879 Bug ID: 400879 Summary: New icon request: torch on/off (monochrome) Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: bhus...@gmail.com CC: kain...@gmail.com Target Milestone: --- For usage in mobile. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399647] PackageKit sources show up as "undefined"
https://bugs.kde.org/show_bug.cgi?id=399647 Bhushan Shah changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||bhus...@gmail.com Resolution|FIXED |--- --- Comment #12 from Bhushan Shah --- I can reliably reproduce this on phone -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399962] Making Double-click to open files and folders as the default Click Behavior
https://bugs.kde.org/show_bug.cgi?id=399962 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
