[kdenlive] [Bug 486114] New: Disabled "Add Title Clip" in project menu

[Tristan Grimaux]

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

Bug ID: 486114
   Summary: Disabled "Add Title Clip" in project menu
Classification: Applications
   Product: kdenlive
   Version: 24.02.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: tristangrim...@gmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Open a new Project
2. Click the Project Menu
3. Is disabled

Linux/KDE Plasma: 
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-27-generic (64-bit)
Graphics Platform: X11
Processors: 32 × 13th Gen Intel® Core™ i9-13900
Memory: 62.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2

I'm running two different versions of kdenlive: from packages and the appimage.
On both I observe two different behaviours and both have the exact same
version: 24.02.02:

The appimage allows to add a title but it has problems with the subtitle
options and it's a little unstable. so currently I'm rendering one pass with
the titles and the another pass with version from the packages.

If the version from packages opens a project saved with title clips it displays
"INVALID" over other layers

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

[kwin] [Bug 411094] New windows on the secondary display incorrectly maximized to height of the primary display

[Tristan Miller]

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

--- Comment #7 from Tristan Miller  ---
Still reproducible for me with KWin 6.0.3.1 when using X11.  The problem is not
reproducible when using Wayland (though I can't use Wayland for day-to-day work
due to its various other bugs and missing features).

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

[okular] [Bug 484562] Bad rendering of EPS embedded in DVI at certain zoom levels

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

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

--- Comment #7 from Tristan Miller  ---
Info provided in Comment 5.

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

[okular] [Bug 484562] Bad rendering of EPS embedded in DVI at certain zoom levels

[Tristan Miller]

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

--- Comment #5 from Tristan Miller  ---
(In reply to Albert Astals Cid from comment #4)
> Opening that dvi file says
> 
> Couldn't find file map.pstex
> 
> Is there some magic i have to do to generate that file from the map.text you
> have attached?

If you run `latex map.tex` it will generate the file.

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

[okular] [Bug 484562] Bad rendering of EPS embedded in DVI at certain zoom levels

[Tristan Miller]

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

--- Comment #3 from Tristan Miller  ---
Created attachment 167827
  --> https://bugs.kde.org/attachment.cgi?id=167827=edit
Incorrect rendering at 200% zoom

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

[okular] [Bug 484562] Bad rendering of EPS embedded in DVI at certain zoom levels

[Tristan Miller]

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

--- Comment #2 from Tristan Miller  ---
Created attachment 167826
  --> https://bugs.kde.org/attachment.cgi?id=167826=edit
Correct rendering at 150% zoom

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

[okular] [Bug 484562] Bad rendering of EPS embedded in DVI at certain zoom levels

[Tristan Miller]

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

--- Comment #1 from Tristan Miller  ---
Created attachment 167825
  --> https://bugs.kde.org/attachment.cgi?id=167825=edit
Resulting DVI file

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

[okular] [Bug 484562] New: Bad rendering of EPS embedded in DVI at certain zoom levels

[Tristan Miller]

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

Bug ID: 484562
   Summary: Bad rendering of EPS embedded in DVI at certain zoom
levels
Classification: Applications
   Product: okular
   Version: 23.08.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: DVI backend
  Assignee: okular-de...@kde.org
  Reporter: psychon...@nothingisreal.com
  Target Milestone: ---

Created attachment 167824
  --> https://bugs.kde.org/attachment.cgi?id=167824=edit
LaTeX source file

Attached is a LaTeX file that embeds an EPS graphic.  If you compile the LaTeX
source to DVI (using `latex map.tex`) and view the DVI file in Okular, then it
looks fine when the zoom level is less than 200%, but at 200% or higher the
graphic is improperly rendered.  I attach screenshots of correct rendering at
150% zoom and incorrect rendering at 200% zoom.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12

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

[okular] [Bug 154033] incorrect DVI file rendering

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #6 from Tristan Miller  ---
Still reproducible for me with 23.08.4.

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

[plasmashell] [Bug 476351] Ability to manually colorize/mark/highlight a task

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=480637
 CC||psychon...@nothingisreal.co
   ||m

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

[plasmashell] [Bug 480637] Group and/or mark tasks according to screen

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=476351

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

[plasmashell] [Bug 480637] New: Group and/or mark tasks according to screen

[Tristan Miller]

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

Bug ID: 480637
   Summary: Group and/or mark tasks according to screen
Classification: Plasma
   Product: plasmashell
   Version: 5.27.10
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: psychon...@nothingisreal.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

I have a multi-monitor setup where only one of my screens has a panel with a
task manager.

It would be nice if the task manager provided an option to group tasks
according to what screen they are on.

It would also be nice if the task manager provided an option to somehow mark
tasks (for example, with a different background colour) according to what
screen they are on.  This way the user can see at a glance what task a screen
is on, even if the user has decided to group the tasks according to some other
criterion.

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

[okular] [Bug 478542] Show Signatures Panel should open the sidebar if it is not already visible

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[okular] [Bug 478542] New: Show Signatures Panel should open the sidebar if it is not already visible

[Tristan Miller]

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

Bug ID: 478542
   Summary: Show Signatures Panel should open the sidebar if it is
not already visible
Classification: Applications
   Product: okular
   Version: 23.08.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: psychon...@nothingisreal.com
  Target Milestone: ---

Created attachment 164183
  --> https://bugs.kde.org/attachment.cgi?id=164183=edit
A signed blank document showing the bug

When opening a digitally signed document, Okular displays a "Show Signatures
Panel" button between the toolbar and the top of the document.  If the sidebar
happens to be visible already, then pressing this button shows the signatures
panel.  But if the sidebar is not already visible, then pressing the button
causes the sidebar button in the toolbar to activate, but the sidebar itself
does not appear.


STEPS TO REPRODUCE
1. Make sure the sidebar is hidden.
2. Open any signed document, such as the attached PDF.
3. Press the "Show Signatures Panel" button.

OBSERVED RESULT
4. The "Show Sidebar" button in the toolbar activates, but the sidebar itself
does not appear.

EXPECTED RESULT
4. The "Show Sidebar" button in the toolbar should activate and the sidebar
itself should appear, with the signatures panel active.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11

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

[okular] [Bug 478540] New: Can't edit form field after entering invalid character

[Tristan Miller]

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

Bug ID: 478540
   Summary: Can't edit form field after entering invalid character
Classification: Applications
   Product: okular
   Version: 23.08.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: psychon...@nothingisreal.com
  Target Milestone: ---

Created attachment 164181
  --> https://bugs.kde.org/attachment.cgi?id=164181=edit
Example PDF showing the bug

Some PDF form fields require data in a certain format, and apply some sort of
validation to enforce this requirement. A common example are fields requiring a
telephone number. A problem with Okular is that if the user starts to type
invalid data into such a field, it is no longer possible for the user to edit
or delete the data.  I'm not sure if this is a problem with Okular itself (or
its underlying PDF library) or with how the form designer implemented their
field validation mechanism.  But even if it's the form designer's fault, it
would be nice if Okular could provide some way of overriding the validation and
allowing the user to delete the contents of the field.

