[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

[Enrico Tagliavini]

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

--- Comment #241 from Enrico Tagliavini  ---
(In reply to Nate Graham from comment #235)
> If this were clear-cut, it would have been done ages ago. Instead we have a
> trade-off to make:
> 1. Add the feature for only KDE apps, and then your non-KDE apps will
> display all their formats incorrectly, or at least inconsistently
> 2. Stick to the status quo of consistent systemwide formats, but without
> this desirable feature
> 3. Attempt to work upstream to change the whole world so that we can have
> all of the upsides with none of the downsides
> 
> You're not wrong that #3 is unlikely, which effectively makes it a #2.
> 
> I understand that you personally might prefer #1. However at the moment
> KDE's developers do in fact want to have KDE's apps play nicely with the
> world around them. This is far from something we ignore and is in fact a big
> deal to us. It's why we have a nice-looking GTK theme, a GTK settings
> synchronization service, a first-class implementation of the portal system
> for sandboxed apps. It's why we work upstream on wayland protocol work
> rather than just using private protocols and calling it a day and why we
> just implemented support in Plasma 6 for the FreeDesktop standard sound
> theme spec.
> 
> You might personally prefer that we had different priorities, and that's
> fine. We can't make everyone happy. But we can explain our reasoning and
> hope that people can accept that sometimes there is no ideal solution and we
> have to pick from among a menu of imperfect options.

And this is why Nate is one of the greatest example of a good member of a
community. Always respectful and humble, no matter if he disagrees with you.
Thank you for being a member if this community Sir! You are definitely making a
difference.

Sorry for the "mostly useless" comment, but I think it's important to also show
some support for the community members, as a lot of times the negative one are
under the spot light.

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

[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)

[Enrico Tagliavini]

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

--- Comment #145 from Enrico Tagliavini  ---
(In reply to Claus-Justus Heine from comment #144)
> Alll this was not happening until around start of January this year. This is
> why I do not believe that this is still the same issue as it was back in
> 2015 when this bug-report was created.

I second that, I have this bug, very similar to what Claus-Justus described
since a few weeks on Fedora 35 on Intel GPU. It started appear after either a
Plasma 5.24 update or a kf 5.91 update. Before this I never had this bug for
several years.

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

[plasma-nm] [Bug 449984] Plasma 5.24.0 NetworkManager cannot get secrets using DBus when using a proxy

[Enrico Tagliavini]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

[Enrico Tagliavini]

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

--- Comment #199 from Enrico Tagliavini  ---
(In reply to cat22 from comment #198)
> To me, i would think it shouldn't take more than writing a function that
> does the work 
> and a few lines of code to decide whether to call it or not. It just can't
> be so difficult that 
> someone couldn't fix it in an afternoon.
> Be honest and change the status to "WILL NOT FIX" and we can be done with
> this bickering

Your expectations on how hard this would be is unrelated to how hard and how
much work it actually is. Yes it sucks to have a bug for 7 years, but there
might be more urgent and higher priority problems to solve first, take a look
at the bug list.

I would suggest you stick to the technical discussion. You and many other
people have made clear about your frustration on this issue, there is no need
to keep pushing.

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

[krdc] [Bug 391759] krdc accept invalid certificates (e.g. self signed) without asking confirmation

[Enrico Tagliavini]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Enrico Tagliavini  ---
Almost two years and nobody even had a look at this? Guys this is a serious
security issue, KRDC accepts any kind of borked / invalid / expired
certificates without issue or warning.

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

[kio-extras] [Bug 415241] Trouble opening an MTP device

[Enrico Tagliavini]

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

--- Comment #12 from Enrico Tagliavini  ---
(In reply to Christoph Feck from comment #11)
> So can this ticket get closed?

It looks like the problem was solved for Fedora 32, so I think it can be close.
Possibly wait a few days for the original reporter to give a feedback.

Thank you.

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

[kio-extras] [Bug 415241] Trouble opening an MTP device

[Enrico Tagliavini]

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

--- Comment #10 from Enrico Tagliavini  ---
Seems to be working for me now. There were a few updates since my last comment
and probably some KDE libraries / frameworks was included too.

For reference I'm running Fedora 32, Plasma 5.18.5

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

[kio-extras] [Bug 415241] Trouble opening an MTP device

[Enrico Tagliavini]

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

--- Comment #9 from Enrico Tagliavini  ---
(In reply to Christoph Feck from comment #8)
> Do you have any other application that links to libmtp running? This library
> unfortunately only allows to be used by one client at a time.

As I said I have to killall kiod5, which seems to be the one keeping the device
busy. If I do that, I can then use other libmtp based tools, but not KDE based
one. As soon as I try to access the phone with dolphin I get the error again.

Ultimately this is a design limitation in libmtp I think. Not having
multiplexing is like the ALSA days before pulse.

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

[kio-extras] [Bug 415241] Trouble opening an MTP device

[Enrico Tagliavini]

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

--- Comment #7 from Enrico Tagliavini  ---
(In reply to vytas from comment #6)
> For anyone else stumbling upon this in an effort to find a workaround
> atleast, a thing that fixes it every time is, after confirming popup on the
> phone, close and reopen dolphin.

Doesn't help me, still get the error, even if I kill the dolphin daemon in the
background

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

[kio-extras] [Bug 415241] Trouble opening an MTP device

[Enrico Tagliavini]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||enrico.tagliav...@gmail.com
 Status|REPORTED|CONFIRMED

--- Comment #5 from Enrico Tagliavini  ---
This looks like a problem possibly generated in the KIO module.

Running mtp-detect:

$ mtp-detect
libmtp version: 1.1.16

Listing raw device(s)
Device 0 (VID=2a70 and PID=f003) is a OnePlus OnePlus 2 A2005.
   Found 1 device(s):
   OnePlus: OnePlus 2 A2005 (2a70:f003) @ bus 1, dev 17
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to
initialize device
Unable to open raw device 0
OK.


Running the android file transfer utrility claims the device is already in use:

# aft-mtp-mount $HOME/mtpfs/
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
connect failed: no MTP device found


stracing mtp-detect shows
ioctl(3, USBDEVFS_CLAIMINTERFACE, 0x7ffd33ff178c) = -1 EBUSY (Device or
resource busy)


so it looks like the KDE kio module is locking the USB device and not releasing
it at some point early right after the USB cable is connected


killall kiod5, seems to help, after running it the MTP file system is
accessible with any libmtp based software (e.g. mtp-detect, gvfs-mtp, jmtpfs
and so on) except the KDE one. Trying to access the phone with a KIO based
application causes the device to be locked again and kiod5 needs to be killed
again to make it accessible.

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

[kio-extras] [Bug 395130] cant connect to mtp-device (unknown error code 150)

[Enrico Tagliavini]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

--- Comment #5 from Enrico Tagliavini  ---
(In reply to Axel Braun from comment #4)
> (In reply to Christoph Feck from comment #1)
> > Might be a duplicate of bug 387454.
> 
> I have tried the proposed workaround (comment #25 in the bug description)
> and now get the error 'Could not read. Reason: I/O-Problem'
> Before it listed at least the content of the folder, just on copy the error
> occured.

Probably not very helpful but the proposed workaround in comment #25 of bug
#387454 works for me on Fedora with kernel 4.17 and 4.18. Can this be related
to OpenSuse only or specific to the phone model you have?

Also consider using KDE connect, it's quite great.

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

[frameworks-solid] [Bug 395300] Inelegant handling of LUKS encrypted USB Drives when automounting is turned off

[Enrico Tagliavini]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14

[Enrico Tagliavini]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasmashell] [Bug 395647] New: No action proposed by notifier for encrypted removable devices (dmcrypt LUKS)

[Enrico Tagliavini]

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

Bug ID: 395647
   Summary: No action proposed by notifier for encrypted removable
devices (dmcrypt LUKS)
   Product: plasmashell
   Version: 5.12.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Device Notifier
  Assignee: plasma-b...@kde.org
  Reporter: enrico.tagliav...@gmail.com
  Target Milestone: 1.0

Created attachment 113459
  --> https://bugs.kde.org/attachment.cgi?id=113459=edit
Actions showed for normal partition, but not for dmcrypt LUKS

Description of the problem:

When a removable device with an encrypted partition is inserted the device
notifier will show it, but will propose no action for it. Clicking on the item
will do nothing. Only clicking the little "eject" icon will trigger the mount
(and, even when successful it will show an error message "You are not
authorized to mount this device"; the device is correctly accessible from
/run/media despite what the error says).

In the attached screenshot an example of the problem can be seen. This is an
external USB HDD with two partitions, first one 800 GB vfat, second one 1 TB
dmcrypt LUKS with ext4 on top. Clicking the first one will show the possible
expected list of actions, but none would be shown when clicking on the second
partition label. At least the "Open with file manager" action would be
expected, also in line with what is shown for closed Vaults.


Steps to reproduce:
1. take a removable device, such as a USB based storage
2. create at least one partition with your favorite partition editor
3. create a LUKS device on at least one of the created partitions:
   cryptsetup luksFormat --cipher aes-xts-plain64 --key-size 512
--verify-passphrase /dev/path/to/partition
4. open the device to create a file system on it:
   cryptsetup luksOpen /dev/path/to/partition encrypted-partition-alias
5. create the FS: mkfs.ext4 /dev/mapper/encrypted-partition-alias
6. remove the USB device, insert it again
7. check device notifier

Reproducible: always

Note clicking on the disk label used to work before. I'm not entirely sure when
it stopped as I didn't used the device very often in the last couple of months

Versions infomation:
OS: Fedora 28 up to date
Plasma: 5.12.5
kf5: 5.47 (just updated, problem was present also with 5.46)
Qt: 5.10.1

I'll try Plasma 5.13 as soon as it's released as an update in Fedora 28 and
report back.

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

[dolphin] [Bug 394649] FTP cannot paste into current *empty* folder

[Enrico Tagliavini]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

--- Comment #1 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
I can confirm the same issue happens. I don't use FTP, but I experienced this
issue with MTP and sftp (or whatever KDE connect uses to browse the phone files
from the computer).

If I instead drag and drop the files I want to copy over it works as expected.
Copy and paste via right click doesn't.

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

[krdc] [Bug 391759] New: krdc accept invalid certificates (e.g. self signed) without asking confirmation

[Enrico Tagliavini]

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

Bug ID: 391759
   Summary: krdc accept invalid certificates (e.g. self signed)
without asking confirmation
   Product: krdc
   Version: 17.12
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: RDP
  Assignee: uwol...@kde.org
  Reporter: enrico.tagliav...@gmail.com
  Target Milestone: ---

Created attachment 111339
  --> https://bugs.kde.org/attachment.cgi?id=111339=edit
Remmina prompting the user for action

When connecting to an RDP server with self signed or invalid certificate krdc
will not prompt the user for decision making, it will simply go ahead and
continue, potentially opening to MITM attacks.

The xfreerdp client will instead report the invalid certificate, prompting the
user for action, for example:

$ xfreerdp /v:test-rdp
[15:57:01:496] [28780:28781] [INFO][com.freerdp.client.common.cmdline] -
loading channelEx cliprdr
[15:57:01:497] [28780:28781] [INFO][com.freerdp.client.x11] - No user name set.
- Using login name: testuser
[15:57:01:530] [28780:28781] [ERROR][com.freerdp.crypto] -
@@@
[15:57:01:530] [28780:28781] [ERROR][com.freerdp.crypto] - @   WARNING:
CERTIFICATE NAME MISMATCH!   @
[15:57:01:530] [28780:28781] [ERROR][com.freerdp.crypto] -
@@@
[15:57:01:531] [28780:28781] [ERROR][com.freerdp.crypto] - The hostname used
for this connection (test-rdp:3389) 
[15:57:01:531] [28780:28781] [ERROR][com.freerdp.crypto] - does not match the
name given in the certificate:
[15:57:01:531] [28780:28781] [ERROR][com.freerdp.crypto] - Common Name (CN):
[15:57:01:531] [28780:28781] [ERROR][com.freerdp.crypto] -  XRDP
[15:57:01:531] [28780:28781] [ERROR][com.freerdp.crypto] - A valid certificate
for the wrong name should NOT be trusted!
Certificate details:
Subject: CN = XRDP
Issuer: CN = XRDP
Thumbprint: b3:b1:a6:32:89:48:a0:8c:0a:ae:c4:44:43:5c:9b:d8:39:d2:b3:bb
The above X.509 certificate could not be verified, possibly because you do not
have
the CA certificate in your certificate store, or the certificate has expired.
Please look at the OpenSSL documentation on how to add a private CA to the
store.
Do you trust the above certificate? (Y/T/N)


Steps to reproduce:
1. install xrdp, it will use a self signed certificate by default (at least it
does on fedora)
2. if necessary generate a self signed certificate for xrdp, helper makefile
can be found in keygen folder of xrdp source code
3. start xrdp
4. connect with krdc to this freshly created xrdp server

Actual result:
krdc happily connect without complaining about the self singed certificate

Expected result:
krdc should prompt the user showing basic info for the certificate and
thumbprint, asking the user for a decision (see also screenshot taken from
remmina client)

This seems to be done on purpose as the xfreerdp command started by krdc
contains the /cert-ignore option. A better alternative might be the use of
/cert-tofu instead of /cert-ignore if not willing to prompt for action?

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

[klipper] [Bug 391246] Cannot copy and paste - Klipper empty entry

[Enrico Tagliavini]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

--- Comment #3 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
I also saw this a few times. It's happening very rarely and I cannot relate it
to any action for the time being. I have 10 entries in klipper (more one some
PCs), and sometimes I find myself pasting nothing, looking at the entry list
the last is empty, even though I'm fairly sure I didn't copied something empty.

This is very hard to reproduce for me so... feel free to take this with a grain
of salt

-- 
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

[Enrico Tagliavini]

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

--- Comment #296 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Agreed, always double check with a live environment if you can. Some config
files are not under config. One example: the kscreen config files (exactly the
files about your monitor configuration, size, definition, etc) are located in
~/.local/share/kscreen . Cleaning .config wont help you a single bit. One of
the problems solved was corrupted kscreen files and I think they need to be
cleaned manually once upgraded to a fixed version for the bug to go away... but
I might be wrong, a lot of time passed since I had these problems.

-- 
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

[Enrico Tagliavini]

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

--- Comment #276 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
And keep in mind another thing: this bug and a bunch of others, as far as I'm
aware, do happen solely when the proprietary driver is in use and you know how
much collaborative Nvidia is for some matters. It's either their way or
nothing. Now this doesn't mean Nvidia is the big evil and it's all their fault,
but I would put 50% of the blame on them.

But you might have another option today, and no it's not nouveau, it's AMD (or
Intel if you don't need the heavy rendering power). That's what the KDE
community focuses on. If keeping Nvidia is more of a priority for you then you
do well using another DE that works better with their driver. No need to come
here and be offensive. Bumping for attention might be ok from time to time,
being offensive is not.

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

[frameworks-kio] [Bug 386042] Only one attempt to enter correct webdav password. It will not be asked a second time

[Enrico Tagliavini]

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

--- Comment #1 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
This is on Fedora 26, Plasma 5.10.5, dolphin 17.04

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

[frameworks-kio] [Bug 386042] New: Only one attempt to enter correct webdav password. It will not be asked a second time

[Enrico Tagliavini]

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

Bug ID: 386042
   Summary: Only one attempt to enter correct webdav password. It
will not be asked a second time
   Product: frameworks-kio
   Version: 5.38.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: enrico.tagliav...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

When trying to access my nextcloud instance via webdavs URL in dolphin I have
only one change to put the correct password in. If I don't put it in right the
first time password will never be asked again.

>From the nextcloud logs I can see dolphin flooding authentication requests,
failing because the password is wrong. Eventually this is detected as a brute
force by nextcloud.

Given I have a fairly long password (24+ chars) and I'm a quite terrible write
this happens often. Only way to get back in is to reboot the computer so I'm
asked again for the password.

Even using webdavs://user:passw...@host.tld/ works after the failed first
attempt.

Steps to reproduce:
1. try to access a Nextcloud (or equivalent) instance via
"webdavs://host.tld/nextcloud/remote.php/webdav/"
2. when asked for username and password put the wrong password in
3. observe nothing happens. Page stays empty, not login failure message is
shown, password is not asked again
4. attempt again, from another dolphin window or from a file open dialogue in
kwrite, or any other application. Nothing will work

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

[okular] [Bug 169847] split view feature

[Enrico Tagliavini]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[okular] [Bug 384851] Multiple indipendent pages view

[Enrico Tagliavini]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@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

[Enrico Tagliavini]

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

--- Comment #256 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Stefano Forli from comment #255)
> Any clues on when it's going to be addressed?

For me this has been fixed a long time ago, namely in plasma version 5.8. It
looks like someone may still experience the issue when using the proprietary
nvidia driver. While this is unfortunate it is also not trivial at all to fix
as it's a driver specific problem.

I would recommend to be sure you are using nothing older than plasma 5.8 and,
for the sake of testing, trying to switch to a different driver if you are
using the proprietary nvidia driver.

-- 
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

[Enrico Tagliavini]

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

--- Comment #251 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Vitaliy Gorbunov from comment #250)
> This comment
> https://blog.martin-graesslin.com/blog/2016/07/multi-screen-woes-in-plasma-5-
> 7/#comment-71314 makes it kind of hopeless for me that this issue will be
> fixed any time soon.

To my best understanding the issue is not trivial at all, and involves multiple
components. My experience (Fedora + Intel driver) is that the issue is indeed
fixed. I think you need not only plasma 5.8 but also some version of the Qt
libraries. I'm not sure which version, I know Fedora 24 now ships with 5.6.2 so
I guess this version works. So I would check this out.

However issue might still be present for someone. Do you use nvidia driver by
any chance?

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

--- Comment #18 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Created attachment 102168
  --> https://bugs.kde.org/attachment.cgi?id=102168=edit
callgrind record of plasma shell (slow performance)

I've run a profiling run with callgrind. I started it with

valgrind --tool=callgrind --instr-atstart=no
--callgrind-out-file=plasmashell-callgrind.out -- plasmashell --shut-up

so the instrumentation was not on during the whole startup. I waited a couple
of hours with two panels and something animating in the systray. Once the CPU
usage was maximized I started the instrumentation and also started switching
active window as fast I could by using the mouse between two. Then I stopped
instrumentation and stopped valgrind.

Oddly enough, while plasma uses a lot of CPU and is quite slower compared to a
fresh start, the system performance was not dragged down as much. Usually the
whole system feels slower when plasma starts using more resources, for example
kwin animations are much slower. Firefox feels slower. Probably everything
related to rendering feels slower. Likely valgrind just shuffling the
conditions, but I thought I should mention it.

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

--- Comment #14 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Interesting new discovery. Yesterday and today the CPU usage of plasma was
quite more tame than usual.

I have to digress a bit here, sorry: it's quite a long time I have two
identical panels in my desktop, one per monitor. The reason is the infamous
problematic multi screen support. If I was booting the laptop without an
external monitor attached there was quite an high chance (around 50%) that my
panel was not displayed. So I added a second one and this worked the problem
around, I was getting one of the two. [end of digression].

With 5.8 multi screen situation improved, and I'm hopeful I can actually remove
the second panel and live with only one. So I removed the second panel yesteday
morning. Today I was a bit surprised because, while the plasma CPU usage
increased over time it increased at a slower peace. So I added a second
(default) panel. Plasmashell exhausted the system memory in a matter of second
(for a total of 10 GB, the rest was already in use by other stuff)

[23477.201126] Out of memory: Kill process 2358 (plasmashell) score 535 or
sacrifice child
[23477.201134] Killed process 2358 (plasmashell) total-vm:19426516kB,
anon-rss:10795480kB, file-rss:0kB, shmem-rss:28452kB
[23477.682638] oom_reaper: reaped process 2358 (plasmashell), now anon-rss:0kB,
file-rss:0kB, shmem-rss:28452kB

I started a new one, the second panel was there. I sent myself a message to
trigger the telepathy icon in the systray (I had two of them now), issue
appeared quite quickly. I removed the telepathy notification and also the
second panel. CPU usage of plasma is still very high.

So I think this is quite an important condition to reproduce the issue: have
more than one panel. I'm not sure if some of the widgets are more involved than
others, but I guess the systray could be a good start. That however is not
involved at all in the window switching, which would point to the task manager
instead. In my testing I had two of both.

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 Attachment #102089|0   |1
is obsolete||

--- Comment #12 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Created attachment 102105
  --> https://bugs.kde.org/attachment.cgi?id=102105=edit
perf record of plasma shell (still working good)

Well, since 'kquitapp5 plasmashell ; plasmashell --shut-up' temporarily fixes
the issue I just restarted plasmashell and recorded it again.

In this record I constantly switch window to have a similar situation when high
CPU usage is triggered. In this case plasmashell doesn't even reach 50% (it's
between 40 and 50%) of a single core and the system feels perfectly responsive
and smooth. Still a pretty significant CPU usage just for switching window.
This again without any effect triggering, the two windows are not overlapping,
the only visible change is the status bar color change. Also, for what I
understand, the animation is done by kwin process.

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

--- Comment #11 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
So I think I've added enough information for the time being. Please put the bug
in OPEN status again (I can't I'm not the original reporter).

Tomorrow I'll also take the perf statistic after a fresh boot, as the one I
posted is with the debugging symbol not installed.

Thank you Rex for pointing out the copr provides debuginfos... I couldn't find
them myself and got fooled by a stupid typo :)

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

--- Comment #10 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Created attachment 102103
  --> https://bugs.kde.org/attachment.cgi?id=102103=edit
perf record of plasma shell (systray animation when in slow performance
condition)

I've done an additional capture (which actually happened right before the
previous one I posted). Here I'm just doing my usual work, I'm not heavily
triggering the Windows change on purpose. However I have the telepathy little
message systray icon animation happening. I actually left it there quite a
while before doing this capture. I thought about adding it since it might be
related... better safe than sorry.

Also I think this might actually have accelerated the performance degeneration
as well. I've had KRDC and virt-manager open the whole day, but it was not as
bad. Performance was going down, but not too fast. So the systray animation
might actually be a heavy contributor.

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

--- Comment #9 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Created attachment 102102
  --> https://bugs.kde.org/attachment.cgi?id=102102=edit
perf record of plasma shell (slow performance)

Sorry epic fail on my side. I had a typo in the command to install the
debuginfo packages (I used dnf debuginfo-install --enable-repo instead of
--enablerepo, dnf doesn't complain the option doesn't exist when using the
debuginfo-install plugin... sorry!).

I've the debuginfo installed! Here is the perf data collected as root. I have
all my applications open (as in previous comment + okular + KRDC). Here I'm
constantly jumping between windows to trigger the high CPU utilization (to make
number higher let's say). It's using 100% of one core. When I just don't move
from a window the CPU utilization is near zero. Also changing window without
involving any animation triggers the CPU utilization.

Note I had to compress it due to the size exceeding 4 MB limitation of this
bugzilla.

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

--- Comment #6 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Created attachment 102089
  --> https://bugs.kde.org/attachment.cgi?id=102089=edit
perf record of plasma shell (still working good)

I thought about giving you a comparison, hoping it's useful, between a fresh
boot of the system (when plasma is still working as expected and there is no
issue exposed yet), and when the issue is very visible.

In this capture I have all my applications open (firefox, kmail, quassel,
konsole, yakuake, virt-manager) and doing my normal work (answering emails and
the like). This is a fresh boot and plasma performance is still good and there
is no issue.

I've installed the debug symbols for plasma-workspace dependencies. However
debug info RPMs for the copr repo with plasma 5.8.3 are not available to my
best knowledge.

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

--- Comment #4 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
As suggested by Rex I tried the Plasma 5.8.3 packages from the Fedora KDE
unstable copr repository (which is what will become the official Fedora
packages) https://copr.fedorainfracloud.org/coprs/g/kdesig/plasma-5-unstable/

Problem still exists unfortunately. I have the impression using programs like
virt-manager and krdc makes the problem easier to reproduce. I frequently have
a CentOS 7 VM running and open in virt-manager and I use a desktop on it. I
also use krdc quite frequently to connect to remote Windows systems right after
closing KRDC I noticed plasmashell process eating between 50 and 100% of one
core (it started before I closed KRDC I noticed the environment to become less
and less responsive).

To be clear: I think krdc and virt-manager are making the issue appear faster,
they are not the only trigger

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Enrico Tagliavini]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

--- Comment #2 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Same for me on Fedora 24

After multi hours usage on a laptop with external monitor attached, powered by
Skylake CPU and GPU (i7-6700HQ), Plasma becomes slower and slower, even the
mouse pointer slows down. I observed the plasmashell process using more and
more CPU and RAM over time. Restarting plasmashell fixes the issue temporarily,
it reappears after enough time.

I just found another user on IRC (Lipsum) having the exact same problem. He
also has multi monitor and Skylake.

I tried both modesetting DDX and intel DDX, it happens with both. With
modesetting it's worst though, probably because glamor is slower than SNA.

Version-Release number of selected component (if applicable):
root@enrico-dell ~ # rpm -qa | grep
'plasma-workspace-5\|mesa-dri\|modset\|xorg-x11-server-Xorg'
xorg-x11-server-Xorg-1.18.4-4.fc24.x86_64
plasma-workspace-5.7.5-2.fc24.x86_64
mesa-dri-drivers-12.0.3-2.fc24.x86_64

Steps to Reproduce:
1. Multi monitor setup is required
2. Start a plasma session and use it normally
3. Monitor plasmashell CPU and RAM usage over time
4. Notice the performance of plasma, especially on the external monitor, become
sluggish

Actual results:
Plasma uses more and more RAM and CPU, performance is degraded and user
experience is affected (sluggish interaction, slow response from the plasma
shell)


Expected results:
CPU and RAM usage should be faily constant over time. Responsiveness of the
shell should be constant in time and not sluggish.


Additional info:
I'm not sure if a better than full HD monitor is required. I have the following
configration:

taglenri@enrico-dell ~ $ xrandr
Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
eDP1 connected primary 1920x1080+2560+0 (normal left inverted right x axis y
axis) 350mm x 190mm
   1920x1080 59.93*+
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1368x768  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm
x 340mm
   2560x1440 59.95*+
   2048x1152 60.00  
   1920x1200 59.95  
   1920x1080 60.0060.0050.0059.9430.0025.0024.00   
29.9723.98  
   1920x1080i60.0050.0059.94  
   1600x1200 60.00  
   1680x1050 59.88  
   1280x1024 75.0260.02  
   1200x960  59.99  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   720x480i  60.0059.94  
   640x480   75.0060.0059.94
   720x400   70.08  
HDMI2 disconnected (normal left inverted right x axis y axis)   
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


It is quite easy to notice the issue earlier if enabling the "Slide back"
effect for Kwin compositing.

-- 
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

[Enrico Tagliavini]

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

--- Comment #231 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Mohammed Arafa from comment #230)
> i just deleted ~/.config/kwinrc and rebooted and logged in 
> 

FYI kwin is (almost) totally unrelated to multi-monitor configuration. That's
kscreen. If you want to reset the multi-monitor setup you should delete
~/.local/share/kscreen/, while not running KDE (yes you need to do it from
another DE or tty). This will bring you to the default when you login next.

As far as I understand what you describe is this bug (wrong panel positioning),
plus screen configuration issues, which are unrelated to this problem. In KDE
the kscreen component will configure the screens (like what you can do with
xrandr from command line). The panel positioning is job for plasma workspace. I
think you should open a new bug for the screeens configuration.

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

[gwenview] [Bug 371027] gwenview crash when cropping a specific image (works on most images)

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #1 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Created attachment 101607
  --> https://bugs.kde.org/attachment.cgi?id=101607=edit
Sample image causing the crash when cropped

This is an image from a very old camera. It could be it has some weird meta
information or something like that.

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

[gwenview] [Bug 371027] New: gwenview crash when cropping a specific image (works on most images)

[Enrico Tagliavini via KDE Bugzilla]

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

Bug ID: 371027
   Summary: gwenview crash when cropping a specific image (works
on most images)
   Product: gwenview
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: enrico.tagliav...@gmail.com
CC: myr...@kde.org

Application: gwenview (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.7-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
Steps to reproduce:
1. open the (soon to be attached) image with gwenview
2. select edit -> crop
3. cut off some part of image and hit the crop button
4. press save and observe the crash

Actual result:
gewnview terminates unexpectedly without saving the cropped image.

Expected results:
save the cropped image correctly

The crash can be reproduced every time.

-- Backtrace:
Application: Gwenview (gwenview), signal: Aborted
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7f0488a9c0 (LWP 10221))]

Thread 4 (Thread 0x7f7ef2e5f700 (LWP 10224)):
[KCrash Handler]
#6  0x7f7f12b6a6f5 in raise () at /usr/lib64/libc.so.6
#7  0x7f7f12b6c2fa in abort () at /usr/lib64/libc.so.6
#8  0x7f7f12b62f97 in __assert_fail_base () at /usr/lib64/libc.so.6
#9  0x7f7f12b63042 in  () at /usr/lib64/libc.so.6
#10 0x7f7f1893568e in Exiv2::Internal::TiffMnEntry::doAddPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#11 0x7f7f1892f432 in Exiv2::Internal::TiffComponent::addPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#12 0x7f7f1892fee7 in Exiv2::Internal::TiffDirectory::doAddPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#13 0x7f7f1892f432 in Exiv2::Internal::TiffComponent::addPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#14 0x7f7f1893528d in Exiv2::Internal::TiffSubIfd::doAddPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#15 0x7f7f1892f432 in Exiv2::Internal::TiffComponent::addPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#16 0x7f7f1892fee7 in Exiv2::Internal::TiffDirectory::doAddPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#17 0x7f7f1892f432 in Exiv2::Internal::TiffComponent::addPath(unsigned
short, std::stack >&,
Exiv2::Internal::TiffComponent*, std::auto_ptr)
() at /usr/lib64/libexiv2.so.14
#18 0x7f7f1894fc3c in
Exiv2::Internal::TiffEncoder::add(Exiv2::Internal::TiffComponent*,
Exiv2::Internal::TiffComponent*, unsigned int) () at /usr/lib64/libexiv2.so.14
#19 0x7f7f1893bec6 in
Exiv2::Internal::TiffParserWorker::encode(Exiv2::BasicIo&, unsigned char
const*, unsigned int, Exiv2::ExifData const&, Exiv2::IptcData const&,
Exiv2::XmpData const&, unsigned int, void
(Exiv2::Internal::TiffEncoder::*(*)(std::__cxx11::basic_string const&, unsigned int,
Exiv2::Internal::IfdId))(Exiv2::Internal::TiffEntryBase*, Exiv2::Exifdatum
const*), Exiv2::Internal::TiffHeaderBase*, Exiv2::Internal::OffsetWriter*) ()
at /usr/lib64/libexiv2.so.14
#20 0x7f7f188c3807 in Exiv2::ExifParser::encode(std::vector >&, unsigned char const*, unsigned int,
Exiv2::ByteOrder, Exiv2::ExifData const&) () at /usr/lib64/libexiv2.so.14
#21 0x7f7f188e0616 in Exiv2::JpegBase::doWriteMetadata(Exiv2::BasicIo&) ()
at /usr/lib64/libexiv2.so.14
#22 0x7f7f188e1d23 in Exiv2::JpegBase::writeMetadata() () at
/usr/lib64/libexiv2.so.14
#23 0x7f7f1ad76837 in Gwenview::JpegContent::save(QIODevice*) () at
/usr/lib64/libgwenviewlib.so.5
#24 0x7f7f1ad3a311 in

[plasmashell] [Bug 353975] Black screen on second display.

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #83 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Marcelo Rocha from comment #81)
> Did you try to unninstall your video driver? 
> 
> I tried removing my xf86-video-intel and let it run only with modsetting,
> and the issue was fixed for me now.

Let's try to avoid confusion, this is a KDE bug, not a video driver bug. I
don't say switching to modesetting didn't helped you (especially for Skylake
many distros are switching to modesetting over intel, including Fedora 24 which
uses modesetting only by default), but the black screen issue might have been a
fluke.

It has also been officially confirmed that Plasma releases before 5.7 has
sup-par multi screen support. The first system change a user might attempt to
fix this problem should be trying Plasma 5.8, not messing with the video driver
(it's messy, a lot of time is usually needed and here it's not the most likely
cause). See also
https://vizzzion.org/blog/2016/09/lts-releases-align-neatly-for-plasma-5-8/ and
let me quote Sebastian Kügler's comment "Especially support for multi-screen
systems in 5.7 is sub-par, those users would really benefit from getting Plasma
5.8."

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

[okular] [Bug 267350] filling out a PDF form saves data to some file i ~/.kde/share/apps/okular/docdata/

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasma-nm] [Bug 356342] Size of popup of plasma-nm inside panel or desktop is very small

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #13 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Jan Grulich from comment #12)
> Git commit f1284fb32ba7bfff634916fce861ad6fa79e23a5 by Jan Grulich.
> Committed on 12/05/2016 at 09:02.
> Pushed by grulich into branch 'master'.
> 
> Make the size of popup applet slightly bigger
> 
> M  +2-2applet/contents/ui/main.qml
> 
> http://commits.kde.org/plasma-nm/f1284fb32ba7bfff634916fce861ad6fa79e23a5

Thank you Jan, much appreciated

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

[frameworks-plasma] [Bug 350825] kf5 5.12.0 broke plasma-nm 5.3.2 and power management widgets popup windows

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 Depends on||356342

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

[plasma-nm] [Bug 356342] Size of popup of plasma-nm inside panel or desktop is very small

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 Blocks||350825

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

[plasma-nm] [Bug 362734] networkmanager plasmoid doesn't export any Layout.minimumWidth/minimumHeight

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 Blocks||350825

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

[plasmashell] [Bug 362735] battery and brightness plasmoid doesn't export any Layout.minimumWidth/minimumHeight

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 Blocks||350825

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

[frameworks-plasma] [Bug 350825] kf5 5.12.0 broke plasma-nm 5.3.2 and power management widgets popup windows

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 Depends on||362734, 362735

--- Comment #23 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Marco Martin from comment #22)
> the problem is actually in the networkmanager plasmoid, as it doesn't export
> any Layout.minimumWidth/minimumHeight in its full representation, which is
> mandatory.
> same thing for the battery monitor

Ok then, opened bug #362734 for the network widget and bug #362735 for the
battery widget and used this one soft of as a tracker.

Thank you for looking into this

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

[plasmashell] [Bug 362735] New: battery and brightness plasmoid doesn't export any Layout.minimumWidth/minimumHeight

[Enrico Tagliavini via KDE Bugzilla]

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

Bug ID: 362735
   Summary: battery and brightness plasmoid doesn't export any
Layout.minimumWidth/minimumHeight
   Product: plasmashell
   Version: 5.6.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Battery Monitor
  Assignee: k...@privat.broulik.de
  Reporter: enrico.tagliav...@gmail.com
CC: plasma-b...@kde.org

As stated in comment 22 bug #350825 . Since the update to kf5 5.12.0 the
battery and brightnes applet, when used from a panel, has a very small popup,
hard to see / use. It's smaller than the one popping up when used from the
systray, which works better. See bug #350825 for some screenshot

Reproducible: Always

Steps to Reproduce:
1. add the battery widget to a panel
2. open the battery widget from a panel
3. compare the pop up size with the one from the battery widget from the
systray

Actual Results:  
Notice the size difference between the two, sometimes, when many elements are
present in the widget (multiple batteries, brightness controls or applications
preventing the power management) some of them might be unreachable due to the
size of the window and the lack of scroll possibility. Also the battery
information section is reduced too much in size in such situation

Expected Results:  
The networks battery window should be bigger when used from the panel, ideally
the same size as when used from the systray. If needed some additional
adjustment to accommodate when a lot of elements are present filling also a
bigger window.

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

[plasma-nm] [Bug 362734] New: networkmanager plasmoid doesn't export any Layout.minimumWidth/minimumHeight

[Enrico Tagliavini via KDE Bugzilla]

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

Bug ID: 362734
   Summary: networkmanager plasmoid doesn't export any
Layout.minimumWidth/minimumHeight
   Product: plasma-nm
   Version: 5.6.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: enrico.tagliav...@gmail.com
CC: lu...@kde.org

As stated in comment 22 bug #350825 . Since the update to kf5 5.12.0 the
networkmanager applet, when used from a panel, has a very small popup, hard to
see / use. It's smaller than the one popping up when used from the systray,
which works as expected.

See bug #350825 for some screenshot

Reproducible: Always

Steps to Reproduce:
1. add the networks widget to a panel
2. open the network widget from a panel
3. compare the pop up size with the one from the network widget from the
systray

Actual Results:  
Notice the size difference between the two, sometimes, when used from the
panel, the networks widget window is too small to be easy to use

Expected Results:  
The networks widget window should be bigger when used from the panel, ideally
the same size as when used from the systray or anyway big enough not to preset
any impairment

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

[i18n] [Bug 360163] Missing option to set a 24 hour clock and Sunday to Thursday weekday

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasmashell] [Bug 353975] Black screen on second display.

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #23 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Bernd Steinhauser from comment #19)
> You can have the bug with other resolutions as well and also if the screens
> have the same resolution.
> The resolution doesn't matter as far as I can tell.

Yep scratch what I said... today the setup that used to work (which I use
rarely) actually messed up (for the first time) upon login  :(

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

[plasmashell] [Bug 353975] Black screen on second display.

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #17 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Maybe that's a fluke but it seems like this happens only in some specific,
albeit common, configuration. In my case I move my laptop between two desks.
One has a 1080p monitor (exactly the same resolution as the laptop screen), the
other has a 1680x1050 monitor. I get the black screen after login only with the
former one. The latter works as expected.

Anybody with this problem and two monitors of different resolutions by any
chance?

However, oddly enough, for my colleague desktop (note: not a laptop), where he
has two monitors of the same resolution, everything works fine. However, being
a desktop, he never connect or disconnect monitors which might be related (see
bug #353052).

This all is on Fedora 22 and 23, fully up to date. Currently using plasma 5.5.5

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

[korganizer] [Bug 359314] New: Folder property "Block reminders locally" doesn't work (at least for google calendars)

[Enrico Tagliavini via KDE Bugzilla]

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

Bug ID: 359314
   Summary: Folder property "Block reminders locally" doesn't work
(at least for google calendars)
   Product: korganizer
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: reminder daemon (korgac)
  Assignee: korganizer-de...@kde.org
  Reporter: enrico.tagliav...@gmail.com

Version of Korganizer (it's missing in the drop down list): 4.14.10
KDE Development Platform version: 4.14.14
OS: Fedora 22 fully up to date as of the time of this writing

Calendar is a Google calendar

Reproducible: Always

Steps to Reproduce:
1. Add a google calendar of type Google Calendar
2. Right click on its folder in the bottom left corner of the main interface of
korganizer and select Folder properties...
3. Check the "Block reminders locally" option

Actual Results:  
wait for the correct time and notice the reminder (being it email or display)
is actually dispatched

Expected Results:  
no notification should be shown for any reminder set in this calendar

The only workaround is to disable reminders by right clicking in the systray
icon, but this applies to all calendars, not only the one I want to ignore.

-- 
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

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #15 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Another workaround is to open krunner (alt + space by default) and run:

kquitapp5 plasmashell ; /usr/bin/plasmashell --shut-up

After the first time krunner will remember the command, so you just need to
start typing it. This also seems to suggest that if plasma is started it will
detect the monitors and choose where to put the panels correctly. It's just not
recomputed correctly after a change at runtime. Or maybe it get confused by the
monitor being removed, but the virtual is not changed immediately (see xrandr
-q output example in comment 3 in bug #310168 ).

-- 
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

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasmashell] [Bug 355953] Desktop on screens are switched on restart

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasmashell] [Bug 353975] Black screen on second display.

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasmashell] [Bug 347637] When I unplug the HDMI output, my desktop gets a bigger resolution - Samsung R480

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

--- Comment #6 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
For xrandr -q outputs see my comments on bug #310168 . Sorry copy and paste
doesn't work for some weird reason :(

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

[KScreen] [Bug 353052] Disconnecting secondary screen leaves primary screen with huge virtual resolution

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[frameworks-plasma] [Bug 350825] kf5 5.12.0 broke plasma-nm 5.3.2 and power management widgets popup windows

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #21 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
For me the content of the battery widget is not shown completely and I have no
way of displaying it other than putting the widget on the desktop, see the
attachments. Resizing the popup might help but, to be honest, I would rather go
for option B: the popup should have the same size regardless where it comes
from. If it comes from a widget on a panel it should have the same size as a
widget in the systray. Consistency in the UI is good isn't it? Maybe it's just
personal preference though.

That said the major usability issue is solved, this is a lesser problem

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

[KScreen] [Bug 353052] Disconnecting secondary screen leaves primary screen with huge virtual resolution

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #1 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Same issue for me, see comment 3 in bug #310168 for xrandr outputs (sorry copy
and paste is not behaving :( )

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

[kwin] [Bug 310168] Application stays in invisible screen area even after disabling disconneted display in System Settings

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #5 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Thank you for the info, I CCed to the other one :)

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

[plasmashell] [Bug 328593] Dual screen has regressed in plasma-shell

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[kwin] [Bug 310168] Application stays in invisible screen area even after disabling disconneted display in System Settings

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #3 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
(In reply to Thomas Lübking from comment #2)
> what's the output of "xrandr -q" (assuming you're using that rather than
> actual "multihead") before and after disconnecting the screen?

[Note I'm not the original reporter but I have this problems since an update to
plasma 5.3.something IIRC]

It's problematic to answer this question since running xrandr will actually
trigger the notification and screen reconfiguration (as it should happen
automatically).

Output with both monitors connected:
$ xrandr -q
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y
axis) 294mm x 165mm
   1920x1080 59.93*+
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1368x768  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x
268mm
   1920x1080 60.00*+
   1680x1050 59.95  
   1280x1024 75.0260.02  
   1152x864  75.00  
   1024x768  75.0860.00  
   800x600   75.0060.32  
   640x480   75.0060.00  
   720x400   70.08  
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

If I disconnect the DP1 connected monitor screen config doesn't change. All
applications on it are still not visible, I'm able to move windows there and so
on, everything like if the monitor is connected, but I have to do it blindly.

Now if I run xrandr I get:
$ xrandr -q
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y
axis) 294mm x 165mm
   1920x1080 59.93*+
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1368x768  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 disconnected 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  1920x1080 (0x49) 148.500MHz
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  67.50KHz
v: height 1080 start 1084 end 1089 total 1125   clock  60.00Hz

(notice the VIRTUAL1) My screen flickers a bit, reconfiguration happens, I can
see all the Windows, running xrandr again now and I get:

$ xrandr -q
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
294mm x 165mm
   1920x1080 59.93*+
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1368x768  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

VIRTUAL1 is gone and the screen layout is what it should be.



Now if I do the opposite (I connect the monitor back) nothing happens again.
Monitor stays in power save mode, running xrandr will trigger the automatic
config:

$ xrandr -q
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
294mm x 165mm
   1920x1080 59.93*+
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1368x768  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 connected (normal left inverted right x axis y axis)
   1920x1080 60.00 +
   1680x1050 59.95  
   1280x1024 75.0260.02  
   1152x864  75.00  
   1024x768  75.0860.00  
   800x600   75.0060.32  
   640x480   75.0060.00  
   720x400   70.08  
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Note there is no '*' 

[frameworks-plasma] [Bug 350825] kf5 5.12.0 broke plasma-nm 5.3.2 and power management widgets popup windows

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #18 from Enrico Tagliavini <enrico.tagliav...@gmail.com> ---
Update about version: with kf5 5.17 + plasma 5.5.1 (again on Fedora 22)
situation seems better. While still undersized (connect button and connection
name do overlap quite a bit and it is much smaller than the popup from the
systray) the plasma-nm widget is now usable from the panel! The battery widget
popup is still undersized as well, plus it missed a scroll bar in case multiple
applications are preventing laptop power save.

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

[kwin] [Bug 310168] Application stays in invisible screen area even after disabling disconneted display in System Settings

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <enrico.tagliav...@gmail.com> changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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