[plasmashell] [Bug 423390] Bottom Plasma panel and desktop are not fully adjacent to screen border (1 pixel on the right and bottom) when PLASMA_USE_QT_SCALING=1 is set on X11

2024-03-10 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=423390

Andrew Brouwers  changed:

   What|Removed |Added

 CC||abrouw...@gmail.com

--- Comment #17 from Andrew Brouwers  ---
I see a similar issue, occasionally, on wayland + plasma 6.  I'm at 150%
scaling, and this will happen sporadically.  Restarting the desktop fixes it,
but it'll eventually come back (after some yet-to-be-determined action occurs).

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

[krunner] [Bug 482196] Disabling history doesn't disable memory of last-typed search

2024-03-05 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=482196

--- Comment #5 from Andrew Brouwers  ---
(In reply to Nate Graham from comment #4)
> Currently this behavior is intentional, but I can see how it's somewhat
> confusing: disabling history doesn't disable *recent* history, only long
> term history. Maybe we need another setting for this:
> 
> > History: ( ) Disable
> >  ( ) Only last-typed search
> >  ( ) Suggestions from all past searches
> >  (o) Auto-complete from all past searches

Yeah, I would expect disable history to start with a blank input, every time.

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

[krunner] [Bug 482196] History setting not effective

2024-03-02 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=482196

--- Comment #3 from Andrew Brouwers  ---
Created attachment 166311
  --> https://bugs.kde.org/attachment.cgi?id=166311=edit
konsole launched, while "kons" retained in a future krunner instance

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

[krunner] [Bug 482196] History setting not effective

2024-03-02 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=482196

--- Comment #2 from Andrew Brouwers  ---
(In reply to Alexander Lohnau from comment #1)
> Hmm, I am not sure how to handle this. It is not any persistent history, but
> just your last typed query. In case a window opens and KRunner closes, you
> might otherwise miss your previously typed text. Though you should be able
> to override the text with just one keystroke.
> 
> A sensible differentiation might be the cause for closing KRunner. Like the
> escape key could be handled separately and clear the text when a match is
> run. Though I am not sure if this behavior seems consistent to the average
> user.

I should clarify, even if I type "kons," hit "enter" once konsole is
highlighted (ie, it didn't get interrupted, but rather successfully launched my
searched-for app), it *still* shows in my history.  The history setting just
seems broken in plasma 6.

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

[krunner] [Bug 482196] New: History setting not effective

2024-03-01 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=482196

Bug ID: 482196
   Summary: History setting not effective
Classification: Plasma
   Product: krunner
   Version: 5.93.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

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

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've unchecked disabled history in krunner's settings.  If I spawn krunner,
start typing something, and escape (say, "fir"), it will be be present the next
time I open krunner.  In the attached screenshot, the text shown was not
entered in the current krunner "session," but from the time previously.

STEPS TO REPRODUCE
1. Disable history
2. Open krunner, type something, hit escape
3. Open krunner again, notice text still present

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: plasma 6.0 & Qt 6.6

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

[kwin] [Bug 482140] New: Window Color changes during close animation

2024-03-01 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=482140

Bug ID: 482140
   Summary: Window Color changes during close animation
Classification: Plasma
   Product: kwin
   Version: 5.93.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

I use breeze light, but prefer a dark konsole.  Historically, I've made a
window rule for konsole, but now use the built-in setting (from the drop-down
menu) to set breeze-dark.  This is minor, but when I hit "close," I can briefly
see it change back to breeze (light), before / during the closing animation.

STEPS TO REPRODUCE
1. Set breeze-dark in konsole's settings
2. Close konsole
3. Briefly witness the window border change to light, before closing animation
completes

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.0.0 w/ Qt 6.6

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

[kwin] [Bug 480638] xwayland always loaded in simple plasma-wayland session

2024-02-06 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=480638

--- Comment #2 from Andrew Brouwers  ---
(In reply to Nate Graham from comment #1)
> Right, we don't yet support launching XWayland on demand. It's something we
> want and are looking into, but it's not here yet.

Thanks, I guess I misunderstood this commit.  Sad, I was looking forward to
running a Wayland only plasma experience!

https://invent.kde.org/plasma/kwin/-/merge_requests/3527

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

[kwin] [Bug 480638] xwayland always loaded in simple plasma-wayland session

2024-01-31 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=480638

Andrew Brouwers  changed:

   What|Removed |Added

Summary|xwayland loaded in simple   |xwayland always loaded in
   |plasma-wayland session  |simple plasma-wayland
   ||session

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

[kwin] [Bug 480638] New: xwayland loaded in simple plasma-wayland session

2024-01-31 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=480638

Bug ID: 480638
   Summary: xwayland loaded in simple plasma-wayland session
Classification: Plasma
   Product: kwin
   Version: 5.93.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

SUMMARY
I installed a relatively simple plasma 6 RC2 environment, including only plasma
(6) environment & apps, plus firefox.  In summary, nothing that should require
xwayland explicitly.  After running "startplasma-wayland," xwayland is observed
as always running, without any way to disable.  

STEPS TO REPRODUCE
1. Install plasma 6
2. Check running processes
3. 

OBSERVED RESULT
xwayland is loaded

EXPECTED RESULT
Similar to gnome, I'd expect xwayland to start on-demand.

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

[kwin] [Bug 477235] Cascading behavior eventually stops; should *always* keep cascading as additional windows are opened

2023-11-30 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=477235

--- Comment #5 from Andrew Brouwers  ---
Created attachment 163675
  --> https://bugs.kde.org/attachment.cgi?id=163675=edit
gnome_screencast

I'm not advocating for copying gnome - if you feel the kwin behavior is
expected, feel free to close.  When I did the action, my perception was "wow,
kwin got confused," especially given the fairly large shadow density.  I almost
questioned if the compositor crashed or something.

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

[kwin] [Bug 477235] kwin confused with lots of windows

2023-11-29 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=477235

--- Comment #3 from Andrew Brouwers  ---
Created attachment 163628
  --> https://bugs.kde.org/attachment.cgi?id=163628=edit
gnome cascade

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

[kwin] [Bug 477235] kwin confused with lots of windows

2023-11-29 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=477235

Andrew Brouwers  changed:

   What|Removed |Added

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

--- Comment #2 from Andrew Brouwers  ---
I would have expected that, yes - wouldn't you?  Here's a sample of gnome, for
what it's worth.
Also, the drop-shadow density looks pretty ridiculous and poorly rendered, if
the intent WAS to just keep opening them in the center).

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

[kwin] [Bug 477235] New: kwin confused with lots of windows

2023-11-19 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=477235

Bug ID: 477235
   Summary: kwin confused with lots of windows
Classification: Plasma
   Product: kwin
   Version: 5.27.9
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

Created attachment 163290
  --> https://bugs.kde.org/attachment.cgi?id=163290=edit
kwin placement & shadow

SUMMARY
When opening a bunch of konsole windows, I noticed kwin eventually got a little
confused with placement, and then created a pretty ugly shadow in the position
of the last few entries.  Sorry - tough to describe, but hopefully the
screenshot shows the issue.


STEPS TO REPRODUCE
1. Open konsole
2. ctl+n a few dozen times

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

[kdeplasma-addons] [Bug 389766] Weather widget does not show the temperature beside or over the icon in the Plasma panel when I use wetter.com provider

2023-02-20 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=389766

--- Comment #9 from Andrew Brouwers  ---
Is it possible to switch providers, or offer others (for example, met.no or
openweathermap seem popular with other OSS projects) for people to choose?  It
seems broken to ship wetter if it will never work for such a common case.

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

[plasmashell] [Bug 462980] In Panel Edit Mode, "Maximize" button is inappropriately enabled while Panel is already maximized

2023-01-04 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=462980

--- Comment #6 from Andrew Brouwers  ---
OK, I guess I won't argue about the UX; I think it's not discoverable and
poorly laid out.  But, perhaps just disabling "maximize" when the panel is
already in a "maximized" state (be it floating or not) would "nudge" the user
in the right direction, and allow them to figure it out.

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

[plasmashell] [Bug 462980] In Panel Edit Mode, "Maximize" button is inappropriately enabled while Panel is already maximized

2023-01-04 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=462980

--- Comment #4 from Andrew Brouwers  ---
Yeah, I understand that - I'm just saying "Maximize" and "Floating Panel" (and,
Remove) are presented with the same alignment, font size, etc, making them look
like they all perform separate tasks.  It's pretty confusing that one would
select the second button on the list, and then understand that the button above
it actually can be a sub-option of the second button.

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

[plasmashell] [Bug 462980] In Panel Edit Mode, "Maximize" button is inappropriately enabled while Panel is already maximized

2023-01-04 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=462980

--- Comment #2 from Andrew Brouwers  ---
Ah, then I misunderstood.  Because of the alignment and presentation of the
buttons, I assumed "Maximize" meant "full width, no gaps" (ie, the
normal/default layout, fully expanded).  It's really confusing if "maximize" is
actually an option of "floating," but the "Maximize" button exists above the
"floating" button, with the same alignment, etc.

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

[kdeplasma-addons] [Bug 389766] Weather widget shows no temperature aside the icon in the plasma panel when I use wetter.com provider

2022-12-21 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=389766

--- Comment #6 from Andrew Brouwers  ---
Also, if "wetterer" will never allow this to be possible, it might make sense
to remove this as an option in the settings?  It doesn't seem right to offer a
feature that could never possibly work.

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

[kdeplasma-addons] [Bug 389766] Weather widget shows no temperature aside the icon in the plasma panel when I use wetter.com provider

2022-12-21 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=389766

--- Comment #5 from Andrew Brouwers  ---
Any thought to providing another backend, then?  I think gnome uses met.no, for
example.

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

[konsole] [Bug 463293] New: Small white dot in upper-left corner

2022-12-20 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=463293

Bug ID: 463293
   Summary: Small white dot in upper-left corner
Classification: Applications
   Product: konsole
   Version: 22.12.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

Created attachment 154721
  --> https://bugs.kde.org/attachment.cgi?id=154721=edit
konsole screenshot

SUMMARY
I recently updated to 22.12.0, and noticed a small, white dot in the corner of
my konsole window.


STEPS TO REPRODUCE
1.  Launch Konsole (running zsh if it matters)

OBSERVED RESULT
Small white dot - see screenshot

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.26.5
KDE Frameworks Version:  5.101.0
konsole: 22.12.0
Qt: 5.15.7+kde+r177

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

[kdeplasma-addons] [Bug 463273] New: Temp Display next to Icon doesn't work

2022-12-20 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=463273

Bug ID: 463273
   Summary: Temp Display next to Icon doesn't work
Classification: Plasma
   Product: kdeplasma-addons
   Version: 5.26.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Weather
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

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

SUMMARY
The weather applet doesn't seem to work very well; I don't seem to get temp
updates too frequently, though I suspend/wake my laptop somewhat frequently, so
maybe the "30 minute update" minimum is too much (why can't this be
lowered???).

But mostly, clicking "Show Beside Icon" doesn't seem to do anything - see
screenshot.

STEPS TO REPRODUCE
1. Try to use weather applet

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

[plasmashell] [Bug 462980] New: "Maximize" button doesn't work when trying to un-float panel

2022-12-12 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=462980

Bug ID: 462980
   Summary: "Maximize" button doesn't work when trying to un-float
panel
Classification: Plasma
   Product: plasmashell
   Version: 5.26.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY
Today, I tested the floating panel.  Not liking it, I went to undo this; trying
again to edit, I was presented with "Maximize," "Floating Panel" (which was
highlighted/active), and the option to remove.  Intuitively, I tried "Maximize"
to return to a full-width panel.  It LOOKS like I'm clicking a button, but
takes no action.  Instead, I had to click "Floating Panel" again, which made
the maximize text/button active.

Instead, I'd propose the "maximize" button actually do something, or remove the
response when I click the text.

STEPS TO REPRODUCE
1. Right click -> More Options -> Floating Panel
2. Right click -> More Options -> "Maximize"

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

[plasmashell] [Bug 451171] New: "Built-In Audio" pop-up when logging in after fresh boot

2022-03-05 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=451171

Bug ID: 451171
   Summary: "Built-In Audio" pop-up when logging in after fresh
boot
   Product: plasmashell
   Version: 5.24.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 147304
  --> https://bugs.kde.org/attachment.cgi?id=147304=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
***

I'm using pipewire(-pulse), which may or may not matter.  But, after logging in
from a fresh boot, plasma displays a "Built-In Audio Analog Stereo" pop-up for
a few seconds.  This feels like a "papercut" bug that should be hidden?

STEPS TO REPRODUCE
1.  Fresh boot
2.  Login, view pop-up
3. 

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version:  5.13.3

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

[Breeze] [Bug 447895] New: "breeze" & "breeze dark" confusing names for window switchers

2022-01-03 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=447895

Bug ID: 447895
   Summary: "breeze" & "breeze dark" confusing names for window
switchers
   Product: Breeze
   Version: 5.23.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

SUMMARY
(Sorry if this is mis-filed!).

I dislike the default alt-tab visualization.  After browsing settings, I
finally found Window Management -> Task Switcher, and "Visualization." 
Personally, I think "Breeze" and "Breeze Dark" are pretty poorly named, since
they provide very different visualizations not tied to the color.  For example,
I prefer "Breeze Dark" regardless if I'm using light or dark colors.  I really
don't agree with the justification that light vs. dark even warrants a separate
visualization (why not just use the same default for both?), but that's
probably a different argument :-)

