[frameworks-kirigami] [Bug 484136] New: Kirigami Applications Visibly flicker while resizing
https://bugs.kde.org/show_bug.cgi?id=484136 Bug ID: 484136 Summary: Kirigami Applications Visibly flicker while resizing Classification: Frameworks and Libraries Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: rawat.ar...@protonmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided Created attachment 167541 --> https://bugs.kde.org/attachment.cgi?id=167541=edit Flickering on Resize SUMMARY When resizing a Kirigami App, the app flickers, with the content of the app seemingly moving into a region outside the frame of the window. STEPS TO REPRODUCE Resize the app OBSERVED RESULT Notice the black bar appearing on resize in the video above, as well as the visible flickering of application controls. EXPECTED RESULT Seamless resizing, as happens with QtWidgets. SOFTWARE/OS VERSIONS Kirigami master Application running on wayland w/ Qt 6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 469873] New: Comments within context blocks aren't rendered / don't work like comments
https://bugs.kde.org/show_bug.cgi?id=469873 Bug ID: 469873 Summary: Comments within context blocks aren't rendered / don't work like comments Classification: Frameworks and Libraries Product: frameworks-syntax-highlighting Version: 5.106.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: rawat.ar...@protonmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- Example: Try the following in QML: property string example: "ex" property string /* a comment */ example2: "ex" OBSERVED RESULT The comment delimiters aren't followed, and the comment is not treated as a comment, causing the syntax highlighting to break for the line. The syntax highlighting file has the following context block: EXPECTED RESULT The comment is ignored by the syntax-highlighting engine in matching parts of the context. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.106 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 452975] New: Support Interface Combinations on Physical interfaces
https://bugs.kde.org/show_bug.cgi?id=452975
Bug ID: 452975
Summary: Support Interface Combinations on Physical interfaces
Product: plasma-nm
Version: master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: rawat.ar...@protonmail.com
Target Milestone: ---
SUMMARY
Currently, plasma-nm does not allow a network card to run in both AP and
managed modes. In order for an active connection to be shared, there must be a
second wifi interface available.
Some network cards are able to do both simultaneously, such as all recent intel
cards. This can be checked with iw phy | grep -A 2 "interface combinations" ,
which returns
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 3, #channels <= 2
with an intel ax210 card. Accordingly, plasma-nm should support configuring the
network card to run in both managed and AP. This has an obvious use case, as
well as an implementation in windows for precedent.
STEPS TO REPRODUCE
1. Connect to a network (must be on a device with one wifi card and no wwan,
usually a laptop)
2. Hotspot button disappears
3. Can't create hotspot
OBSERVED RESULT
The hotspot button disappears, and no hotspot can be created
EXPECTED RESULT
Dependent on the hardware capabilities, the current wifi connection can be
shared through a hotspot.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.17.2
(available in About System)
KDE Plasma Version: Master
KDE Frameworks Version: Master
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 447924] Kicker cannot adapt with long list of favorites
https://bugs.kde.org/show_bug.cgi?id=447924 arawat changed: What|Removed |Added CC|rawat.ar...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447924] Kicker cannot adapt with long list of favorites
https://bugs.kde.org/show_bug.cgi?id=447924 arawat changed: What|Removed |Added CC||rawat.ar...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432926] Cannot update Flatpak apps and addons installed to system location, rather than user location
https://bugs.kde.org/show_bug.cgi?id=432926 arawat changed: What|Removed |Added CC||rawat.ar...@protonmail.com --- Comment #7 from arawat --- It looks like the flatpak backend downloads the first app, then attempts to install it to the system-wide flatpak installation, which causes the polkit permissions dialog to pop up. The problem with "Flatpak system operation Deploy not allowed for user" occurs when the backend tries to update a second flatpak while the polkit dialog is still open - this causes the installation attempt to fail immediately. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432780] Annotations cannot be edited after saving a document
https://bugs.kde.org/show_bug.cgi?id=432780 --- Comment #2 from arawat --- Created attachment 136133 --> https://bugs.kde.org/attachment.cgi?id=136133=edit After saving, the typewriter annotation turns into a popup note -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432780] New: Annotations cannot be edited after saving a document
https://bugs.kde.org/show_bug.cgi?id=432780 Bug ID: 432780 Summary: Annotations cannot be edited after saving a document Product: okular Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: rawat.ar...@protonmail.com Target Milestone: --- SUMMARY After saving or opening a document with typewriter annotations, the typewriter annotations are falsely classified as popup notes. These notes cannot be edited. STEPS TO REPRODUCE 1. Create a typewriter annotation 2. Save and click away from the typewriter annotation 3. Click the typewriter annotation and see it cannot be edited or resized OBSERVED RESULT Above. EXPECTED RESULT Typewriter annotation can be edited after saving. SOFTWARE/OS VERSION: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15 KDE Frameworks Version: 5.78 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429613] New: Plasmashell's edit application does not allow one to change the icon of the application
https://bugs.kde.org/show_bug.cgi?id=429613 Bug ID: 429613 Summary: Plasmashell's edit application does not allow one to change the icon of the application Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: rawat.ar...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On the right click menu on any application entry found in kickoff, their is an option to "Edit Application". However, the edit application dialog - which changes the corresponding .desktop file - does not allow the user to change the icon, if the .desktop file is found in the computer's root directory (/usr/share/applications). STEPS TO REPRODUCE 1. Open the "Edit Application" dialog through right clicking on a kickoff application entry. 2. See window 3. Icon can not be changed, unfortunately OBSERVED RESULT Icon can't be changed EXPECTED RESULT Icon can be changed, through replicating the desktop file in the user's home directory (.local/share/applications). Plasma already replicates the file to modify the name, description and command properties under the "Application" tab of the the edit application window. Why can it not do the same for the icon? SOFTWARE/OS VERSION: Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 426166] Some radio streams do not play, but they played before the latest applications update
https://bugs.kde.org/show_bug.cgi?id=426166 --- Comment #1 from arawat --- Additional information - Looking through Elisa's terminal output, the error message is "Error: "This appears to be a text file"" -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 426166] New: Some radio streams do not play, but they played before the latest applications update
https://bugs.kde.org/show_bug.cgi?id=426166 Bug ID: 426166 Summary: Some radio streams do not play, but they played before the latest applications update Product: elisa Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: rawat.ar...@protonmail.com Target Milestone: --- SUMMARY When adding certain radio streams to elisa, elisa fails to play. However, the radio stream can be played with vlc and other media players. Prior to the most recent update, these radio streams worked excellently in elisa. STEPS TO REPRODUCE 1. Enter a stream - http://a.files.bbci.co.uk/media/live/manifesto/audio/simulcast/hls/nonuk/sbr_low/llnw/bbc_world_service.m3u8 - HLS stream with AAC encoding 2. Watch as elisa fails to play the stream 3. Play the same stream through a media player like vlc or mpd OBSERVED RESULT An error occurs, and the radio icon is replaced by a "not available" icon EXPECTED RESULT Elisa plays the stream successfully SOFTWARE/OS VERSION: Linux/KDE Plasma: openSUSE Tumbleweed 20200901 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73 Qt Version: 5.15 ADDITIONAL INFORMATION Also tested with git master -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 423411] New: Clicking "Open Containing Folder" does not open file in default file manager
https://bugs.kde.org/show_bug.cgi?id=423411 Bug ID: 423411 Summary: Clicking "Open Containing Folder" does not open file in default file manager Product: Spectacle Version: 20.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: rawat.ar...@protonmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Opening the path of the saved file from the gui of spectacle opens the path in a file manager that may not be the default. STEPS TO REPRODUCE 1. Set default file manager to something other than dolphin 2. Take screenshot, and save 3. Click button "Open Containing Folder" OBSERVED RESULT Clicking button opens path in dolphin. Uninstalling dolphin results in spectacle crashing, but the path opens in the default file manager. EXPECTED RESULT Path opens in default file manager SOFTWARE/OS VERSIONS Linux/KDE Plasma: TW 20200621 (available in About System) KDE Plasma Version: 5.19.8 KDE Frameworks Version: 5.72 Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
