[plasmashell] [Bug 475013] Global menu prevents the panel to disappear when set to "windows can cover"

2023-09-29 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475013

--- Comment #1 from Matthias  ---
It seems like this happens without global menu being used as well. 

I move it for now, maybe someone can reproduce.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475013] Global menu prevents the panel to disappear when set to "windows can cover"

2023-10-01 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475013

--- Comment #4 from Matthias  ---
Created attachment 161990
  --> https://bugs.kde.org/attachment.cgi?id=161990=edit
Click on the circle, with global menu placed there and Firefox open, eg.

So this seems like an issue, that always comes up, once global menu is
triggered. Even if its not opening any menu, or even containing one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475013] Global menu prevents the panel to disappear when set to "windows can cover"

2023-10-01 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475013

--- Comment #3 from Matthias  ---
I think this is still a global menu issue. 

I have an empty space at the place, where it is showing up, when an application
is open, that supports global menu. 
When I press on that empty space, it persists as well. 

See the screenshot. 

Click on the circled area, when the global menu extension is placed there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475013] Global menu prevents the panel to disappear when set to "windows can cover"

2023-10-01 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475013

Matthias  changed:

   What|Removed |Added

  Component|Panel   |Global Menu
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 475363] Blacklist for "Window placement: Maximized"

2023-10-11 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475363

--- Comment #2 from Matthias  ---
Well, sure. Still, some states just make no sense, and users run into those,
the second they set to maximized and open one of these apps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475534] New: Panel does not show up when "windows can cover" and Kate lays upon it

2023-10-12 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475534

Bug ID: 475534
   Summary: Panel does not show up when "windows can cover" and
Kate lays upon it
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

STEPS TO REPRODUCE
1.  Set panel to "windows can cover"
2. Open Kate

OBSERVED RESULT

Panel does not appear

EXPECTED RESULT

Panel appears


Operating System: Garuda Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.6-zen2-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

ADDITIONAL INFORMATION

Panel appears with both Firedragon (Firefox fork) and Dolphin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475535] New: "Windows can cover" blocks windows from expanding

2023-10-12 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475535

Bug ID: 475535
   Summary: "Windows can cover" blocks windows from expanding
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 162259
  --> https://bugs.kde.org/attachment.cgi?id=162259=edit
Wallpaper selection is supposed to be fully maximized

This only happens on Wayland. 

STEPS TO REPRODUCE

1.  Set panel to "Windows can cover"
2. Open Yakuake
3. Open Wallpaper selection

OBSERVED RESULT


EXPECTED RESULT

See screenshots

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.6-zen2-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475535] "Windows can cover" blocks windows from expanding

2023-10-12 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475535

--- Comment #1 from Matthias  ---
Created attachment 162260
  --> https://bugs.kde.org/attachment.cgi?id=162260=edit
Yakuake is supposed to be fully maximized

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475534] Panel does not show up when "windows can cover" and Kate lays upon it

2023-10-12 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475534

--- Comment #1 from Matthias  ---
Sorry, under Wayland, I should have mentioned. 
Does not happen with X11.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475535] "Windows can cover" blocks windows from expanding

2023-10-12 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475535

--- Comment #2 from Matthias  ---
Yakuake is already reported: 
https://bugs.kde.org/show_bug.cgi?id=462762

"Windows can cover" seems to be still quite buggy at Wayland in general.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475292] New: Centric alignment // Zen Mode

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475292

Bug ID: 475292
   Summary: Centric alignment // Zen Mode
Classification: Applications
   Product: kate
   Version: 23.08.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 162127
  --> https://bugs.kde.org/attachment.cgi?id=162127=edit
Alignment adjustable

SUMMARY

VSCode has the ability to center the text and since we all stare at our screens
in a straight line, does it take the bending of our neck, to look at the (left)
side of the screen. 

I suggest introducing a centric alignment as well. 
This is also used for the zen mode. 

Which could be another improvement ;)


OBSERVED RESULT

The neck hurts :D

EXPECTED RESULT

I can see the text aligned in the middle. 

The ideal solution could involve, that the edges of the view area, can be
expanded and shrinked. 
I added a short video, to explain this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 475286] New: Valgrind won't install (missing archives)

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475286

Bug ID: 475286
   Summary: Valgrind won't install (missing archives)
Classification: Developer tools
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: southwickmatth...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. sudo apt install valgrind (ubuntu latest)

OBSERVED RESULT

Err:9 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libc6-i386
amd64 2.35-0ubuntu3.1
  404  Not Found [IP: 91.189.91.81 80]
Err:10 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libc6-dbg
amd64 2.35-0ubuntu3.1
  404  Not Found [IP: 91.189.91.81 80]
Get:11 http://archive.ubuntu.com/ubuntu jammy/main amd64 valgrind amd64
1:3.18.1-1ubuntu2 [14.1 MB]
Fetched 19.0 MB in 5s (3852 kB/s)
E: Failed to fetch
http://archive.ubuntu.com/ubuntu/pool/main/g/glibc/libc6-i386_2.35-0ubuntu3.1_amd64.deb
 404  Not Found [IP: 91.189.91.81 80]
E: Failed to fetch
http://archive.ubuntu.com/ubuntu/pool/main/g/glibc/libc6-dbg_2.35-0ubuntu3.1_amd64.deb
 404  Not Found [IP: 91.189.91.81 80]
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?

EXPECTED RESULT
For it to be installed successfully

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu Latest
(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.

[systemsettings] [Bug 475363] New: Blacklist for "Window placement: Maximized"

2023-10-08 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475363

Bug ID: 475363
   Summary: Blacklist for "Window placement: Maximized"
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwinoptions
  Assignee: kwin-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 162162
  --> https://bugs.kde.org/attachment.cgi?id=162162=edit
Thats all I see

SUMMARY

I really love the setting "Window placement: Maximized"
The only thing I see as a drawback, is that certain apps, who are clearly meant
to be launched in its own, small window - not maximized - end up like in my
screenshot. 

The app in discussion is color picker. Could we please provide an exposed list,
that lets us set certain apps, to not maximize?

STEPS TO REPRODUCE
1. Set Window placement to Maximized
2. Open Color Picker
3. 

OBSERVED RESULT

Color picker occupies the whole screen with two gigantic icons.  

EXPECTED RESULT

Color pickers opens normal, as intended by its developer. 
Operating System: Garuda Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.5-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

ADDITIONAL INFORMATION

Please see the screenshot.

-- 
You are receiving this mail because:
You are watching all bug changes.

[cantor] [Bug 475366] New: Blog outdated

2023-10-08 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475366

Bug ID: 475366
   Summary: Blog outdated
Classification: Applications
   Product: cantor
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cantor-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

I just saw that the Cantor homepage has received no sign of life for almost 3
years. 
A short "we are still alive, and the app gets updates" could help to let the
project look alive. 

https://cantor.kde.org/
Maybe we could involve @kde-www?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475367] New: Jupyter Notebook support for Kate

2023-10-08 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475367