Any thoughts on simply renaming these to something not tied to light & dark
theme?

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

[dolphin] [Bug 440924] Compress opens new window or tab

2021-08-13 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=440924

--- Comment #1 from Andrew Brouwers  ---
Created attachment 140690
  --> https://bugs.kde.org/attachment.cgi?id=140690=edit
after

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

[dolphin] [Bug 440924] New: Compress opens new window or tab

2021-08-13 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=440924

Bug ID: 440924
   Summary: Compress opens new window or tab
   Product: dolphin
   Version: 21.08.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: abrouw...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

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

SUMMARY
When using the right click --> compress service, a new window/tab opens with
the same context as the original.

STEPS TO REPRODUCE
1. Right click -> compress a directory
2. Observe new dolphin window
3. 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.22.4
KDE Frameworks Version: 5.84 
Qt Version: 5.15.2

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

[plasmashell] [Bug 437519] "Show all Entries" displays drop-down arrow

2021-05-23 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=437519

--- Comment #4 from Andrew Brouwers  ---
Strangely, mine corrected itself after restarting plasma (without changes to
the applets I had loaded).

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

[plasmashell] [Bug 437519] New: "Show all Entries" displays drop-down arrow

2021-05-22 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=437519

Bug ID: 437519
   Summary: "Show all Entries" displays drop-down arrow
   Product: plasmashell
   Version: 5.21.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Created attachment 138691
  --> https://bugs.kde.org/attachment.cgi?id=138691=edit
