[Breeze] [Bug 363147] Breeze cursors should have more sizes, and support arbitrary sizes if possible

[bugzilla_noreply]

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

--- Comment #22 from fanzhuyi...@gmail.com ---
*** Bug 477489 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 363147] Breeze cursors should have more sizes, and support arbitrary sizes if possible

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

Summary|Breeze cursors should have  |Breeze cursors should have
   |more sizes (patch included) |more sizes, and support
   ||arbitrary sizes if possible

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 363147] Breeze cursors should have more sizes (patch included)

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

--- Comment #21 from fanzhuyi...@gmail.com ---
477489 asks for arbitrary cursor sizes.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 363147] Breeze cursors should have more sizes (patch included)

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||puspitaadak9...@gmail.com

--- Comment #20 from fanzhuyi...@gmail.com ---
*** Bug 477489 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

r...@alum.mit.edu changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #18 from r...@alum.mit.edu ---
This has not happened to me in quite some time.  I'm fine with it being closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 377357] configurable timer setting to turn off the keyboard's backlight

[bugzilla_noreply]

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

--- Comment #10 from a.v.sh...@gmail.com ---
(In reply to Kai Uwe Broulik from comment #9)
> Splitting out the keyboard backlight into a separate action would also
> enable us to dim the keyboard while keeping the screen on, like when a video
> player forces the screen on, you probably still want the keyboard backlight
> to turn off as to not be distracting.

Yes, exactly the case that I have. Keyboard backlight is too bright on my
laptop, and when watching a video in a dark room I have to turn it off
manually.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 377357] configurable timer setting to turn off the keyboard's backlight

[bugzilla_noreply]

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

a.v.sh...@gmail.com changed:

   What|Removed |Added

 CC||a.v.sh...@gmail.com

--- Comment #7 from a.v.sh...@gmail.com ---
I think that it's good to have an ability to control keyboard backlight
auto-dimming independently from screen auto-dimming. Not even for power saving
purposes. Some applications prevent screen dimming, like watching video. But at
the same time you don't need keyboard backlight when you watch a video, it
could even be distracting in a dark environment. I think this commit
https://invent.kde.org/arrowdodger/powerdevil/-/commit/5ec53c84a59357782c34cda7ca7dde8938491cbb
might be solving this, but it seems no merge request was ever opened for it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[systemsettings] [Bug 357456] Power management should allow both locking and blanking screen

[bugzilla_noreply]

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

gudv...@gmail.com changed:

   What|Removed |Added

 CC||gudv...@gmail.com

--- Comment #6 from gudv...@gmail.com ---
It is sad that you still need to write scripts to make a workarounds for that.

And even then it doesn't work as it should. For example, if you set idle time
for too long and someone touches keyboard or mouse you'll end up with lit up
screen that just burns pixels.
For that to actually work there should be significantly lower delay to power
off screen when it is still locked.

That looks like small thing but it pisses me off on a daily basis.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 374311] it is too easy to activate context menu item if mouse moves during right-click

[bugzilla_noreply]

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

--- Comment #15 from krzmb...@gmail.com ---
Okay thanks. Guess that means we're stuck with this until KDE switches to Qt 6.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 374311] it is too easy to activate context menu item if mouse moves during right-click

[bugzilla_noreply]

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

--- Comment #13 from krzmb...@gmail.com ---
What is the status of this? I am still having this issue but all Qt bug reports
I found on this were closed for one reason or another.

Generally speaking though I think another solution would be to straight off
disable selecting anything using the right mouse button. You can't trigger
regular buttons with the right mouse button, so why should you be able to
select a context menu entry with it?
Idk if this is something that you even have control of or whether this (too) is
something that has to be fixed on Qt's side.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kwrited] [Bug 429652] [Feature Request] Notification applet should also save images

[bugzilla_noreply]

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

--- Comment #3 from yuan...@live.com ---
(In reply to yuannan from comment #2)
> I've been a silly willy, this should go in the clipboard applet board. I've
> filed a feature request for notifications and must have gotten them
> confused. 
> 
> What I meant by this is that the clipboard applet has a history of your
> copied texts and it would be neat to have pictures saved in the history as
> well.

I've just had a look and they already have this as a feature. Sorry for this,
please close this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kwrited] [Bug 429652] [Feature Request] Notification applet should also save images

[bugzilla_noreply]

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

--- Comment #2 from yuan...@live.com ---
I've been a silly willy, this should go in the clipboard applet board. I've
filed a feature request for notifications and must have gotten them confused. 

What I meant by this is that the clipboard applet has a history of your copied
texts and it would be neat to have pictures saved in the history as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kwrited] [Bug 429652] New: [Feature Request] Notification applet should also save images

[bugzilla_noreply]

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

Bug ID: 429652
   Summary: [Feature Request] Notification applet should also save
images
   Product: kwrited
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: yuan...@live.com
  Target Milestone: ---

SUMMARY

Not sure if this is the right section so feel free to move this if need be.


STEPS TO REPRODUCE
1. Open kde notifcation applet
2. Look at how you don't have images
3. cry and then go on bugs.kde.org


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.20.3-1
(available in About System)
KDE Plasma Version: 5.20.3-1
KDE Frameworks Version: 5.76.0-1
Qt Version: 5.15.2-1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 372955] Enabling "Suspend session" doesn't suspend session.

[bugzilla_noreply]

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

swagfortr...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #2 from swagfortr...@gmail.com ---
I can no longer reproduce this bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348082] monitor is randomly powered back on

[bugzilla_noreply]

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

--- Comment #13 from fr.fr...@gmail.com ---
I'm now using Gentoo, with:
kde-plasma/powerdevil-5.20.3

The problem seems to be really tied to the mouse itself.
It's actually a trackball:
Kensington Slimblade Trackball

I have to disconnect the trackball from its USB bus to not get randomly
woken-up.

It doesn't appear to be a powerdevil bug.

Maybe implementing or documenting a finer granularity on what events can
wake-up the system would allow to ignore mouse events. But that's just a
wish-list item.

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[systemsettings] [Bug 357456] Power management should allow both locking and blanking screen

[bugzilla_noreply]

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

--- Comment #4 from r...@alum.mit.edu ---
Bug 427990 is not the same request as this.  That one is asking for a way to
turn off the screen on the fly; this request is about behavior when a laptop
lid is closed.

Bug 312425 is partly a bug, and partly a request for something unrelated to
this (focus policy when unlocking the screen).

Bug 423174 is related, but not specifically about laptop lid behavior.  It's
more closely related than the others, but isn't really the same, either,
although the solution could be the same.  However, I might not want to tie
screen blanking to screen locking in general; my request here is related solely
to laptop lid behavior.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[ksysguard] [Bug 361281] migrate away from qtwebkit (gui)

[bugzilla_noreply]

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

gr...@kde.org changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
 CC||gr...@kde.org

--- Comment #3 from gr...@kde.org ---
This has happened some time in the past nearly-four years. (The bug Martin
refers to has been fixed since Qt 5.10, it seems)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 350365] Battery monitor in tray randomly shows there is no battery

[bugzilla_noreply]

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

antsupov.v...@gmail.com changed:

   What|Removed |Added

 CC||antsupov.v...@gmail.com

--- Comment #51 from antsupov.v...@gmail.com ---
Just had this happen on my Acer laptop, definitely not a Lenovo only thing

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 340137] Implement support for window groups (window tabs) in Breeze

[bugzilla_noreply]

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

kouka...@gmail.com changed:

   What|Removed |Added

 CC||kouka...@gmail.com

--- Comment #10 from kouka...@gmail.com ---
I am in need of this feature. I have not updated to KDE5 because of it. I
really hope someone will implement it, as I don't have the skills to do it
myself. I am sure that there will be many users to find peace.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