Bug ID: 475367
   Summary: Jupyter Notebook support for Kate
Classification: Applications
   Product: kate
   Version: 23.08.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

I know, this is a huge one. Notebooks from Jupyter are a popular tool for data
scientists, and are also useful to teach programming, as its really convenient
to make tutorials in them. 

If we want them in Kate, I am sure we can reuse parts of Cantor and LabPlot. 
Both are maintained and should contain most of the code, that is needed. 

Hope this helps with the adoption.


STEPS TO REPRODUCE
1. 
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.

[kate] [Bug 475534] Panel does not show up when "windows can cover" and Kate lays upon it

2023-10-18 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475534

Matthias  changed:

   What|Removed |Added

   Target Milestone|1.0 |---
Version|master  |23.08.1
  Component|Panel   |general
Product|plasmashell |kate
   Assignee|plasma-b...@kde.org |kwrite-bugs-n...@kde.org

--- Comment #2 from Matthias  ---
I think I should reassign this to Kate, as it seems an issue with it
specifically.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475824] New: Panels dont reappear with multi monitor setup bordering

2023-10-19 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475824

Bug ID: 475824
   Summary: Panels dont reappear with multi monitor setup
bordering
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY

The multi monitor arrangement does prevent panels that are set to "windows can
cover" from appearing when hovering. 

The issue is clearly, that the second monitor borders to the area, where the
panel is located. 

STEPS TO REPRODUCE
1.  Put the second monitor in the display configuration ABOVE the primary one. 
2.  Set a panel bordering that area to "windows can cover" (so a panel at the
top, in this example)
3.  See that you cant reliably (if at all) bring that panel back, by hovering
over its activation area. 

OBSERVED RESULT

Panel does not reappear, until I remove the second monitor from the bordering
area. 

EXPECTED RESULT

The panel reappears when hovering over its designated space. 

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.7-zen2-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

ADDITIONAL INFORMATION

I tested this in Wayland.

I wanted to see, if this was a Wayland-exclusive bug, and then switched in SDDM
to my X11 session. 
Now, inxi -F shows me the following data, which does indicate - together with
the 'about this system' KCM - that I am still in Wayland nonetheless. This is
most likely a quirk with my distro, as they just recently added this. 

> Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.1 
> compositor: kwin_wayland

Let us assume, for now, that this is not confirmed in X11. 

PERSONAL NOTE: 

I am running Plasma 5 with Wayland for 2 Weeks now. 7/8 bugs I discovered, are
related to "windows can cover" panels.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475367] Jupyter Notebook support for Kate

2023-10-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475367

--- Comment #2 from Matthias  ---
Well, I guess I was suggesting that we make a plugin based on their sources. 
Not that we fork anything, more that we make it compatible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475466] New: Key to confirm suggestion

2023-10-11 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475466

Bug ID: 475466
   Summary: Key to confirm suggestion
Classification: Applications
   Product: kate
   Version: 23.08.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 162220
  --> https://bugs.kde.org/attachment.cgi?id=162220=edit
Idea for the implementation

SUMMARY

I like to insert the suggested value of auto-completion with tab, and not with
Enter. 
Please see the attached screenshot, to see how this could look like.  

The current approach allows only to disable autocompletion at all or to disable
the preselection of the first suggestion. 
Other than that, is there no way, to not have the enter key insert suggestions,
when I actually just want to insert a newline. 

Other editors, like VSCode, already support this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[docs.kde.org] [Bug 475923] New: Wrong link to bugs.kde.org

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475923

Bug ID: 475923
   Summary: Wrong link to bugs.kde.org
Classification: Websites
   Product: docs.kde.org
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: docs.kde.org
  Assignee: kde-doc-engl...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 162476
  --> https://bugs.kde.org/attachment.cgi?id=162476=edit
Link

The link shown in the screenshot is outdated (uses old handle)

See Screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[www.kde.org] [Bug 475925] New: Missing dead link checker - dead links

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475925

Bug ID: 475925
   Summary: Missing dead link checker - dead links
Classification: Websites
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 162477
  --> https://bugs.kde.org/attachment.cgi?id=162477=edit
dead links

SUMMARY

I found several dead links. 

There are applications (I don't know of open-source ones that work great) that
check them methodologically. 

I suggest to implement such a tool, that automatically checks for dead links. 

There is a short search (limited to 2000 checks per page) shown in the
screenshot. 
(That instance does not allow me to share the link, sorry)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475534] Panel does not show up when "windows can cover" and Kate lays upon it

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475534

--- Comment #4 from Matthias  ---
So we just leave this buggy? Or is this something the plasma panel can do about
it? Do you know the origin of this problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475563] Panel disappears in Wayland

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475563

--- Comment #5 from Matthias  ---
I got it to disappear on its own. 
It seems highly likely, to be caused by this application. 

I guess by that, its up to the widget?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475563] Panel disappears in Wayland

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475563

--- Comment #6 from Matthias  ---
I think this is yet another issue, that only happens with "windows can cover"

Lots of issues appear only with this setting, I suspect it has not been updated
yet to work with Wayland.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 382422] Use all threads by default

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=382422

--- Comment #3 from Matthias  ---
How do we inform the user currently about this?

It could simply set the threads to the maximum possible by default?
Whats the point of reducing this by default for all cases, who can use more?
Seems like we can fine tune this and indicate somewhere, which effects are
thread save.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 382422] Use all threads by default

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=382422

Matthias  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|NOT A BUG   |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-syntax-highlighting] [Bug 475933] New: Fish syntax reported falsely as error

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475933

Bug ID: 475933
   Summary: Fish syntax reported falsely as error
Classification: Frameworks and Libraries
   Product: frameworks-syntax-highlighting
   Version: unspecified
  Platform: Archlinux
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: walter.von.entfer...@posteo.net
  Target Milestone: ---

This is a false error flag for the fish scripting language

STEPS TO REPRODUCE
1. echo [(date +"%Y-%m-%dT%T%z")] [FISH] System is updated
2. Send this line in an active fish session
3. You will get this output, as intended

[2023-10-21T19:35:38+0200] [FISH] System is updated

OBSERVED RESULT

See Screenshot 1

The part [FISH] is reported as an error. 
The Kate syntax highlighting does format the specific part according to the
setting done within the "error" field in the settings. 

EXPECTED RESULT

The part is actually just a normal input and should be highlighted as the
'normal' setting. 

The brackets most likely confuse the framework, but this is valid code, I just
like to print [FISH]

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.5.7-zen2-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

ADDITIONAL INFORMATION

I want the output as described since it is supposed to look like that in a log
file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-syntax-highlighting] [Bug 475933] Fish syntax reported falsely as error

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475933

Matthias  changed:

   What|Removed |Added

 Attachment #162481|0   |1
is obsolete||

--- Comment #2 from Matthias  ---
Created attachment 162482
  --> https://bugs.kde.org/attachment.cgi?id=162482=edit
Screenshot 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-syntax-highlighting] [Bug 475933] Fish syntax reported falsely as error