Screenshot of fresh 5.22 desktop

SUMMARY

I've upgraded to plasma 5.22 beta, and started with a fresh profile.  I always
select "always show all entries" under the sys-tray settings.  On 5.22, this
still shows the drop-down arrow (which is empty when I click it).  As with
previous plasma releases, this arrow should disappear with this option emabled,
IMO.

STEPS TO REPRODUCE
1. "Always show all entries
2. Observe drop-down
3.

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

[konsole] [Bug 432473] Window Rule overide to color - not effective in creating "new tab" in konsole

2021-02-03 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=432473

--- Comment #2 from Andrew Brouwers  ---
It doesn't seem to, no.  I set the window rule immediately when installing
plasma, and the "tab" colors are wrong every time.  But, if I just change
breeze globally to "Breeze Dark," every new konsole instances shows a dark tab
bar.  So, it seems to be related to forcing the color per-application in
Plasma's settings.

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

[plasmashell] [Bug 432473] New: Window Rule overide to color - not effective in creating "new tab" in konsole

2021-02-03 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=432473

Bug ID: 432473
   Summary: Window Rule overide to color - not effective in
creating "new tab" in konsole
   Product: plasmashell
   Version: 5.20.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: abrouw...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

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

SUMMARY

I set "Breeze Light" globally, but have a rule to force "Breeze dark" for
konsole.  This works great, until I create a new tab within konsole.  As shown
in the attached, it creates a "breeze light" tab.  Changing globally to "breeze
dark" shows a dark tab in konsole, so I assume this has to do with the logic of
setting the color per application.  That is, is it a one-time thing that gets
run when konsole first launches, and then "forgets" to apply it when creating
the new tab?

