[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update

2018-11-24 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=398538

Giuseppe Margarita  changed:

   What|Removed |Added

   Keywords||reproducible

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

[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update

2018-11-24 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=398538

--- Comment #6 from Giuseppe Margarita  ---
STEPS TO REPRODUCE
1. You have a pulseaudio sink, let's call it "Stereo Internal Audio", linked to
your sound card and it's the default after a fresh install.
2. Make a new pulseaudio sink, i.e. using PulseEffects, and let's make it the
default sink.
3. Change the volume through keyboard key and PulseEffects default sink is
affected correctly.
4. Let's start a song or a video file and you make sure that the default
PulseEffects sink is used by the application.
5. Change the volume and you will see that PulseEffetcs sink IS NOT affected by
plasma-pa. Volume is changed on the sound card sink: Stereo Internal Audio. You
can also notice that nothing is changed in pulseaudio configuration:
PulseEffects is still the default sink.
6. Stop the reproduction, close the mediaplayer application and change the
volume again. PulseEffects is affected.

OBSERVED RESULT
plasma-pa does not respect the control on the default sink when an audio stream
is reproduced.

EXPECTED RESULT
plasma-pa should always change the volume on the default sink, or at least it
should let you choose the preferred sink to control even if it's not the
default in the pulseaudio config, just like it's done in kmix.

ADDITIONAL INFORMATION
kmix is another volume manager and it lets you choose one sink to control and
volume control always affects that sink even if it's not the default sink.
While the behavior in plasma-pa is clearly a bug because considering that: 

- It does not let you choose a preferred sink to control;
- It lets you switch the default pulseaudio sink changing the pulseaudio
configuration and the sink to be used by all applications

When you set a default sink different from the one associated to the sound card
and reproduce something, it won't control the volume on default sink.

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

[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update

2018-11-22 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=398538

Giuseppe Margarita  changed:

   What|Removed |Added

 CC||giuseppemargar...@gmail.com

--- Comment #4 from Giuseppe Margarita  ---
Hello everyone, same issue reported here:
https://bugs.kde.org/show_bug.cgi?id=400789

The title here has a small mistake. plasma-pa is not changing the default sink,
it's only changing the volume on the first sink (usually the sink linked to the
audio card, i.e. HDMI or Internal Card). In my experience, it was changing
volume on the default sink when nothing was reproduced, but when I play
something, the behavior is the same reported here.

Anyway, you can work around this bug getting rid of plasma-pa and installing
Kmix. Configured in the right way, it can control only one sink chosen by the
user (even a sink not configured as the default). The only lack is that you
can't choose the default sink from the applet, but you can set it from command
line using pacmd set-default-sink.

In your case, set the simultaneous output as the default sink from pacmd and
choose from Kmix to control the simultaneous sink and everything will work.

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

[plasma-pa] [Bug 400789] plasma-pa does not change the volume on the default pulseaudio sink when audio is reproduced

2018-11-07 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=400789

Giuseppe Margarita  changed:

   What|Removed |Added

   Keywords||reproducible

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

[plasma-pa] [Bug 400789] New: plasma-pa does not change the volume on the default pulseaudio sink when audio is reproduced

2018-11-07 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=400789

Bug ID: 400789
   Summary: plasma-pa does not change the volume on the default
pulseaudio sink when audio is reproduced
   Product: plasma-pa
   Version: 5.14.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: giuseppemargar...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
When you change the default pulseudio sink from the one of your sound card to
another (maybe the equalizer or PulseEffetcs), pulseaudio won't control the
volume of the default sink when audio is playing.
It only controls the default sink when no audio is playing.

STEPS TO REPRODUCE
1. You have a pulseaudio sink, let's call it "Stereo Internal Audio", linked to
your sound card and it's the default after a fresh install.
2. Make a new pulseaudio sink, i.e. using PulseEffects, and let's make it the
default sink.
3. Change the volume through keyboard key and PulseEffects default sink is
affected correctly.
4. Let's start a song or a video file and you make sure that the default
PulseEffects sink is used by the application.
5. Change the volume and you will see that PulseEffetcs sink IS NOT affected by
plasma-pa. Volume is changed on the sound card sink: Stereo Internal Audio. You
can also notice that nothing is changed in pulseaudio configuration:
PulseEffects is still the default sink.
6. Stop the reproduction, close the mediaplayer application and change the
volume again. PulseEffects is affected.

OBSERVED RESULT
plasma-pa does not respect the control on the default sink when an audio stream
is reproduced.

EXPECTED RESULT
plasma-pa should always change the volume on the default sink, or at least it
should let you choose the preferred sink to control even if it's not the
default in the pulseaudio config, just like it's done in kmix.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
kmix is another volume manager and it lets you choose one sink to control and
volume control always affects that sink even if it's not the default sink.
While the behavior in plasma-pa is clearly a bug because considering that: 

- It does not let you choose a preferred sink to control;
- It lets you switch the default pulseaudio sink changing the pulseaudio
configuration and the sink to be used by all applications

When you set a default sink different from the one associated to the sound card
and reproduce something, it won't control the volume on default sink.

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

[systemsettings] [Bug 350688] Mouse acceleration setting has no effect with libinput

2017-02-12 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=350688

Giuseppe Margarita <giuseppemargar...@gmail.com> changed:

   What|Removed |Added

 CC||giuseppemargar...@gmail.com

--- Comment #9 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
Acceleration works, but it can't be set below 0:
https://bugs.kde.org/show_bug.cgi?id=350688

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

[Touchpad-KCM] [Bug 357749] [libinput] Pointer acceleration cannot be set below 0

2017-01-27 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=357749

--- Comment #1 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
Same problem to me.
https://bbs.archlinux.org/viewtopic.php?pid=1686729
https://forum.kde.org/viewtopic.php?f=66=138655

libinput is the default library for pointing devices. Please fix this bug.

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

[Touchpad-KCM] [Bug 357749] [libinput] Pointer acceleration cannot be set below 0

2017-01-27 Thread Giuseppe Margarita
https://bugs.kde.org/show_bug.cgi?id=357749

Giuseppe Margarita <giuseppemargar...@gmail.com> changed:

   What|Removed |Added

 CC||giuseppemargar...@gmail.com

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

[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets

2016-02-10 Thread Giuseppe Margarita via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357597

--- Comment #18 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
Did you find out something in my log?
I had to return to set "running: false" in that file because plasmashell
process uses 6-7% of CPU load that seems excessive to me for one network and
CPU monitor widget, even if it's not worse than the other friend.

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


[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets

2016-02-09 Thread Giuseppe Margarita via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357597

--- Comment #6 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
(In reply to David Edmundson from comment #4)
> Some improvement was added in latest frameworks speeding up a certain event
> filter.
> 
> 
> 
> also I need some sort of logs
> 
> Please can you run:
> kquitapp5 plasmashell
> valgrind --tool=callgrind --instr-atstart=no plasmashell
> 
> wait till CPU usage is high then
> 
> callgrind_control -i on
> *wait a  bit*
> callgrind_control -i off
> 
> then quit plasma and upload the relevant callgrind.something.out file.

Have I to do this with "running: visible" in NotificationIcon.qml file?

Ah, please, change status. This bug is not resolved.

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


[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets

2016-02-09 Thread Giuseppe Margarita via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357597

--- Comment #8 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
(In reply to David Edmundson from comment #7)
> without the change.
> 
> also it is marked as being a duplicate of another bug which is tracking a
> practically identical discussion.

OK, I'll do the log when I can.

But this is the first time I try that.
After quitting plasma, where can I find callgrind.something.out file? Same
directory in which I executed Konsole?

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


[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets

2016-02-09 Thread Giuseppe Margarita via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357597

--- Comment #3 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
(In reply to Quantum Five from comment #2)
> Unfortunately I can confirm that KUbuntu is also affected ...
> 
> I am running KUbuntu 15.10 with all available patched applied from
> ppa:kubuntu-ppa/backports. My plasmashell version is 5.5.3 and I am using
> System Load widget. Interestingly is that after several hours the widget
> becomes completely unresponsive (but I can launch the program it via K menu).
> 
> I use my system for day to day work and I can confirm that after 8 hours the
> CPU usage is rather high (~30%) when no other programs are running (and you
> can feel that your computer has become sluggish). Killing and restarting
> plasmashell always cures it (I can provide a screen shot of "before" and
> "after"). It's VERY obvious.
> 
> Last Friday I left the computer running over the weekend (my session running
> and locked with no screen saver, no programs running), and when I logged
> back in on Monday, the CPU usage was so high, couldn't do anything but
> restart it.
> 
> My desktop has a 8 x Intel Core i7-4770 CPU @ 3.4 GHz CPU and 16G of RAM. So
> it's certainly not an old and slow machine.
> 
> I hope you guys will now believe that this is indeed a KDE issue.
> 
> Thank you.

Hi, I find a workaround on my Arch Linux system.

Open NotificationIcon.qml file with root permission in
/usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui

Search for line 
"running: visible"
in "PlasmaComponents.BusyIndicator" section and change it in
"running: false"

After that, plasmashell should use only 4-5% of CPU load.

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


[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets

2016-02-09 Thread Giuseppe Margarita via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357597

--- Comment #10 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
Created attachment 97113
  --> https://bugs.kde.org/attachment.cgi?id=97113=edit
Valgrind log 2

Did another. 
With two network monitor and one CPU monitor, during reproduction of a YouTube
video, plasmashell/valgring process at about 20 % CPU load.

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


[plasmashell] [Bug 357597] High Plasmashell CPU Usage With Animated Desktop Widgets

2016-02-09 Thread Giuseppe Margarita via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357597

--- Comment #9 from Giuseppe Margarita <giuseppemargar...@gmail.com> ---
Created attachment 97112
  --> https://bugs.kde.org/attachment.cgi?id=97112=edit
Valgrind log

Firts time I use valgrind. Don't know If I did the job well.

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