2023-10-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475933

--- Comment #1 from Matthias  ---
Created attachment 162481
  --> https://bugs.kde.org/attachment.cgi?id=162481=edit
Screenshot 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475013] Global menu prevents the panel to disappear when set to "windows can cover"

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475013

--- Comment #5 from Matthias  ---
I could not reproduce this on a new installation, same distro. So probably a
configuration issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475270] New: Items of global menu sometimes not shown

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475270

Bug ID: 475270
   Summary: Items of global menu sometimes not shown
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Global Menu
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: k...@privat.broulik.de, mvourla...@gmail.com
  Target Milestone: 1.0

Created attachment 162113
  --> https://bugs.kde.org/attachment.cgi?id=162113=edit
Proof video

SUMMARY

See the video (thanks for the functionality to record desktops at Spectacle ;))

STEPS TO REPRODUCE
1. Move over one entry of the global menu
2. Click on the entry
3. Move along the other entries

OBSERVED RESULT

Some entries open, some don't 

EXPECTED RESULT

All entries open

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.5-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 475270] Items of global menu sometimes not shown

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475270

--- Comment #1 from Matthias  ---
This may be Wayland related, as I have not seen it yet on X11.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475271] New: Allow to move sidepanels

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475271

Bug ID: 475271
   Summary: Allow to move sidepanels
Classification: Applications
   Product: kate
   Version: 23.08.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 162114
  --> https://bugs.kde.org/attachment.cgi?id=162114=edit
Allow to move modules

SUMMARY

This has been possible in previous versions, so I assume this is a regression. 

I like to have my sidebar on the right side, and optionally, the ability to
freely choose, if I put the modules into the status or sidebar. Currently, the
different entries are limited to the location they are currently in. As an
example, I would also like to be able to move "Git" into the status bar.

I attach two screenshots. 


STEPS TO REPRODUCE
1. 
2. 
3. 

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.5-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475273] New: Clear output after synchronizing to path

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475273

Bug ID: 475273
   Summary: Clear output after synchronizing to path
Classification: Applications
   Product: kate
   Version: 23.08.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 162116
  --> https://bugs.kde.org/attachment.cgi?id=162116=edit
Confusing output

SUMMARY

That is one of my favorite features of Kate: It syncs into the folder, where
the current file is stored. 

I see, that this is implemented by sending a cd command to the console, and I
think its neat, to add a `&& clear` to it. 

So that its output is clean when the console becomes available to the user. 
Thanks

STEPS TO REPRODUCE
1. Open Konsole as part of Kate
2. See the output 

OBSERVED RESULT

The output looks a bit distracting. See my screenshot. 

EXPECTED RESULT

Clean output

ADDITIONAL INFORMATION

This can be very easily achieved, by just adding a `&& clear` to the `cd
/path/`

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 385531] Visual feedback when download starts

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=385531

--- Comment #3 from Matthias  ---
Can the plasma-browser-integration already send a notification at all, or is
this not implemented entirely?

As, can the notification widget be notified by the browser integration, that a
download has occurred?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475271] Allow to move sidepanels

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475271

--- Comment #1 from Matthias  ---
Created attachment 162115
  --> https://bugs.kde.org/attachment.cgi?id=162115=edit
Allow to move the sidebar

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475271] Allow to move sidepanels and modules

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475271

Matthias  changed:

   What|Removed |Added

Summary|Allow to move sidepanels|Allow to move sidepanels
   ||and modules

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475271] Allow to move sidepanels

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475271

Matthias  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475271] Allow to move sidepanels

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475271

--- Comment #3 from Matthias  ---
Thanks, that is how I want it. 

Can I also arrange the modules along the bar, like by dragging them?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475271] Allow to move sidepanels

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475271

--- Comment #5 from Matthias  ---
I did that by moving the elements to another side panel and then moving them
back to the desired panel in order.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475275] New: Remove line between line count and editor segment

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475275

Bug ID: 475275
   Summary: Remove line between line count and editor segment
Classification: Applications
   Product: kate
   Version: 23.08.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 162121
  --> https://bugs.kde.org/attachment.cgi?id=162121=edit
Depiction of the line

SUMMARY

I would like to be able to remove the line, that separates the line count and
the editor section. 
See screenshot. 

OBSERVED RESULT

I cannot remove the visible line. 

EXPECTED RESULT

I like to see an option to disable the line between the line count and the
editor section. 

ADDITIONAL INFORMATION

This might be already possible. I was a good boy and really tried my best to
find the solution. 

Did not find something yet :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475271] Allow to move sidepanels

2023-10-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475271

Matthias  changed:

   What|Removed |Added

Summary|Allow to move sidepanels|Allow to move sidepanels
   |and modules |

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it

2023-10-23 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=349785

Matthias  changed:

   What|Removed |Added

 CC||shaloksha...@protonmail.ch

--- Comment #31 from Matthias  ---
How is "intelligent autohide" different from the now-implemented "Windows can
cover"
Is there any difference in functionality?
Or is this simply a new name, a new implementation, and the same functionality?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475466] Key to confirm suggestion

2023-10-11 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475466

--- Comment #2 from Matthias  ---
Created attachment 162221
  --> https://bugs.kde.org/attachment.cgi?id=162221=edit
Conflict with this setting

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 475466] Key to confirm suggestion

2023-10-11 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475466

--- Comment #1 from Matthias  ---
In case we implement that, be aware that it conflicts with the setting "Cycle
through the results with tab/shift+tab"

Two possible ways to solve that could be:

a) Make the key(s) to cycle through the results customizable as well
b) Disable this setting, if the other setting is enabled and vice versa

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 473537] Double Keybinding - Establishing standards to prevent this

2023-08-19 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=473537

Matthias  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 473539] New: Double binding of a shortcut with varying results

2023-08-19 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=473539

Bug ID: 473539
   Summary: Double binding of a shortcut with varying results
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Archlinux
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

Hi there. 

Cut (usually on Ctrl+X) and Delete File (usually Shift+Del) has, for some
reason, the same shortcut. 
Cut has Shift + Del as alternative keybinding. 

If I try to delete a file (with Shift + Del) does it show up a message box,
that does tell me about the conflict. 

I am aware, that this is the case for at least two other people, who are also
on Arch. 
They do not experience the issue, and the system just prefers the delete
function to the cut function. 

OBSERVED RESULT

I have to delete the alternative shortcut binding of "Cut" in order to use the
"Delete" functionality. 
By default, I get an error about the ambiguity of the shortcut "Shift + Del" 


EXPECTED RESULT

Delete file when pressing Shift + Del

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 473537] New: Double Keybinding - Establishing standards to prevent this

2023-08-19 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=473537

Bug ID: 473537
   Summary: Double Keybinding - Establishing standards to prevent
this
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

Hi there. KDE seems to regularly ship releases with double and triple usages of
certain key combinations as shortcuts, who all even each other out, and KDE
then tells to to manually check. 