STEPS TO REPRODUCE
1. Set breeze light
2. Create a rule to force "breeze dark" for "konsole" matches
3. Create new tab

OBSERVED RESULT
Attached SS.

EXPECTED RESULT
Tab would follow "breeze dark" direction.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.21-beta

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

[plasmashell] [Bug 432472] New: Allow date to be placed next to time

2021-02-03 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=432472

Bug ID: 432472
   Summary: Allow date to be placed next to time
   Product: plasmashell
   Version: 5.20.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: 1.0

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

SUMMARY
Currently, I use a 32px horizontal panel; selecting "Show Date" on the clock
adds the date directly below the time makes both the time and date extremely
tiny.  But, I have a LOT of space unused on my panel.  I'd love the ability
select where the date gets placed - above/below (for vertical panels?) &
right/left (for horizontal panels).  Basically, I'd expect something more
similar to MacOS:

https://www.apple.com/newsroom/images/product/mac/standard/apple_macos-bigsur-availability_maps-guides_11122020_big_carousel.jpg.large.jpg

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.21-beta

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

[plasmashell] [Bug 431992] New: Edit Panel - Actions not always working in corner

2021-01-23 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=431992

Bug ID: 431992
   Summary: Edit Panel - Actions not always working in corner
   Product: plasmashell
   Version: 5.20.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: notm...@gmail.com
  Reporter: abrouw...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

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

