[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #12 from Simone Gaiarin  ---
I've noticed that the two problematic monitors have the same identifiers also
in .config/monitors.xml. So this bug seems generated by X bad naming. Also it
seems that X remembers all the monitors ever connected. How is it possible to
rename/forget one of them?

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #11 from Simone Gaiarin  ---
I need to make a correction (still the considerations in comment #6 are still
valid):

Attachment 101767 is my correct HOME configuration:
DP1: Notebook screen
DP1-2: Dell U2414H

Attachment 101769 is my correct WORK configuration:
eDP1: Notebook screen
DP1-1: DELL U2412M
DP1-2: HP LA2205wg

Attachment 101768 is a WRONG configuration created by KScreen (the two DELL
monitors have never been in the same place!)
eDP1: Notebook screen
DP1-1: DELL U2412M (my DELL screen at work)
DP1-2: DELL U2414H (my DELL screen at home)

Also notice that I purged all the configuration after upgrading to KDE/Plasma
5.8.1, so all the configuration have been created by that version of KScreen.

I hope I have provided enough (but not too much) information, and that they are
clear enough. Otherwise please ask me clarification, I really hope we can fix
this bug.

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #10 from Simone Gaiarin  ---
Created attachment 101769
  --> https://bugs.kde.org/attachment.cgi?id=101769=edit
Kscreen configuration WORK (Correct version)

This is the correct version of my WORK configuration:
eDP1: Notebook screen
DP1-1: DELL U2412M
DP1-2: HP LA2205wg

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #9 from Simone Gaiarin  ---
The kscreen.log in comment #4 is probably irrelevant, refer to the info in
comment #6 which refer to a more accurate test.

@Sergio Can you please verify if you have a similar situation, where two
screens in different location are named the same way? So we can try to narrow
down the problem.

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #8 from Simone Gaiarin  ---
Created attachment 101768
  --> https://bugs.kde.org/attachment.cgi?id=101768=edit
Kscreen configuration WORK

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #7 from Simone Gaiarin  ---
Created attachment 101767
  --> https://bugs.kde.org/attachment.cgi?id=101767=edit
Kscreen configuration HOME

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #6 from Simone Gaiarin  ---
Here is a clue on what may be the cause of the problem: it seems that one
monitor at home is named as one monitor at work, so when I wake from suspend,
kscreen doesn't notice the difference.

HOME: eDP1, DP1-2
WORK: eDP1, DP1-1, DP1-2

>From docked at HOME > Suspend notebook > Dock at WORK > Wake it up > Wrong
config

In detail what happens is that the notebook screen (eDP1) is activated
correctly, DP1-1 is not activated and DP1-2 is activated with a wrong
resolution (the panel is on it, and it shouldn't), so DP1-2 at WORK is treated
as if it's the DP1-2 at home.

Moreover after waking up the notebook, none of the files in
~/.local/share/kscreen are touched and kscreen.log is not written, so it seems
that kscreen doesn't perform any action at all.

I attach the kscreen configuration for the HOME and WORK configuration.

- EXTRA INFO PROBABLY IRRELEVANT 
Working configuration:
>From undocked > Suspend notebook > Dock at HOME > Wake it up > OK
>From docked at HOME > Suspend notebook > Undock> Wake it up > OK

>From undocked > Suspend notebook > Dock at WORK > Wake it up > OK
>From docked at WORK > Suspend notebook > Undock> Wake it up > OK

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #4 from Simone Gaiarin  ---
Created attachment 101732
  --> https://bugs.kde.org/attachment.cgi?id=101732=edit
kscreen.log after resuming notebook in a different location

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

--- Comment #3 from Simone Gaiarin  ---
I have the same problem in Plasma 5.8.1. I attach the kscreen.log file. Is this
enough or do you still need the xev output? What other information can I
provide?

In another bug this same problem was already discussed, and if I'm not wrong a
developer said that kscreen would check the X configuration after the resume
event (without waiting passively to be notified by X). Is that correct? Or if X
doesn't notify there is no solution to this problem?

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #28 from Simone Gaiarin  ---
I have a similar problem. Basically when waking the notebook up after undocking
(or docked to a different docking station with different moitors) mess the
configuration. Undocking and redocking restore the configuration in some cases.

I can provide a log if the one provided by the other user are not enough.

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

[KScreen] [Bug 371131] New: Multi monitor configuration not respected

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 371131
   Summary: Multi monitor configuration not respected
   Product: KScreen
   Version: 5.8.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: simg...@gmail.com

Running Plasma 5.8.1 some of the multi monitor problems have been fixed but I
still have some.
In particular when I configure my hdmi monitor to be the only one active when
my laptop lid is closed, the configuration is lost as soon as I open the lid
and close it again.

Moreover the panel is still placed in a wrong position time to time and plasma
is not working on some screen. (probably these deserve to be bugs on their
own). See step below.

I've removed the content of .local/share/kscreen and
~/.config/plasma-org.kde.plasma.desktop-appletsrc

The content in the attached kscreen.log contains only the log of the steps
below (I've deleted it before starting the test).

I've performed the following steps:
Starting configuration: DP1-2 primary, active, panel on it; eDP1 active no
panels; HDMI1 active no panels
- Configure HDMI1 to be disabled
- Close the lid
- Open the lid
- Close the lid
- Open the lid
- Close the lid [Ok everything is maintained]
- Configure HDMI1 to be the only one active (wrong resolution) [No primary
output]
- Set correct resolution [Cannot set it]
- Close display settings
- Open display settings
- Set correct resolution [Set correctly]
- Set HDMI1 as primary output
- Open the lid [Panel on eDP1 (wrong position), eDP1 with black desktop,
impossible to interact with plasma on it]
- Close the lid [HDMI1 not active, DP1-2 active with panel on it] [Only HDM1
should be active instead]

When the desktop is black plasma output "requesting unexisting screen 1"

Reproducible: Always

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

[KScreen] [Bug 371131] Multi monitor configuration not respected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #1 from Simone Gaiarin  ---
Created attachment 101626
  --> https://bugs.kde.org/attachment.cgi?id=101626=edit
Kscreen log

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

[kdeconnect] [Bug 369597] Cannot control volume of spotify

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
Just a brief update on this. This is the reply of one developer of spotify:

"Nobody is working on it currently, but it is tracked internally as "Add more
MPRIS functionality", that I want to do eventually. There are some linux crash
bugs that I want to focus on first. I can set aside one day every two weeks to
help fixing bugs in the linux system specific parts of the desktop client. That
is roughly the pace of development currently."

https://community.spotify.com/t5/Desktop-Linux-Windows-Web-Player/Cannot-control-volume-using-MPRIS-D-bus/m-p/1465152/highlight/false#M167907

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #83 from Simone Gaiarin  ---
The video lag on chrome may be related to other causes. I had the problem as
well. 
See this:
https://forum.manjaro.org/t/chrome-chromium-and-html5-video-lags-low-fps/2257/30

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #78 from Simone Gaiarin  ---
My workaround for the spinning file transfer is to modify the qml code and make
it not spin. What other  "animated task manager (?) icons"  are causing the
problem beside the file transfer spinner?

I still haven't tried your patch for the system tray icon. Can I just recompile
the system tray or does it require to recompile the whole plasma?

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #72 from Simone Gaiarin  ---
Is it there any progress on this? Plasma 5.8 is LTS and still has this bug,
that seems quite critical to  me. There are multiple animated icons in the task
bar and some of them keep the animation running for a long time causing the CPU
to be always on.


- File transfer
- Skype
- Update notification on Manjaro (I need to kill this or update the system, or
my CPU is always on).

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

[kdeconnect] [Bug 369597] Cannot control volume of spotify

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
I imagined that. I'll try to reach them.
Thanks.

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

[kdeconnect] [Bug 369599] Show multimedia style notification when multimedia player is active

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

Summary|Use multimedia style|Show multimedia style
   |notification when   |notification when
   |multimedia player is active |multimedia player is active

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

[kdeconnect] [Bug 369599] New: Use multimedia style notification when multimedia player is active

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 369599
   Summary: Use multimedia style notification when multimedia
player is active
   Product: kdeconnect
   Version: 1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: simg...@gmail.com

It would be nice to have the multimedia controls in the notification area of
Android when a multimedia player is active on the PC.

In particular I suggest the following behaviour (I take VLC as an example):

- VLC is started on the PC - No multimedia notification
- User access KDE Connect/Multimedia on Android > Notification is shown
- Notification remains in place until VLC is open
..or until the user closes it with the X (this should not cause the closing of
VLC on the PC).


Possibly a second behaviour can be added (but a setting to switch between the
two must be added in the app)

Behaviour 2:

- Notification is shown as soon as VLC is started on the PC
- The X in the multimedia notification closes VLC on the PC and removes the
notification


Finally if more than one multimedia player is active on the PC, the previous
behaviour should apply only for the multimedia player selected in the combobox
of the kdeconnect app.

Reproducible: Always

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

[kdeconnect] [Bug 369597] New: Cannot control volume of spotify

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 369597
   Summary: Cannot control volume of spotify
   Product: kdeconnect
   Version: 1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: simg...@gmail.com

Volume control works for VLC but not for spotify.

Reproducible: Always

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

[kdeconnect] [Bug 368812] New: Kdeconnect forgets paired devices

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 368812
   Summary: Kdeconnect forgets paired devices
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: simg...@gmail.com

As the title says, kdeconnect forgets the paired device after a day or so.

Using latest git version, fresh config folder and latest android app.

Reproducible: Always

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

[frameworks-solid] [Bug 368713] Solid doesn't detect disk as mounted

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #1 from Simone Gaiarin  ---
Actually udisks --dump shows ismounted: 0 on the dm partition. So probably it's
related to udisk not to solid.

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

[frameworks-solid] [Bug 368713] Solid doesn't detect disk as mounted

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

Summary|Solid doesn't detected disk |Solid doesn't detect disk
   |as mounted  |as mounted

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

[frameworks-solid] [Bug 368713] New: Solid doesn't detected disk as mounted

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 368713
   Summary: Solid doesn't detected disk as mounted
   Product: frameworks-solid
   Version: 5.24.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: simg...@gmail.com
CC: kdelibs-b...@kde.org

I have a LUKS dm-crypt encrypted partition which I mount with pam_mount at
login.

The problem is that it is not detected as mounted by Dolphin. I guess the
problem resides in solid.
Running the following command:

solid-hardware details '/org/freedesktop/UDisks2/block_devices/dm_2d0'

I get:

StorageAccess.accessible = false  (bool)


If I click on the disk listed as unmounted in dolphin it is mounted for a
second time on a different mount point and the result of the command becomes
true. 

Reproducible: Always

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

[ktouch] [Bug 350336] KTouch lags and uses full (100%) CPU resources when typing fast.

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

--- Comment #5 from Simone Gaiarin  ---
For arch users I've created the package kdeedu-ktouch-patched in AUR, that
provides the proposed patch, while we wait it's merged upstream.

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

[plasma-nm] [Bug 366708] Set default network priority not to zero

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #5 from Simone Gaiarin  ---
Great! Thanks

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

[plasma-nm] [Bug 366708] Set default network priority not to zero

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
Hi Lamarque,
your answer made me read the NM specifications and I've found that the value
autoconnect-priority is int32 which  can possibly be negative (other parameters
require specifically uint32).

Executing the command:
nmcli connection modify MYCONNECTION connection.autoconnect-priority -10

doesn't rise any error and running

nmcli connection show MYCONNECTION 

shows that the value has been set.

I cannot test if this priority works in this moment, but if it's the case it
would be enough to let the priority value be negative in the UI spinbox and the
problem would be solved.

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

[ktouch] [Bug 367891] New: Cannot use custom keyboard layout

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 367891
   Summary: Cannot use custom keyboard layout
   Product: ktouch
   Version: 2.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sebastiangottfr...@web.de
  Reporter: simg...@gmail.com

I've created a custom keyboard layout for the Italian keyboard. The only
difference from the standard layout in ktouch is that I want to hit some keys
with different fingers.

Now if I name the layout it_win (as in the example provided in the manual), the
layout autodetection feature of ktouch will never be able to detect this layout
becuase the layout in use is indeed it, so the lessons associated to it cannot
be used.

There should be a way to manually select the layout one want to use, by turning
off the autodetection feature.

Reproducible: Always

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #69 from Simone Gaiarin  ---
Searching I've found a workaround to disable the spinning in BusyIndicator.
Works for me, but disables the animation.

https://bugs.kde.org/show_bug.cgi?id=312920#c3

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #68 from Simone Gaiarin  ---
What is the modification to NotificationIcon.qml mentioned by Nicholas? I've
the same problem especially for copying file over the network,

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[plasmashell] [Bug 367666] New: Add option to change wallpaper to all screen in one click.

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 367666
   Summary: Add option to change wallpaper to all screen in one
click.
   Product: plasmashell
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: simg...@gmail.com

I have 3 screens, and when I want to change the wallpaper I need to repeat the
operation 3 times once for each screen. Considering that I have multiple
activities, the time I need to repeat the operation is even higher.

It would be nice to have an "Apply to all desktop" button, so that once chosen
a wallpaper it's applied to all the screen (in the same activity).

(Actually I'm not one that change wallpapers so often, but currently I often
have the need to change wallpaper, just because the multimonitor configuration
mess it up. Still I think it's an useful feature in general.)

Reproducible: Always

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

[plasmashell] [Bug 367631] New: Lack of feedback when adding widget to the panel make it difficult (especially near task manager)

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 367631
   Summary: Lack of feedback when adding widget to the panel make
it difficult (especially near task manager)
   Product: plasmashell
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: simg...@gmail.com

When I drag a widget to add it to the desktop a blue square appears to show the
position where the widget will be positioned. This doesn't happen when I try to
add a widget to the panel.
It's true that the other widgets move around to show the user that the widget
will be placed in the empty space.

The problem is that most of the empty space of my panel is actually occupied by
the task manager (icon only task manager), so when a widget is dragged over
this empty space there is no feedback on whether the task manager widget has
shrunken or not. Because of this often releasing the mouse button causes the
widget to not be placed correctly.

Reproducible: Always

Steps to Reproduce:
1.Create an empty panel
2.Add icon only task manager to the panel
3.Try to add another plasmoid by dragging it to the empty space on the panel

Actual Results:  
Unless the plasmoid is positioned in the extreme right of the panel, the
placement of the plasmoid will fail with no clear reason to the user

Expected Results:  
Showing a blue square where the plasmoid will be placed can be used as a
feedback by the user to understand if he placed the plasmoid correctly before
releasing the mouse button.

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

[Breeze] [Bug 367620] New: Request: Icons for redshift

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 367620
   Summary: Request: Icons for redshift
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: simg...@gmail.com
CC: kain...@gmail.com

Redshift is a popular app to manage the screen colour temperature. By default
it has a gtk interface called redshift-gtk.

I'm the developer of the plasmoid "redshift plasmoid" which is a plasmoid that
aim to provide a native kde interface to redshift. I would to ask if you can
design the icons of redshift in breeze style.

The redshift package comes with the following icons:
* redshift
* redshift-status-on
* redshift-status-off
(https://github.com/jonls/redshift/tree/master/data/icons)

My plasmoid requires also the icon:
* redshift-status-manual

The icons are included in my plasmoid as svgz and you can find them here:
https://github.com/simgunz/redshift-plasmoid/tree/master/icons

I include also the hicolor icons that come by default with redshift because
sometimes redshift is packaged without the GUI in some distributions.

Some themes like the default Manjaro linux icon theme Vertex Maia already come
with new icons for redshift, but the manual status is missing there.
https://github.com/manjaro/vertex-maia-icon-themes/blob/master/Vertex-Maia/apps/22x22/status/

There is another plasmoid called redshift control by another developer, but
that one uses a custom icon for redshift.

I hope you can help me with this.

Reproducible: Always

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

[kdeconnect] [Bug 339685] Add plugin for computer power management

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #5 from Simone Gaiarin  ---
Even though the run command plugin allows to create custom commands, and it
works fine to suspend the PC. I suggest to populate it with some defaults for
normal users, like the power management commands. I think the use case
suggested by Daniel Vrátil is a pretty common one.

Creating a script with a dbus command to suspend your pc seems a action for
power users.

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

[kdeconnect] [Bug 357783] Add option to suspend to ram/ turn off pc remotely

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Simone Gaiarin  ---


*** This bug has been marked as a duplicate of bug 339685 ***

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

[kdeconnect] [Bug 339685] Add plugin for computer power management

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

--- Comment #4 from Simone Gaiarin  ---
*** Bug 357783 has been marked as a duplicate of this bug. ***

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

[KScreen] [Bug 366721] Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #5 from Simone Gaiarin  ---
Good to hear that.

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #10 from Simone Gaiarin  ---
I had a similar problem, though disabling and reenabling in kscreen didn't
help. Kernel 4.7 solved the problem for me.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #177 from Simone Gaiarin  ---
So I did some quite extensive test today with Neon Dev unstable (KDE 5.7.90) 
and seems that most of the problems are gone. I was suffering ALL the kind of
weird bugs connected to multi monitor.

Test 1:
Boot laptop (LAP)
OK Connect external monitor EX1
OK Switch position of LAP left to right of EX1
OK Set screens vertically misaligned
!! Set external monitor as primary
  -Panel moves to EX1 properly
  - Phantom panel is left on LAP. Impossible to interact with it. Restart
plasma to remove it.
OK Detach EX1
  - Panel moves to LAP
OK Reattach EX1
  Panel moves back to EX1
OK Close lid of LAP
  - Panel stays in place in EX1
  - All windows moved to EX1
OK Open lid of lap
  - Panel stays in place in EX1
  - Only windows originally in LAP move back to LAP
KO Suspend and resume (Intel related bug probably)
  - Monitor doesn't turn on
  - KScreen detects it as active ( I can move the mouse in there and I can see
it active in display configuration)
  - Need to detach and reattach EX1 to wake it up
Disconnect EX1
KO Connect HDMI1. Kernel panic I think. PC reboot. (Reproducible) [Not related
to Kscreen I guess]

Test 2
Boot with HDMI1 connected to avoid kernel panic
OK Tinker configuration of HDMI1 + LAP. 
OK HDMI1 primary. Suspend with HDMI1 connected, detach HDMI1, resume
  - Panel found in LAP after resume
OK Disconnect HDMI1, Connect EX1 and tinker configuration. EX1 primary.
OK Close the lid, suspend, detach EX1, resume
  - Panel found in LAP

So I really hope we solved it for real this time. Great job.

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

[KScreen] [Bug 366721] Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
So I did some quite extensive test today with Neon Dev unstable (KDE 5.7.90) 
and seems that most of the problems are gone. I was suffering all the kind of
weird bugs connected to multi monitor.

This bug seems to be gone, though it happened once that the wallpaper was not
shown, but the desktop was in place with icons and the possibility to interact
with it. I couldn't reproduce it.

Other minor bug: If a screen is attached or detached when "Display
configuration" is open the screen positions in the config dialog are messed up.

I'll report the full test in the panel positioning bug, since it's more
relevant for that.

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

[KScreen] [Bug 366721] Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #1 from Simone Gaiarin  ---
Removing the kscreen configuration files doesn't solve the problem.

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

[KScreen] [Bug 366721] New: Connecting an external monitor causes the laptop screen to go black with only the mouse cursor visible

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 366721
   Summary: Connecting an external monitor causes the laptop
screen to go black with only the mouse cursor visible
   Product: KScreen
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: simg...@gmail.com

It seems that plasma doesn't build the desktop on that screen. Tested with KDE
Neon live image developer edition stable.

Configuration:
- External monitor set as primary

Reproducible: Always

Steps to Reproduce:
1.Connect external monitor (dock)
2.
3.

Actual Results:  
Black screen on laptop with mouse only

Expected Results:  
To have the plasma desktop

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[KScreen] [Bug 351390] Corrupted kscreen config breaks KDE startup process

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[KScreen] [Bug 366468] When set screens to be not vertically aligned kscreen breaks

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
Tested with KDE Neon live image branch stable and the bug seems to not be
present.

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

[kdeconnect] [Bug 357783] Add option to suspend to ram/ turn off pc remotely

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #1 from Simone Gaiarin  ---
Any plan to implement this?

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

[plasma-nm] [Bug 366708] New: Set default network priority not to zero

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 366708
   Summary: Set default network priority not to zero
   Product: plasma-nm
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: simg...@gmail.com
CC: jgrul...@redhat.com

With the current implementation of plasma-nm it's possible to set different
priorities to different networks, it would be useful to have the default
priority set to a value different to zero (something like 50), so that it's
possible to create a new connection with lower priority than all the other
networks.

Use case:
I create a share network connection and I want to automatically connect to it
when I'm at work. Since it's a shared wireless network connection, this will be
available everywhere. Of course I don't want to automatically connect to it in
every place. To avoid this I need to raise the priority of every new network
I'll connect to.

Solution:
If the default priority for every new network is 50, I can create the shared
network connection and set a priority of 40, so that I'll automatically connect
to it only when I'm at work without changing the priority of all the other
networks.

Reproducible: Always

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

[KScreen] [Bug 366468] When set screens to be not vertically aligned kscreen breaks

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
I can try to download a Neon image and test it. Is it ok? Should I choose the
stable branch or unstable branch version of the developer edition?

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

[plasmashell] [Bug 357315] Resume from Standby (Suspend to RAM) results in black screen (but with themed cursor)

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
I forget to say, that a workaround is to restart plasma.

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

[plasmashell] [Bug 357315] Resume from Standby (Suspend to RAM) results in black screen (but with themed cursor)

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

--- Comment #1 from Simone Gaiarin  ---
Same problem here. To me it happens on a single screen (the laptop screen) when
using a multimonitor configuration.

The panel is on the external monitor, which is set as primary.

Resuming from sleep causes the laptop screen to be black, and impossible to
interact with. The screen is on, and I can see the mouse cursor. The external
monitor works just fine.

How can I provide more debugging information?

Running plasma 5.7.3

Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
   Display Server: X.Org 1.17.4 driver: intel Resolution:
1920x1080@60.02hz, 1920x1080@60.00hz
   GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa
12.0.1

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

[KScreen] [Bug 366468] New: When set screens to be not vertically aligned kscreen breaks

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 366468
   Summary: When set screens to be not vertically aligned kscreen
breaks
   Product: KScreen
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: simg...@gmail.com

When I set the vertical alignment of my two screens in kscreen to be not
vertical aligned (because my real two monitors are not), the following happens:

- One screen is turned off and in the other I see the bottom part of the
desktop on the top of the screen and viceversa, and then it's impossible to
interact with plasma
- When I logout and login from KDE I get a black screen with only the mouse
pointer visible. The mouse pointer is snapped on one edge of the screen and can
only be moved vertically.

To solve I need to delete all the kscreen configurations from shell (probably
there is only one that is corrupted) and login again.


Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
   Display Server: X.Org 1.17.4 driver: intel Resolution:
1920x1080@60.02hz, 1920x1080@60.00hz
   GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa
12.0.1

Reproducible: Always

Steps to Reproduce:
1.Set the screens vertically misaligned in kscreen config
2.Click apply
3.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #167 from Simone Gaiarin  ---
To start fresh I've also removed all the files in ./.local/share/kscreen/. In
my case some of them were read only (I've set them so time ago) and caused
problems.

As I said everything works better now, but to reach a good result I need to
perform the steps in a very specific order or I can still end up in bad
configurations.

As an example

Working process:

1. Laptop only (so primary)
- Place a panel

2. Attach external monitor
- Set external monitor as primary (panel is not moved from laptop to external)
- Move the panel manually to the external screen

3. Detach external monitor
- Panel moves to laptop correctly

Non working process:

1. Laptop only (so primary)
- Place a panel

2. Attach external monitor
- Set external monitor as primary (panel is not moved from laptop to external)

3. Detach external monitor
- Panel disappears

4. Reattach external monitor
- No more panels (invisible panel)

What seems to be partially broken is that sometimes, switching the primary
output won't move the panel right away, and the operation needs to be done
manually.

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

[KScreen] [Bug 345227] Desktop turns black and plasmoids disappear when docking notebook

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #7 from Simone Gaiarin  ---
This problem appeared again in a different form. Sometimes after boot, the
external monitor is black without plasmoids, without the right click menu, but
the mouse cursor is visible. Moreover the panel that should be in this screen
is in the laptop screen.

Restarting plasma solves the problem.

It seems that the external monitor is not detected by plasma and kscreen.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[KScreen] [Bug 365146] Panel disappears on primary laptop screen after closing and reopening lid

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
I confirm this.

External monitor: Primary screen
Numer of panels: 1

I close the lid, the panel disappers from the external monitor.
I reopen the lid, the panel appears again.

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

[KScreen] [Bug 365146] Panel disappears on primary laptop screen after closing and reopening lid

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #163 from Simone Gaiarin  ---
After a preliminary testing, I confirm that the situation seems to be improved
even if not 100% reliable.

In particular a problem I've noticed is that if I close the notebook lid with
an external monitor connected (configured as primary screen), the panel in the
external monitor disappears, while the widgets remain in place.

Reopening the lid brings the panel back.

Testing this I've noticed, but this may be reported as a new bug, that all the
windows in the external monitor are moved to the notebook monitor even if they
were originally placed in the external monitor before closing the lid.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #161 from Simone Gaiarin  ---
Are there other config files beside the ones in comment #150? I've tried to
delete those, but the problem persist.

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

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #29 from Simone Gaiarin  ---
Yes that's a good point. Still the behavior proposed for the portrait mode will
not affect this use case in landscape, and I doubt someone wants to tile
left/right in portrait, having the window be two long stripes (I may be wrong).

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

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #27 from Simone Gaiarin  ---
Another idea regarding the placement by touching the edge would be to make the
window expand to the upper half  of the screen when  the upper edge is touched
only when the screen is in portrait mode. And possibly use the right or left
edge to maximize the window.

I guess that tile to top and bottom would be not so common in landscape mode
and the same for left/right in portrait.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #122 from Simone Gaiarin  ---
> I still get this issue on the 5.7 Beta, although it seems to happen not quite 
> as often as before. 

New release placebo effect. :-)

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

[KScreen] [Bug 345225] External monitors not activated after resuming from sleep

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #12 from Simone Gaiarin  ---
Also, I have this option related to the Intel driver in grub. Can this by
related to the issues?

GRUB_CMDLINE_LINUX=" acpi=force 
   acpi_enforce_resources=lax i915.enable_rc6=1 i915.enable_fbc=1 
   i915.lvds_downclock=1 i915.semaphores=1"

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

[KScreen] [Bug 345225] External monitors not activated after resuming from sleep

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #11 from Simone Gaiarin  ---
Another detail on this issue, is that sometimes there is no way to activate the
monitor at all. In KScreen clicking enable and apply won't change anything.
Often in this situation the list of resolutions available are wrong, so the
monitor information are probably not detected at all, even though the monitor
itself is detected as connected.

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

[KScreen] [Bug 345225] External monitors not activated after resuming from sleep

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #10 from Simone Gaiarin  ---
 I can suspend/resume via laptop lid/graphical interface/physical button and in
any case the monitor doesn't wake up.

Still present in Plasma 5.6. I cannot apply the workaround suggested above,
because the problems in comment #8 are still present as well.

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

[kdeconnect] [Bug 363947] kde connect: Could not mount device.

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #21 from Simone Gaiarin  ---
Here:

kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: KdeConnect daemon started
"Google Nexus 4" - warning, device uses a different protocol version 6 expected
5
kdeconnect.core: Loaded plugin: "kdeconnect_notifications"
kdeconnect.core: Loaded plugin: "kdeconnect_battery"
kdeconnect.core: Loaded plugin: "kdeconnect_ping"
kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.vlc" -> "VLC
media player"
kdeconnect.core: Loaded plugin: "kdeconnect_mpriscontrol"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "Google Nexus 4"
kdeconnect.core: Loaded plugin: "kdeconnect_sftp"
kdeconnect.core: Loaded plugin: "kdeconnect_clipboard"
kdeconnect.core: Loaded plugin: "kdeconnect_share"
kdeconnect.core: Loaded plugin: "kdeconnect_telephony"
kdeconnect.core: Loaded plugin: "kdeconnect_pausemusic"
kdeconnect.core: Loaded plugin: "kdeconnect_mousepad"
kdeconnect.core: Device "Google Nexus 4" status changed. Reachable: true .
Paired:  true
kdeconnect.plugin.notification: removeNotification
"com.lucid_dreaming.awoken::1"
kdeconnect.plugin.notification: removeNotification
"com.splunchy.android.alarmclock::2131623957"
kdeconnect.plugin.notification: removeNotification
"com.lucid_dreaming.awoken::1"
kdeconnect.plugin.notification: removeNotification
"com.splunchy.android.alarmclock::2131623957"
"Google Nexus 4" - warning, device uses a different protocol version 6 expected
5
"Google Nexus 4" - warning, device uses a different protocol version 6 expected
5
kdeconnect.plugin.sftp: Mount device: "Google Nexus 4"
kdeconnect.plugin.sftp: Created mounter
kdeconnect.plugin.sftp: Starting loop to wait for mount
kdeconnect.plugin.sftp: Timeout: device not responding
kdeconnect.plugin.sftp: Destroy mounter
kdeconnect.plugin.sftp: Unmount QObject(0x0)

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

[kdeconnect] [Bug 363947] kde connect: Could not mount device.

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #18 from Simone Gaiarin  ---
I have the same problem and my desktop version is 0.9.g. Android version is
1.0.

Error reported by dolphin:

"Could not mount device.
The reported error was:
Could not mount device filesystem"

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

[kdeconnect] [Bug 363947] kde connect: Could not mount device.

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[cantor] [Bug 356103] Python 3 backend is not functional

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #8 from Simone Gaiarin  ---
Python 3.5.1

On Thu, May 26, 2016 at 9:34 PM Alexander Semke via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=356103
>
> --- Comment #7 from Alexander Semke  ---
> which python version do you use in the terminal?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

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

[cantor] [Bug 356103] Python 3 backend is not functional

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #6 from Simone Gaiarin  ---
import numpy and import scipy works fine for me in a python shell run from
bash. While I still get the error from within cantor.

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

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC|simg...@gmail.com   |

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #83 from Simone Gaiarin  ---
Remember that Screen=0 is always the primary screen (empirically). So the
numbers 0 1 2 are not absolute, but relative to the primary screen.

See my comment #58 where I raised a question regarding the tricky behavior
related to primary screen.

On Wed, Apr 27, 2016 at 3:57 PM via KDE Bugzilla 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=356225
>
> --- Comment #82 from m...@eisgr.com ---
> Does anyone else experience crashing in other apps when dis/connecting
> monitors?  Like https://bugs.kde.org/show_bug.cgi?id=349512 ?
> I feel like these are related, but can't be sure.  I believe the
> Plasma/KWin
> crashing is related, but I'm guessing the panel problems are related to the
> crashing?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

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

[KScreen] [Bug 353885] KCM module asks to apply settings twice

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

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

--- Comment #1 from Simone Gaiarin  ---
Seems solved in Plasma 5.6.

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

[KScreen] [Bug 361953] When monitors are not vertically aligned, some windows are wrongly vertically placed

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #5 from Simone Gaiarin  ---
Created attachment 98463
  --> https://bugs.kde.org/attachment.cgi?id=98463=edit
systemmonitor xprop and xwininfo outputs

Here is the output of systemmonitor

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

[KScreen] [Bug 361953] When monitors are not vertically aligned, some windows are wrongly vertically placed

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

  Attachment #98459|0   |1
is obsolete||

--- Comment #3 from Simone Gaiarin  ---
Created attachment 98460
  --> https://bugs.kde.org/attachment.cgi?id=98460=edit
Screenshot of the two screens together

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

[KScreen] [Bug 361953] When monitors are not vertically aligned, some windows are wrongly vertically placed

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #1 from Simone Gaiarin  ---
Created attachment 98458
  --> https://bugs.kde.org/attachment.cgi?id=98458=edit
KScreen settings

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

[KScreen] [Bug 361953] When monitors are not vertically aligned, some windows are wrongly vertically placed

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
Created attachment 98459
  --> https://bugs.kde.org/attachment.cgi?id=98459=edit
Screenshot of the two screens together

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

[KScreen] [Bug 361953] New: When monitors are not vertically aligned, some windows are wrongly vertically placed

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 361953
   Summary: When monitors are not vertically aligned, some windows
are wrongly vertically placed
   Product: KScreen
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: simg...@gmail.com

I have a notebook and an external monitor. Since the screen of the laptop is in
a lower position respect the external monitor I've configured KScreen
accordingly (see attached picture). 

When I open some windows with a shortcut (System activity, MATLAB splashscreen,
and maybe others) they are always placed in the leftmost screen (notebook in
this case) even if the mouse is in the rightmost one. More important is that
they are positioned as if the screen is a whole big rectangle (see attached
picture 2) so that they are placed outside the screen. (I can only see the
lower part of the windows, or in some case I cannot see it at all (but thanks
to the minimization animation I can see where it was)).

The explanation is tricky, but the two images should help.

Reproducible: Always

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

[plasmashell] [Bug 341674] High CPU load when using second panel in multiscreen setup

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[cantor] [Bug 359927] Cantor crashes when "Integrate plots in Worksheet" is checked (python2)

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
I've tried now and it works correctly. Maybe updating some python packages
fixed the problem.

On Fri, Apr 8, 2016 at 8:06 PM Filipe Saraiva via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=359927
>
> --- Comment #1 from Filipe Saraiva  ---
> Hello Simone, I can not to reproduce this bug. Please, can you verify if
> you
> have this bug yet?
>
> I run the follow commands:
>
> x = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
> from matplotlib import pylab
> pylab.clf()
> pylab.plot(x)
> pylab.show()
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[Powerdevil] [Bug 357621] Screen cannot be turned on after it has been set to "energy saving" (goes off)

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #5 from Simone Gaiarin  ---
Yes that workaround works also for me. Very annoying tough.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #58 from Simone Gaiarin  ---
I confirm that the behavior is improved with Qt 5.6 but not solved.

I have a question tough?

What is the expected behavior of the panel in first place in relation to
primary screen setting?(It's necessary to understand how the panels should
behave to debug then what's happening).

_No Primary Output_: Each screen remembers its own panels, and panels are never
moved around.
(This seems to work)

_Primary Output Set_: My understanding is that the panel in the primary screen,
is always placed in the primary screen when this is changed.

Examples:
Laptop screen (LP) and external screen (EX)
Two panels: P1 and P2

Case 0:
When I change the primary screen in the configuration, the panels on the old
primary screen and on the new one are swapped, so that the panels follow the
primary screen.
(This works sometimes, but not always)

Case 1: LP set as primary always (with and without EX connected)
Supposed behavior:
- P1 is always kept on LP
- P2 is always kept on EX
(Works sometimes)

Case 2: EX set as primary (single panel)
I drag P1 from LP to EX, so that LP has no panels

If I disconnect EX I expect P1 to go back to LP. Is this correct?
(this is not happening to me)

Case 3: EX set as primary (two panels)
P1 on LP and P2 on EX

The the panel in the primary screen is brought back to LP when the externals
monitor are disconnected. (again this is not happening)

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

[plasmashell] [Bug 352581] Move panels to other screens and lock them there.

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
This problem seems to be solved.

Running Qt 5.6 and Plasma 5.6.1 (was already solved for me in Plasma 5.5.x)

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

[kdeplasma-addons] [Bug 353091] Cannot specify own periods for timer widget

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
Thanks. I've missed the tooltip informations

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

[kdeplasma-addons] [Bug 360115] Add option to change font size of the text word by word

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
Created attachment 97689
  --> https://bugs.kde.org/attachment.cgi?id=97689=edit
little note

Changing the whole system font size to change the font of a note on the desktop
is totally counter intuitive to me. This seems to me the usability issue. 

I think it's a typical case to want the notes on the desktop to be bigger than
the rest to make them evident. See the attached image. A tiny note in the
middle of a huge desktop.

Having the option to set at least the font for all the text in the note
(instead of setting it word by word) as you thought would be very useful.

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

[kdeplasma-addons] [Bug 360115] New: Add option to change font size of the text word by word

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 360115
   Summary: Add option to change font size of the text word by
word
   Product: kdeplasma-addons
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: simg...@gmail.com

Using the system font size is not the best option in a note widget. I may want
to write a word bigger than the others, without changing the whole font
configuration of KDE.

So I suggest to add an option to "format options" to specify the font size of
the written text.

Reproducible: Always

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

[kdeplasma-addons] [Bug 353091] Cannot specify own periods for timer widget

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

--- Comment #1 from Simone Gaiarin  ---
This should really be fixed, since it breaks the main functionality of the
widget!

Moreover it should be possible to specify a time interval on the fly, without
the need to open the settings and add a new item in the list.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #27 from Simone Gaiarin  ---
Thanks for the script!! 

I'll add it with all my other fix[Name broken kde component].sh scripts. ;-)

(Just joking, thanks to all the developers for the great job they're doing,
Let's hope that Qt5.6 fixes some of these multimonitor related bugs).

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

[cantor] [Bug 359927] New: Cantor crashes when "Integrate plots in Worksheet" is checked (python2)

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 359927
   Summary: Cantor crashes when "Integrate plots in Worksheet" is
checked (python2)
   Product: cantor
   Version: 0.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: python2-backend
  Assignee: fil...@kde.org
  Reporter: simg...@gmail.com
CC: alexanderrie...@gmail.com

If I enable "Integrate plots in Worksheet" in the python2 backend and then I
try to plot something, cantor crashes. Backtrace attached.

I've tried with the git version of Cantor.

(gdb)  thread apply all backtrace

Thread 2 (Thread 0x7fffe60d7700 (LWP 25451)):
#0  0x71aa9e5d in poll () from /usr/lib/libc.so.6
#1  0x7fffed5eeae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fffed5f0757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fffe7a02379 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x726a9b8e in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7033c4a4 in start_thread () from /usr/lib/libpthread.so.0
#6  0x71ab2dcd in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x77e2a800 (LWP 25445)):
#0  0x719fd3c8 in raise () from /usr/lib/libc.so.6
---Type  to continue, or q  to quit---
#1  0x719fe84a in abort () from /usr/lib/libc.so.6
#2  0x726971e1 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
#3  0x7fffc67db9a2 in ?? () from
/usr/lib/python2.7/site-packages/PyQt5/QtCore.so
#4  0x7fffc67e173d in ?? () from
/usr/lib/python2.7/site-packages/PyQt5/QtCore.so
#5  0x7fffc67e2017 in ?? () from
/usr/lib/python2.7/site-packages/PyQt5/QtCore.so
#6  0x728b94d0 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#7  0x728c6238 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib/libQt5Core.so.5
#8  0x7fffc66cc30b in ?? () from
/usr/lib/python2.7/site-packages/PyQt5/QtCore.so
#9  0x728ba193 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#10 0x7fffc66cc26b in ?? () from
/usr/lib/python2.7/site-packages/PyQt5/QtCore.so
#11 0x7317d9ac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#12 0x73182e86 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
---Type  to continue, or q  to quit---
#13 0x7288abab in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#14 0x728e036d in QTimerInfoList::activateTimers() () from
/usr/lib/libQt5Core.so.5
#15 0x728e0871 in ?? () from /usr/lib/libQt5Core.so.5
#16 0x7fffeee8edc7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#17 0x7fffeee8f020 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x7fffeee8f0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#19 0x728e154f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#20 0x7288857a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#21 0x7289053c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#22 0x004183ce in main (argc=1, argv=0x7fffdd58) at
/media/dataHD/development/kde/bugs/cantor/src/main.cpp:138


Reproducible: Always

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

[cantor] [Bug 356103] Python 3 backend is not functional

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

--- Comment #4 from Simone Gaiarin  ---
Still present in KDE 5.19

System: Manjaro Linux

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

[dolphin] [Bug 278236] Cannot drag file onto chromium upload form input

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[frameworks-kdeclarative] [Bug 346134] HIgh CPU usage of the QML plotter component

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[plasma-pa] [Bug 351367] On the fly audio output switching

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[okular] [Bug 358068] Shape of drawn polygon is not previewed

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #2 from Simone Gaiarin  ---
I've added the VDG to CC by mistake while I was reviewing some other  VDG
related bugs of okular, but I couldn't remove it.

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

[okular] [Bug 358068] Shape of drawn polygon is not previewed

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||visual-des...@kde.org

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

[okular] [Bug 358069] Browse mode pointer should be an arrow not an hand to improve precision

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||visual-des...@kde.org

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

[frameworks-kio] [Bug 359233] Improve usability of "Open with > Other" file dialog

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||visual-des...@kde.org

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

[frameworks-kio] [Bug 359233] Improve usability of "Open with > Other" file dialog

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #4 from Simone Gaiarin  ---
Created attachment 97317
  --> https://bugs.kde.org/attachment.cgi?id=97317=edit
Mockup of the open with dialog

My two cents on how to implement the solution:

See attached mockup first.

* Set window title to the file name without the full path (see red circle in
mockup)
* Add "Advanced section" to hide terminal options (see mockup)
* Line edit should behave like this:
  * When the user start typing the know applications are filtered out leaving
only the ones that match the query
  * It can also behave as a terminal to run a command, but I would activate the
dropdown suggestion list of commands only if the user presses "arrow down". The
current behavior of showing it as the user starts typing will let it hide the
known application list underneath. In this way the know application list is
considered the way of choosing the application with highest priority, while the
terminal command is a secondary option.


In any case let's wait for the VDG suggestions, otherwise I suggest to
implement as I described if none has anything against it.

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

[frameworks-kio] [Bug 359233] Improve usability of "Open with > Other" file dialog

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #3 from Simone Gaiarin  ---
Thanks for the interest.

I've actually opened a topic in the VDG section of the forum, but for now the
discussion haven't received much interest. Let's wait a bit and see if someone
post something there.

https://forum.kde.org/viewtopic.php?f=285=131014

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

[frameworks-kio] [Bug 359233] New: Improve usability of "Open with > Other" file dialog

[Simone Gaiarin via KDE Bugzilla]

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

Bug ID: 359233
   Summary: Improve usability of "Open with > Other" file dialog
   Product: frameworks-kio
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: simg...@gmail.com
CC: kdelibs-b...@kde.org

Here I want to point out some usability issues with the "Open with > Other"
file dialog.

1. Taking into account the phylosophy "Simple by Default, Powerful When Needed"
the "Run in terminal" option should be hidden in an Advanced section (Something
like a collapsible group box).
2. The title of the file dialog doesn't carry much information. Most of the
times I can just see the beginning of the full path of the file. Why don't we
just show the file name or some more usable information? (see also:
https://bugs.kde.org/show_bug.cgi?id=110146)
3. The input text box should filter the results in the Know application tree
instead of being a command line. Again: a command line is for advanced user,
should be hidden in the Advanced section.

Scenario:
I want to open a text file with kate.
1. I right click the file and kate is not listed in the "Open with" menu
2. I click "Other.."
3. Kate is part of the know applications. 

Current behavior:
Possibility 1:
I navigate the tree until I find it. This takes time, especially if the
application is nested multiple times and if there is a long list of entries.

Possibility 2:
I type "kate" in the text box. This will associate the file with the COMMAND
kate not with the application kate. 

Problems:
1. Some commands need parameters (See:
https://bugs.kde.org/show_bug.cgi?id=358139)
2. Next time we will open the "Open with.." menu there will be two entries of
kate (See attached image).

Desired behavior: I type "kate" in the text box and the applications  in the
"known application" list are filtered in such a way that only Kate is shown so
I can click on it, saving the hassle of searching for it in the tree.

I would suggest to involve the Visual Design Group in this.

Related bugs:
https://bugs.kde.org/show_bug.cgi?id=358139
https://bugs.kde.org/show_bug.cgi?id=195214
https://bugs.kde.org/show_bug.cgi?id=110146

Reproducible: Always

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