Sorry, why do we need to set the standard to instantly delete files in Dolphin
to Shift + Del, as we do since ever, and then also as an optional command to
Ctrl+X? Like, whats the point? I am pretty sure I already used Shift + Del to
delete stuff in Windows 98SE, and KDE luckily adopts that standard. 

Now, since the newest update, is Shift + Del set to "Cut" as well, and neither
works. 

STEPS TO REPRODUCE
1. Go into Dolphin
2. Mark some file that you like to delete
3. Hit Shift + Del

OBSERVED RESULT

KDE spawns a message, that tells me that the shortcut is set for multiple
commands, and it does not know which one you like. It does not say which
shortcut that is, it does also not offer to spawn the shortcut application for
you with the command pre-applied in the search bar, to handle this. 

EXPECTED RESULT

It just works. Shift + Del deletes the file 

Arch rolling

Operating System: Garuda Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: HP
Product Name: HP EliteBook 820 G3


ADDITIONAL INFORMATION

Sorry guys. Could we just setup some standard, that does not allow, that such a
setup ever ships? There needs to be some regulatory statement around this
issue, it just comes back time after time

Prevent people from shipping double keybindings, particularly if they **did not
test if it actually works** 
Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[krusader] [Bug 473790] New: Feature Request: Open in new Yakuake Tab, not new Konsole

2023-08-26 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=473790

Bug ID: 473790
   Summary: Feature Request: Open in new Yakuake Tab, not new
Konsole
Classification: Applications
   Product: krusader
   Version: 2.8.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: mat_...@gmx.de
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY
By pressing the Shortcut F (Console) ist should be possible to open Path in new
Yakuake Tab not the Konsole. That shoud be Cofigurable by User. 

OBSERVED RESULT
opens Konsole

EXPECTED RESULT
open in Yakuake if configured

ADDITIONAL INFORMATION
Would be very nice to have this one Day. Thanks for your work, I really like
using Krusader.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 454727] New: Klick von Protokollierung zu Bearbeiten verschieben sich das komplette Menü nach rechts

2022-06-02 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=454727

Bug ID: 454727
   Summary: Klick von Protokollierung zu Bearbeiten verschieben
sich das komplette Menü nach rechts
   Product: kdenlive
   Version: 22.04.1
  Platform: Microsoft Windows
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: krem...@matthiasstanke.de
  Target Milestone: ---

Created attachment 149390
  --> https://bugs.kde.org/attachment.cgi?id=149390=edit
UI Screenshot oben rechts

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Klick auf Protokollierung
2. Klick auf Bearbeiten
3. 

OBSERVED RESULT
Das gesamte Eingabefeld verschiebt sich nach rechts.
Alle anderen Klicks auf Audio, Effekte oder Farbe provozieren diesen Fehler
nicht.
Vorläufige Notlösung:
Fenster vom Vollbildmodus zu Fenstermodus und wieder Vollbildmodus.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows:  11
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.

[kdenlive] [Bug 454470] New: Warning about preview keeps showing up

2022-05-27 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=454470

Bug ID: 454470
   Summary: Warning about preview keeps showing up
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

The clip monitor is used to preview online resources. 
The warning, that the clip may take some while, appears unnecessary and
annoying to me personally. 
But the whole purpose of this issue is, to get rid of the warning, after it has
been shown once.   


STEPS TO REPRODUCE
1.  Preview Online Ressources
2. 
3. 

OBSERVED RESULT

Warning is shown again and again
This is distracting

EXPECTED RESULT

Warning shows just the first time. 

SOFTWARE/OS VERSIONS

Operating System: Garuda Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 480 Graphics

ADDITIONAL INFORMATION

https://youtu.be/BY0pDhMoe7w

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 456456] New: Make it possible to move to up, back and forward

2022-07-07 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=456456

Bug ID: 456456
   Summary: Make it possible to move to up, back and forward
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 150475
  --> https://bugs.kde.org/attachment.cgi?id=150475=edit
Screenshot

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

STEPS TO REPRODUCE
1. Drag a file to the back, forward or upwards button. 

OBSERVED RESULT

Currently, no file is moved

EXPECTED RESULT

File moves to the desired location. 

ADDITIONAL INFORMATION

See screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 456456] Make it possible to move files and directories to the up, back and forward locations.

2022-07-07 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=456456

Matthias  changed:

   What|Removed |Added

Summary|Make it possible to move to |Make it possible to move
   |up, back and forward|files and directories to
   ||the up, back and forward
   ||locations.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 453489] New: Timeline unable to load any files

2022-05-07 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=453489

Bug ID: 453489
   Summary: Timeline unable to load any files
   Product: kdenlive
   Version: 22.04.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 148628
  --> https://bugs.kde.org/attachment.cgi?id=148628=edit
kdenliverc (rename to that, in order to bugtrack, this can overwrite your
personal setup. backup that one by renaming it similary.)

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

I provide a kdenliverc, that deleted all my files from the timeline after a
save & restart (the first I had done after working on this project) 

The project lost all of its files from the timeline and couldn't accept any
others into it as well. It simply wouldn't drop/accept. 

Notice, that once I deleted/renamed kdenliverc, and restarted, all worked fine
again. Both restoring the old .kdenlive, as well as loading files from the file
bin. 

Notice, that loading the old .kdenlive, the timeline wouldn't be restored, on
both my computer and that from Massimo Stella, whom I reached on
Telegram/Matrix. 

So I am confused about that, since he has obviously another kdenliverc, so it
might be worth investigating his file of that name as well. Maybe there is some
misconfiguration. 

I suspect that is happening when the kdenliverc is loaded, since the issue only
occurred after me saving and restarting (for the purpose of potentially fixing
another issue, uff :)) 

Thanks a lot

ADDITIONAL INFORMATION

I am on Garuda Linux, Arch. All current versions and fully updated and rebooted
system. 

Operating System: Garuda Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.5-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 480 Graphics

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 453489] Timeline unable to load any files

2022-05-07 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=453489

--- Comment #1 from Matthias  ---
Created attachment 148629
  --> https://bugs.kde.org/attachment.cgi?id=148629=edit
I also add the kdenlive

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 458372] New: Notify about crashed compositor

2022-08-27 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=458372

Bug ID: 458372
   Summary: Notify about crashed compositor
   Product: plasmashell
   Version: master
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: k...@privat.broulik.de
  Target Milestone: 1.0

Created attachment 151628
  --> https://bugs.kde.org/attachment.cgi?id=151628=edit
Screenshot

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Bring your compositor to crash
2.  Dont get notified about it. 

OBSERVED RESULT

No notification

EXPECTED RESULT

Notification **in the systray/via popup)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch 
Operating System: Garuda Linux

KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.3-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 480 Graphics
Manufacturer: ASUS

ADDITIONAL INFORMATION

I got no notification, that my composition broke due to a misaligned device
driver. I just lost transparency of my latte dock, and got no clue, why. 