SUMMARY
With a fresh 5.21-beta install, I'm having trouble interacting with plasma
applets located in the corner of the screen.  Initially, when moving my panel
to the top, I tried to remove the "Show Desktop" button (Edit Panel -> Hover ->
"Remove").  This wouldn't work, regardless of how many times I hit the button;
moving it out of the corner allowed it to work.

Now, I was trying to edit the systray (Edit Panel -> Hover -> "Configure"), and
find it's also not working reliably.

SS attached of my approximate setup; panel size is small, at around 32px.


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.20.90
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

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

[plasmashell] [Bug 431961] New: Cannot remove custom wallpapers from "Desktop Settings"

2021-01-22 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=431961

Bug ID: 431961
   Summary: Cannot remove custom wallpapers from "Desktop
Settings"
   Product: plasmashell
   Version: 5.20.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: abrouw...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

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

SUMMARY

After updating to 5.21-beta, I removed my settings and started with a fresh
plasma environment.  I added a few custom wallpapers, but ended up sticking
with stock.  Trying to use the trash icon (and, the "open folder" button) isn't
doing anything - the wallpapers remain, and dolphin isn't spawned.

STEPS TO REPRODUCE
1. Switch to Desktop layout
2. Add custom wallpaper
3. Attempt to delete with built-on buttons

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

[plasmashell] [Bug 427033] Set order no longer persistent since plasma 5.20

2020-09-27 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=427033

--- Comment #2 from Andrew Brouwers  ---
Created attachment 131970
  --> https://bugs.kde.org/attachment.cgi?id=131970=edit
after

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

[plasmashell] [Bug 427033] New: Set order no longer persistent since plasma 5.20

2020-09-27 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=427033

Bug ID: 427033
   Summary: Set order no longer persistent since plasma 5.20
   Product: plasmashell
   Version: 5.19.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: abrouw...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY

Previous to plasma 5.20, I could set the exact order of icons I wanted in the
icons-only task manager.  I usually set: chromium, konsole, dolphin.

Now, since plasma 5.20, launching applications will cause the order to change. 
Attached is a before/after; launching spectacle made "konsole" jump to the
first entry on the list.

EXPECTED RESULT
The order that I set is permanent and retained, as with previous plasma
versions.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.19.90
KDE Plasma Version: 5.19.90

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

[plasmashell] [Bug 427033] Set order no longer persistent since plasma 5.20

2020-09-27 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=427033

--- Comment #1 from Andrew Brouwers  ---
Created attachment 131969
  --> https://bugs.kde.org/attachment.cgi?id=131969=edit
before

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

[plasmashell] [Bug 424653] New: "Show All Entries" results in everything being "Disabled" (nothing can be disabled)

2020-07-25 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=424653

Bug ID: 424653
   Summary: "Show All Entries" results in everything being
"Disabled" (nothing can be disabled)
   Product: plasmashell
   Version: 5.19.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: 1.0

Created attachment 130394
  --> https://bugs.kde.org/attachment.cgi?id=130394=edit
screenshot of settings

SUMMARY

I recently created a fresh user; I typically do "Show All Entries" for the
systray, and then disable ones I don't want (klipper, touchpad, etc).  To my
surprise, all entries were actually "Disabled" by default, meaning I could not
disable anything.

STEPS TO REPRODUCE
1. Fresh user
2. Configure System Tray
3. Show all Entries
4. Try to disable something
5. Cry

Running plasma 5.19.3, Qt 5.15.0

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

[plasmashell] [Bug 422111] Battery applet not showing up in tray.

2020-06-29 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=422111

--- Comment #23 from Andrew Brouwers  ---
Then, after a kquitapp & kstart plasmashell, (which makes it appear pretty
consistently):

$ qdbus org.freedesktop.DBus /org/freedesktop/DBus
org.freedesktop.DBus.ListNames
org.freedesktop.DBus
org.freedesktop.Notifications
:1.227
org.freedesktop.PowerManagement
org.kde.kappmenu
org.kde.kaccess
org.freedesktop.systemd1
org.pulseaudio.Server
org.kde.KScreen
:1.250
org.kde.klauncher5
:1.251
:1.23
org.kde.kscreen.osdService
:1.253
:1.231
org.freedesktop.PowerManagement.Inhibit
org.kde.Solid.PowerManagement
:1.233
org.kde.StatusNotifierHost-51999
:1.234
:1.257
:1.235
org.kde.KWin
org.kde.screensaver
:1.258
ca.desrt.dconf
:1.236
:1.237
:1.238
org.freedesktop.ScreenSaver
:1.239
org.kde.plasmashell
org.kde.plasmanetworkmanagement
org.kde.konsole-51945
local.org_kde_powerdevil
org.kde.kglobalaccel
org.kde.kwalletd5
org.PulseAudio1
org.kde.polkit-kde-authentication-agent-1
com.canonical.Unity
org.kde.kded5
org.kde.ActivityManager
org.kde.keyboard
:1.260
org.kde.kuiserver
:1.240
org.kde.StatusNotifierWatcher
:1.241
org.kde.JobViewServer
:1.0
:1.242
:1.244
org.kde.ksmserver
org.kde.kcookiejar5
:1.246
org.kde.Solid.PowerManagement.PolicyAgent
:1.247
:1.248

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