--- Comment #28 from goodmi...@goodmirek.com ---
(In reply to arne anka from comment #27)
> (In reply to goodmirek from comment #25)
> > (In reply to arne anka from comment #22)
> > > (In reply to goodmirek from comment #19)
> > > > arne anka: The issue seems to be there is not enough people able to
> > > > contribute their manpower or money to buy such a manpower.
> > > > If I create an issue for this bug on bountysource.com and add $50 
> > > > bounty,
> > > > how much will you contribute?
> > > 
> > > @goodmirek: well, I'm prepared to offer between 50 and 100.
> > 
> > I have just created an issue for this bug on bountysource.com and added $50
> > bounty.
> > Please feel free to make your contributions here:
> > https://www.bountysource.com/issues/72539369-turn-off-screen-after-lock-
> > screen
> 
> Got only just now to checking out bountysource.com -- they only offer
> PayPal, and PayPal is a No-Go. I wouldn't touch that particular company with
> a ten-foot-pole.
> If you have an idea how I can add my share in a sane and trustworthy way,
> let me know.

Bountysource.com might be able to accept donations in ETH.

Anyway, the conditions did not change since me and arne anka made an agreement
to make a donation. I have kept my part of the promise.
I believe anyone who wants to complain about a state of any FOSS project should
first contribute their effort and/or money.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

--- Comment #26 from goodmi...@goodmirek.com ---
(In reply to Nate Graham from comment #24)
> *** Bug 405344 has been marked as a duplicate of this bug. ***

The bug 405344 is not a duplicate of this bug 348529, although it is related.
The bug 405344 might need to be solved in order to make a fix for this bug
348529 working.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

goodmi...@goodmirek.com changed:

   What|Removed |Added

Version|5.3.1   |5.15.4

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

--- Comment #25 from goodmi...@goodmirek.com ---
(In reply to arne anka from comment #22)
> (In reply to goodmirek from comment #19)
> > arne anka: The issue seems to be there is not enough people able to
> > contribute their manpower or money to buy such a manpower.
> > If I create an issue for this bug on bountysource.com and add $50 bounty,
> > how much will you contribute?
> 
> @goodmirek: well, I'm prepared to offer between 50 and 100.

I have just created an issue for this bug on bountysource.com and added $50
bounty.
Please feel free to make your contributions here:
https://www.bountysource.com/issues/72539369-turn-off-screen-after-lock-screen

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

--- Comment #19 from goodmi...@goodmirek.com ---
arne anka: The issue seems to be there is not enough people able to contribute
their manpower or money to buy such a manpower.
If I create an issue for this bug on bountysource.com and add $50 bounty, how
much will you contribute?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery

[bugzilla_noreply]

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

hiwatari.se...@gmail.com changed:

   What|Removed |Added

 CC||hiwatari.se...@gmail.com

--- Comment #34 from hiwatari.se...@gmail.com ---
I am also having this problem.

upower -d

Device: /org/freedesktop/UPower/devices/line_power_ADP1
  native-path:  ADP1
  power supply: yes
  updated:  Sa 15 Dez 2018 22:37:07 CET (1277 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  no
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:  BAT1
  model:G71C000JQ110
  serial:   6
  power supply: yes
  updated:  Sa 15 Dez 2018 22:58:23 CET (1 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
energy:  30,802 Wh
energy-empty:0 Wh
energy-full: 30,802 Wh
energy-full-design:  36,024 Wh
energy-rate: 2,28 W
voltage: 11,4 V
time to empty:   13,5 hours
percentage:  100%
capacity:85,5041%
technology:  lithium-ion
icon-name:  'battery-full-symbolic'
  History (rate):
1544911103  2,280   unknown
1544911102  2,228   discharging
1544911101  2,416   discharging
1544911100  2,468   discharging
1544911099  2,661   discharging
1544911044  2,728   discharging

Device: /org/freedesktop/UPower/devices/battery_BAT2
  native-path:  BAT2
  model:G71C000JQ510
  serial:   6
  power supply: yes
  updated:  Sa 15 Dez 2018 22:58:23 CET (1 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
energy:  29,298 Wh
energy-empty:0 Wh
energy-full: 31,521 Wh
energy-full-design:  36,024 Wh
energy-rate: 2,28 W
voltage: 11,4 V
time to empty:   12,9 hours
percentage:  92%
capacity:87,5%
technology:  lithium-ion
icon-name:  'battery-full-symbolic'
  History (charge):
1544911094  92,000  discharging
  History (rate):
1544911103  2,280   unknown
1544911102  2,228   discharging
1544911101  2,416   discharging
1544911100  2,468   discharging
1544911099  2,661   discharging
1544911044  2,719   discharging

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Sa 15 Dez 2018 22:58:23 CET (1 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   discharging
warning-level:   none
energy:  60,1 Wh
energy-full: 62,323 Wh
energy-rate: 4,56 W
time to empty:   13,2 hours
percentage:  96,4331%
icon-name:  'battery-full-symbolic'

Daemon:
  daemon-version:  0.99.9
  on-battery:  yes
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: PowerOff

--

And my journal is spammed with the following two error messages:


file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:43:39:
Unable to assign [undefined] to bool
Dez 15 23:00:29 linux-ti0n plasmashell[23869]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:53:39:
Unable to assign [undefined] to int

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules

[bugzilla_noreply]

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

--- Comment #5 from battagli...@gmail.com ---
Finally, I note the problem may result from a discrepancy between upower and
acpi. Note the following terminal results. Both of these are in the state where
the AC is not plugged in, but the tray icon still says discharging (even though
battery panel icon says discharging):

$ acpi -V
Battery 0: Discharging, 50%, 01:55:40 remaining
Battery 0: design capacity 5006 mAh, last full capacity 4092 mAh = 81%
Adapter 0: off-line  <- NOTE HERE
Thermal 0: ok, 40.0 degrees C
Thermal 0: trip point 0 switches to mode hot at temperature 240.0 degrees C
Thermal 1: ok, 35.3 degrees C
Thermal 1: trip point 0 switches to mode hot at temperature 60.0 degrees C
Thermal 2: ok, 0.0 degrees C
Thermal 2: trip point 0 switches to mode hot at temperature 97.0 degrees C
Thermal 3: ok, 38.0 degrees C
Thermal 3: trip point 0 switches to mode hot at temperature 54.0 degrees C
Cooling 0: x86_pkg_temp no state information available
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: intel_powerclamp no state information available
Cooling 4: pch_skylake no state information available
Cooling 5: Processor 0 of 10
Cooling 6: Processor 0 of 10


Note that Adapter 0 is offline. On the other hand, here's upower -u. Note
Adapter 0 (line_power_ADP1) is ONLINE!

~ $ upower -d
Device: /org/freedesktop/UPower/devices/line_power_ADP1
  native-path:  ADP1
  power supply: yes
  updated:  Thu 05 Jul 2018 12:54:02 AM EDT (2262 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes  <- SEE HERE
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:  BAT1
  vendor:   SMP
  model:X910527
  serial:   39135
  power supply: yes
  updated:  Thu 05 Jul 2018 01:31:23 AM EDT (21 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
energy:  15.547 Wh
energy-empty:0 Wh
energy-full: 31.192 Wh
energy-full-design:  38.152 Wh
energy-rate: 7.507 W
voltage: 7.567 V
time to empty:   2.1 hours
percentage:  49%
capacity:81.7572%
technology:  lithium-ion
icon-name:  'battery-good-symbolic'
  History (charge):
1530768666  49.000  discharging
  History (rate):
1530768683  7.507   discharging
1530768682  18.735  charging
1530768675  7.695   discharging
1530768666  8.580   discharging

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Thu 05 Jul 2018 01:31:23 AM EDT (21 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   discharging
warning-level:   none
energy:  15.547 Wh
energy-full: 31.192 Wh
energy-rate: 7.507 W
time to empty:   2.1 hours
percentage:  49%
icon-name:  'battery-good-symbolic'

Daemon:
  daemon-version:  0.99.4
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules

[bugzilla_noreply]

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

--- Comment #4 from battagli...@gmail.com ---
Created attachment 113772
  --> https://bugs.kde.org/attachment.cgi?id=113772=edit
All charging

One more - now things are plugged in. Note that the tray icon is "charging",
and now the battery icon in the panel dropdown is also "charging." In the
previous screenshot, the battery icon in the panel dropdown was the normal
"discharging" battery.

However, crucially, in both cases, the battery tray icon was charging -- even
though it is only really charging in this one and not the last one. The tray
icon seems to dictate which power management behaviors are followed, so that it
always does AC mode even if discharging.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules

[bugzilla_noreply]

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

--- Comment #3 from battagli...@gmail.com ---
Created attachment 113771
  --> https://bugs.kde.org/attachment.cgi?id=113771=edit
Battery inconsistency

Note the tray icon still has the battery in AC mode, even though it is listed
as "Discharging" in the panel.

More importantly, the power management settings still respond as if the AC were
plugged in. I want it to auto-suspend only if battery is discharging and not
suspend if AC is plugged in. The result here is that it thinks the AC is
plugged in, discharges, and drains the battery.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 361708] System stuck in ac-plugged in mode ignoring Power management rules

[bugzilla_noreply]

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

battagli...@gmail.com changed:

   What|Removed |Added

 CC||battagli...@gmail.com

--- Comment #2 from battagli...@gmail.com ---
Same exact issue - on Neon Xenial running Plasma 5.13. `acpi` and `upower` will
show the battery charge/discharge status correctly responding to AC plug on/off
events, but the plasmashell battery icon will remain on "plugged in" mode even
if I unplug.

Strangely, sometimes the battery icon will still say "plugged in," even though
when I click on the battery, it still says "discharging". Screenshot attached
below.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

gade...@gmail.com changed:

   What|Removed |Added

 CC||gade...@gmail.com

--- Comment #15 from gade...@gmail.com ---
gnome-shell does this natively. In KDE, user is still forced to write a script
for this and attach it to lock screen even notification trigger.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 343580] All look and feel, icons, theme are not configurable and all icons are gone

[bugzilla_noreply]

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

jarlgjess...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from jarlgjess...@gmail.com ---
Thanks problem is solved now!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy

[bugzilla_noreply]

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

adr.fant...@gmail.com changed:

   What|Removed |Added

 CC||adr.fant...@gmail.com

--- Comment #5 from adr.fant...@gmail.com ---
This is still relevant. GNOME uses it and it works beautifully, especially for
screen rotation for tablets and 2-in-1 laptops. An example implementation is
given by:
https://github.com/mrquincle/yoga-900-auto-rotate

KDE will sooner or later need to have an autorotation feature and
iio-sensor-proxy really seems the right way forward.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 349795] nfs kio produces "Internal error in server RPC error 3"

[bugzilla_noreply]

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

ti...@zukunft.com changed:

   What|Removed |Added

 CC||ti...@zukunft.com

--- Comment #1 from ti...@zukunft.com ---
Same with a Netgear NAS and Kubuntu 17.04

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 304696] Display is dimmed in half the time you configure to dim

[bugzilla_noreply]

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

--- Comment #12 from da-kdebugs...@abelonline.de ---
This is still open. Setting "Dim screen" to "3 min" makes the display dim after
90s (instead of 180s). Unchecking "Dim screen" disables dimming, so it is
likely due to this setting.

System settings 5.11.3 on KDE neon.

Can't believe this has been open for 5+ years.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 304696] Display is dimmed in half the time you configure to dim

[bugzilla_noreply]

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

da-kdebugs...@abelonline.de changed:

   What|Removed |Added

 CC||da-kdebugs...@abelonline.de

--- Comment #11 from da-kdebugs...@abelonline.de ---
Created attachment 108874
  --> https://bugs.kde.org/attachment.cgi?id=108874=edit
Screenshot of dim screen setting

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 382097] New: Powerdevil config window too big and unresizable

[bugzilla_noreply]

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

Bug ID: 382097
   Summary: Powerdevil config window too big and unresizable
   Product: Powerdevil
   Version: 5.10.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: domenico.iezzi@gmail.com
  Target Milestone: ---

Created attachment 106491
  --> https://bugs.kde.org/attachment.cgi?id=106491=edit
Screenshot of the powerdevil settings

Powerdevil settings windows is too big for 1366x768 screens, the buttons fall
under the bottom bar. The window is unresizable, so the only way to apply
changes in settings it to switch tab (for example from Energy Saving to
Activity Settings).
I added a screenshot as attachment to show the problem.

* OS: Arch Linux
* linux: 4.11.9
* plasma-desktop: 5.10.3
* powerdevil: 5.10.3

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 381199] Broken brightness control with kernel module (ex. nvidia-bl)

[bugzilla_noreply]

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

--- Comment #2 from vsnrain@gmail.com ---
it returns "raw"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 381199] New: Broken brightness control with kernel module (ex. nvidia-bl)

[bugzilla_noreply]

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

Bug ID: 381199
   Summary: Broken brightness control with kernel module (ex.
nvidia-bl)
   Product: Powerdevil
   Version: 5.10.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: vsnrain@gmail.com
  Target Milestone: ---

Overview:
Since 5.10, it is no longer possible to adjust brightness on my system, which
requires special kernel module for brightness to work. I tried to look at what
caused this, and found that in following commit 
https://cgit.kde.org/powerdevil.git/commit/?id=86c3548d103ff5966366788220796de629be9230
Was attempt to add feature that powerdevil will control only brightness of
active device. Part of relevant code is following:

/daemon/backends/upower/backlighthelper.cpp
bool BacklightHelper::isRawBacklightEnabled(const QString )
{
QFile file(BACKLIGHT_SYSFS_PATH + interface + "/device/enabled");

if (!file.open(QIODevice::ReadOnly | QIODevice::Text)) {
return false;
}

QByteArray buffer = file.readLine().trimmed();
if (buffer == "enabled") {
return true;
   }

return false;
}

As you can see, it was implemented by skipping all brightness devices which in
BACKLIGHT_SYSFS_PATH + interface + "/device/enabled" does not return "enabled".
The problem is, there is no property "device/enabled" in my nvidia_backlight
device:

ls -la /sys/class/backlight/nvidia_backlight/  
total 0
drwxr-xr-x 3 root root0 Jun  2 22:50 .
drwxr-xr-x 3 root root0 Jun  2 22:50 ..
-r--r--r-- 1 root root 4096 Jun  2 23:02 actual_brightness
-rw-r--r-- 1 root root 4096 Jun  2 23:02 bl_power
-rw-r--r-- 1 root root 4096 Jun  2 22:54 brightness
-r--r--r-- 1 root root 4096 Jun  2 22:50 max_brightness
drwxr-xr-x 2 root root0 Jun  2 23:02 power
lrwxrwxrwx 1 root root0 Jun  2 22:50 subsystem ->
../../../../class/backlight
-r--r--r-- 1 root root 4096 Jun  2 22:50 type
-rw-r--r-- 1 root root 4096 Jun  2 22:50 uevent

so powerdevil tries to open this file, fails, and always skips this brightness
device. I recompiled powerdevil with "return true" in mentioned function, and
brightness control works again, so it seems that problem in indeed in this
part.

Steps to Reproduce:
use kernel module for brightness device, tested on Nvidia GF 9400M with
nvidia-bl kernel module.

Actual Results:
powerdevil always skips brightness device, because it cannot open file
/sys/class/backlight/nvidia_backlight/device/enabled, which does not exist.

Expected Results:
register and control brightness device.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[bugzilla_noreply]

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

--- Comment #4 from lordgearian2...@gmail.com ---
Have run kdeinit5 nothing relevant information came up with that. Best
guess right now it that there needs to be a look into the protocols that
samsung lg and other brands are using for their devices. Since they cater
to Microsoft they are using something the runs on a Microsoft driver and or
protocol.

On Jun 13, 2017 11:09 AM, "Christoph Feck"  wrote:

> https://bugs.kde.org/show_bug.cgi?id=379680
>
> --- Comment #3 from Christoph Feck  ---
> To further investigate this issue, KDE developers need the information
> requested in comment #1. If you can provide it, or need help with finding
> that
> information, please add a comment.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 381114] New: Can't control brightness

[bugzilla_noreply]

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

Bug ID: 381114
   Summary: Can't control brightness
   Product: Powerdevil
   Version: 5.10.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: sun...@hotmail.ru
  Target Milestone: ---

Notebook. Trying to change brightness with plasma shell applet or automaticly
doesn't work. It works with cli though: echo 7 | sudo tee
/sys/class/backlight/acpi_video0/brightness

It did work before, unfortunately i don't remember what was the last working
version.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://

[bugzilla_noreply]

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

--- Comment #32 from vlao...@gmail.com ---
For me (MTP protocol with Nexus 5), action "paste" is disabled only when folder
have no files. I have installed kio-extras 17.0.4 and kio 5.34.0-r2

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://

[bugzilla_noreply]

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

--- Comment #30 from johan.claudebreunin...@gmail.com ---
The protocol is MTP.

With the an up to date Arch Linux install.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #45 from maxp...@gmail.com ---
I have discovered that konqueror works fine. I can make folders with it, change
names etc. Nothing is greyed out in the root share.

This is without any patch or anything.

Interestingly enough konquerors file management is supposedly provided by
dolphin:

https://forum.kde.org/viewtopic.php?f=22=127884#p374651

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #43 from madc...@atlas.cz ---
(In reply to Luca Beltrame from comment #30)
> If you want the developers to look at the patch, please submit it to
> https://phabricator.kde.org. Patches in Bugzilla unfortunately tend to get
> lost.

Is it just me or is there currently no obvious way how to get a phabricator
account? Thanks...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #41 from tempel.jul...@gmail.com ---
Would this patch also fix the behavior that files like large videos are first
copied to the client system before they can be watched?
This is another _HUGE_ restriction of the current Samba share support of KDE.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #39 from madc...@atlas.cz ---
(In reply to Christoph Feck from comment #37)
> > kio_smb sets the permissions on the UDSEntries correctly but Dolphin seems 
> > to have a mind of its own.
> 
> In other words, using Dolphin copying fails, but using "kioclient5 cp" works?

I just got it to happen again and yes, this is exactly the case. The patch to
set the UDSEntry access still seems to be needed but it is not the only issue
at play here.

It seems that it may have something to do with login credentials. This is how I
managed to trigger the problem:

I accessed a share that is usually unwritable. In this particular instance
everything seemed to be OK and I could write into it through Dolphin. I opened
a directory in that share and got asked for my login credentials again for some
reason. Until I OK'ed the creds prompt, the "Create new" item in the rightclick
menu in Dolphin was greyed out. When I returned back to the share's root, the
write access to it from Dolphin was gone by kioclient worked. Weird...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #38 from madc...@atlas.cz ---
Created attachment 105687
  --> https://bugs.kde.org/attachment.cgi?id=105687=edit
Debugging patch

If there is anybody able to reproduce the problem reliably, there is a small
testing patch that dumps the access permissions set by smb_kio into the system
log.

In order to see the debugging info, launch "kdebugdialog5", make sure that
"kio_smb" is checked, restart Dolphin, try to access your samba shares and post
the output of "journalctl -b | grep kio_smb". systemd-less distributions might
dump the info into the terminal instead.

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #36 from madc...@atlas.cz ---
Thanks, I figured that the logs are dumped through systemd already. This still
does not answer the question where does Dolphin get the access permissions info
from. Either some other layer messes with them along the way or the
UDSEntry::ACCESS is not the source of access permissions used by Dolphin. As
far as the debug output tells me, kio_smb with my patch sets the access
permissions correctly.

I believe that this is the actual root cause of the problem. I gave it a quick
spin on another machine at work where this has been acting up and somehow
miraculously I could write into the usually unwritable share this morning. Note
that the machine runs vanilla Fedora 25 with no custom patches anywhere.

As far as I can tell *something* randomly makes the root share look unwritable
for whatever reason.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #34 from madc...@atlas.cz ---
There has got to be something else going in. kio_smb sets the permissions on
the UDSEntries correctly but Dolphin seems to have a mind of its own.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

madc...@atlas.cz changed:

   What|Removed |Added

 Attachment #105680|0   |1
is obsolete||

--- Comment #29 from madc...@atlas.cz ---
Comment on attachment 105680
  --> https://bugs.kde.org/attachment.cgi?id=105680
Allow write access to root samba share

>diff --git a/smb/kio_smb_browse.cpp b/smb/kio_smb_browse.cpp
>index 67e2fa09..7092e41c 100644
>--- a/smb/kio_smb_browse.cpp
>+++ b/smb/kio_smb_browse.cpp
>@@ -381,7 +381,7 @@ void SMBSlave::listDir( const QUrl& kurl )
>udsentry.insert( KIO::UDSEntry::UDS_FILE_TYPE, S_IFDIR );
> 
>// Set permissions
>-   udsentry.insert(KIO::UDSEntry::UDS_ACCESS, (S_IRUSR | S_IRGRP 
>| S_IROTH | S_IXUSR | S_IXGRP | S_IXOTH));
>+   udsentry.insert(KIO::UDSEntry::UDS_ACCESS, (S_IRWXU | S_IRWXG 
>| S_IROTH | S_IXOTH));
> 
>if (dirp->smbc_type == SMBC_SERVER) {
>// QString workgroup = m_current_url.host().toUpper();

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #28 from madc...@atlas.cz ---
Created attachment 105683
  --> https://bugs.kde.org/attachment.cgi?id=105683=edit
Patched Arch Linux PKGBUILG

Archers are welcome to try this patched PKGBUILD.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #27 from madc...@atlas.cz ---
Created attachment 105682
  --> https://bugs.kde.org/attachment.cgi?id=105682=edit
Allow write access to root samba share

The code still does not work entirely as expected - I am allowed to try to
write into server shares or workgroup listing which is obviously nonsensical
and the code seems to try to prevent that, it just does not work. I cannot
investigate this any further unless I can pry some debugging output out of the
smb_kio plugin. The problem of unwritable share root seems to be gone though.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #25 from madc...@atlas.cz ---
Created attachment 105680
  --> https://bugs.kde.org/attachment.cgi?id=105680=edit
Allow write access to root samba share

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #24 from madc...@atlas.cz ---
Getting any debug output from kio_smb has proven to be next to impossible so I
took a bit of an educated guess. Can you guys try the attached patch, it seems
to work for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://

[bugzilla_noreply]

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

johan.claudebreunin...@gmail.com changed:

   What|Removed |Added

 CC||johan.claudebreuninger@gmai
   ||l.com

--- Comment #28 from johan.claudebreunin...@gmail.com ---
Problem still exists in  kio-extras 17.04.1-1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #16 from r...@alum.mit.edu ---
Happened again in charge_state_changed.

This *may* have been at the time my laptop reached full charge but I have no
logs.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

madc...@atlas.cz changed:

   What|Removed |Added

 CC||madc...@atlas.cz

--- Comment #23 from madc...@atlas.cz ---
I believe I have been seeing this too but in a somewhat different setup. There
are multiple shares with different access permissions set up on the server in
question. I have no problems accessing my de-facto "home" folder, I do,
however, get no write access to another folder even though the permissions set
by Samba and the underlying FS seem to be correct. If I either mount the share
manually or try to write to in from Windows there is no problem.

Here is a relevant excerpt from smb.conf:
[home] # This one works
path = /mnt/storage/home
valid users = @ECHMET_Users
browsable = yes
writable = yes
read only = no
force create mode = 600
force directory mode = 700
create mask = 700
directory mask = 700

[everyone] # This gets no write access through KIO
path = /mnt/storage/everyone
valid users = @ECHMET_Users
browsable = yes
writable = yes
read only = no
force create mode = 660
force directory mode = 770
create mask = 660
directory mask = 770
force group = ECHMET_Users

KF5 5.34, KDE Apps 17.04.1, up-to-date Arch Linux.

Since I need this working quite badly at work, can anybody at least point me
where to look in the SMB KIO source?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379902] Samba shares no longer work

[bugzilla_noreply]

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

eva...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379902] Samba shares no longer work

[bugzilla_noreply]

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

--- Comment #2 from eva...@gmail.com ---
Thanks for your reply - I had left the office before I read it. I had to reboot
my laptop into Windows at home to use a specific piece of software so obviously
I have a fresh boot of Mint this morning, and the bookmarks are working again.
I did install a few updates yesterday. Should have tried restarting, but I just
followed the instructions :)

Sorry for wasting time - now resolved - possibly an issue with updated to Mint
KDE installed between 14 May and 16 May?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 379858] Windows open too small

[bugzilla_noreply]

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

--- Comment #2 from fr...@hmrt.nl ---
Ok, will do. But are you sure? It is happening with almost all apps in plasma.
Do they really all make the same mistake?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #15 from r...@alum.mit.edu ---
And another one, involving chargePercentChanged.  The laptop had been on AC for
an extended period of time prior, and was likely at 100% charged, but that
doesn't mean that ACPI can't report changes.

Installing all of the debuginfo packages is a pain, but would installing the
debuginfo for libKF5Solid alone be helpful?

#0  0x7ff626da413b in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x7ff626d2962a in malloc () from /lib64/libc.so.6
#2  0x7ff6270e7e38 in operator new(unsigned long) () from
/usr/lib64/libstdc++.so.6
#3  0x7ff62876765d in QQmlProperty::QQmlProperty(QObject*, QString const&)
() from /usr/lib64/libQt5Qml.so.5
#4  0x0040c65e in ?? ()
#5  
#6  0x7ff626d26634 in _int_free () from /lib64/libc.so.6
#7  0x7ff621144097 in QDBusUtil::isValidBusName(QString const&) () from
/usr/lib64/libQt5DBus.so.5
#8  0x7ff62111a721 in QDBusConnection::connect(QString const&, QString
const&, QString const&, QString const&, QStringList const&, QString const&,
QObject*, char const*) () from /usr/lib64/libQt5DBus.so.5
#9  0x7ff62111b013 in QDBusConnection::connect(QString const&, QString
const&, QString const&, QString const&, QObject*, char const*) () from
/usr/lib64/libQt5DBus.so.5
#10 0x7ff6135ee28a in ?? () from /usr/lib64/libKF5Solid.so.5
#11 0x7ff6135eac04 in ?? () from /usr/lib64/libKF5Solid.so.5
#12 0x7ff6135bf87e in
Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#13 0x7ff5f83324b4 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#14 0x7ff5f8333255 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#15 0x7ff62766871c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#16 0x7ff61361fc06 in Solid::Battery::chargePercentChanged(int, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#17 0x7ff613622817 in ?? () from /usr/lib64/libKF5Solid.so.5
#18 0x7ff6276680d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#19 0x7ff61361f726 in ?? () from /usr/lib64/libKF5Solid.so.5
#20 0x7ff6135f0c5d in ?? () from /usr/lib64/libKF5Solid.so.5
#21 0x7ff613621a2d in ?? () from /usr/lib64/libKF5Solid.so.5
#22 0x7ff6276680d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#23 0x7ff613628ce3 in ?? () from /usr/lib64/libKF5Solid.so.5
#24 0x7ff62112549b in ?? () from /usr/lib64/libQt5DBus.so.5
#25 0x7ff627669886 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#26 0x7ff62764030c in QCoreApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Core.so.5
#27 0x7ff627640245 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#28 0x7ff6276422a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#29 0x7ff62768f043 in ?? () from /usr/lib64/libQt5Core.so.5
#30 0x7ff623230134 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#31 0x7ff623230388 in ?? () from /usr/lib64/libglib-2.0.so.0
#32 0x7ff62323042c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#33 0x7ff62768e88c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#34 0x7ff62763e6ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#35 0x7ff627646344 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#36 0x00409bf4 in ?? ()
#37 0x7ff626cce6e5 in __libc_start_main () from /lib64/libc.so.6
#38 0x00409e49 in _start ()

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #14 from r...@alum.mit.edu ---
Happened again:

#0  0x7ff984e2d13b in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x7ff984db262a in malloc () from /lib64/libc.so.6
#2  0x7ff985170e38 in operator new(unsigned long) () from
/usr/lib64/libstdc++.so.6
#3  0x7ff9867f065d in QQmlProperty::QQmlProperty(QObject*, QString const&)
() from /usr/lib64/libQt5Qml.so.5
#4  0x0040c65e in ?? ()
#5  
#6  0x7ff984daf0b6 in _int_free () from /lib64/libc.so.6
#7  0x7ff984db1980 in _int_realloc () from /lib64/libc.so.6
#8  0x7ff984db2daf in realloc () from /lib64/libc.so.6
#9  0x7ff985590897 in QString::reallocData(unsigned int, bool) () from
/usr/lib64/libQt5Core.so.5
#10 0x7ff9855910d4 in QString::append(QString const&) () from
/usr/lib64/libQt5Core.so.5
#11 0x7ff97f1aa292 in ?? () from /usr/lib64/libQt5DBus.so.5
#12 0x7ff97f1ac253 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x7ff97f1ac464 in ?? () from /usr/lib64/libQt5DBus.so.5
#14 0x7ff97f1a4013 in QDBusConnection::connect(QString const&, QString
const&, QString const&, QString const&, QObject*, char const*) () from
/usr/lib64/libQt5DBus.so.5
#15 0x7ff97582212b in ?? () from /usr/lib64/libKF5Solid.so.5
#16 0x7ff97581ec04 in ?? () from /usr/lib64/libKF5Solid.so.5
#17 0x7ff9757f387e in
Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#18 0x7ff9513a24b4 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#19 0x7ff9513a3255 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#20 0x7ff9856f171c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#21 0x7ff975853c06 in Solid::Battery::chargePercentChanged(int, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#22 0x7ff975856817 in ?? () from /usr/lib64/libKF5Solid.so.5
#23 0x7ff9856f10d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#24 0x7ff975853726 in ?? () from /usr/lib64/libKF5Solid.so.5
#25 0x7ff975824c5d in ?? () from /usr/lib64/libKF5Solid.so.5
#26 0x7ff975855a2d in ?? () from /usr/lib64/libKF5Solid.so.5
#27 0x7ff9856f10d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#28 0x7ff97585cce3 in ?? () from /usr/lib64/libKF5Solid.so.5
#29 0x7ff97f1ae49b in ?? () from /usr/lib64/libQt5DBus.so.5
#30 0x7ff9856f2886 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#31 0x7ff9856c930c in QCoreApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Core.so.5
#32 0x7ff9856c9245 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#33 0x7ff9856cb2a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#34 0x7ff985718043 in ?? () from /usr/lib64/libQt5Core.so.5
#35 0x7ff9812b9134 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#36 0x7ff9812b9388 in ?? () from /usr/lib64/libglib-2.0.so.0
#37 0x7ff9812b942c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#38 0x7ff98571788c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#39 0x7ff9856c76ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#40 0x7ff9856cf344 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#41 0x00409bf4 in ?? ()
#42 0x7ff984d576e5 in __libc_start_main () from /lib64/libc.so.6
#43 0x00409e49 in _start ()

Again, I don't know this code, but there are some commonalities about the stack
traces:

1) They're always in a signal handler that's invoking
QQmlProperty::QQmlProperty, allocating memory.

2) Above the signal handler, they're allocating or freeing memory (not really
all that surprising; most versions of malloc aren't re-entrant).