In the Garuda forum
(https://forum.garudalinux.org/t/transparency-effect-for-latte/21956/14) I got
pitched about the composition settings, where an extensive and pretty
informative explanation of the case waited for me. 

I would love to see a notification, including it being clickable and linking to
said settings page, in the notification widget. 
There are a lot of little details listed there and such a major crash - that
doesnt solve itself by waiting or so - does get hidden away at the current
time. 

Thanks a lot

-- 
You are receiving this mail because:
You are watching all bug changes.

[rkward] [Bug 404431] RKWard crashes when changing the class of an opened object

2022-09-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=404431

Matthias  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #2 from Matthias  ---
The bug persists with the following versions:

R version (compile time): 4.0.2  (2020-06-22 r78730)
R runtime session info:
R version 4.1.2 (2021-11-01)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 22.04.1 LTS

Matrix products: default
BLAS:   /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.10.0
LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.10.0

locale:
 [1] LC_CTYPE=de_DE.UTF-8  LC_NUMERIC=C 
 [3] LC_TIME=de_DE.UTF-8   LC_COLLATE=de_DE.UTF-8   
 [5] LC_MONETARY=de_DE.UTF-8   LC_MESSAGES=de_DE.UTF-8  
 [7] LC_PAPER=de_DE.UTF-8  LC_NAME=de_DE.UTF-8  
 [9] LC_ADDRESS=de_DE.UTF-8LC_TELEPHONE=de_DE.UTF-8 
[11] LC_MEASUREMENT=de_DE.UTF-8LC_IDENTIFICATION=de_DE.UTF-8

attached base packages:
[1] stats graphics  grDevices utils datasets  methods   base 

other attached packages:
[1] rkward_0.7.2

loaded via a namespace (and not attached):
[1] compiler_4.1.2 tools_4.1.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[rkward] [Bug 404431] RKWard crashes when changing the class of an opened object

2022-09-21 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=404431

--- Comment #4 from Matthias  ---
Sorry, my bad. The bug can be triggered with this script:

#Preparation
library(likert)
set.seed(1)
n <- 100

# Create dataframe df
df <- data.frame(
id=sample(1:5,n, replace=T), 
rating=factor(sample(1:5,n, replace=T),
labels=c("Good","Neither","Poor","Very Good","Very Poor"))
)

#Now open df in Rkward's viewer, then run:
df <- likert(items=df[,2, drop = FALSE], nlevels = 5)

-- 
You are receiving this mail because:
You are watching all bug changes.

[docs] [Bug 457549] New: docs.kde.org are outdated

2022-08-06 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=457549

Bug ID: 457549
   Summary: docs.kde.org are outdated
   Product: docs
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: docs.kde.org
  Assignee: kde-doc-engl...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

The docs.kde.org page is hugely outdated. The logo is still from KDE 3, the
shipped documentation seems to at least 3 years old, sometimes even 10 years: 

https://docs.kde.org/stable5/en/kdevelop/kdevelop/index.html

Since this is, what people find when they google (how I just did) would I
recommend to take this site down. 
I hope somebody has access to it (or can even update it with the current state
of the documentation)

-- 
You are receiving this mail because:
You are watching all bug changes.

[docs] [Bug 457549] docs.kde.org are outdated

2022-08-07 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=457549

--- Comment #3 from Matthias  ---
And also updating the logo.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-syntax-highlighting] [Bug 463969] New: Nim: Fails at "\\"

2023-01-07 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=463969

Bug ID: 463969
   Summary: Nim: Fails at "\\"
Classification: Frameworks and Libraries
   Product: frameworks-syntax-highlighting
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: walter.von.entfer...@posteo.net
  Target Milestone: ---

SUMMARY

Nim highlighting breaks at "\\"

STEPS TO REPRODUCE
1.  Load this file https://github.com/Vindaar/shell/blob/master/shell.nim
2.  See it breaking at line 17
3.  Compare with VSCode

OBSERVED RESULT

Syntax highlighting breaks. 

EXPECTED RESULT

Syntax highlighting doesnt break. 

SOFTWARE/OS VERSIONS
Windows:  Windows 10 Pro 21H2
Kate Nightly:
https://charlotte.kde.org/binary-factory/Kate_Nightly_win64/lastSuccessfulBuild/kate-master-1812-windows-cl-msvc2019-x86_64.exe

ADDITIONAL INFORMATION

Code is confirmed to be valid. 
VSCode highlights correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 397982] Half of the predefined color sets are incompatible with Nuget errors

2022-12-16 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=397982

Matthias  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Matthias  ---
:D

That is 4 years old, so I guess its safe to assume, this is solved by now

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 411252] The output of HDMI sound over DP

2022-12-18 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=411252

Matthias  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #3 from Matthias  ---
I am on a different setup now, so closing 

Thanks :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480159] Add option to make Caps lock key a 'bindable' key (F12)

2024-01-22 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=480159

Matthias  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|NOT A BUG   |---
 Ever confirmed|0   |1

--- Comment #2 from Matthias  ---
So far as I understand, is this dependent on X11 and considering we phase that
out, is it wise to find a solution that doesnt require a component of X11,
right?

I guess there will be a replacement for the whole Advanced tab.

I am more looking for a solution, that can actually be accieved within Plasma
and not some external component.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kfind] [Bug 430437] Copy from KFind to Dolphin with multiple files

2024-02-11 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=430437

Matthias  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WORKSFORME  |FIXED

--- Comment #3 from Matthias  ---
Yep, resolved

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 477764] New: Dark mode for KHelpcenter

2023-11-30 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=477764

Bug ID: 477764
   Summary: Dark mode for KHelpcenter
Classification: Applications
   Product: khelpcenter
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-doc-engl...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

Currently, I see no way to read KHelpcenter with a black background. 


STEPS TO REPRODUCE
1.  Open KHelpcenter
2.  Try to make the screen not flood your eyes with bright light

Particularly in the night, when I have everything dark - Browser and Webpages,
Plasma, and all other apps, is this convenient.

Thanks a lot



ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480159] New: Add option to make Caps lock key a 'bindable' key (F12)

2024-01-22 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=480159

Bug ID: 480159
   Summary: Add option to make Caps lock key a 'bindable' key
(F12)
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_keyboard
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
CC: butir...@gmail.com, natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 165119
  --> https://bugs.kde.org/attachment.cgi?id=165119=edit
Example of the category

SUMMARY

I like to bind Yakuake to Caps lock. 

In order to do this, I need two things: Disable the normal caps lock behavior
(why the heck isnt this default :P) and do bind it instead to a key, that can
be used to create a shortcut. 

I add the following suggestion to the project: Please create an entry in
Keyboard > Advanced > Caps lock behavior (why are there two entries of this
category?) and let this entry say and do:

Caps lock sends F12

F12 is used to bind any application to caps lock really, and it could also be
another key. (But really, use F12, its the default and established key to
launch Yakuake and generally a good generic key to bind things to. People who
dont use Yakuake, have it free for other things.)

It could also be a custom key, but considering there is no such example in the
whole KCM yet for it, I imagine the API for it has not been implemented or
written yet, or it is against a design decision. 

Thanks