[plasmashell] [Bug 422111] Battery applet not showing up in tray.

2020-06-29 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=422111

--- Comment #22 from Andrew Brouwers  ---
I just restarted plasma, and successfully had it not appear (running 5.19.2)

$ qdbus org.freedesktop.DBus /org/freedesktop/DBus
org.freedesktop.DBus.ListNames
org.freedesktop.DBus
org.freedesktop.Notifications
:1.227
org.freedesktop.PowerManagement
org.kde.kappmenu
org.kde.kaccess
org.freedesktop.systemd1
org.pulseaudio.Server
org.kde.KScreen
:1.250
org.kde.klauncher5
:1.251
:1.23
org.kde.kscreen.osdService
:1.253
:1.231
org.freedesktop.PowerManagement.Inhibit
org.kde.Solid.PowerManagement
:1.254
:1.233
:1.234
:1.235
org.kde.KWin
org.kde.screensaver
ca.desrt.dconf
:1.236
:1.237
:1.238
org.freedesktop.ScreenSaver
:1.239
org.kde.plasmashell
org.kde.plasmanetworkmanagement
org.kde.konsole-51945
local.org_kde_powerdevil
org.kde.kglobalaccel
org.kde.kwalletd5
org.PulseAudio1
org.kde.polkit-kde-authentication-agent-1
com.canonical.Unity
org.kde.kded5
org.kde.ActivityManager
org.kde.keyboard
org.kde.kuiserver
:1.240
org.kde.StatusNotifierHost-51566
org.kde.StatusNotifierWatcher
:1.241
org.kde.JobViewServer
:1.0
:1.242
:1.243
:1.244
org.kde.ksmserver
org.kde.kcookiejar5
:1.246
org.kde.Solid.PowerManagement.PolicyAgent
:1.247
:1.248

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

[plasmashell] [Bug 422111] Battery applet not showing up in tray.

2020-06-23 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=422111

Andrew Brouwers  changed:

   What|Removed |Added

 CC||abrouw...@gmail.com

--- Comment #17 from Andrew Brouwers  ---
Happening for me on a fresh 5.19.2 config.

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

[plasmashell] [Bug 423271] New: Consolidate "configuration" options in digital clock

2020-06-20 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=423271

Bug ID: 423271
   Summary: Consolidate "configuration" options in digital clock
   Product: plasmashell
   Version: 5.19.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: 1.0

SUMMARY:

As a possible UI simplification, I wanted to change the format of the digital
clock (to 24hr).  To my surprise, right clicking produced three extremely
similar options:

* Adjust date and time
* Set time format
* Configure digital clock

It took me three tries to actually find the correct location.  Perhaps these
three should be consolidated in to a single "configure clock" option?  I can
see the first two being simple buttons within the menu of the third.

STEPS TO REPRODUCE
1. Right click on digital clock

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

[krunner] [Bug 423270] New: Number of "Folder" runners is confusing

2020-06-20 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=423270

Bug ID: 423270
   Summary: Number of "Folder" runners is confusing
   Product: krunner
   Version: 5.19.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: abrouw...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY

I was disabling some runners in krunner, and found that many are either poorly
named, or seem very redundant.  Specifically, the number of "folders" or
"bookmarks":

* Bookmarks: "Find and open bookmarks"
* Locations: "File and URL opener"
* Places: "Open devices and folder bookmarks"
* Recent Documents: "?"

This leads to a pretty confusing user experience.  Perhaps the first three
could be consolidated?  I've been using KDE/plasma for several years, and even
I have no idea how these are different; I'm sure it's extra confusing for new
users.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.19.1

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

[Powerdevil] [Bug 422678] battery indicator not showing up, widget shows no batteries attached

2020-06-11 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=422678

Andrew Brouwers  changed:

   What|Removed |Added

 CC||abrouw...@gmail.com

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