3) Above that there are a variety of things, but they all seem to happen from
Solid::Battery::chargePercentChanged or Solid::Battery::chargeStateChanged.

In this case -- it hasn't always been true -- I had just driven home from work
with the laptop suspended, so the battery would have run down a bit.  I had
plugged it back in, resumed it, checked email, and then shut the lid (locking
the screen, but not suspending the laptop).  The hang happened about 10 minutes
after I first resumed it, so it's certainly possible that the laptop's charge
percent might have changed.  In other cases, though, it happened overnight,
when the laptop was surely fully charged.  That doesn't guarantee that the
charge state isn't changing, though.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #20 from tempel.jul...@gmail.com ---
Two other workarounds:
1.:
Mount a networkfolder to make it look like it was local to Plasma.
Via terminal:
sudo mount -t cifs -o
username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770
//hostname.local/sharename/ /home/user/mountfolder/

Permanent via fstab:
//hostname.local/sharename/ /home/user/mountfolder/ cifs
defaults,username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0
2

Or 2.:
Install a GTK file browser like Thunar with gvfs + gvfs-smb (+gnome-keyring for
saving login data). With it you can drag & drop stuff from and into SMB shares
or open media files without having to fully copy them first.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #18 from mathoj...@gmail.com ---
(In reply to Christoph Feck from comment #17)
> If it was easy to fix, someone actually (still?) using Samba could
> trace/analyze the code and check where it fails.
> 
> Otherwise we cannot even confirm _where_ the bug is, so no need to change
> the bug status.
> 
> Note that I know of no KDE developer using Samba, so unless someone steps
> in, this will probably not be fixed.

@Christoph Feck

Hello Christoph,

If none of KDE developers are making use of Samba, what network file sharing
protocol are they using ?
NFS ? No, NFS is not implemented an integrated in Plasma at all.

I can't believe that they don't use any NAS or Network Multimedia Drives.

The status is that, if you have a NAS (so you need to copy/paste drag
files into it, from your computer), you should avoid KDE Plasma.

It's a very bad signal !

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

maxp...@gmail.com changed:

   What|Removed |Added

 CC||maxp...@gmail.com

--- Comment #16 from maxp...@gmail.com ---
openSUSE 42.2 here and can confirm I also have this bug.

I have literally wasted hours messing around with smb.conf and trying various
permission states.

I am disappointed to see this as "unconfirmed" but glad to see others have the
same issue as me and its not just something I was doing wrong.

I have an opensuse server, a windows desktop and an opensuse laptop.

Windows desktop seems to be able to access the server and read/write just fine.

Opensuse laptop with KDE has issues and cannot write to the root level dirctory
as others have mentioned.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #15 from mathoj...@gmail.com ---
Thank you, I use a workaround too : I use ftps ;)

