[Discover] [Bug 371658] Items on the sources list in Settings section are rendered outside layout borders

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 101773
  --> https://bugs.kde.org/attachment.cgi?id=101773=edit
Image shows how sources with long text are rendered outside layout borders

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

[Discover] [Bug 371658] New: Items on the sources list in Settings section are rendered outside layout borders

[soee via KDE Bugzilla]

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

Bug ID: 371658
   Summary: Items on the sources list in Settings section are
rendered outside layout borders
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kont...@soee.pl

Inside Settings section on sources list we have often entries with long text
and such text is than rendered outside current layout borders. Those texts
should fit to current windows size (we should hide or cut to long content or
break it to new line etc.).

Reproducible: Always

Steps to Reproduce:
1. Open Discover
2. Navigate to Settings view
3. Try to resize window to a smaller size

Actual Results:  
Observe how items on the list are rendered outside layout if they d not fix
actual window size

Expected Results:  
The items text should be hidden on cut to prevent rendering it outside layout.

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

[Breeze] [Bug 370248] The Person Widget is using the Desktop icon in ...

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

 CC||kont...@soee.pl

--- Comment #2 from soee  ---
I can confirm this bug on Plasma 5.9-dev (Neon dev/unstable).

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

[kscreenlocker] [Bug 369857] Images from the wallpapers list can't be removed

[soee via KDE Bugzilla]

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

--- Comment #2 from soee  ---
(In reply to Kai Uwe Broulik from comment #1)
> Images marked for deletion are only removed when you apply the dialog. While
> this isn't very ideal and obvious, it's the same for the desktop and lock
> screen settings. Only if you Apply it will remove the image from the list,
> just closing the dialog won't, in both cases.

By "apply" you mean pressing the Apply button or OK? If we mark image for
deletion that Apply button is never active either in desktop settings or kcm.
Pressing OK button indeed removes image when we are in desktop settings but
does not work inside kcm.

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

[kscreenlocker] [Bug 369857] New: Images from the wallpapers list can't be removed

[soee via KDE Bugzilla]

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

Bug ID: 369857
   Summary: Images from the wallpapers list can't be removed
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: plasma-b...@kde.org
  Reporter: kont...@soee.pl
CC: bhus...@gmail.com, mgraess...@kde.org

It looks like Screen Locking kcm for selecting wallaper uses the same component
that we see in desktop settings. The problem with it when using inside kcm is
that we can't remove and image from the wallpapers list.

When having opened desktop settings, wallpaper can be removed if we mark it to
remove and close the window. Inside Screen Locking kcm if we do the same and
close the window the wallpaper is never removed.

Reproducible: Always

Steps to Reproduce:
1. Open Screen Locking kcm
2. Go to Wallpaper tab and mark any image to be removed from the list
3. Close the window
4. Open Screen Locking kcm again

Actual Results:  
Image marked to remove is still here.

Expected Results:  
Image marked to be remove should be removed.

>From the UX, UI point of view this is pretty strange how this wallpapers
removal works atm. I think if we mark any image to remove than "Apply" button
should switch to active and we should be able to apply changes by clicking on
it and not waiting to close the window to have those images removed.

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

[kdeplasma-addons] [Bug 369116] New: [FEATURE] Make Quicklaunch widget configurable per activity

[soee via KDE Bugzilla]

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

Bug ID: 369116
   Summary: [FEATURE] Make Quicklaunch widget configurable per
activity
   Product: kdeplasma-addons
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Quicklaunch
  Assignee: now...@gmail.com
  Reporter: kont...@soee.pl

It would be cool to have an option to confgure Quicklaunch widget to use
launchers configured for current activity only. So by default it would use some
global setup but if user check option to restrict configuration for current
activity, then it will show only launchers set and visible on this activity.

Reproducible: Always

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

[plasmashell] [Bug 368803] New: Panel shadow is not restored with compositor

[soee via KDE Bugzilla]

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

Bug ID: 368803
   Summary: Panel shadow is not restored with compositor
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kont...@soee.pl
CC: bhus...@gmail.com, plasma-b...@kde.org

I have some apps like Steam or single games windows set to disable compositor
when they run. This works pretty good. The only small issue is that when i
close such app, compositor is restored but panel shadow is missing. To bring it
back i have to toggle desktop effects ALT + SHIFT + F12.

Reproducible: Always

Steps to Reproduce:
1. Configure some app to disable compositor when running.
2. Run app
3. Close app

Actual Results:  
Panel shadow is missing after compositor was restored.

Expected Results:  
Panel shadow should be rendered after compositor ws enabled again.

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

[digikam] [Bug 367847] New: Digikam crashed when we right click on albums area

[soee via KDE Bugzilla]

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

Bug ID: 367847
   Summary: Digikam crashed when we right click on albums area
   Product: digikam
   Version: 5.5.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: kont...@soee.pl

Digikam crashes as soon as i right click on Albums area:

Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc723d20b80 (LWP 18611))]