STEPS TO REPRODUCE
1. 
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.

[systemsettings] [Bug 480161] Add entry "move windows to other screen" to shortcuts

2024-01-22 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=480161

--- Comment #1 from Matthias  ---
Created attachment 165125
  --> https://bugs.kde.org/attachment.cgi?id=165125=edit
Move windows to other screen

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480161] New: Add entry "move windows to other screen" to shortcuts

2024-01-22 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=480161

Bug ID: 480161
   Summary: Add entry "move windows to other screen" to shortcuts
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

Hi there :)

I like to move my windows with a shortcut. The functionality for it is there,
seen in the screenshot. Currently only available with the mouse. Thanks a lot

Sidenote: The systemsettings product category here in the Bugtracker misses the
kcm_shortcuts component. 




STEPS TO REPRODUCE
1. 
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.

[kate] [Bug 480206] New: Add Julia LSP support

2024-01-22 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=480206

Bug ID: 480206
   Summary: Add Julia LSP support
Classification: Applications
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: task
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

Hi there. This Wiki contains the code needed to enable support for the LSP of
Julia. 

https://github.com/julia-vscode/LanguageServer.jl/wiki/Kate#custom-lsp-setting

As you can see, is all what the user needs to do, is to run: 

1. julia
2. ]
3. add LanguageServer

Ideally, we could run those lines initially as well, but I think its the policy
of Kate, to let that to the user entirely.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 477052] New: Plasma 6: Desktop Effects > Appearance

2023-11-15 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=477052

Bug ID: 477052
   Summary: Plasma 6: Desktop Effects > Appearance
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

The massive amount of desktop effects are purely cosmetic changes, so I claim
that they fit under the Appearance category.

They do not change the behavior of the system in any meaningful way, and its
counter-intuitive to place it there. 

I see the change to Plasma 6 as an opportunity, to change this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-syntax-highlighting] [Bug 475933] Fish syntax reported falsely as error

2023-11-11 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=475933

--- Comment #5 from Matthias  ---
Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 476878] New: Missed string highlight in Nix file

2023-11-12 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=476878

Bug ID: 476878
   Summary: Missed string highlight in Nix file
Classification: Applications
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: scripting
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 163074
  --> https://bugs.kde.org/attachment.cgi?id=163074=edit
String not highlighted

SUMMARY

The string in line 4 is not highlighted as such: 

```nix
  programs.firefox = {
enable = true;
preferences = {
  "widget.use-xdg-desktop-portal.file-picker" = 1;
  "widget.use-xdg-desktop-portal.mime-handler" = 1;
  "browser.backspace_action" = 0;
};
  };
```

STEPS TO REPRODUCE
1.  Open file
2.  Paste above content into it
3.  Name it blabla.nix or set file type to Nix
4.  Look at line 4

OBSERVED RESULT

String not highlighted

EXPECTED RESULT

String highlighted as all the other strings 

Operating System: NixOS 23.05
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.10
Kernel Version: 6.6.0 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION

See screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property

2024-03-10 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=479712

Matthias  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #17 from Matthias  ---
Sorry, we failed. That issue here is indeed solved and we encountered an
independent problem in Qbittorrent. Closing

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property

2024-03-10 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=479712

Matthias  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 CC||shaloksha...@protonmail.ch

--- Comment #15 from Matthias  ---
At least two people on 6.0.1 confirm that this bug is still active. 
Tested with QBittorrent. 

NixOS and Arch Linux.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property

2024-03-10 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=479712

--- Comment #16 from Matthias  ---
Created attachment 166894
  --> https://bugs.kde.org/attachment.cgi?id=166894=edit
missing icon in 6.0.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 483495] New: Some commands are named differently in certain distros

2024-03-13 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=483495

Bug ID: 483495
   Summary: Some commands are named differently in certain distros
Classification: Applications
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 167136
  --> https://bugs.kde.org/attachment.cgi?id=167136=edit
Discussion in chat

SUMMARY

Some of the LSP commands are renamed at the packaging level of some distros. 
It seems they had contributed the original config for vscode language server of
css and html, at least.

See screenshot

P.S: Kate has no LSP component here in the bug tracker. I think its worth it,
doing one. 

Operating System: NixOS 24.05
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.0 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)

2024-03-28 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484599

--- Comment #2 from Matthias  ---
Do I understand this right, that the text now says 'Show Sidebar' both when its
already open, and when its closed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 484592] External display rendered unusable due to misconfiguration

2024-03-28 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484592

--- Comment #3 from Matthias  ---
No. I missed to specify that, but the error occurs, when I confirm a
configuration, that doesnt work.

As you can read from my report, I am already in a situation, that prevents me
from using that TV as an external display.

There is no way, to restore its functionality so far as I can see. (Not even
modifiying a text file can help, sincs that one is generated and cannot be
modified seemingly.)

The issue is, that the irrevertable action does not come with the KCM setting
itself, but by using the Fn+F7 menu (dont know its name) with which you
determine the output configuration.

It allows you to choose between several options, among those: 

) Switch to internal display 
) Switch to external display
) Unify output
) Extend left
) Extend right

If you choose to follow the steps outlined in the original report, and then
choose 'Switch to external display' there is no way of changing the setup
again. 

And plugging the device in, will always result in a black screen on both
devices. 

Since it is only possible to edit it once plugged in, and plugging it in, it
switches to 'external screen only' - even though that one is in an ill state. 

The TV rejects the format, and we seem to have no detection for that.

Another possible solution would be, to never except such an illegal state in
the first place. 

My TV does not accept a seemingly plausible resolution (2560 x 1440) and shows
this on its screen.

I dont know, if it reports this back on an API as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)

2024-03-28 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484599

--- Comment #4 from Matthias  ---
So it will show 'Hide Sidebar' when open?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)

2024-03-28 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484599

--- Comment #6 from Matthias  ---
I am just confused

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 485269] New: 'Unifying output' leaves the system with no display output

2024-04-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485269

Bug ID: 485269
   Summary: 'Unifying output' leaves the system with no display
output
Classification: Plasma
   Product: KScreen
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY
I had a TV connected to my laptop, and chose only it as the shown output. Then
I hit Fn +  F7 to open the screen layout widget, and chose "Unify output". 

The result was a black screen on both the laptop and the TV. Removing the cable
connection, was not restoring the display output on the laptop. Rebooting
booted straight into a black screen as well.

I booted into my second installation (first is KaOS, second NixOS) and tried
the same thing there again, with the same outcome. 

This has to be due to a recent change, as I use both systems on a rolling
release, and had used that feature in the past with the same hardware, and no
such issue occurred. 

In this case, no user error was involved. Still, I managed to reach a similar
bad state (with only the TV being inaccessible) with a bad configuration, that
involved me confirming a display resolution for the TV as valid, that wasnt. 

In both cases, the simple usage of a multi monitor setup meant partly, or
complete loss of display functionality. 