But using a workaround is not a deal. And I really think that a network
protocols should have a high priority in a DE. More and more NAS, multimedia
servers ... are making use of :
- SMB (bad implementation on KDE)
- NFS (not implemented in KDE... incredible, but true)
- DLNA/uPnP : there was a kio package for that, but I never successed to use it

It's really not serious for a DE. I don't know how all of this is working on
Gnome (never tried, because I'm an early fan of KDE, and plasma), but network
protocols are a just weak and poor on KDE, and it's a big anomaly.


I still hope a developper will fix it (and if he could work on NFS, and
DLNA/uPnP  would be great)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

tempel.jul...@gmail.com changed:

   What|Removed |Added

 CC||tempel.jul...@gmail.com

--- Comment #14 from tempel.jul...@gmail.com ---
I have found a workaround:
When you login with "*" for both user and password for a share which doesn't
require a password, add another "*" to the adress.
Example: You have opened a share and the adress looks like this:
smb://*@pcname/sharename/

Change it to
smb://*:*@pcname/sharename/
and press enter. Voila, you should have write access.

Can this please get fixed? It should be so easy and it's really annoying...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #13 from r...@alum.mit.edu ---
That's not likely what happened here; this most often happens overnight when I
had shut the laptop's lid, and it's not right after I shut it either (I have my
lid set to lock when shut, not suspend).

I wasn't able to induce this behavior.  The problem is that the lock sequence
must consist of at least two keys (main key and modifier), and as soon as one
of the keys is touched during the grace period, the screen unlocks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #10 from r...@alum.mit.edu ---
Note that frame 5 is a signal handler, so it's hardly surprising that frame 4
and frame 7 are unrelated.

I don't know this code, but it sure looks to me like something (in the second
trace, isValidBusName; in the first case, probably something different but I
didn't have debug symbols installed) was in the middle of free'ing something,
during which time kscreenlocker_greet() received a signal, and the signal
handler did a new QQmlProperty while the memory allocator was locked by the
free() called synchronously above it, so we have a deadlock.

My own guess -- and obviously this isn't my code -- is that something in
kscreenlocker_greet has set a signal handler (possibly a timeout) that is
allocating memory -- a no-no, unless you're using a re-entrant version of
malloc.

I'm pretty certain I had the right -debuginfo packages installed; rpm does the
version checking quite well.  And I don't think it's bad memory either; the
problem is consistently within the signal handler within kscreenlocker_greet,
and I don't see any other indications of bad memory on the system.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #7 from r...@alum.mit.edu ---
Still happens with kscreenlocker (and powerdevil) 5.9.4.

It's rare, so I can't reproduce it reliably.  And I don't have the debuginfo
packages -- my normal source for KDE packages doesn't have the debuginfo
packages so I have to go back to download.opensuse.org and download them
specially for doing this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 378606] Please replace those childish avatar images