This issue happens very often with forms that ask for a phone number and
require only numeric data (but don't tell the user this on the form itself). 
If one starts typing "+" as the prefix for the country code, the field refuses
to accept any further input, and it's also not possible to remove the "+" using
backspace, delete, undo, etc.  The only thing one can do is reload the form and
start filling it in all over again.

STEPS TO REPRODUCE
1. Open the attached PDF.
2. Press the "Show Forms" button.
3. Click on the field for the home phone number.  This field expects a
nine-digit phone number.
4. Type any character other than a digit, such as "+".

OBSERVED RESULT
5. At this point, the field largely stops responding to user input.  No further
data can be typed.  Pressing backspace has no effect. The Undo command has no
effect. Pressing the left cursor key puts the insertion point to the left of
the +, but pressing delete has no effect.  The + can be selected with the
mouse, but it cannot be deleted with backspace, delete, or the Cut command.

EXPECTED RESULT
5. Okular should allow the contents of the field to be edited, or at least the
Undo command should reset the field to its previously blank state.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11

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

[okular] [Bug 478540] Can't edit form field after entering invalid character

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[plasmashell] [Bug 475266] Plasma crash after launching Firefox from Task Manager, Asahi Linux

[Tristan Busch]

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

--- Comment #5 from Tristan Busch  ---
Created attachment 162118
  --> https://bugs.kde.org/attachment.cgi?id=162118=edit
The firefox desktop file

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

[plasmashell] [Bug 475266] Plasma crash after launching Firefox from Task Manager, Asahi Linux

[Tristan Busch]

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

--- Comment #4 from Tristan Busch  ---
I have added my desktop file to the attachments. There are, however, two other
firefox desktop files in my /usr/share/applications ending in »-wayland« and
»-x11« which have appeared in my program list since the update and which
weren't there before.

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

[plasmashell] [Bug 475266] Plasma crash after launching Firefox from Task Manager, Asahi Linux

[Tristan Busch]

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

Tristan Busch  changed:

   What|Removed |Added

 CC||xlkil...@gmail.com

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

[kwin] [Bug 411094] New windows on the secondary display incorrectly maximized to height of the primary display

[Tristan Miller]

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

--- Comment #5 from Tristan Miller  ---
(In reply to Nate Graham from comment #4)
> *** This bug has been marked as a duplicate of bug 461142 ***

Are you sure about this, Nate?  That bug, and its other duplicates, all report
that manually maximizing a window results in an incorrect window size.  With my
bug, manually maximizing a window works fine.  It's only the window manager's
initial placement of new windows that's broken.  (In fact, the workaround to my
bug is to manually maximize the window.)

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

[kwin] [Bug 411094] New windows on the secondary display incorrectly maximized to height of the primary display

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
Version|5.16.4  |5.27.6
 Resolution|UNMAINTAINED|---
 Ever confirmed|0   |1

--- Comment #3 from Tristan Miller  ---
Still reproducible with 5.27.6.

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

[plasma-nm] [Bug 470959] New: Automatically open browser to log in to a network

[Tristan Miller]

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

Bug ID: 470959
   Summary: Automatically open browser to log in to a network
Classification: Plasma
   Product: plasma-nm
   Version: 5.27.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: psychon...@nothingisreal.com
  Target Milestone: ---

When plasma-nm connects to a network and detects that there is no Internet
access, it emits a notification to the effect that the user needs to log in to
the network.

Rather than simply informing the user of the need to log in, please add a
configuration option (either global or for each network) that, when enabled,
will also cause plasma-nm to automatically open the system default web browser
to http://networkcheck.kde.org/, without the user needing to click on anything
first.  This will save some time, especially for users that very frequently
connect to networks requiring such logins.

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

[kwin] [Bug 427571] Windows sometimes open in an offscreen area with multiple monitors

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||psychon...@nothingisreal.co
   ||m
 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---

--- Comment #6 from Tristan Miller  ---
Reopening this bug as I'm able to consistently reproduce this behaviour.  I
have two identical monitors (Samsung Syncmaster H9XS317491), one of which is
rotated 90 degrees.  Almost every new window that appears on the unrotated
monitor appears partially offscreen.

I'm running the following:

Operating System: openSUSE Tumbleweed 20230308
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.2.1-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

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

[kwalletmanager] [Bug 400928] after boot, WiFi authorization does not launch kwallet password request on first connect, does on second try

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[plasmashell] [Bug 466566] Kickoff button too large with super thick panel

[Tristan Miller]

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

--- Comment #4 from Tristan Miller  ---
(In reply to Nate Graham from comment #2)
> Sorry, this is the new design goal, as making some buttons mysteriously
> remain rectangles for no clear reason confused the heck out of a lot of
> people and we go no end of bug reports about it.

I suspect the new behaviour is also going to confuse the heck out of a similar
number of people, and you'll get no end of bug reports about it (as evidenced
by my own duplicate Bug 467004).  If there are legitimate use cases for both
sizing policies, why not make the sizing policy user-configurable in the
Appearance module of the Application Launcher Settings dialog?

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

[plasmashell] [Bug 464971] Kickoff gets extra top/bottom paddings in a vertical panel

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=467004

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

[plasmashell] [Bug 467004] Application Launcher icon ridiculously large in vertical panel

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=464971

--- Comment #1 from Tristan Miller  ---
Is this bug perhaps a consequence of either of the following recent commits?

* applets/kickoff: fix: height larger than previous version in vertical panel:
https://github.com/KDE/plasma-desktop/commit/1988f0756ec9b61d6eff6eae14c1023502d7f701
* [kicker, kickoff] Port away from panel icon size hint:
https://github.com/KDE/plasma-desktop/commit/277758af8c3f701c92f0b77aa8ecfc8d07ab9ac9

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

[plasmashell] [Bug 414153] Application Launcher/Menu icon size probably shouldn't be dictated by your icon theme.

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=467004

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

[plasmashell] [Bug 467004] Application Launcher icon ridiculously large in vertical panel

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=414153

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

[plasmashell] [Bug 467004] New: Application Launcher icon ridiculously large in vertical panel

[Tristan Miller]

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

Bug ID: 467004
   Summary: Application Launcher icon ridiculously large in
vertical panel
Classification: Plasma
   Product: plasmashell
   Version: 5.27.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: psychon...@nothingisreal.com
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

Created attachment 157081
  --> https://bugs.kde.org/attachment.cgi?id=157081=edit
Screenshot showing ridiculously large Application Launcher icon

I upgraded today from Plasma 5.26.5 to 5.27.2.  The Application Launcher icon
in my vertical panel now takes up the full width of the panel, whereas before
the upgrade it was only a few dozen pixels wide.  The new size is far too large
-- see attached screenshot.

STEPS TO REPRODUCE
1. Add a vertical panel with a width of, say, 256 pixels.
2. Add the Application Launcher to the panel.

OBSERVED RESULT
1. The Application Launcher icon is ridiculously large, spanning the full width
of the panel, and taking up too much vertical space.

EXPECTED RESULT
1. The Application Launcher icon should be the same size as the application
icons it contains.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.27.2
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[kwin] [Bug 252314] Emacs window resizes whenever a buffer is closed (openSUSE 11.3)

[Tristan Miller]

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

--- Comment #48 from Tristan Miller  ---
Problem is still reproducible with openSUSE 15.4 with Emacs 28.2 and Plasma
5.24.4.  (And the workaround from Comment 37 still works.)

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

[plasmashell] [Bug 393957] Horizontal layout option for horizontal panels

[Tristan Miller]

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

--- Comment #19 from Tristan Miller  ---
(In reply to Nate Graham from comment #18)
> Well that's the problem. :) This option is only present on horizontal
> panels, because generally vertical panels are too narrow to be able to show
> the time and date on the same line without the text becoming unreadably
> small. I gather you have an extremely wide panel such that everything might
> actually fit?

Yes, I've got a wide monitor and a correspondingly wide panel.  I wouldn't call
it "extremely" wide, but it's certainly wide enough to fit an ISO date and time
on one line.

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

[plasmashell] [Bug 393957] Horizontal layout option for horizontal panels

[Tristan Miller]

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

--- Comment #17 from Tristan Miller  ---
(In reply to Nate Graham from comment #16)
> Is the clock located on a horizontal panel or a vertical panel?

It's on a vertical panel, as can be seen in the screenshot.  I want the date
and time to appear beside to each other so as to save vertical space.

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

[plasmashell] [Bug 393957] Horizontal layout option for horizontal panels

[Tristan Miller]

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

--- Comment #15 from Tristan Miller  ---
Created attachment 155024
  --> https://bugs.kde.org/attachment.cgi?id=155024=edit
Screenshot showing digital clock settings

(In reply to Nate Graham from comment #14)
> It's the first thing in the settings window:
> 
> Information: [x] Show date [adaptive location]

Not on my system -- see the attached screenshot.  Am I missing something here?

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

[plasmashell] [Bug 393957] Horizontal layout option for horizontal panels

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #13 from Tristan Miller  ---
(In reply to Nate Graham from comment #12)
> Git commit cd68df165a9360e6c0f94b7f7c0c7ebb04df370a by Nate Graham, on
> behalf of Momo Cao.
> Committed on 26/03/2021 at 04:56.
> Pushed by ngraham into branch 'master'.
> 
> Add a setting to show date and time in one line
> FIXED-IN: 5.22
> 
> M  +8-0applets/digital-clock/package/contents/config/main.xml
> M  +7-13   applets/digital-clock/package/contents/ui/DigitalClock.qml
> M  +20   -4applets/digital-clock/package/contents/ui/configAppearance.qml
> 
> https://invent.kde.org/plasma/plasma-workspace/commit/
> cd68df165a9360e6c0f94b7f7c0c7ebb04df370a

Did this fix ever make it into a stable release?  I'm running Plasma 5.26.4.1
on openSUSE Tumbleweed.  The Digital Clock applet shows a version of 3.0 in the
"About" section of the settings.  I see no setting to have the time and date
beside vs. on top of one another.

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

[k3b] [Bug 269485] References to CDDB are inaccurate and misleading; should be replaced

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #5 from Tristan Miller  ---
I've tested with K3B 22.08.3; it seems references to CDDB have been replaced
with "CD Database".  I'm tentatively marking this issue as resolved, but if I
overlooked any stray occurrences of "CDDB", please indicate exactly where they
are and reopen this bug.

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

[k3b] [Bug 282168] Enable freedb lookup/Query CDDB mismatch

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

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

--- Comment #4 from Tristan Miller  ---
Confirming that the problem still exists with K3b 22.08.3.

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

[kteatime] [Bug 394855] hides itself too well

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 CC||psychon...@nothingisreal.co
   ||m
 Status|NEEDSINFO   |REPORTED

--- Comment #3 from Tristan Miller  ---
Confirming that this is still an issue with KTeaTime 22.12.0.  No dialog
appears when starting KTeaTime for the very first time.

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

[plasmashell] [Bug 461983] Show Hidden Icons button wastefully takes up an entire row in a vertical panel

[Tristan Miller]

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

--- Comment #1 from Tristan Miller  ---
> This way, it can appear to the left of the application icons

Sorry, I meant to write here "to the right of the application icons".

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

[plasmashell] [Bug 461983] New: Show Hidden Icons button wastefully takes up an entire row in a vertical panel

[Tristan Miller]

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

Bug ID: 461983
   Summary: Show Hidden Icons button wastefully takes up an entire
row in a vertical panel
Classification: Plasma
   Product: plasmashell
   Version: 5.26.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: psychon...@nothingisreal.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Created attachment 153856
  --> https://bugs.kde.org/attachment.cgi?id=153856=edit
Screenshot showing system tray in a vertical panel

When the System Tray widget is placed in a vertical panel, the "Show Hidden
Icons" button always appears all by itself of its own row, thus wasting
vertical space in the panel.  (See attached screenshot.)  Please change how
this button is treated for the purposes of layout: it would be better if it
were treated is a normal application icon, except that it should always appear
last in the list.  This way, it can appear to the left of the application icons
(if there is space on the row) rather than below them in a row by itself.

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

[KScreen] [Bug 407519] Primary display setting does not persist

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Tristan Miller  ---
I still have the same monitor setup and have just retested.  The issue is no
longer reproducible with Plasma 5.26.3.

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

[plasmashell] [Bug 458536] New: Plasma crash after plugging in external screen (Wayland)

[Tristan Lins]

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

Bug ID: 458536
   Summary: Plasma crash after plugging in external screen
(Wayland)
   Product: plasmashell
   Version: 5.25.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: tris...@lins.io
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.25.4)

Qt Version: 5.15.5
Frameworks Version: 5.97.0
Operating System: Linux 5.15.0-46-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
After plugging in the external screen, plasma crashed randomly.
Especially when plugged in / removed the external, while in StandBy and then
wake up, plasma crashed every time.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[New LWP 3329]
[New LWP 3330]
[New LWP 3342]
[New LWP 3472]
[New LWP 3514]
[New LWP 3515]
[New LWP 3516]
[New LWP 3517]
[New LWP 3518]
[New LWP 3519]
[New LWP 3520]
[New LWP 3521]
[New LWP 3522]
[New LWP 3523]
[New LWP 3524]
[New LWP 3525]
[New LWP 3526]
[New LWP 3527]
[New LWP 3528]
[New LWP 3529]
[New LWP 3530]
[New LWP 3531]
[New LWP 3532]
[New LWP 3624]
[New LWP 3642]
[New LWP 3643]
[New LWP 3644]
[New LWP 3749]
[New LWP 3919]
[New LWP 3920]
[New LWP 3921]
[New LWP 3922]
[New LWP 3923]
[New LWP 3924]
[New LWP 4397]
[New LWP 4398]
[New LWP 4399]
[New LWP 9599]
[New LWP 13435]
[New LWP 13436]
[New LWP 13437]
[New LWP 13462]
[New LWP 13463]
[New LWP 13464]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f97af35199f in __GI___poll (fds=0x7ffc261b3b78, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f97ab4729c0 (LWP 3299))]

Thread 45 (Thread 0x7f96a97fa700 (LWP 13464)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5610779da0b0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5610779da060,
cond=0x5610779da088) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5610779da088, mutex=0x5610779da060) at
pthread_cond_wait.c:647
#3  0x7f97af6e75fb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f97b13822f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f97b1382769 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f97af6e1553 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f97af074609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f97af35e133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 44 (Thread 0x7f96aa7fc700 (LWP 13463)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x561079348950) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561079348900,
cond=0x561079348928) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x561079348928, mutex=0x561079348900) at
pthread_cond_wait.c:647
#3  0x7f97996365eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f97996361eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f97af074609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f97af35e133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 43 (Thread 0x7f96aaffd700 (LWP 13462)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5610792ca310) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5610792ca2c0,
cond=0x5610792ca2e8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5610792ca2e8, mutex=0x5610792ca2c0) at
pthread_cond_wait.c:647
#3  0x7f97996365eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f97996361eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f97af074609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f97af35e133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 42 (Thread 0x7f97360a9700 (LWP 13437)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x7f97a0013c10) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f97a0013bc0,
cond=0x7f97a0013be8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7f97a0013be8, mutex=0x7f97a0013bc0) at
pthread_cond_wait.c:647
#3  0x7f97af6e75fb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f97b13822f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  

[systemsettings] [Bug 374971] On Wayland previewing designs of tabbox doesn't clean them up afterwards

[Tristan Busch]

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

Tristan Busch  changed:

   What|Removed |Added

 CC||xlkil...@gmail.com

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

[kwin] [Bug 445151] New: "Add Property…" button in settings dialog not initially visible

[Tristan Miller]

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

Bug ID: 445151
   Summary: "Add Property…" button in settings dialog not
initially visible
   Product: kwin
   Version: 5.22.5
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: psychon...@nothingisreal.com
CC: isma...@gmail.com
  Target Milestone: ---

In the "Edit Application-Specific Settings" and "Edit Window-Specific Settings"
dialog, before any rules have been added, the following message appears in the
bottom of the dialog:

No window properties changed
Click the Add Property… button below to add some window properties that will be
affected by the rule

However, there is no such button visible in the dialog.  The only buttons
visible are "Reset", "OK", "Apply", and "Cancel".  It's only if you resize the
dialog (or even just start to resize it, such as by dragging the window edge)
that the "Add Property…" button, along with the "Detect Window Properties"
button and the time input, appears.  This doesn't appear to be a case of the
dialog being initially too small to contain the extra buttons, since resizing
it even just one pixel (or even making the dialog smaller) causes the extra
buttons to suddenly appear.

Steps to reproduce:

1. Right-click on the title bar of a window/application for which no special
window/application settings have yet been defined.
2. In the context menu that appears, select "Configure Special Window Settings"
or "Configure Special Application Settings" from the "More actions" cascading
menu.
3. Resize the settings dialog by maximizing it or by dragging the window
border.

Observed behaviour:
2a. A settings dialog appears with a message referring to an "Add property…"
button, but no such button is visible.
3a. The "Add property…" button suddenly pops into view.

Expected behaviour:
2a. A settings dialog appears with a message referring to an "Add property…"
button, and this button is visible.

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

[kwin] [Bug 187539] Special Application Settings not remembered

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #31 from Tristan Miller  ---
No longer reproducible for me with Plasma 5.22.5.  I followed the steps in my
Comment 9 (modulo some changes to the UI in the last ten years) and the
settings now persist as expected.

I'm tentatively marking this issue as RESOLVED/WORKSFORME but of course if
anyone else can still reproduce this, the bug should probably be reopened.

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

[kwin] [Bug 443340] slow redraw/flicker with Intel graphics

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[systemsettings] [Bug 444258] New: Applying a window decoration using the GetNewStuff Dialogue does not activate the "Apply" button of the kcm

[Tristan Busch]

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

Bug ID: 444258
   Summary: Applying a window decoration using the GetNewStuff
Dialogue does not activate the "Apply" button of the
kcm
   Product: systemsettings
   Version: 5.22.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwindecoration
  Assignee: kwin-bugs-n...@kde.org
  Reporter: xlkil...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
When a new window decoration is applied using the GetNewStuff dialogue and the
dialogue is then closed, the previously selected decoration can not be applied,
even though it is no longer the one currently used.

STEPS TO REPRODUCE
1. Select/highlight the currently used window decoration
2. Download and apply a new one using the GetNewStuff dialogue
3. Try to apply the previously used decoration

OBSERVED RESULT
The previously used decoration can not be applied, as the kcm might not have
been informed about the decoration change. To apply it, any other decoration
(even the already applied one) has to be applied first.

EXPECTED RESULT
It should be possible to reapply the previous decoration immediately.

SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.13-200

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

[i18n] [Bug 443391] Bluetooth Tray Tooltip (2)

[Tristan Busch]

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

Tristan Busch  changed:

   What|Removed |Added

 Attachment #142206|Screenshot des tooltips |Screenshot of the tooltips
description||

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

[i18n] [Bug 443391] New: Bluetooth Tray Tooltip (2)

[Tristan Busch]

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

Bug ID: 443391
   Summary: Bluetooth Tray Tooltip (2)
   Product: i18n
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: de
  Assignee: kde-i18n...@kde.org
  Reporter: xlkil...@gmail.com
  Target Milestone: ---

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