Thread 14 (Thread 0x7fc6157fa700 (LWP 18668)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc74be59863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fc74c17a051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fc75222f6fa in start_thread (arg=0x7fc6157fa700) at
pthread_create.c:333
#4  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fc615ffb700 (LWP 18667)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc74be59863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fc74c17a051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fc75222f6fa in start_thread (arg=0x7fc615ffb700) at
pthread_create.c:333
#4  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fc6167fc700 (LWP 18666)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc74be59863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fc74c17a051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fc75222f6fa in start_thread (arg=0x7fc6167fc700) at
pthread_create.c:333
#4  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fc616ffd700 (LWP 18665)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc74be59863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fc74c17a051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fc75222f6fa in start_thread (arg=0x7fc616ffd700) at
pthread_create.c:333
#4  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fc6177fe700 (LWP 18664)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc74be59863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fc74c17a051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fc75222f6fa in start_thread (arg=0x7fc6177fe700) at
pthread_create.c:333
#4  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fc617fff700 (LWP 18663)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc74be59863 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fc74c17a051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fc75222f6fa in start_thread (arg=0x7fc617fff700) at
pthread_create.c:333
#4  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fc654ff9700 (LWP 18662)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc74be58834 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fc74c17a051 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fc75222f6fa in start_thread (arg=0x7fc654ff9700) at
pthread_create.c:333
#4  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fc6557fa700 (LWP 18661)):
#0  0x7fc7552c7e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc74cc5239c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc74cc524ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc7561d723b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc756181cea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc755fa6fb4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc755fabb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc75222f6fa in start_thread (arg=0x7fc6557fa700) at
pthread_create.c:333
#8  0x7fc7552d3b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fc709db1700 (LWP 18618)):
#0  0x7fc7552988dd in nanosleep () at 

[systemsettings] [Bug 367667] New: Modules use different left margin value for content section

[soee via KDE Bugzilla]

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

Bug ID: 367667
   Summary: Modules use different  left margin value for content
section
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
   URL: http://wstaw.org/m/2016/08/22/Spectacle.J12228.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kont...@soee.pl

Check added link to an image to see the problem. All modules should use the
same left margin for content section. Now this value is different in various
modules and it also does not equal the section title/header left margin.

All modules should be checked and the left margin for content section unified
to be the same and match header margin.

Reproducible: Always

Steps to Reproduce:
1. Open System Settings -> Desktop Behaviour -> Workspace module
2. Open System Settings -> Desktop Behaviour -> Screen Locking module
3. Compare both and see where the content starts (under section title)

Actual Results:  
The left margin is not the same and does not equal header margin.

Expected Results:  
All modules should have left margin for content section unified to be the same
and make sureit matches also left header margin.

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #12 from soee  ---
So i should wait with any more tests until your patch lands in master?

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #9 from soee  ---
Created attachment 100662
  --> https://bugs.kde.org/attachment.cgi?id=100662=edit
Working screens configuration

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #8 from soee  ---
Before i do the check i wanted to report one thing: 

having the problem i switched back to Nvidia profile and did come power
configuration setup changes System Settings -> Power Management -> Energy
Saving:

[X] Button events handling 
When laptop is closed: Turn Off Screen
[X] Even when an external monitor is connected

Than i closed laptop's lid and had only external screen active - pretty good os
far. 
After reboot though GRUB/sddm is always loading on laptop screen (probably
because user configuration is not available here) so i have to open laptop lid,
login and ... this time even with laptop lid opened i had it's screen disabled
as i wanted (see attached screenshot 3). Though i'm not sure why and how it
started to work.

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #6 from soee  ---
Yes i have the same issue on Intel profile.

Also - as you can see on the second attached screen - after hdmi cable is
unplugged and plugged in again (as i mentioned in bug report) the laptop screen
is black (after i move whole panel to connected screen) and i do not have
context menu when i right click on it etc. I have to restart plasmashell to
have them laptop screen configuration back (wallpaper etc).

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #4 from soee  ---
Some more info:

Dell Inspiron with hybrid graphics: Intel + Nvidia (working on  nvidia profile
with 370.23 propriety driver version). External screen is LG 29UC97C using
2560x1080 resolution.

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #3 from soee  ---
Created attachment 100660
  --> https://bugs.kde.org/attachment.cgi?id=100660=edit
kscreen.log

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #2 from soee  ---
Created attachment 100659
  --> https://bugs.kde.org/attachment.cgi?id=100659=edit
Wrong panel rendering after unplugging/plugging in hdmi cable

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

[KScreen] [Bug 367490] Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 100658
  --> https://bugs.kde.org/attachment.cgi?id=100658=edit
Screens configuration is System Settings

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

[KScreen] [Bug 367490] New: Disabling laptop screen makes it also external screen disabled

[soee via KDE Bugzilla]

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

Bug ID: 367490
   Summary: Disabling laptop screen makes it also external screen
disabled
   Product: KScreen
   Version: git
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: libkscreen
  Assignee: se...@kde.org
  Reporter: kont...@soee.pl

I'm working on a setup like this: laptop + connected external screen through
hdmi. As my external screen is ultra wide i do not want/need to use laptop's
screen. 

To use only connected screen i'm trying to configure it in System Settings ->
Display & Monitor -> Display Configuration as follow (see attached screenshot
nr 1):

1. Primary display: HDMI-1
2. Laptop Screen (LVDS-1) -> Display [Enabled]  unchecked
3. Apply settings
4. Both screens get turned off

Than after this changes when i had both screens OFF and i unplugged hdmi cable
from my laptop it's screen (laptop) turned ON. After that i plugged in hdmi
cable again and external screen was also ON.

With this screens problem i noticed also panel issue. I was using single panel
on external screen. After hdmi cable was unplugged the panel was moved to
laptop screen. After conecting hdmi cable again, panel was rendered like 80% on
laptop screen and 20% on external screen (see attached screen nr 2).

Reproducible: Always

Steps to Reproduce:
1. Have 2 screens setup (laptop + external in my case)
2. Configure through System Settings one screen (laptop in my case) to be
disabled and set the connected one as a primary display.
3. Apply changes and observe like both screens are turning off

Actual Results:  
When disabling main (laptop) screen than also external screen gets
disabled/turned off.

Expected Results:  
When disabling main screen only this on shoudl be disabled and external one
shoudl work.

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

[kdeplasma-addons] [Bug 366827] Widget location configuration is lost after reboot

[soee via KDE Bugzilla]

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

--- Comment #2 from soee  ---
It is lost. There are no any signs of it beeing restored. I will test more with
cable connection also as not im using LTE (usb modem with sim). So when i boot
my system modem needs ~ 2-3 min. to connect but when rebooting it is usually
active at start.

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

[kdeplasma-addons] [Bug 366828] New: When we type location in "Location" field and press ENTER key, configuration window gets closed

[soee via KDE Bugzilla]

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

Bug ID: 366828
   Summary: When we type location in "Location" field and press
ENTER key, configuration window gets closed
   Product: kdeplasma-addons
   Version: 5.7.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: weather
  Assignee: kosse...@kde.org
  Reporter: kont...@soee.pl
CC: plasma-b...@kde.org

If we type any location name inside "Location" field in configuration window
than natural action is to hit ENTER key to search for given place. But if we
hit ENTER than configuration window is closed.

Reproducible: Always

Steps to Reproduce:
1. Open widget configuration window
2. Type some location name
3. Hit ENTER key

Actual Results:  
Configuration window gets closed.

Expected Results:  
Widget should search for selected location when ENTER key is pressed after name
was entered.

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

[kdeplasma-addons] [Bug 366827] New: Widget location configuration is lost after reboot

[soee via KDE Bugzilla]

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

Bug ID: 366827
   Summary: Widget location configuration is lost after reboot
   Product: kdeplasma-addons
   Version: 5.7.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: weather
  Assignee: kosse...@kde.org
  Reporter: kont...@soee.pl
CC: plasma-b...@kde.org

If we set location for the widget it is lost after system reboot and thus
widget show only dummy icon without any weather data.

Reproducible: Always

Steps to Reproduce:
1. Add widget
2. Select location
3. Reboot system

Actual Results:  
Location configuration is lost after reboot

Expected Results:  
Location shoudl be always available after it was configured.

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

[rsibreak] [Bug 366478] Make systray icon monochrome dark/light variants

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

Summary|Make systray icon   |Make systray icon
   |monochrmoe dark/light   |monochrome dark/light
   |wariants|variants

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

[rsibreak] [Bug 366478] Make systray icon monochrmoe dark/light wariants

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 100483
  --> https://bugs.kde.org/attachment.cgi?id=100483=edit
RSIBreak icons compared to other systray items on Plasma desktop

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

[rsibreak] [Bug 366478] New: Make systray icon monochrmoe dark/light wariants

[soee via KDE Bugzilla]

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

Bug ID: 366478
   Summary: Make systray icon monochrmoe dark/light wariants
   Product: rsibreak
   Version: 0.12
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: aa...@kde.org
  Reporter: kont...@soee.pl

It would be great if we could have an option to use monochrome icon in systray.
Desktop environments like Plasma or GNOME allow to set different themes for
users desktops and usually icons in systray are all monochrome.

When it comes to KDE Plasma, i'm sure that Visual Design Group could provide
monochrome version if someone could implement it.

Reproducible: Always

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

[Discover] [Bug 366412] At the upper left corner of the menu icon there is 3-4 pixels artifact

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 100454
  --> https://bugs.kde.org/attachment.cgi?id=100454=edit
Artifact near search field and menu button

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

[Discover] [Bug 366412] New: At the upper left corner of the menu icon there is 3-4 pixels artifact

[soee via KDE Bugzilla]

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

Bug ID: 366412
   Summary: At the upper left corner of the menu icon there is 3-4
pixels artifact
   Product: Discover
   Version: 5.7.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kont...@soee.pl

Between search field and hamburger menu button there are some 3-4 dark pixels
(probably some small shape of something). See attached screenshot for more
details.

Reproducible: Always

Steps to Reproduce:
1. Open Discover

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

[Discover] [Bug 366410] Search field should have 'clear' button

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 100452
  --> https://bugs.kde.org/attachment.cgi?id=100452=edit
Second element shows search field with button to clear entered text

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

[Discover] [Bug 366410] New: Search field should have 'clear' button

[soee via KDE Bugzilla]

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

Bug ID: 366410
   Summary: Search field should have 'clear' button
   Product: Discover
   Version: 5.7.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kont...@soee.pl

The main search field should have like other similiar elements in KDE
Application the "Clear" button. Please check attached image for details.

Reproducible: Always

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

[Discover] [Bug 366405] New: Progress bar does not work as expected for package download status

[soee via KDE Bugzilla]

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

Bug ID: 366405
   Summary: Progress bar does not work as expected for package
download status
   Product: Discover
   Version: 5.7.3
  Platform: Neon Packages
   URL: https://www.youtube.com/watch?v=YQDvzOGFohg
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Updater
  Assignee: aleix...@kde.org
  Reporter: kont...@soee.pl

hen we are updating packages than for each of them progress bar is rendered.
For some reason it reaches ~ 75% for each of packages and that for a moment all
progress bars are set to ~ 15% and packages start to install. See link to the
video - it demonstrates this behaviour.

Reproducible: Always

Steps to Reproduce:
1. Open Discover Updater when there are some updates available
2. Click Update
3. Observe progress bars (they all reach ~ 75% than it jumps to ~ 15%)
4. See packages beeing installed

Actual Results:  
Progress par for package download reaches ~ 75% than jumps to 15%.

Expected Results:  
Progress bar should reach 100% for package that is downloaded and never jump to
lower value.

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

[kinfocenter] [Bug 366158] Switching sections inside Info module results with small lag when rendering their content

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 100329
  --> https://bugs.kde.org/attachment.cgi?id=100329=edit
About System kcm content with variables placeholders inside Info mdule

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

[kinfocenter] [Bug 366158] New: Switching sections inside Info module results with small lag when rendering their content

[soee via KDE Bugzilla]

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

Bug ID: 366158
   Summary: Switching sections inside Info module results with
small lag when rendering their content
   Product: kinfocenter
   Version: 5.7.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: kont...@soee.pl

When switching Info module sections that use some variables loaded for example
from files, than we see for a moment those variables placeholders like
{NameVersionLabel} or {UrlLabel} in About System section.

See attached screenshot to see it.

Reproducible: Always

Steps to Reproduce:
1. Open Info module
2. Switch between Memory and About System sections
3. Observ the lag when loading and replacing placeholders in About System
section content

Actual Results:  
For a moment we see variables placeholders like {NameVersionLabel}

Expected Results:  
Placeholders hsould never be seen  - just final output

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

[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics

[soee via KDE Bugzilla]

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

--- Comment #4 from soee  ---
Typo: the removed text was in more than 13.000 lines.

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

[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics

[soee via KDE Bugzilla]

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

--- Comment #3 from soee  ---
Created attachment 100327
  --> https://bugs.kde.org/attachment.cgi?id=100327=edit
.xsession-errors file content

I removed one text that spammed this file (more than 13.00 lines were):
kde.systemtray: Wrong IconThemePath
"/home/soee/.dropbox-dist/dropbox-lnx.x86_64-6.4.14/images" : too short or does
not end with 'icons'

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

[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics

[soee via KDE Bugzilla]

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

--- Comment #2 from soee  ---
I should also mention that doing it from the other side -  switching from intel
to nvidia profile  - does not generate any crash.

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

[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 100326
  --> https://bugs.kde.org/attachment.cgi?id=100326=edit
ksmserver-20160726-175540.kcrash.txt

Crash report.

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

[ksmserver] [Bug 366156] New: ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics

[soee via KDE Bugzilla]

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

Bug ID: 366156
   Summary: ksmserver crashes when switching from nvidia to intel
profile/GPU on laptop with hybrid graphics
   Product: ksmserver
   Version: 5.7.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: kont...@soee.pl

Each time i try to switch GPU profile from nvidia to intel on a laptop with
Optimus technology the ksmserver crashes. 

I think this started since upgrade to Plasma 5.7 or latest Frameworks
(5.23/5.24).

Reproducible: Always

Steps to Reproduce:
1. Work/have nvidia GPU set as active on your machine
2. Using nvidia-settings GUI or command line change GPU profile to intel
3. Try to logout and login again (as it it required to make the changes work)
4. After Logout button is clicked ksmserver crashes

Actual Results:  
ksmserver crashes when trying to logout after we try to switch from nvidia to
intel GPU profile. Having the crash window visible (without decorations) we can
save stack trace and/or click on "Restart application" button and sometimes
clicking it moves us to sddm and sometimes screen becomes unresponsive.

Expected Results:  
After GPU profile is changed from nvidia to intel and we click on Logout
button, we should be moved to sddm without any crashes.

I have attached crash report so it might help finding the problem source.

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

[frameworks-plasma] [Bug 365947] New: Icons inside toolbutton are not centered vertically/horizontally

[soee via KDE Bugzilla]

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

Bug ID: 365947
   Summary: Icons inside toolbutton are not centered
vertically/horizontally
   Product: frameworks-plasma
   Version: 5.24.0
  Platform: Neon Packages
   URL: http://i.imgur.com/6PkUAIW.jpg
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: kont...@soee.pl

Icons inside toolbutton are not centered vertically/horizontally (close button
for notification or windows in present mode)

Reproducible: Always

Steps to Reproduce:
1. Load some element that uses toolbutton, it can be dummy (notify-send test)
or real notification or trigger the present windows effect (and hover one of
them)
2. The tollbutton for closing those elements has icon inside that is not
centered vertically/horizontally
3.

Actual Results:  
Icon inside  toolbutton is not centered v/h

Expected Results:  
Icon inside  toolbutton should be centered v/h

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

[plasmashell] [Bug 365706] New: Dialog position is not updated properly

[soee via KDE Bugzilla]

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

Bug ID: 365706
   Summary: Dialog position is not updated properly
   Product: plasmashell
   Version: 5.7.1
  Platform: Neon Packages
   URL: https://www.youtube.com/watch?v=BUTgDLr-Kkg
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: kont...@soee.pl

As shown on the video, after one panel is resized the dialog postion on smaller
panel is not updated and there is an empty space between panel and opened
dialog (like systray extended view or kicker). This might be related to multi
screen setup.

Reproducible: Always

Steps to Reproduce:
1. Create 2 panels at the bottom of the screens
2. Make one panel higher or smaller than the second one
3. Open systray extended view or kicker on smaller panel and observe empty
space between panel and dialog.

Actual Results:  
There is an epty space between panel and dialog.

Expected Results:  
Dialog shoudl always stick to the panel.

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

[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor

[soee via KDE Bugzilla]

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

--- Comment #12 from soee  ---
Created attachment 100035
  --> https://bugs.kde.org/attachment.cgi?id=100035=edit
WORKING plasma-org.kde.plasma.desktop-appletsrc

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

[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor

[soee via KDE Bugzilla]

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

--- Comment #13 from soee  ---
Created attachment 100036
  --> https://bugs.kde.org/attachment.cgi?id=100036=edit
PANEL MOVED plasma-org.kde.plasma.desktop-appletsrc

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

[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

 CC||kont...@soee.pl

--- Comment #11 from soee  ---
This problem exists sometimes after system reboot - panel from my laptop screen
jumps to connected screen and covers the one that exists there. 

I was asked to post 'working' plasma-org.kde.plasma.desktop-appletsrc file
content and after panel jumps/is moved to wrong screen. So check the attached
files for them.

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

[Discover] [Bug 365150] Running Discover for the first time - see not too detailed message about Appstream

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 99886
  --> https://bugs.kde.org/attachment.cgi?id=99886=edit
Current message rendered in Discover

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

[Discover] [Bug 365150] New: Running Discover for the first time - see not too detailed message about Appstream

[soee via KDE Bugzilla]

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

Bug ID: 365150
   Summary: Running Discover for the first time - see not too
detailed message about Appstream
   Product: Discover
   Version: 5.6.95
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kont...@soee.pl

If we run Discover for the first time we will see hilighted message: "Please
make sure that Appstream is properly setup on your system". This message
doesn't explain how/what to do to check if Appstream is ssetup as it should.
Please add more detailed message what steps user should take to make sure all
is configured as required by Discover.

Reproducible: Always

Steps to Reproduce:
1. Run Discover first time

Actual Results:  
See simple message "Please make sure that Appstream is properly setup on your
system"

Expected Results:  
We shoudl see more detailed message that explains what user has to do to check
the setup.

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

[plasmashell] [Bug 342873] After removing a second panel with taskbar, windows still animate minimization into it

[soee via KDE Bugzilla]

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

--- Comment #7 from soee  ---
This bug exists in Plasma 5.7.

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

[plasmashell] [Bug 365137] Application minimizing animation direction points to the removed task manager instance

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

Summary|Application minimizing  |Application minimizing
   |animation is rendered to|animation direction points
   |the removed task manager|to the removed task manager
   |instance|instance

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

[plasmashell] [Bug 365137] Application minimizing animation is rendered to the removed task manager instance

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

Summary|Application minimaizng  |Application minimizing
   |animation is rendered to|animation is rendered to
   |the removed taska manager   |the removed task manager
   |instance|instance

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

[plasmashell] [Bug 365137] New: Application minimaizng animation is rendered to the removed taska manager instance

[soee via KDE Bugzilla]

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

Bug ID: 365137
   Summary: Application minimaizng animation is rendered to the
removed taska manager instance
   Product: plasmashell
   Version: 5.6.95
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: kont...@soee.pl
CC: plasma-b...@kde.org

I have 2 screens setup: latop + external monitor connected through hdmi. Both
screens have separate panels with tasks managers configured a bit different. 

I have application runnig on screen 2. Than i have added new default panel on
screen 1 and removed it. Now my application minimize effect direction points to
removed panel/task manager so ot is completly wrong :)

Reproducible: Always

Steps to Reproduce:
1. Run some app and have it displayed on current panel task manager
2. Add next/new defaulr panel to the desktop
3. Remove this new panel

Actual Results:  
Running application will be minimized to the direction of removed panel - task
manager it contained not the existing instance.

Expected Results:  
Application should be minimized to the existing task manager instance on the
current screen not removed one.

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

[plasmashell] [Bug 365097] Krunner has broken shadow / corners

[soee via KDE Bugzilla]

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

--- Comment #6 from soee  ---
Created attachment 99875
  --> https://bugs.kde.org/attachment.cgi?id=99875=edit
Other dropdowns have the same problem

The dropdown in panel settings has the same issue.

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

[plasmashell] [Bug 365097] Krunner has broken shadow / corners

[soee via KDE Bugzilla]

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

--- Comment #5 from soee  ---
I don't know why but this problem is back. It was working fin for some time but
all of sudden is roken again and i'm not sure why :/

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

[plasmashell] [Bug 365111] Widgets explorer is missing a lot of icons for its items

[soee via KDE Bugzilla]

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

--- Comment #3 from soee  ---
Created attachment 99862
  --> https://bugs.kde.org/attachment.cgi?id=99862=edit
Missing icons in widgets explorer

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

[plasmashell] [Bug 365111] Widgets explorer is missing a lot of icons for its items

[soee via KDE Bugzilla]

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

--- Comment #2 from soee  ---
(In reply to Marco Martin from comment #1)
> screenshot?

There is a link to video in this bug report but ok here is the screenshot:

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

[plasmashell] [Bug 365111] New: Widgets explorer is missing a lot of icons for its items

[soee via KDE Bugzilla]

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

Bug ID: 365111
   Summary: Widgets explorer is missing a lot of icons for its
items
   Product: plasmashell
   Version: 5.6.95
  Platform: Neon Packages
   URL: https://youtu.be/yYed-56WJmw
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kont...@soee.pl
CC: bhus...@gmail.com, plasma-b...@kde.org

As presented on the video (see attached link) widgets  explorer items are
missing their unique icons. We see blank document icons instead.

Reproducible: Always

Steps to Reproduce:
1. Open widgets explorer
2. See a lot of missing icons (white document icon instead)
3.

Actual Results:  
We see a lot of missing icons wor presented widgets.

Expected Results:  
Each widget in the explorer shoudl have own, unique icon.

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

[plasmashell] [Bug 365097] Krunner has broken shadow / corners

[soee via KDE Bugzilla]

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

--- Comment #4 from soee  ---
Indeed it was cache issue. I have removed ~/.cache and /var/tmp/kdecache-$USER
and the problem is gone.

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

[plasmashell] [Bug 365099] New: Settings window - scrollbar for smaller window covers buttons

[soee via KDE Bugzilla]

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

Bug ID: 365099
   Summary: Settings window - scrollbar for smaller window covers
buttons
   Product: plasmashell
   Version: 5.6.95
  Platform: Neon Packages
   URL: http://i.imgur.com/Fo6tBVM.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: kont...@soee.pl

If we open Systray settings window and got to Elements section, than if
scrollbar is rendered (for smaller sized window) it hovers the 'cancel' buttons
for shortcuts (see attached screenshot).

Reproducible: Always

Steps to Reproduce:
1. Open Systray settings window
2. Go to Elements section 
3. If scrollbar isnot visible, make teh window a bit smaller to have it
4. Observe how the scrollbar covers buttons

Actual Results:  
'Cancel' buttons are partially covered by scrollbar.

Expected Results:  
Scrollbar should be rendered next to buttons not cover them.

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

[plasmashell] [Bug 365097] New: Krunner has broken shadow / corners

[soee via KDE Bugzilla]

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

Bug ID: 365097
   Summary: Krunner has broken shadow / corners
   Product: plasmashell
   Version: 5.6.95
  Platform: Neon Packages
   URL: http://i.imgur.com/8qUPVhm.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kont...@soee.pl
CC: bhus...@gmail.com, plasma-b...@kde.org

As attached image shows, krunner widget has broken corner / shadows.

Reproducible: Always

Steps to Reproduce:
1. Run krunner
2. See broken corners / shadows

Actual Results:  
Two bottom corners are broken and makes teh shadow looks broken.

Expected Results:  
Whole shadow around krunner widget shoudl be visible without whitespaces.

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[soee via KDE Bugzilla]

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

--- Comment #25 from soee  ---
(In reply to Jasem Mutlaq from comment #24)
> On KDE Neon with latest packages, Meta+Tab switches the next activity
> correctly.

Try to assign custom shortcuts for each activity.

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[soee via KDE Bugzilla]

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

--- Comment #21 from soee  ---
Created attachment 99655
  --> https://bugs.kde.org/attachment.cgi?id=99655=edit
2 activities with shortcutsassigned

As you can see on the screen, i have 2 activities defined with shorcuts for
each of them (it was hard to assign them from activities inspector but i did it
through shortcuts module). This shortcuts dont have any effect though.

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

 CC||kont...@soee.pl

--- Comment #20 from soee  ---
Activities shortcuts does nto work on Neon - Plamsma 5.6.5 and Frameworks 5.23.
I think this was broken somewhere in Frameworks 5.23 as on Kubutnu it wrked
pretty well (Plasma 5.6.4 + Frameworks 5.22).

Please reopen this bug.

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

[plasmashell] [Bug 352345] Quick activity switch makes it use wrong wallpaper

[soee via KDE Bugzilla]

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

--- Comment #5 from soee  ---
I should add that the quick switch also makes desktop widgets in activities to
be gone.

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

[plasmashell] [Bug 352345] Quick activity switch makes it use wrong wallpaper

[soee via KDE Bugzilla]

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

--- Comment #4 from soee  ---
Bug still exists in Plasma 5.6.3.

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

[Discover] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied

[soee via KDE Bugzilla]

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

--- Comment #61 from soee  ---
@Adam Kubuntu developers are doing what they can to make system stable and fix
bugs they can fix but atm. all the resources are focused on 16.04 release. As
you know this bug is fixed in Xenial and it is strongly recommended to update
to LTS when it is released (tomorrow) as it will also get new Plasma etc.

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

[kdeplasma-addons] [Bug 360777] Due to faulty configuration desktop loading time is ~20 seconds longer

[soee via KDE Bugzilla]

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

--- Comment #2 from soee  ---
I have switched GPU profile from nvidia to intel and this happend again. After
i removed file mentioned in my first comment, bootking time is super fast
again.

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

[kdeplasma-addons] [Bug 360777] New: Due to faulty configuration desktop loading time is ~20 seconds longer

[soee via KDE Bugzilla]

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

Bug ID: 360777
   Summary: Due to faulty configuration desktop loading time is
~20 seconds longer
   Product: kdeplasma-addons
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: kont...@soee.pl

After some updates and testing various widgets i have noticed that my desktop
is loading ~ 20 seconds longer (screen after sddm) - progress bar  reaches 100%
and than waits mention time. 

To track down the issue i have removed whole .config folder. It helped but than
i go further and located 'faulty' file. It was:
`./config/plasma-org.kde.plasma.desktop-appletsrc`. And again going deeper i
faound the problem inside following configuration (removing it solved the
loading time problem):

[Containments][114]
activityId=795e1540-a8a7-486f-a0f4-f5c2ef8f9e0c
formfactor=0
immutability=1
lastScreen=1
location=0
plugin=org.kde.desktopcontainment
wallpaperplugin=org.kde.image

And related configuration to this path: [Containments][114] in this file is
also:

[Containments][114][Applets][112]
immutability=1
plugin=org.kde.plasma.analogclock

[Containments][114][Applets][112][Configuration][ConfigDialog]
DialogHeight=660
DialogWidth=880

[Containments][114][ConfigDialog]
DialogHeight=660
DialogWidth=880

[Containments][114][General]
ItemsGeometries=Applet-112:1600,816,224,192,0;
ToolBoxButtonState=topright
ToolBoxButtonX=1883
pressToMove=false
showToolbox=false

[Containments][114][Wallpaper][org.kde.image][General]
FillMode=2
Image=file:///home/soee/ownCloud/Zdjęcia/Tapety/1920x1080 (2).png
height=1080
width=1920

The only wrong thing i noticed here (from my point of view) is path to not
existing image: Image=file:///home/soee/ownCloud/Zdjęcia/Tapety/1920x1080
(2).png - i have removed whole ownCloud dir in my home folder some time ago
(btw. shouldn't such invalid images path be handled/removed by Plasma
automatically?). But removing this
[Containments][114][Wallpaper][org.kde.image][General] part from configuration
didn't solve the loading time problem so some other part of pasted
configuration causes it.

We have some ToolBox related configuration here - i don't know itf it is
important but the ToolBox (old cashew) i have disabled by default.


Reproducible: Always

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

 CC||kont...@soee.pl

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

[muon] [Bug 358018] New: Updates icon stays visible in systray when all updates were installed

[soee via KDE Bugzilla]

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

Bug ID: 358018
   Summary: Updates icon stays visible in systray when all updates
were installed
   Product: muon
   Version: 5.5.3
  Platform: Kubuntu Packages
   URL: https://youtu.be/K3esuhuXK6o
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: notifier
  Assignee: echidna...@kubuntu.org
  Reporter: kont...@soee.pl
CC: aleix...@kde.org, sit...@kde.org

If there are some updates available we can see icon in systray that informs us
about it. If we install those updates this icon stays visible in systray until
next login.

There is laso other problem: if we run `apt update` command and it shows us
that there are some new updates, this icon in systray still will show
information that system is up to date.

Reproducible: Always

Steps to Reproduce:
1. Check if notifier shows icon in systray tat informs about  new updates
2. Install updates
3. Icon will stay visible in systray while it should get hidden

Actual Results:  
Notifier systray icon is visible after all updates were installed.

Expected Results:  
Notifier icon should be hidden in systray (available in extened systray view)
when there are no updates.

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

[plasmashell] [Bug 358009] New: Task Manager has problems with rendering its items when placed on a panel in different screen adges

[soee via KDE Bugzilla]

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

Bug ID: 358009
   Summary: Task Manager has problems with rendering its items
when placed on a panel in different screen adges
   Product: plasmashell
   Version: 5.5.3
  Platform: Kubuntu Packages
   URL: https://youtu.be/avLxs6koHJg
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: kont...@soee.pl
CC: plasma-b...@kde.org

If we place Task Manager or Icons Only Task Manager (they probably share some
code) on a panel and start moving panel to different screen adges, than Task
Manager starts to have problems with rendering its items.

- if we move to left screen edge, than its items loose spacing 
- if we move to different edge (top on video) than Icons Only Task Manager have
horizontal spaces but Task Manager doesn't
- if we move panel again (right screen edge on video), spaces are lost again
and Tasks Managers items have also different width (different margins from
panel edges). If we start hovering itmes with mouse cursor than horizontal
spaces starts to render and items width starts to fix itslef

Please watch video for detailed overview of the issue.

Reproducible: Always

Steps to Reproduce:
1. Put Icons Only Task Manager or Task Manager on pael
2. Start moving panel to different screen edges
3. Observ problems with Task Manager items rendering

Actual Results:  
Task Manager / Icons Only Task Manager does not render its items the same way
when panel is moved across desktop.

Expected Results:  
Task Manager / Icons Only Task Manager should always render its items the same
way - no matter where panel is placed/moved.

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

[plasmashell] [Bug 358009] Task Manager has problems with rendering its items when placed on a panel in different screen adges

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Also: as you can see on the video, the items contour isn't updated as it should
when Task Manager chnages position.

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

[dolphin] [Bug 352097] Dolphin Version 15.08.0 trash strange behavior after deleting files.

[soee via KDE Bugzilla]

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

--- Comment #14 from soee  ---
Looks like the problem is gone with Frameworks 5.18.

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

[plasmashell] [Bug 357835] Hard to resize panel when in vertical mode

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Small update: i think this started to happen after upgrade to Frameworks 5.18
bit i'm not 100% sure.

There are also other visual issues when panel is in horizontal view like task
manager items are missing spaces and this worked fine on Frameworks 5.17.

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

[plasmashell] [Bug 357835] New: Hard to resize panel when in vertical mode

[soee via KDE Bugzilla]

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

Bug ID: 357835
   Summary: Hard to resize panel when in vertical mode
   Product: plasmashell
   Version: 5.5.3
  Platform: Kubuntu Packages
   URL: https://www.youtube.com/watch?v=x1iIDnL-0j0
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: kont...@soee.pl

If we make our panel vertical (move it to the left screen edge) there are
problems when resizing it. For egzample if we make it wider and wan't lower
size after that (the same action) we can't. But if we  make few attempts
increase/decrease size it starting to change it but there are visual glitches -
please see attached viedeo.

Reproducible: Always

Steps to Reproduce:
1. Move panel to left screen edge
2. Make it wider
3. Try lowering size

Actual Results:  
We can't lower size or after several attempts the gui starts to flickering.

Expected Results:  
Panel should smoothly change size like it does when in horizontal mode.

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

[kdeplasma-addons] [Bug 357699] New: Disk Quota widget does nothing and is missing icon etc.

[soee via KDE Bugzilla]

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

Bug ID: 357699
   Summary: Disk Quota widget does nothing and is missing icon
etc.
   Product: kdeplasma-addons
   Version: 5.5.3
  Platform: Kubuntu Packages
   URL: https://www.youtube.com/watch?v=HciTJC1DuMQ=yo
utu.be
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: kont...@soee.pl

Disk Quota widget shows no content and has not icon in widgets explorer or in
systray settings. Please see attached video for details.

Reproducible: Always

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

[plasmashell] [Bug 357704] Muon notifier crashes on apt package list updates

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

 CC||kont...@soee.pl

--- Comment #1 from soee  ---
I can confirm this problem.

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

[muon] [Bug 357613] New: Misleading notification after updates installation

[soee via KDE Bugzilla]

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

Bug ID: 357613
   Summary: Misleading notification after updates installation
   Product: muon
   Version: 5.5.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: notifier
  Assignee: echidna...@kubuntu.org
  Reporter: kont...@soee.pl
CC: aleix...@kde.org, sit...@kde.org

Notification title and body text rendered after all updates are installed are
misleading. Title says "System update available" and the body text "System up
to date". So the title should be changed to something like "All updates have
been installed" and body text "Your system is now up to date"

Reproducible: Always

Steps to Reproduce:
1. If there are some updates pending, just appy them
2. Wait for notification to be rendered


Actual Results:  
Notification with title "System update available" and the body text "System up
to date" is rendered.

Expected Results:  
Notification title should be changed to mach current system state - all updates
are installed.

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

[muon] [Bug 357613] Misleading notification after updates installation

[soee via KDE Bugzilla]

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

--- Comment #1 from soee  ---
Created attachment 96485
  --> https://bugs.kde.org/attachment.cgi?id=96485=edit
Shows mentioned notification

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