[bugzilla_noreply]

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

--- Comment #8 from slartibar...@gmail.com ---
I added screenshots of previous avatar icons, perfectly in harmony with breeze
icon set. Something like this should remain the default, not some random choice
out of a list. (just my 2 cents)

@Jens.. please add some penguins to the avatar list, would be fun! (seriously)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 378606] Please replace those childish avatar images

[bugzilla_noreply]

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

--- Comment #7 from slartibar...@gmail.com ---
Created attachment 104948
  --> https://bugs.kde.org/attachment.cgi?id=104948=edit
avatar2

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 378606] Please replace those childish avatar images

[bugzilla_noreply]

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

--- Comment #6 from slartibar...@gmail.com ---
Created attachment 104947
  --> https://bugs.kde.org/attachment.cgi?id=104947=edit
avatar1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 378606] Please replace those childish avatar images

[bugzilla_noreply]

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

--- Comment #4 from slartibar...@gmail.com ---
Agreed, 
it's not your fault if distros choose silly avatar icons.

I mean, the samples you showed in http://i.imgur.com/eOZn8D8.png are the
problem i am speaking of. No offence, but why are the blue/green icons the ones
chosen by default (esp. the 'user' icon)?
What about a more 'technical' looking avatar/icon that is taken first?

See, you/the plasma team have come to great lengths choosing an appropriate
style for the whole user experience. The icon sets, the themes, the colors...
maybe not to everyones taste, but uniform (btw, i like it!)