To make matters worse, kscreen is not a declarative file anymore. I think that
is a very big mistake, and I strongly suggest to restore that functionality.
Today, it seems that the entire display configuration is created by a binary,
that then creates a yaml file. That one cannot be edited and reloaded. This
goes against the UNIX philosophy and makes it very hard to restore from such a
case. I would need to do dark magic, or have a rollback feature on filesystem
level enabled, to recover from this. 

I thought about several mechanisms to prevent such issues. 

1) Ask if the configuration is fine for the 'Screen Layout' widget as well. 
At least when the configuration involves new settings. Maybe when the API
and/or hardware changes. 

2.) Implement a shortcut, that resets the configuration to its default state. 

3.) Implement such a button to reset the configuration in the KScreen KCM.
This could have helped with the second case, where only the external display
was inaccessible.

I put this on major, and think it could be ranked more severe even. 


STEPS TO REPRODUCE
1. 
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.

[systemsettings] [Bug 484592] External display rendered unusable due to misconfiguration

2024-04-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484592

Matthias  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 485285] New: Countdown confirmation for the OSD and Plasma applet

2024-04-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485285

Bug ID: 485285
   Summary: Countdown confirmation for the OSD and Plasma applet
Classification: Plasma
   Product: KScreen
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: OSD and Plasma applet
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY
The OSD and Plasma widget has currently no confirmation timer, to avoid setting
configurations, who happen to lead into issues. The KScreen KCM has such one,
and this proposal is about adding that to the OSD/Plasma widget as well. 

Related:

https://bugs.kde.org/show_bug.cgi?id=485269
https://bugs.kde.org/show_bug.cgi?id=484592

I would prefer, that configurations who are known to work, will not be asked
for confirmation after the first time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 484592] New: External display rendered unusable due to misconfiguration

2024-03-27 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484592

Bug ID: 484592
   Summary: External display rendered unusable due to
misconfiguration
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

I managed to setup the external TV in a way, that it is completely unusable
from this installation. 
There is currently no GUI way, to restore its functionality as external
display. 
I suggest to implement a functionality, that allows to configure previous
output devices even when they are not connected. (Or at least restore their
settings)


STEPS TO REPRODUCE
1. Connect an external display
2. Choose an incompatible resolution (2560x1440)
3. Switch to it as the only output source (Fn+F7 in my case)

I also set the TV as the primary display in the KCM, idk if thats important to
replicate. 

OBSERVED RESULT

Both devices stay black, once the TV is connected.

EXPECTED RESULT

Either the OS recognizing and accommodating for the issue, or providing an
option to reset the ill setting manually before the connection happens. ab 

Operating System: NixOS 24.05
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.6.22 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION

I like to add, that the chosen resolution is not only made available by the
KCM, it is also a theoretically compatible format (16:9 on this LG E9)

So this can happen easily to common users. 

I actually replicated that based on an issue, 
that a friend of mine just experienced on Windows. 

Seems like we can do better here ;)

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 484592] External display rendered unusable due to misconfiguration

2024-03-27 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484592

--- Comment #1 from Matthias  ---
Maybe we add kscreen-doctor to the KCM? (By the way, there is no component for
KScreen here in the bugtracker)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 484599] New: Name of UI element too long (Hide/Show Sidebar)

2024-03-27 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484599

Bug ID: 484599
   Summary: Name of UI element too long (Hide/Show Sidebar)
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 167845
  --> https://bugs.kde.org/attachment.cgi?id=167845=edit
UI Element

SUMMARY

The current name for the toolbar element to show and hide the sidebar is
unnecessary long: 

Hide/Show the component sidebar

This makes it uneasy, to use this as a dedicated button in the toolbar. 
(See screenshot)

First, there is no other sidebar, so "component" is superfluous to begin with. 

Second, other buttons have the option to change, depending on the state. 

Like in Dolphin, where the "Split" element changes into "Close" and vice versa. 
We could implement, to do the same here. 

Otherwise, I suggest to rename the element simply into "Sidebar" and call it a
day. 
Also consider, that this causes the translators to do work, so let us decide on
this with foresight.  :)

Thanks a lot


STEPS TO REPRODUCE
1.  Open Kontact, switch to the KMail panel (I assume standalone Kmail is the
same)
2.  Add the 'Hide/Show the component sidebar' element to the toolbar. 
3.  Acknowledge, that it takes much space. 


Operating System: NixOS 24.05
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.6.22 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 483495] Some commands are named differently in certain distros

2024-03-29 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=483495

--- Comment #2 from Matthias  ---
To be honest, I think this is not on Kate to fix. Distros diverting from
standards, and causing problems for others, should not be something that we
support.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Haruna] [Bug 485043] Ctrl + ` doesnt work

2024-04-04 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485043

Matthias  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[Haruna] [Bug 485043] New: Ctrl + ` doesnt work

2024-04-04 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485043

Bug ID: 485043
   Summary: Ctrl + ` doesnt work
Classification: Applications
   Product: Haruna
   Version: unspecified
  Platform: KaOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Hi there :)

Ctrl + ` does not open the Action Dialog for me. It works, when I set the right
click to it, so I guess its only the keybinding. 
It is set in the settings, just doesnt trigger. 