[okular] [Bug 416688] New: Okular (kirigami) shows up in Lost and Found

2020-01-24 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=416688

Bug ID: 416688
   Summary: Okular (kirigami) shows up in Lost and Found
   Product: okular
   Version: 1.9.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

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

SUMMARY

I believe "/usr/share/applications/org.kde.okular.kirigami.desktop" is to
blame, but on my Arch linux system, okular produces an entry in KDE's "Lost and
Found" catagory.  I would think this plugin shouldn't show up in the menu at
all?

I'm running plasma 5.17.5, and Okular from Applications 19.12.1.

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

[Breeze] [Bug 412170] Chromium incognito should (optionally) provide breeze-dark window borders, to match the GTK theme

2019-11-30 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=412170

--- Comment #5 from Andrew Brouwers  ---
Sure, I've uploaded some screenshots.  My use is actually breeze light, but
expecting the Chromium Incognito window to use dark window borders.

Thinking more about it, I think what I want isn't technically possible.  I use
BreezeEnhanced, usually, with my controls on the left hand side (ala MacOS). 
For that reason, using the GTK theme / border (instead of system) isn't
possible, because it uses the regular breeze buttons (and, won't put them on
the "left" side, ala screenshot #2).

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

[Breeze] [Bug 412170] Chromium incognito should (optionally) provide breeze-dark window borders, to match the GTK theme

2019-11-30 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=412170

--- Comment #4 from Andrew Brouwers  ---
Created attachment 124205
  --> https://bugs.kde.org/attachment.cgi?id=124205=edit
Incognito2

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

[Breeze] [Bug 412170] Chromium incognito should (optionally) provide breeze-dark window borders, to match the GTK theme

2019-11-30 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=412170

--- Comment #3 from Andrew Brouwers  ---
Created attachment 124204
  --> https://bugs.kde.org/attachment.cgi?id=124204=edit
Incognito1

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

[Breeze] [Bug 412170] New: Chromium incognito should (optionally) provide breeze-dark window borders, to match the GTK theme

2019-09-21 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=412170

Bug ID: 412170
   Summary: Chromium incognito should (optionally) provide
breeze-dark window borders, to match the GTK theme
   Product: Breeze
   Version: 5.16.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: uhh...@gmail.com
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

SUMMARY

I use breeze-light color scheme, generally (with a few overrides, such as
konsole).  I was excited to read the following from the changelog for 5.17:

"Our Breeze GTK theme now provides a better appearance for the Chromium/Chrome
web browsers and applies your color scheme to GTK and GNOME apps."

However, a feature I still find missing is launching chromium as an incognito
instance.  When selecting "use GTK theme" from chromiums settings, I get a
darker theme, as expected.  However, my window titlebars are still
breeze-light, which looks poor.  On gnome, for example, the title bar darkens
to match the theme.  Unfortunately, it doesn't seem possible to create a rule
for an incognito instance, since it just shows "chromium."

STEPS TO REPRODUCE
1. Set breeze-light, install breeze-gtk, set chromium to use "GTK" theme
instead of classic
2. Open incognito instance of chromium


OBSERVED RESULT
Breeze-light window border does not match GTK theme.

EXPECTED RESULT
Breeze-dark would instead be used to match darker GTK theme

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.16.90
KDE Frameworks Version: 5.62.0
Qt Version: 5.13.1

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

[Falkon] [Bug 407319] New: "Tools -> New Window" opens incognito from incognito window

2019-05-07 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=407319

Bug ID: 407319
   Summary: "Tools -> New Window" opens incognito from incognito
window
   Product: Falkon
   Version: 3.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

SUMMARY
If I'm in an incognito window, I'd expect "Tools -> New Window" to open a
regular window, and "Tools -> New Incognito Window" to open an incognito
window.  However, both appear to just open an incognito window.

STEPS TO REPRODUCE
1. Open an incognito window
2. Tools -> New Window
3. 

OBSERVED RESULT
New window is "incognito" too


EXPECTED RESULT
A normal window.

SOFTWARE/OS VERSIONS
falkon 3.1.0.66.g3bc0c165-1
qt5-base 5.12.3-2
qt5-declarative 5.12.3-1
qt5-graphicaleffects 5.12.3-1
qt5-location 5.12.3-1
qt5-multimedia 5.12.3-1
qt5-quickcontrols 5.12.3-1
qt5-quickcontrols2 5.12.3-1
qt5-script 5.12.3-1
qt5-sensors 5.12.3-1
qt5-speech 5.12.3-1
qt5-svg 5.12.3-1
qt5-tools 5.12.3-1
qt5-webchannel 5.12.3-1
qt5-webengine 5.12.3-2
qt5-webkit 5.212.0alpha2-28
qt5-x11extras 5.12.3-1

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

[plasmashell] [Bug 393975] Calendar popup reports incorrect day (but, hover, date, and settings are correct)

2018-05-29 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=393975

--- Comment #5 from Andrew Brouwers  ---
It's still an issue for me on 5.12.90 as well.  Could this be related to Qt
5.11?  I'm not sure how to provide more information for troubleshooting.  I
have the issue with a fresh KDE instance (new config) with the following:

[andrew@thinkpad]$ pacman -Q plasma-desktop qt5-base
plasma-desktop 5.12.90.1-1
qt5-base 5.11.0-1

[andrew@thinkpad]$ ls -l /etc/localtime 
lrwxrwxrwx 1 root root 37 May 19 22:16 /etc/localtime ->
../usr/share/zoneinfo/America/Detroit

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

[plasmashell] [Bug 393975] Calendar popup reports incorrect day (but, hover, date, and settings are correct)

2018-05-08 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=393975

--- Comment #3 from Andrew Brouwers <abrouw...@gmail.com> ---
Not sure if it's helpful, but it's still 1 day off here (my timezone,
American/Detroit, has changed to Tuesday, and the pop-up displays Monday).  I
haven't changed any settings, and can't seem to locate "week starts with
weekday" to try toggling.  None of the settings changes make it jump forward a
day, and hovering, the systemsettings "Date and Time" module, etc. all show
Tuesday correctly.

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

[plasmashell] [Bug 393975] Calendar popup reports incorrect day (but, hover, date, and settings are correct)

2018-05-07 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=393975

--- Comment #1 from Andrew Brouwers <abrouw...@gmail.com> ---
Created attachment 112490
  --> https://bugs.kde.org/attachment.cgi?id=112490=edit
Popup2

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

[plasmashell] [Bug 393975] New: Calendar popup reports incorrect day (but, hover, date, and settings are correct)

2018-05-07 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=393975

Bug ID: 393975
   Summary: Calendar popup reports incorrect day (but, hover,
date, and settings are correct)
   Product: plasmashell
   Version: 5.12.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Calendar
  Assignee: plasma-b...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: 1.0

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

My calendar popup is 1 day off.  "date," KDE's "Adjust date and time," and even
the calender hover pop-up show the correct date.  However, the grid is exactly
1 day off.

I'm running plasma 5.12.5, kde-frameworks 5.45.0, and Qt 5.11.0beta4.

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

[plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf?

2017-11-09 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=386665

--- Comment #2 from Andrew Brouwers <abrouw...@gmail.com> ---
Thanks for the response - right, I guess my point was that gconf is an old
gnome technology (one which a standard gnome install doesn't even use these
days), so it's odd that KDE (actually only plasma-pa) requires it.

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

[plasma-pa] [Bug 386665] New: Drop dependency on pulseaudio-gconf?

2017-11-08 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=386665

Bug ID: 386665
   Summary: Drop dependency on pulseaudio-gconf?
   Product: plasma-pa
   Version: 5.11.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: abrouw...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

On my distribution, plasma-pa is the only pulse front-end (outside of paprefs)
which requires pulseaudio-gconf.  That is, even on gnome, pulseaudio-gconf (and
thus, gconf) are not required for the mixer.  It seems really strange that KDE
is brining in gconf, but not gnome (!).  plasma-pa is the only KDE component
pulling in gconf.

Is it possible to eliminate this dependency?  I'm not sure how gnome-shell (and
other pulseaudio front-ends, for that matter) get around this.

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

[konsole] [Bug 380518] New: Konsole does not create profiles by default

2017-06-03 Thread Andrew Brouwers
https://bugs.kde.org/show_bug.cgi?id=380518

Bug ID: 380518
   Summary: Konsole does not create profiles by default
   Product: konsole
   Version: 17.04.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

On a default arch linux install (konsole 17.04.1), I noticed some really odd
behavior around profiles.  First, there weren't any populated profiles by
default.  I had to create one manually; upon making some changes, the list of
profiles was still only my newly created default (after closing and re-opening
konsole several times).  However, after making deeper changes (to fonts, hiding
scroll bar), konsole create 4 new profiles, and had changed the default to
Profile 4.  As a result, most of my settings were made to this profile, even
though I had my default profile selected prior to making changes.

In summary, something odd is going on; there appears to be no default profile
upon first use, and some setting change appears to cause them to get created,
and blindly change over to using it.  

This is re-creatable with a new user.

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