And now, we start greeting a first time user to plasma with the blue/green user
avatar? A hairless bloke with a big nose
I have no problem choosing another avatar, but you should think of new users of
the plasma DE and their first impressions. The 'other' DE's are a bit more on
the 'serious side', you can select - even silly - images if you don't agree to
the default avatar. But the default looks just suitable to the rest of the DE
experience.

I completely agree with funny or silly avatar icon sets. Please keep them in
the selection. I don't even mind the hairless bloke in the list. But give the
users a fitting initial choice and don't rely on the distributions to provide
proper avatars.

I mean, take the previous (<5.9.4) technical avatar image consisting of just
circles. Clean, fitting to the breeze icon set. Just... OK. Not fancy, nothing
too shiny. And gender neutral.

Even if you - as a user - wouldn't care about avatars you weren't forced to
change it, because it was a technical thing and not disturbing. Now, every time
you open the application-kicker menu or lock the screen, this blue/green avatar
thingy grins at you.

I have the feeling, that now you push users to make an active approach into
changing this.
If this was the intention, then you succeeded...


Please do understand: I am very happy with the new plasma experience, the
modifications and the experiments and their implications. For example, it also
took some time for the logoff dialog to become what it is today.
I see this avatar stuff pretty similar, it will change eventually into
something proper.
But as far as i am concerned, i would opt for a 'breezy' looking avatar as a
default. Something non-disturbing when you open menus or lock your screen. This
shouldn't be too hard, should it? Just take the old one for starters