STEPS TO REPRODUCE
1. Open Haruna
2. Press Ctrl + `
3. Nothing happens

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
Action dialog opens

SOFTWARE/OS VERSIONS
Operating System: KaOS (2024) 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Kernel Version: 6.7.9-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82L0
System Version: Yoga Slim 7 Carbon 14ACN6

-- 
You are receiving this mail because:
You are watching all bug changes.

[Haruna] [Bug 485042] New: Use subtitles in same directory as the movie

2024-04-04 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485042

Bug ID: 485042
   Summary: Use subtitles in same directory as the movie
Classification: Applications
   Product: Haruna
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

I am not quite sure, I understand, how subtitles are supposed to work in
Haruna, so forgive me, if this is redundant. 

STEPS TO REPRODUCE
1.  Open up a video
2.  Have the subtitle in the same directory
3.  Being unable to select it as a primary or secondary subtitle

OBSERVED RESULT
Subtitles have to be chosen as "external subtitle"

EXPECTED RESULT
Being able to load the subtitle easily. 

Operating System: KaOS (2024) 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Kernel Version: 6.7.9-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82L0
System Version: Yoga Slim 7 Carbon 14ACN6

ADDITIONAL INFORMATION

I am also confused by the default value in the settings. It says "Subs" in the
field that is meant to contain a directory. 
What is this supposed to mean?

There is no explanation to that, and it seems to serve no purpose.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 485269] 'Unify output' using the OSD or widget leaves the system with no display output

2024-04-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485269

--- Comment #3 from Matthias  ---
I have no idea, what caused this error. The error in 484592 is known and
reproducible. 
This error also disables the main laptop screen, and renders the entire
installation of the OS essentially inaccessible. 
The error in 484592 only renders the specific external device unusable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 485298] New: Detect misconfigurations and automatically reset them

2024-04-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485298

Bug ID: 485298
   Summary: Detect misconfigurations and automatically reset them
Classification: Plasma
   Product: KScreen
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

SUMMARY

There are several cases of misconfigurations, who lead to parts of the monitor
setup, or the entirety of it, as inaccessible. 
Those are major issues, since essentially the entire installation of the OS is
not usable anymore, or certain hardware with that installation. I raised one
proposal, that aims to prevent that by introducing a countdown/confirmation
button to the OSD widget. Still, by accidentally confirming such an ill setup,
this issue could occur as well. Also, the confirmation countdown could render
the OSD/Plasma widget as cumbersome, since it is intended to provide a quick
and easy way, to change the output device. 

This proposal intents to detect ill setups and automatically corrects them. 

Currently, KScreen and KWin are completely fine with establishing a connection,
that results in a black screen so long as it had been confirmed by the KScreen
KCM before. 

That results in several issues, where KScreen connects to a device, that is not
showing any content, while simultaneously applying the ill configuration. So
KScreen/Kwin definitely detects the hardware, and does act upon it, despite the
hardware not showing any content. 

I am confident, that we can simply restore to a healthy default, when we detect
that the output is not displayed at all?

Or do (some) displays not even report this back? 
I mean, isnt there a way to read the resolution, etc, which would - assumingly
- not be valid? 

Or maybe the refresh rate? 
Are there really displays out there, who report the values we might expect,
despite not showing anything?
Including my very own internal laptop display?

Reference list: 

First issue: https://bugs.kde.org/show_bug.cgi?id=485269
Second issue: https://bugs.kde.org/show_bug.cgi?id=484592
Countdown feature proposal: https://bugs.kde.org/show_bug.cgi?id=485285

Thanks a lot

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 485285] Countdown confirmation for the OSD and Plasma applet

2024-04-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485285

--- Comment #3 from Matthias  ---
*** Bug 484592 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 484592] External display rendered unusable due to misconfiguration

2024-04-09 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=484592

Matthias  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Matthias  ---


*** This bug has been marked as a duplicate of bug 485285 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 485269] 'Unify output' using the OSD or widget leaves the system with no display output

2024-04-10 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485269

--- Comment #5 from Matthias  ---
So, I could reproduce this now on the Garuda and KaOS live ISOs. Both show
again the same behavior: 

Wayland sessions get every time into a black screen on both the laptop and the
TV. 
I tried it as well on X11, and both Garuda and KaOS show the same behavior as
well.
In this case, the OSD disappears, but no change is applied, and that counts for
all options of the OSD. 

With Wayland, only the Unify button misbehaves, in X11 all of them show no
effect at all. 
I should mention, that with both, Wayland and X11, I get an extended to the
side view, when I start the live mode with the TV attached. 
That one works perfectly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 485269] 'Unify output' using the OSD or widget leaves the system with no display output

2024-04-10 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485269

Matthias  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #4 from Matthias  ---
So, I just got this issue on Arch as well. 
Makes three independent distributions.

This is definitely due to a recent update.
I did this on a LG E9. Who knows, how many devices could possibly also
effected.

3 Installations rendered unusable. 
I need another way of bugtracking this 

-- 
You are receiving this mail because:
You are watching all bug changes.

[Haruna] [Bug 485042] Use subtitles in same directory as the movie

2024-04-16 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485042

--- Comment #3 from Matthias  ---
Its all srt files from opensubtitle. 

It does work with a baked in subtitle, so when it is part of the mkv file. 
mpv behaves weird: It either does not manage to open a file at all, or the OSD
is not showing. 
Hnn, maybe related?

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 485644] New: Neochat: Screen shows no conversations or rooms, just spaces

2024-04-16 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485644

Bug ID: 485644
   Summary: Neochat: Screen shows no conversations or rooms, just
spaces
Classification: Applications
   Product: NeoChat
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: shaloksha...@protonmail.ch
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 168590
  --> https://bugs.kde.org/attachment.cgi?id=168590=edit
Neochat

OBSERVED RESULT
Screen shows no conversations and channels anymore

EXPECTED RESULT
Conversations and rooms are shown. 

Operating System: KaOS (2024) 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.6-1-next (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82L0
System Version: Yoga Slim 7 Carbon 14ACN6

ADDITIONAL INFORMATION

I think it had to do with the Plasma 6 update. I updated, and Neochat was still
displaying all correctly. 
After I closed and opened the app, it seems to have resulted in this issue. 
To be sure, I rebooted and still, same result. 

Running the app from command line:

```
Reading access token from the keychain for "@shalokshalom:kde.org"
quotient.main: The library is built with end-to-end encryption (E2EE)
qrc:/org/kde/neochat/qml/main.qml:250:9: QML RoomListPage: Created graphical
object was not placed in the graphics scene.
quotient.jobs.thumbnail: 500 <- GET
https://kde.modular.im/_matrix/media/v3/thumbnail/nixos.org/f4d22fb201b86281502301aea97c3c692c9ea2db
quotient.jobs.thumbnail: "GetContentThumbnailJob" status NetworkError:
Unexpected Error
quotient.jobs.thumbnail: "GetContentThumbnailJob": retry #1 in 5 s
```

And sudo journalctl -b -p err

```
Apr 16 21:48:36 cosmos kernel: ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.LPC0.EC0.OKEC], AE_NOT_FOUND (20230628/psargs-330)
Apr 16 21:48:36 cosmos kernel: ACPI Error: Aborting method \_SB.GPIO._EVT due
to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 16 21:48:42 cosmos bluetoothd[750]: Failed to load LTKs for hci0: Invalid
Parameters (0x0d)
Apr 16 21:48:42 cosmos bluetoothd[750]: Failed to load IRKs for hci0: Invalid
Parameters (0x0d)
Apr 16 21:48:45 cosmos systemd[826]:
/run/user/1000/systemd/generator.late/app-xdg\x2duser\x2ddirs\x2dupdate@autostart.service:18:
WorkingDirectory= path is not absolute, ignoring: 
Apr 16 21:48:45 cosmos bluetoothd[750]: src/gatt-database.c:database_add_chrc()
Failed to create characteristic entry in database
Apr 16 21:48:45 cosmos bluetoothd[750]:
src/gatt-database.c:database_add_service() Failed to add characteristic
Apr 16 21:48:45 cosmos bluetoothd[750]: src/gatt-database.c:database_add_app()
Failed to add service
Apr 16 21:48:45 cosmos bluetoothd[750]: src/gatt-database.c:client_ready_cb()
Failed to create GATT service entry in local database
Apr 16 21:48:46 cosmos kup-daemon[1224]: kup.daemon: "Kup is not enabled,
enable it from the system settings module. You can do that by running kcmshell5
kup"
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[Haruna] [Bug 485042] Use subtitles in same directory as the movie

2024-04-16 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=485042

--- Comment #2 from Matthias  ---
Created attachment 168596
  --> https://bugs.kde.org/attachment.cgi?id=168596=edit
Subtitle not loading

-- 
You are receiving this mail because:
You are watching all bug changes.

<    1   2   3   4   5   6   7   8   9   10   >