If no Bluetooth devices are connected, it should actually say "Keine
verbundenen Geräte" and not "Keine verbundene Geräte".

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

[Skanlite] [Bug 369007] Greyscale images saved as colour

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from Tristan Miller  ---
Yes, the problem seems to be fixed in 21.08.

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

[Skanlite] [Bug 369007] Greyscale images saved as colour

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

--- Comment #4 from Tristan Miller  ---
Yes, this problem is still reproducible with Skanlite 2.2.0.0.  (Sorry for the
delay in responding.)

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

[kwin] [Bug 419227] Can't resize windows (often but not always those run over NX (X2Go))

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

Summary|Can't resize windows run|Can't resize windows (often
   |over NX (X2Go)  |but not always those run
   ||over NX (X2Go))

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

[kwin] [Bug 419227] Can't resize windows run over NX (X2Go)

[Tristan Miller]

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

--- Comment #6 from Tristan Miller  ---
On further testing, the problem sometimes happens with windows of locally
running applications, when X2Go isn't even running.  (For example, I'm
currently experiencing the bug with a local konsole window.)  So this is likely
a kwin problem that has nothing to do with X2Go; it's just that the problem is
more consistently reproducible with windows running over X2Go.

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

[KScreen] [Bug 440240] New: i18n [German] OSD of night color toggle in system tray

[Tristan Busch]

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

Bug ID: 440240
   Summary: i18n [German] OSD of night color toggle in system tray
   Product: KScreen
   Version: 5.22.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: xlkil...@gmail.com
  Target Milestone: ---

Created attachment 140310
  --> https://bugs.kde.org/attachment.cgi?id=140310=edit
A screenshot of the OSD when turning night colors on

SUMMARY
The on-screen display when toggling night colors on using the system tray
toggle has a wrong translation string.

Instead of "Nachfarben" it should say "Nachtfarben".


SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Feel free to move this wherever you please. I have no idea how i18n issues
should be reported otherwise.

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

[Bluedevil] [Bug 440239] New: i18n [German] Bluetooth Tray Tooltip

[Tristan Busch]

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

Bug ID: 440239
   Summary: i18n [German] Bluetooth Tray Tooltip
   Product: Bluedevil
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: xlkil...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 140309
  --> https://bugs.kde.org/attachment.cgi?id=140309=edit
Screenshot of the tooltip

SUMMARY
Translation string of the tool tip (Mouse hover on Bluetooth entry in System
Tray) is incorrect. 

It should say "verbunden" instead of "verbundenen".

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

Feel free to move this wherever you like. I have no idea how i18n issues should
be reported otherwise.

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

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[Spectacle] [Bug 437776] Spectacle crashes when closing

[Tristan Busch]

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

--- Comment #1 from Tristan Busch  ---
Created attachment 138840
  --> https://bugs.kde.org/attachment.cgi?id=138840=edit
New crash information added by DrKonqi

spectacle (20.12.2) using Qt 5.15.2

- What I was doing when the application crashed:

Closing Spectacle caused the crash. The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  0x7faeaece3205 in kImageAnnotator::FontPicker::~FontPicker() () from
/lib64/libkImageAnnotator.so.0
#5  0x7faeaeca8105 in
kImageAnnotator::AnnotationItemSettings::~AnnotationItemSettings() () from
/lib64/libkImageAnnotator.so.0
#6  0x7faeaeca84a2 in
kImageAnnotator::AnnotationWidget::~AnnotationWidget() () from
/lib64/libkImageAnnotator.so.0
#7  0x7faeaec9e61b in kImageAnnotator::CoreView::~CoreView() () from
/lib64/libkImageAnnotator.so.0
#8  0x7faeaeca0c7d in kImageAnnotator::KImageAnnotator::~KImageAnnotator()
() from /lib64/libkImageAnnotator.so.0

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

[Spectacle] [Bug 437776] Spectacle crashes when closing

[Tristan Busch]

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

Tristan Busch  changed:

   What|Removed |Added

 CC||xlkil...@gmail.com

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

[plasmashell] [Bug 436502] New: [PipeWire] Audio icon displayed next to every program except program playing audio

[Tristan Busch]

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

Bug ID: 436502
   Summary: [PipeWire] Audio icon displayed next to every program
except program playing audio
   Product: plasmashell
   Version: 5.21.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: xlkil...@gmail.com
  Target Milestone: 1.0

Created attachment 138097
  --> https://bugs.kde.org/attachment.cgi?id=138097=edit
Screenshot of audio icons

SUMMARY
After a while of playing audio, the icons are displayed next to every app icon
except the one playing audio and the ones, which programs are opened (on that
virtual desktop).

STEPS TO REPRODUCE
1. Play audio from any program
2. Wait
3. 

OBSERVED RESULT
False icon positioning; clicking the icon still works and changes the visual
state for all icons.

EXPECTED RESULT
Icon should be at correct position.

SOFTWARE/OS VERSIONS

X11
Linux/KDE Plasma: Fedora 34 (5.10.33)
(available in About System)
KDE Plasma Version: 5.21.4 
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

PipeWire: 0.3.26

ADDITIONAL INFORMATION

Maybe related to 375943?

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

[systemsettings] [Bug 435154] kwin_killer_helper is started when systemd action is executed in systemsettings5 and user is trying to interact with the window

[Tristan Busch]

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

--- Comment #2 from Tristan Busch  ---
(In reply to David Redondo from comment #1)
> Sounds like it's blocking somewhere? Is that shipped by us?

It seems that this might be part of Fedora, though I can't track it down
exactly.
Will file a bug at redhat.bugzilla.com though.

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

[systemsettings] [Bug 435154] New: kwin_killer_helper is started when systemd action is executed in systemsettings5 and user is trying to interact with the window

[Tristan Busch]

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

Bug ID: 435154
   Summary: kwin_killer_helper is started when systemd action is
executed in systemsettings5 and user is trying to
interact with the window
   Product: systemsettings
   Version: 5.20.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: xlkil...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Open systemd entry in systemsettings
2. Do any systemd action
3. Interact with the window (switching settings entry, trying to close the
window)

OBSERVED RESULT
Window is greyscaled and kwin_killer_helper is started after systemd task has
completed

EXPECTED RESULT
Add a visual feedback that something is happening when a systemd task/action is
executed or running.
As systemsettings isn't actually hanging an option to kill it should not be
offered. If possible, the systemsettings window should remain responsive during
the task.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 33 5.10.24-200.fc33.x86_64
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

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

[plasma-nm] [Bug 435152] New: Enabling Hotspot via applet causes kernel problems and firmware error

[Tristan Busch]

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

Bug ID: 435152
   Summary: Enabling Hotspot via applet causes kernel problems and
firmware error
   Product: plasma-nm
   Version: 5.20.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: xlkil...@gmail.com
  Target Milestone: ---

Created attachment 137180
  --> https://bugs.kde.org/attachment.cgi?id=137180=edit
Output from journalctl

STEPS TO REPRODUCE
1. Disconnect from Wifi, no other connections
2. Choose Hotspot from applet

OBSERVED RESULT
All wifi AP entries vanish from applet, network card is not responding, no
hotspot is created

EXPECTED RESULT
Hotspot is created
SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Fedora 33 5.10.24-200.fc33.x86_64
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Attached are Screenshots from journald.
Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 3e)

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

[plasmashell] [Bug 406882] Popup plasmoids flicker and disappear when a remote application (via X2Go) is in focus

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from Tristan Miller  ---
The problem is no longer reproducible for me.  I'm now using the following:

KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
OS: openSUSE Tumbleweed
x2goclient: 4.1.2.3~git21+ga1a2f62

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

[konqueror] [Bug 115851] Konqueror does not support Mozilla's 'Kitchen Sink' (page displayed incorrectly)

[Tristan Miller]

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

--- Comment #11 from Tristan Miller  ---
(In reply to Justin Zobel from comment #10)
> As this report hasn't seen any changes in 10 years or more, we ask if you
> can please confirm that the issue still persists.

I think you may have overlooked comment #9.

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

[ark] [Bug 104404] Support for file type ARJ

[Tristan Miller]

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

--- Comment #14 from Tristan Miller  ---
(In reply to Higa from comment #13)
> If an ARJ archive has folders, it is likely affected by the unarchiver bug.

Then I think you ought to have said that the bug affects paths containing a
slash, not filenames containing a slash.  The former is exceedingly common and
the latter exceedingly uncommon.

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

[systemsettings] [Bug 391471] Application Preference Order not updated when adding an application by path

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Tristan Miller  ---
(In reply to Justin Zobel from comment #1)
> Can you please check and confirm and advise, thank you.


You're right; I can no longer reproduce the bug with systemsettings 5.21.1.

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

[ark] [Bug 104404] Support for file type ARJ

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #11 from Tristan Miller  ---
(In reply to Higa from comment #10)
> Unarchiver has a bug [1] which prevents correct decompression of arj
> archives which contain filenames with slashes, so I have submitted a request
> to revert my commit earlier.

So why reopen this bug report instead of opening a new one for that particular
edge case?  Surely the commit you submitted will add functionality that works
with 99.9+% of ARJ archives, and so it would be better to keep it in place
pending a fix for the bug.

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

[plasmashell] [Bug 413394] An option to set font size

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #3 from Tristan Miller  ---
(In reply to alex285 from comment #0)
> Created attachment 123457 [details]
> a screen with the issue
> 
> Digital clock Applet it is super huge even when we set the date (which btw i
> believe it should be a default option), and while there is an option to
> change the font, there is not an option to change the size

I liked the super-huge time display because it was easy to read.  After
updating Plasma today on my openSUSE Tumbleweed installation, I find that the
time is now displayed in a small font (the same size as the date) and so no
longer so easy to see at a distance.

It would be great if this change to the default styling could be reverted, or
else for this feature request about setting the font size be implemented.

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

[plasmashell] [Bug 430390] Panel has black edge when compositor is disabled

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[plasmashell] [Bug 388477] Plasma crashes when activating the Application Launcher

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #11 from Tristan Miller  ---
I've no longer been able to reproduce this problem for a while now -- I'm
currently using Plasma 5.20.3.

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

[kscreenlocker] [Bug 408493] Desktop briefly visible before lock screen appears

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

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

--- Comment #8 from Tristan Miller  ---
Clearing the needinfo flag as I assume this was due to my mistaken comment.

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

[kscreenlocker] [Bug 408493] Desktop briefly visible before lock screen appears

[Tristan Miller]

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

--- Comment #6 from Tristan Miller  ---
(In reply to Tristan Miller from comment #4)
> I recently changed from the ancient X.Org xf86-video-intel driver
> to the standard modesetting driver, per Bug 395583 Comment 20, and now I am
> no longer experiencing this issue.

Scratch that; I'm now continuing to see the behaviour again, even with the
modesetting driver.  Maybe it happens less often, but it still does happen
occasionally.

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

[frameworks-kwidgetsaddons] [Bug 427141] Unify prompt formatting of KPasswordDialog and KNewPasswordDialog

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

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

--- Comment #2 from Tristan Miller  ---
Well, let me explain how this report arose.

KDialog is more or less a wrapper for the dialog APIs of
frameworks-kwidgetsaddons. With the current Git master of KDialog, invoking

kdialog --newpassword foo\\nbar

results in a new password dialog that says

foo
bar

but invoking it as

kdialog --password foo\\nbar

results in a password dialog that says

foo bar

That is, in one case the newline is being converted to a space and in the other
it is not.  The desired behaviour (at least from KDialog's point of view) is to
preserve the newline.

Since the KDialog code for handling the --password and --newpassword options is
pretty much the same, except that one invokes a KPasswordDialog and the other
invokes a KNewPasswordDialog, I assume that the discrepancy in behaviour lies
in frameworks-kdewidgetsaddons.  From reading its source, I see that the
setPrompt() function on line 291 of kpassworddialog.cpp invokes
d->ui.prompt->setWordWrap(true), whereas the setPrompt() function on line 264
of knewpassworddialog.cpp does not.  I had assumed that this was the cause of
the problem, but did not test this by changing and building the code myself.

If this isn't the cause of the problem, then the cause must lie elsewhere,
though I'm still pretty sure it's in frameworks-kdewidgetsaddons and not
KDialog.

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

[kwin] [Bug 419227] Can't resize windows run over NX (X2Go)

[Tristan Miller]

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

--- Comment #3 from Tristan Miller  ---
The problem is still reproducible with kwin 5.19.5.  Would any kwin developer
like to take a look at this in the near future?  I gather that Ulrich (one of
the nx-libs developers) is eager to collaborate on a solution, and I'm also
available to test patches.

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

[plasmashell] [Bug 395730] Calendar doesn't appear on second virtual desktop

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Tristan Miller  ---
I tested again on Plasma 5.19.5 and it's working for me now.

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

[kscreenlocker] [Bug 408493] Desktop briefly visible before lock screen appears

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #4 from Tristan Miller  ---
(In reply to Martin Flöser from comment #1)
> Most likely a graphics driver failure. The infrastructure ensures to lock
> prior to suspend.

I agree -- I recently changed from the ancient X.Org xf86-video-intel driver to
the standard modesetting driver, per Bug 395583 Comment 20, and now I am no
longer experiencing this issue.

Anyone who is still experiencing this issue, please check if you are using the
xf86-video-intel driver, and if so, try switching to the modesetting driver
instead.  (Or conversely, if you are using the modesetting driver on a very old
Intel graphics controller, try changing to xf86-video-intel.)

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

[plasmashell] [Bug 393956] Digital Clock widget add custom time format

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[kdialog] [Bug 352981] Newline \n does not work with --inputbox

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/util
   ||ities/kdialog/commit/3a34c7
   ||61a0ef28d8ae1028caae82ead20
   ||59a079b

--- Comment #7 from Tristan Miller  ---
Git commit 3a34c761a0ef28d8ae1028caae82ead2059a079b by Tristan Miller.
Committed on 12/10/2020 at 13:59.
Pushed by sitter into branch 'master'.

make \n work with (img)inputbox and (new)password

Note that \n in password prompts are converted to spaces due to
bug#427141.

M  +6-4src/kdialog.cpp

https://invent.kde.org/utilities/kdialog/commit/3a34c761a0ef28d8ae1028caae82ead2059a079b

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

[kdialog] [Bug 427415] --menu, --radiolist, and --checklist show incorrect usage instructions

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

Summary|--menu dialog shows |--menu, --radiolist, and
   |incorrect usage |--checklist show incorrect
   |instructions|usage instructions

--- Comment #1 from Tristan Miller  ---
A similar problem exists with the usage instructions for --radiolist and with
--checklist (which is also missing the ellipsis to indicate that last set of
arguments may be repeated).

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

[kdialog] [Bug 427414] --slider dialog needs documentation and usage instructions

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Blocks||427415


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=427415
[Bug 427415] --menu dialog shows incorrect usage instructions
-- 
You are receiving this mail because:
You are watching all bug changes.

[kdialog] [Bug 427415] --menu dialog shows incorrect usage instructions

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Depends on|427414  |


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=427414
[Bug 427414] --slider dialog needs documentation and usage instructions
-- 
You are receiving this mail because:
You are watching all bug changes.

[kdialog] [Bug 427414] --slider dialog needs documentation and usage instructions

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Blocks|427415  |


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=427415
[Bug 427415] --menu dialog shows incorrect usage instructions
-- 
You are receiving this mail because:
You are watching all bug changes.

[kdialog] [Bug 427415] New: --menu dialog shows incorrect usage instructions

[Tristan Miller]

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

Bug ID: 427415
   Summary: --menu dialog shows incorrect usage instructions
   Product: kdialog
   Version: 20.08
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: psychon...@nothingisreal.com
CC: br...@frogmouth.net
Depends on: 427414
  Target Milestone: ---

When called with the wrong number of arguments, --menu issues incorrect usage
instructions:

Syntax: --menu text [tag item] [tag item] ...

Since this dialog type requires at least one tag and item, the instructions
should actually be as follows:

Syntax: --menu text tag item [tag item] ...


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=427414
[Bug 427414] --slider dialog needs documentation and usage instructions
-- 
You are receiving this mail because:
You are watching all bug changes.

[kdialog] [Bug 427414] New: --slider dialog needs documentation and usage instructions

[Tristan Miller]

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

Bug ID: 427414
   Summary: --slider dialog needs documentation and usage
instructions
   Product: kdialog
   Version: 20.08
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: psychon...@nothingisreal.com
  Target Milestone: ---

Almost all of the dialog types offered by KDialog are sufficiently documented,
either in the tutorial at
,
or else in the man page, or else by emitting usage instructions on the console
when called with the wrong number of arguments.  The only exception is
--slider, which is mentioned only in the man page, but without enough
information to understand how it should be invoked.  And invoking --slider with
only one argument results in a nonsensical slider dialog rather than displaying
usage instructions.

To fix this problem, the following is required:

1. Add a section for --slider to the tutorial (probably as a subsection of
§3.7)

2. When --slider is called with fewer than two or more than four arguments,
KDialog should immediately quit with exit status 255 and the following message
should be output:

Syntax: --slider text min_value max_value increment

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

[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep

[Tristan Miller]

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

--- Comment #20 from Tristan Miller  ---
With the help of the openSUSE developers I have discovered the cause of the
lock screen freezing after resuming from suspend, at least on my computer.  The
problem was not kscreenlocker but rather a recent regression in the X.Org
xf86-video-intel driver.  This driver is known to cause issues when used with
relatively modern graphics hardware (mine is from 2015), particularly with KDE
Plasma, as detailed at
<https://community.kde.org/Plasma/5.9_Errata#Intel_GPUs>.  The solution for me
was to uninstall the xf86-video-intel driver and instead use the modesetting
driver (which is the default on most GNU/Linux distributions these days).

So any of you who are still suffering from this bug, please check if you are
using the xf86-video-intel driver, and if so, try switching to the modesetting
driver instead.  (Or conversely, if you are using the modesetting driver on a
very old Intel graphics controller, try changing to xf86-video-intel.)  If this
solution works for everyone, then the present bug report can be closed (as
INVALID or UPSTREAM or whatever is appropriate).

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

[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

   See Also||https://bugzilla.opensuse.o
   ||rg/show_bug.cgi?id=1177177

--- Comment #19 from Tristan Miller  ---
Downstream bug report for openSUSE:
https://bugzilla.opensuse.org/show_bug.cgi?id=1177177

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

[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep

[Tristan Miller]

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

--- Comment #18 from Tristan Miller  ---
Created attachment 132041
  --> https://bugs.kde.org/attachment.cgi?id=132041=edit
journalctl on an openSUSE 15.2 system

Attached is the output of journalctl on an openSUSE 15.2 system for the period
when this bug occurs for me.  Here is a high-level timeline:

08:00:16 I suspend my computer by pressing the suspend key.

08:24:29 I wake up my computer.  The login screen appears but after typing the
first couple characters of my password, the login screen becomes unresponsive.

08:24:42 I switch to tty1 and log in as root (and do the same on tty2) and then
issue a shutdown -r command.

08:26:24 The system reboots.

Perhaps something in this log indicates what the problem might be.

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

[frameworks-kwidgetsaddons] [Bug 427141] New: Unify prompt formatting of KPasswordDialog and KNewPasswordDialog

[Tristan Miller]

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

Bug ID: 427141
   Summary: Unify prompt formatting of KPasswordDialog and
KNewPasswordDialog
   Product: frameworks-kwidgetsaddons
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: psychon...@nothingisreal.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

The behaviour of KPasswordDialog::setPrompt() and
KNewPasswordDialog::setPrompt() is inconsistent with respect to how the prompt
is formatted: the former applies word wrap whereas the latter does not.  Since
both dialogs are intended for similar purposes (i.e., to enter a password), the
formatting of the prompt should be similar.  Either both prompts should apply
word wrap, or neither of them should.

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

[kdialog] [Bug 352981] Newline \n does not work with --inputbox

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

  Attachment #94749|0   |1
is obsolete||

--- Comment #6 from Tristan Miller  ---
Comment on attachment 94749
  --> https://bugs.kde.org/attachment.cgi?id=94749
Fixes Bug 352981

Patch is now obsolete due to API changes and refactoring/further development of
kdialog.cpp.

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

[kdialog] [Bug 352981] Newline \n does not work with --inputbox

[Tristan Miller]

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

--- Comment #5 from Tristan Miller  ---
The --password and --newpassword dialogs have the same problem.  Possibly
further dialogs are also affected.

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

[kdialog] [Bug 352981] Newline \n does not work with --inputbox

[Tristan Miller]

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

--- Comment #4 from Tristan Miller  ---
Problem is still reproducible with KDialog 20.08.1.

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

[konqueror] [Bug 373318] Crash on visiting https://competitions.codalab.org

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

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

--- Comment #2 from Tristan Miller  ---
No longer reproducible for me when visiting the live version of
https://competitions.codalab.org with Konqueror 20.08.1.

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

[kde] [Bug 117452] All applications should read from stdin where applicable

[Tristan Miller]

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

--- Comment #5 from Tristan Miller  ---
Nate, I appreciate all the work you have been doing lately in pinging ancient
bugs and closing the ones that are not or no longer valid, but I have to
disagree with you in this case (and in the case of Bug 117454).  KDE isn't just
a random collection of applications that behave entirely at the whim of their
developers, but rather a project to create a unified, coherent desktop
environment. This means (among other things) consistent user interface
guidelines and interoperability among applications.

The present bug is as a request for our official development guidelines
(formerly at
<http://developer.kde.org/documentation/standards/kde/style/basics/index.html>
but now at <https://techbase.kde.org/Development/Guidelines>) to codify a -
command-line option as being standard interface behaviour (where appropriate)
so that our developers are at least aware of the need for it.  Strictly
speaking, the bug is "RESOLVED->FIXED" when KDE's developer documentation is
updated, not when every KDE application in existence comes into compliance with
it.

The idea of leaving this issue open as a tracking bug was a suggestion for
coordinating UI updates among our various UI gurus and application developers. 
That is, whenever a new issue is filed for a particular application to
implement the - option, it can simply reference this one so that the reporter
doesn't need to rehash all the information presented here, and conversely those
following the tracking bug will become aware of the dependent ones and perhaps
volunteer to help fix them.  Of course, doing things this way isn't strictly
necessary, though in my experience it's a fairly common one in collaborative
free software projects.

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

[kwin] [Bug 252314] Emacs window resizes whenever a buffer is closed (openSUSE 11.3)

[Tristan Miller]

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

--- Comment #47 from Tristan Miller  ---
On further testing, I can confirm that the workaround from Comment 37 still
works.  Still, it would be nice if this weren't necessary.

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

[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #17 from Tristan Miller  ---
I have the same problem as originally reported, except that switching to a text
console and back again doesn't work around the issue.  That is, about 10% of
the time when the screen locks, the login form doesn't appear when manipulating
the mouse or keyboard.  The date and time displayed on the lock screen are
frozen, but the mouse pointer can still be moved around the screen.  Switching
to a text console works, but running htop doesn't reveal anything out of the
ordinary.  Manually running "loginctl unlock-session n" (where n is the session
number) has no effect.  Trying to force a logout using "qdbus org.kde.ksmserver
/KSMServer logout 0 0 0" seems to work after a long delay (a minute or two) in
that it looks like it shuts down the session and brings back the KDE login
screen, but when you try to log in, the panel and desktop, and many other
Plasma elements fail to appear, making the system almost unusable.

System details:

OS: openSUSE Leap 15.2 (64-bit)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.71.0
Qt Version: 5.12.7
Kernel Version: 5.3.18-lp15236-default
Hardware: Acer TravelMate B115 netbook, which has an Intel ValleyView Gen7
graphics controller driving the built-in display

I'm happy to provide further information (logs, etc.) if someone tells me what
is needed, though since the problem isn't reliably reproducible it might take
me a while.

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

[kscreenlocker] [Bug 415362] Lock after waking from sleep: a glimpse of desktop before lock screen appears.

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #2 from Tristan Miller  ---
Possible duplicate of Bug 408493.

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

[kscreenlocker] [Bug 421320] kscreenlocker does not work properly

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #1 from Tristan Miller  ---
Possible duplicate of Bug 415362.

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

[plasmashell] [Bug 384540] KDE applications segfault when XLIB_SKIP_ARGB_VISUALS is defined

[Tristan Miller]

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

--- Comment #14 from Tristan Miller  ---
I also can't reproduce this problem with openSUSE Tumbleweed.

aux...@gmail.com, openSUSE Leap 15.1 is due to be EOL'd in two months.  Perhaps
you could upgrade to 15.2 and try testing again?

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

[kwin] [Bug 252314] Emacs window resizes whenever a buffer is closed (openSUSE 11.3)

[Tristan Miller]

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

--- Comment #46 from Tristan Miller  ---
Some further details: I was not using any Special Window Settings or Special
Application Settings to force vertical maximization.  (Such settings had not
been necessary after this bug was fixed previously.)  But if I go ahead and add
a Special Application Settings entry to always force vertical maximization,
then the Emacs window shrinks anyway whenever I complete a search with Ctrl+S. 
What's worse, it's no longer possible to adjust the vertical size of the window
by dragging the window edge, and the maximize button is missing from the window
title bar.  And even worse than that, there doesn't seem to be any way of
removing the Special Applications Setting entry, since if I revisit the Special
Applications Setting dialog, the entry is no longer listed at all!

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

[kwin] [Bug 252314] Emacs window resizes whenever a buffer is closed (openSUSE 11.3)

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #45 from Tristan Miller  ---
I think we may have hit a regression, as I can now reproduce this problem.  I
am using the following on openSUSE Tumbleweed:

Emacs 27.1
KDE Plasma 5.19.4
KDE Frameworks 5.73.0
Qt 5.15.0

An easy way to reproduce the behaviour is to open any file with Emacs, press
Ctrl+S to invoke the search function, type in some text to search for, and then
hit Enter.  The Emacs window will then shrink vertically.

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