Anyway, thanks for the comments!
I didn't expect a discussion to start, so please accept my apologies if the
initial bugticket was too harsh. But i think opinions need to be shared...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #10 from mathoj...@gmail.com ---
Hello,

Just wondering... Why is this bug still in "UNCONFIRMED" Status ?? The bug has
been reported here many times, and on duplicates as well...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery

[bugzilla_noreply]

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

--- Comment #15 from gust...@angulosolido.pt ---
Note: the attached tarball contents belong to the plasmoid that got installed
directly from the KDE UI as a user. I then located it in the home folder, put
it into a tarball, deinstalled using the KDE UI and tried to put it system wide
at /usr/share/plasma/plasmoids (which worked). 

I don't know exactly where KDE downloads it from.

Tested with Ubunty 16.04 and KDE LTS backport from the Kubuntu repositiories.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery

[bugzilla_noreply]

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

--- Comment #14 from gust...@angulosolido.pt ---
Created attachment 104918
  --> https://bugs.kde.org/attachment.cgi?id=104918=edit
alternative widget Batterytime

alternative widget Batterytime

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery

[bugzilla_noreply]

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

--- Comment #13 from gust...@angulosolido.pt ---
I still have this problem with KDE 5.8.5 LTS and I confirmed it really is a
problem with powerdevil because an alternative widget works fine.

I'm attaching the widget that I have confirmed that works. It only needs to be
untarred at:

/usr/share/plasma/plasmoids

and then it can be added to the system tray.

In short: the original battery monitor from KDE seems to fail randomly. The
attached one works everytime.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 378498] New: Power settings missing scrollbar

[bugzilla_noreply]

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

Bug ID: 378498
   Summary: Power settings missing scrollbar
   Product: Powerdevil
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: t...@gmx.com
  Target Milestone: ---

Created attachment 104907
  --> https://bugs.kde.org/attachment.cgi?id=104907=edit
power settinng missing scroll bar

On smaller laptop screens the settings for power drop off the screen. You can't
access the bottom section of the power settings window. There is no scroll bar
and the window is not resizing. Even on full screen you can't access all
details.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 363147] Breeze cursors should have more sizes (patch included)

[bugzilla_noreply]

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

--- Comment #13 from andreas.sturmlech...@gmail.com ---
I can see where the web interface would limit you like that, but that shouldn't
happen if you had a clone of the repository, worked in a branch and submitted
your diff using arcanist.

Seems like https://community.kde.org/Infrastructure/Github_Mirror needs an
update as well though, as it still mentions reviewboard and rbtools instead of
phabricator...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 363147] Breeze cursors should have more sizes (patch included)

[bugzilla_noreply]

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

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

--- Comment #11 from andreas.sturmlech...@gmail.com ---
(In reply to James Lee from comment #10)
> So that's how it's going to be.  Guess I won't be contributing to KDE
> anymore.

That would be sad. FYI: https://github.com/KDE

"Official mirror of the KDE project. To contribute code to these repositories,
please see https://community.kde.org/Infrastructure/Github_Mirror;

Bugzilla is good for bug reports, but that's really it; where was the problem,
did you use arcanist for trying to upload your changes?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 377513] New: Wayland sometimes doesn't recover from standby

[bugzilla_noreply]

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

Bug ID: 377513
   Summary: Wayland sometimes doesn't recover from standby
   Product: Powerdevil
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: m...@etruscott.co.uk
  Target Milestone: ---

Wayland doesn't always recover from standby successfully.  I instead get a
blackscreen with a pointer that doesn't respond to input.  Its not possible to
switch to any other terminals either as keyboard input doesn't work.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

mathoj...@gmail.com changed:

   What|Removed |Added

 CC||mathoj...@gmail.com

--- Comment #5 from mathoj...@gmail.com ---
I notice it :
 - When there are files or directories in the shared folder, I can't don't have
write access to the root of the shared folder.

 - When the shared folder is empty (no files, no folders), then I have write
acces to the root of the shared folder.

 - In subfolders of the shared folder, I almost always have write access.


Thank you

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 377357] New: configurable timer setting to turn off the keyboard's backlight

[bugzilla_noreply]

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

Bug ID: 377357
   Summary: configurable timer setting to turn off the keyboard's
backlight
   Product: Powerdevil
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: ar...@protonmail.com
  Target Milestone: ---

I'm running Mint 18.1 KDE on a 2012 MacBook Pro and would love a setting
allowing the keyboard to stay lit for, say 15s of inactivity (no keyboard or
mouse/trackpad input) and then turn off.

Thanks :D

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 376601] "Leave" overlay does not respect Polkit rule

[bugzilla_noreply]

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

patrickrif...@yandex.com changed:

   What|Removed |Added

Summary|Plasma 5 "Leave" overlay|"Leave" overlay does not
   |does not respect Polkit |respect Polkit rule
   |rule|

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 376601] New: Plasma 5 "Leave" overlay does not respect Polkit rule

[bugzilla_noreply]

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

Bug ID: 376601
   Summary: Plasma 5 "Leave" overlay does not respect Polkit rule
   Product: Powerdevil
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: patrickrif...@yandex.com
  Target Milestone: ---

When a custom Polkit rule is set to disable sleep and hibernation the buttons
for both sleep and hibernate are removed from the Application Launcher's
"Leave" menu. However, upon selecting an option from the "Leave" menu the
splash screen that appears still has a "Suspend" button (although it doesn't
function). I would recommend that the splash screen respect the same Polkit
rule the Application Launcher does for consistency.

System Information:
OS: Arch Linux x86_64
KDE Plasma Version: 5.9.2
KDE Frameworks Version: 5.31.0
Qt Version: 5.8.0

Polkit rule contents (/etc/polkit-1/rules.d/10-disable-suspend.rules):

polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.login1.suspend" ||
action.id == "org.freedesktop.login1.suspend-multiple-sessions" ||
action.id == "org.freedesktop.login1.hibernate" ||
action.id == "org.freedesktop.login1.hibernate-multiple-sessions")
{
return polkit.Result.NO;
}
});

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 375826] New: Copying files to a remote SFTP folder opens a popup "Could not change permissions.."

[bugzilla_noreply]

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

Bug ID: 375826
   Summary: Copying files to a remote SFTP folder opens a popup
"Could not change permissions.."
   Product: kio-extras
   Version: 5.9.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: default
  Assignee: plasma-devel@kde.org
  Reporter: g...@section9.follonica.org
  Target Milestone: ---

Copying files to a remote SFTP folder will show the popup "Could not change
permissions for sftp://host/path/filename; for each file being copied.

Reproducible: Always

Steps to Reproduce:
1. Copy or move a file to a remote SFTP folder
2. A popup title 'Information - Dolphin' will appear and show the message
'Could not change permissions for sftp://host/path/filename'

Plasma 5.9 / Dolphin 17.03.70

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 375825] New: Please include 1920x1200 size wallpaper

[bugzilla_noreply]

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

Bug ID: 375825
   Summary: Please include 1920x1200 size wallpaper
   Product: Breeze
   Version: 5.9.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: k...@happyjack.org
  Target Milestone: ---

My monitors have a resolution of 1920x1200, which is not an included size with
the Next wallpaper.  If I select Next as the wallpaper, the size 1680x1050 is
chosen, which either results in black bars all around (if it's centered) or a
somewhat fuzzy image (if it's scaled).  In part this is, I believe, a flaw in
the image selection algorithm (see #375824), but given that 1920x1200 is a
not-uncommon monitor resolution, it would make sense to include a 1920x1200.png
with Next.  For what it's worth, it looks like these sizes were included in
Breeze 5.3 and 5.4.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 375457] Low battery applet animation uses a lot of CPU

[bugzilla_noreply]

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

rockonthemoo...@gmail.com changed:

   What|Removed |Added

 CC||rockonthemoo...@gmail.com

--- Comment #1 from rockonthemoo...@gmail.com ---
this is true for animated connecting network interface applet too,
not powerdevil dependent

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery

[bugzilla_noreply]

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

--- Comment #10 from gust...@angulosolido.pt ---
The problem happens after suspend + resume. Situation goes back to normal with:

killplasmashell
kstart plasmashell

The lock screen has a battery monitory that shows no problems.

Any news on getting this fixed?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

--- Comment #14 from k...@web.de ---
If you set the lockscreen timeout to less than the DPMS timeout (-30s), that
effectively reduces the DPMS timeout to the lockscreen timeout (+30s), making
the DPMS timeout setting ineffective. this must somehow be communicated.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 348529] Turn off screen after lock screen

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #11 from k...@web.de ---
A better workaround:
Go to System Settings > Notifications > Event Source: Screen Saver
Click on "Screen locked"
Enable "Run command" and copy this into the text box:
/usr/bin/sleep 2.0 && /usr/bin/xset dpms force off

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 374255] Notes widget icons not visible depending on Notes background and Plasma Shell Dark/Light variant

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #1 from k...@web.de ---
I lack the knowledge about plasmoids to do this, but it seems like the color of
each PlasmaComponents.ToolButton in
/usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml
should be changed from white to black.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 374255] New: Notes widget icons not visible depending on Notes background and Plasma Shell Dark/Light variant

[bugzilla_noreply]

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

Bug ID: 374255
   Summary: Notes widget icons not visible depending on Notes
background and Plasma Shell Dark/Light variant
   Product: Breeze
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: rockonthemoo...@gmail.com
  Target Milestone: ---

I'm pretty sure this bug shouldn't be reported to Breeze - General, but I don't
know where it belongs.
Well, the problem is pretty easy: user cannot see icons in Note widget
depending on the background color of the widget itself and the Dark or Light
variant of Plasma Workspace theme.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 358224] breeze dark plasma look and feel: KDE4 applications are using mixed (light and dark) colors, rendering text unreadable

[bugzilla_noreply]

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

--- Comment #5 from k...@part4.tech ---
(In reply to David Kahles from comment #4)
> (In reply to kde from comment #2)
> > Can this be switched from resolved? I'm having the same issue with Anki
> > which is still using QT4. The problem also effects input fields.
> 
> Do you have this problem only with Anki, or with some KDE applications too?
> Because I remember that Anki hardcodes some colors, and uses some other
> colors from the theme, so it's hard to read with some themes. (On your
> screenshot it looks like Anki hardcodes the font color to black, but uses
> the background color of the theme)
> If that's the case, you should report this bug to Anki.

Thanks. I'll report it upstream.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 358224] breeze dark plasma look and feel: KDE4 applications are using mixed (light and dark) colors, rendering text unreadable

[bugzilla_noreply]

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

--- Comment #3 from k...@part4.tech ---
Created attachment 102279
  --> https://bugs.kde.org/attachment.cgi?id=102279=edit
Image from Anki

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 358224] breeze dark plasma look and feel: KDE4 applications are using mixed (light and dark) colors, rendering text unreadable

[bugzilla_noreply]

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

k...@part4.tech changed:

   What|Removed |Added

 CC||k...@part4.tech

--- Comment #2 from k...@part4.tech ---
Can this be switched from resolved? I'm having the same issue with Anki which
is still using QT4. The problem also effects input fields.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://

[bugzilla_noreply]

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

--- Comment #25 from vlao...@gmail.com ---
(In reply to Elvis Angelaccio from comment #24)
> @vlaomao: you need kio 5.26 or later

I have installed kde-frameworks/kio-5.27.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://

[bugzilla_noreply]

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

vlao...@gmail.com changed:

   What|Removed |Added

 CC||vlao...@gmail.com

--- Comment #23 from vlao...@gmail.com ---
Hello! I have installed:

kde-apps/kdebase-kioslaves-16.04.3-r1
kde-apps/kioclient-16.04.3
kde-apps/kio-extras-16.08.2
kde-apps/plasma-apps-16.08.2
kde-apps/plasma-runtime-16.04.3
kde-frameworks/kio-5.27.0
kde-frameworks/plasma-5.27.0
kde-plasma/bluedevil-5.8.2
kde-plasma/breeze-5.8.2
kde-plasma/kactivitymanagerd-5.8.2
kde-plasma/kde-cli-tools-5.8.2
kde-plasma/kdecoration-5.8.2
kde-plasma/kdeplasma-addons-5.8.2
kde-plasma/kgamma-5.8.2
kde-plasma/khotkeys-5.8.2
kde-plasma/kinfocenter-5.8.2
kde-plasma/kmenuedit-5.8.2
kde-plasma/kscreen-5.8.2
kde-plasma/kscreenlocker-5.8.2
kde-plasma/ksshaskpass-5.8.2
kde-plasma/ksysguard-5.8.2
kde-plasma/kwallet-pam-5.8.2
kde-plasma/kwayland-integration-5.8.2
kde-plasma/kwin-5.8.2
kde-plasma/kwrited-5.8.2
kde-plasma/libkscreen-5.8.2
kde-plasma/libksysguard-5.8.2
kde-plasma/milou-5.8.2
kde-plasma/oxygen-5.8.2
kde-plasma/oxygen-fonts-5.4.3
kde-plasma/plasma-desktop-5.8.2
kde-plasma/plasma-integration-5.8.2
kde-plasma/plasma-meta-5.8.2
kde-plasma/plasma-nm-5.8.2
kde-plasma/plasma-workspace-5.8.2
kde-plasma/plasma-workspace-wallpapers-5.8.2
kde-plasma/polkit-kde-agent-5.8.2
kde-plasma/powerdevil-5.8.2
kde-plasma/sddm-kcm-5.8.2
kde-plasma/systemsettings-5.8.2
kde-plasma/user-manager-5.8.2


I unable to write files to root of internal MTP memory (dolphin show permission
denied message) my Nexus5, BUT i might write files to subfolders, which have
one or more files inside it (drag and drop, CTRL+V, right-click worked)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[KDE Bugtracking System] REMINDER: current Plasma regressions

[bugzilla_noreply]

Please find below a list of the current regressions reported for Plasma. This 
is a weekly reminder.

  This search was scheduled by myr...@kde.org.


Plasma regressions (1 bugs)
--
Bug 301424:
  https://bugs.kde.org/show_bug.cgi?id=301424
Severity: normal
Priority: NOR
  Status: REOPENED
  Resolution: 
 Product: plasma
Keywords: regression
   Component: widget-systemtray
 Version: 4.9.90 Beta2
 Summary: Cannot open battery monitor applet if set to hidden in systray

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel