[kdeplasma-addons] [Bug 482658] Network speed widget showing nothing, again
https://bugs.kde.org/show_bug.cgi?id=482658 Nicola Mori changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 482658] Network speed widget showing nothing, again
https://bugs.kde.org/show_bug.cgi?id=482658 --- Comment #1 from Nicola Mori --- I fixed the problem by installing networkmanager-qt. Probably this could have fixed everything also for Plasma 5.27. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 482658] New: Network speed widget showing nothing, again
https://bugs.kde.org/show_bug.cgi?id=482658 Bug ID: 482658 Summary: Network speed widget showing nothing, again Classification: Plasma Product: kdeplasma-addons Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: nicolam...@aol.com Target Milestone: --- SUMMARY Please see this bug report: https://bugs.kde.org/show_bug.cgi?id=476537 The upgrade to Plasma 6.0.1 didn't fix it. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 478198] Umbrello import wizard does not recognize the 'override' C++ keyword
https://bugs.kde.org/show_bug.cgi?id=478198 --- Comment #8 from Nicola Mori --- Thank you very much Oliver. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 478198] Umbrello import wizard does not recognize the 'override' C++ keyword
https://bugs.kde.org/show_bug.cgi?id=478198 --- Comment #4 from Nicola Mori --- (In reply to Oliver Kellogg from comment #1) > Created attachment 163981 [details] > Screenshot showing imported classifiers I and C > > Cannot reproduce, see attached screenshot. Nor can I... It's weird, I accurately tested the reproducer before opening the bug report and I'm 100% sure it behaved as I wrote in my first post. Anyway, I can still reproduce garbage behavior with my original header file. You can download it here: https://basket.fi.infn.it:443/f/ee0c58a81b/?dl=1) together with a cpp file for compiling everything and check that it's correct code. Sorry for the poor overall state of the code but it's just a playground for testing ideas, and I was trying to extract the UML with Umbrello after verifying that the overall design works for me. When importing the test.h header the AlgoSequenceDecorator class is imported without any method, and the AlgoSequence and MTScheduler classes are not imported at all. Removing all the override keywords (sed -i 's/override//g' test.h) the AlgoSequenceDecorator is imported with all its methods, and also AlgoSequence is now imported; however MTScheduler is stil missing, so probably there's more than just override. I uploaded two screenshots showing this behavior. The code compiles fine both with and without the override keywords, so it's valid and thus I think this is a problem with Umbrello. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 478198] Umbrello import wizard does not recognize the 'override' C++ keyword
https://bugs.kde.org/show_bug.cgi?id=478198 --- Comment #3 from Nicola Mori --- Created attachment 164046 --> https://bugs.kde.org/attachment.cgi?id=164046=edit Import of full project (see comment 2) without override keywords. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 478198] Umbrello import wizard does not recognize the 'override' C++ keyword
https://bugs.kde.org/show_bug.cgi?id=478198 --- Comment #2 from Nicola Mori --- Created attachment 164045 --> https://bugs.kde.org/attachment.cgi?id=164045=edit Import of full project (see comment 2) with override keywords. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 478198] Umbrello import wizard does not recognize the 'override' C++ keyword
https://bugs.kde.org/show_bug.cgi?id=478198 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 478198] New: Umbrello import wizard does not recognize the 'override' C++ keyword
https://bugs.kde.org/show_bug.cgi?id=478198
Bug ID: 478198
Summary: Umbrello import wizard does not recognize the
'override' C++ keyword
Classification: Applications
Product: umbrello
Version: Git
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: importer
Assignee: umbrello-de...@kde.org
Reporter: nicolam...@aol.com
Target Milestone: ---
SUMMARY
When importing C++ code containing the 'override' keyword Umbrello either does
not import the class, or imports it with missing methods, or the overall import
is screwed. A simple reproducer is available below; correct behavior can be
restored by removing the `override` keyword.
This seems to be a regression since a similar bug has been fixed in
https://bugs.kde.org/show_bug.cgi?id=386258.
Using Umbrello 2.38.3 (Applications 23.08.3); this version is not listed in the
`Version` list of the bug tracker so I chose `Git`.
STEPS TO REPRODUCE
1. Create a simple header file like this:
```
class I {
public:
virtual void Method() = 0;
};
class C: public I {
public:
void Method() override {}
};
```
2. Import it with the Code Importing Wizard
3. Verify that class `I` is parsed in the import logger tab
OBSERVED RESULT
Class `I` is not available in the Tree View
EXPECTED RESULT
Class `I` should be available
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kdeplasma-addons] [Bug 476537] Network speed widget shows nothing
https://bugs.kde.org/show_bug.cgi?id=476537 --- Comment #4 from Nicola Mori --- Well, this is disappointing. A standard feature breaks in the current stable version and there's no plan to fix it. Not everybody will jump on Plasma 6 on day 0 so I was expecting more care for the 5.27 series. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 476537] Network speed widget shows nothing
https://bugs.kde.org/show_bug.cgi?id=476537 --- Comment #2 from Nicola Mori --- Thanks Nate, but as I understand this is being worked for Plasma 6: will the fix be backported to 5.27 series? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 476537] Network speed widget shows nothing
https://bugs.kde.org/show_bug.cgi?id=476537 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 476537] New: Network speed widget shows nothing
https://bugs.kde.org/show_bug.cgi?id=476537 Bug ID: 476537 Summary: Network speed widget shows nothing Classification: Plasma Product: kdeplasma-addons Version: 5.27.9 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: nicolam...@aol.com Target Milestone: --- SUMMARY The Network speed widget shows no graph. No network sensors are available in the Sensors detail panel, although other sensor categories (CPUs, Disks etc.) are listed. Other system monitoring widgets work fine. It is worth mentioning that the network monitor panel in the System load tab of KSysGuard works fine. STEPS TO REPRODUCE 1. Add a Network speed widget to the desktop OBSERVED RESULT The Network speed widget shows no upload/download graphs EXPECTED RESULT The Network speed widget should show upload/download graphs SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.11.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Affected hardware is Dell XPS 15 9570. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428945] Transparency causes flickering in Zoom sessions
https://bugs.kde.org/show_bug.cgi?id=428945 --- Comment #3 from Nicola Mori --- I forgot to mention that I have no problem when sharing screen with other applications like Discord. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428945] Transparency causes flickering in Zoom sessions
https://bugs.kde.org/show_bug.cgi?id=428945 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com --- Comment #2 from Nicola Mori --- I have the same issue. In my case I've been able to fix it by switching to XRender for the compositor rendering backend: no flickering event with active transparency. With openGL 3.1 and 2.0 backends I get flickering, so I guess that OpenGL might play a role also for others affected by this issue. All of the above in a X11 session. My VGA is an Intel UHD Graphics 630 (integrated in a Core i7 8750H mobile CPU), and I'm currently using Mesa 21.0.2 and xf86-video-intel 2.99.917+916+g31486f40. SOFTWARE/OS VERSIONS Linux: Archlinux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433695] New: Can't set the statistics refresh rate of system monitor widgets.
https://bugs.kde.org/show_bug.cgi?id=433695 Bug ID: 433695 Summary: Can't set the statistics refresh rate of system monitor widgets. Product: plasmashell Version: 5.21.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: nicolam...@aol.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY As far as I understand the statistics refresh rate of network monitor widget has been forced to 1 s (see https://bugs.kde.org/show_bug.cgi?id=433063). However, on my system it seems to be about 0.5 s, so I'm wondering why the forced 1 s interval does not work on my system and if it is possible to set the rate at least for other system monitor widgets (I see the same behavior with CPU usage, Memory and Core temp) since I can't find a setting for this and it's too frequent for my taste. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux packages KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm not using NetworkManager to configure my network (I'm using netctl), but I have the networkmanager, networkmanager-qt and libnm packages installed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433063] Network Speed widget is not working
https://bugs.kde.org/show_bug.cgi?id=433063 --- Comment #6 from Nicola Mori --- I just updated to 5.21.0 on my Archlinux box and the network widget now works again after the failure of 5.20 series. I don't use NetworkManager nor have "Networks" popup in my system tray. I still could not find a way to set the refresh rate (currently it seems to be around 2 Hz, too much for me) but at least the widget works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #79 from Nicola Mori --- @Nate Thanks, I already had clear in mind that the fix is going to ship in 5.21. I just had a residual curiosity about what makes the widget work bad in 5.20, since I think I compiled ksysguard with networkmanager-qt and still the widget does not work (maybe I should use NetworkManager to configure my connection?) while ksysguard itself shows the network traffic correctly. But it's not a big deal now that the fix is coming, even if I'd like to restore this functionality possibly without waiting for 5.21. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #77 from Nicola Mori --- According to my package manager, the ksystemstats executable in my system is part of the ksysguard 5.20.5 package: $ pacman -Qo `which ksystemstats` /usr/bin/ksystemstats is owned by ksysguard 5.20.5-1 I don't know if this is relevant or not, but judging from other comments (e.g. comment 62) it seems the --replace option should work with version 5.20.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #75 from Nicola Mori --- @David I just rebuilt ksysguard on my system where networkmanager-qt is installed. The CMake output seems to indicate that Kf5NetworkManagerQy is correctly found: -- The following RECOMMENDED packages have been found: * KF5NetworkManagerQt (required version >= 5.74) Provides an improved backend for Network statistics but libKF5NetworkManagerQt.so is not linked to the ksysguard nor the ksystemstats executables. anyway network information is correctly displayed by ksysguard, the widget still don't work and running "NLCB=debug sudo ksystemstats --replace" gives: Unable to start backend, network information not available. Unable to register DBus service org.kde.ksystemstats. Maybe it is already running? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #72 from Nicola Mori --- I don't use NetworkManager, I just have it installed. But in comment 14 another Arch user reports he is using it and still he has the problem. Maybe Arch builds ksysguard without networkmanager-qt (as per comment 10 I understand this might be the source of teh problem, right?). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #70 from Nicola Mori --- @DavidRedondo as I already explained in comment 61 I have several NetworkManager packages installed in my Archlinux system, yet the network widget doesn't work. This makes me think that the issue might not be 100% connected to NetworkManager, but I got no reply to my comment asking for clarifications. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 432426] Legend will not display anything until legend is full if line chart is filled from end
https://bugs.kde.org/show_bug.cgi?id=432426 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #61 from Nicola Mori --- Thanks David for the fix. I'm not familiar with KDE code but from the comment it seems to me that the fix is a fallback for when NetworkManager is not available. So should the widget work when NetworkManager is present? I'm asking because I have networkmanager and networkmanager-qt installed on my Archlinux system but the widget doesn't work: should I install some other NetworkManager component, or maybe I'm completely wrong and installing NetworkManager is not supposed to fix anything? Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #59 from Nicola Mori --- Also on my Archlinux system the widget still does not work after upgrading to Plasma 5.20.5. It's since Plasma 5.19.0 that it is broken for me, and while being a popular (20 persons in the CC list) and confirmed bug for a basic and default widget still nothing has been done for fixing it. I ask the KDE devs watching this thread if there is anything that we the users can do to support the fix procedure. I'm growing tired of such a basic functionality being broken for so long. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #53 from Nicola Mori --- I've removed the plasma-wayland-session package from my system to remove the Plasam Wayland option as suggested by Vladislav but still the network widget does not work. If the issue is related to Wayland then maybe it's not related to Plasma Wayland itself. Archlinux with Plasma 5.20.4-2, Frameworks 5.76.0-1 and Qt 5.15.2-1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 --- Comment #11 from Nicola Mori --- (In reply to David Redondo from comment #7) > Does it work after restarting plasma? I can see that switching styles > sometimes does not work but also on nvidia and intel Yes, adding a cpu monitor widget with line style to the panel and then restarting plasma it works. Thanks for the suggestion. I think that with this workaround and the patch this report can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 Nicola Mori changed: What|Removed |Added Version|5.20.2 |5.20.3 --- Comment #6 from Nicola Mori --- The bug is still present in 5.20.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #45 from Nicola Mori --- The bug is still present in 5.20.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423616] System monitor desktop widgets are frozen after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=423616 Nicola Mori changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Nicola Mori --- I didn't experience any freeze with 5.20.2 during the last few days, so probably the bug has been incidentally fixed. I think this issue can be closed, I'll reopen it should the freeze happen again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423616] System monitor desktop widgets are frozen after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=423616 --- Comment #5 from Nicola Mori --- It surely happened with bar chart and with text-only. I don't remember exactly about line, and I don't use pie. Actually, it's a bit that I don't notice any problem but I might have overlooked that. I'll keep the eyes opened and report here in a few days. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #42 from Nicola Mori ---
I'm experiencing the same problem. If i try to run ksystemstats I get:
Unable to start backend, network information not available.
Unable to register DBus service org.kde.ksystemstats. Maybe it is already
running?
Running ksysguard the network activity is correctly displayed, and when closing
it I get these messages on the terminal:
QProcess: Destroyed while process ("/usr/lib/ksysguard/ksgrd_network_helper")
is still running.
org.kde.ksysguard.plugin.network: Helper process terminated abnormally!
org.kde.ksysguard.plugin.network: ""
Plasma 5.20.2 with frameworks 5.75 and Qt 5.15.1 on Archlinux.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 424527] Line chart Y range max value for system monitor widget is too small
https://bugs.kde.org/show_bug.cgi?id=424527 Nicola Mori changed: What|Removed |Added Version|5.20.1 |5.20.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424527] Line chart Y range max value for system monitor widget is too small
https://bugs.kde.org/show_bug.cgi?id=424527 --- Comment #3 from Nicola Mori --- Still present in 5.20.2 with frameworks 5.75.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 Nicola Mori changed: What|Removed |Added Version|5.20.1 |5.20.2 --- Comment #5 from Nicola Mori --- Still present in 5.20.2 with frameworks 5.75.0. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 409668] Screen switcher key stopped working in version 5.16
https://bugs.kde.org/show_bug.cgi?id=409668 Nicola Mori changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Nicola Mori --- I found the relevant shortcut in system settings under Shortcuts -> Shortcuts -> KDE daemon -> Switch display. There is a Meta+P default shortcut (and also a Display one which I don't understand and that has no contextual help) which was disabled; re-enabling it makes the display switch key do its job again. I'm sure I never touched it so it must have been toggled off automatically during the 5.15 -> 5.16 upgrade. Anyway my issue is solved. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 428042] KRunner doesn't launch shell scripts anymore
https://bugs.kde.org/show_bug.cgi?id=428042 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 428042] KRunner doesn't launch shell scripts anymore
https://bugs.kde.org/show_bug.cgi?id=428042 --- Comment #1 from Nicola Mori --- I just found the problem: the "~" character. Writing the full path "/home/myuser/scripts/myscript.sh" KRunner behaves as expected. So the problem is in expanding the "~", that was done correctly in 5.19.5 but that stopped working in 5.20.0. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 428042] New: KRunner doesn't launch shell scripts anymore
https://bugs.kde.org/show_bug.cgi?id=428042 Bug ID: 428042 Summary: KRunner doesn't launch shell scripts anymore Product: krunner Version: 5.20.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: nicolam...@aol.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After updating my system to 5.20.0 KRunner doesn't properly recognize and launch shell scripts. In 5.19.5 and previous versions I could start with alt+F2, then type the path to an executable shell script (e.g. "~/scripts/myscript.sh") the suggested action was something like "Run script", and then pressing enter the script was executed. In 5.20.0 and 5.20.1, doing the same procedure the only suggested action is "Get GNU Image Manipulation Program" from the "Software center" plugin. Disabling the plugin, no action is suggested and nothing happens when pressing enter. The "Command line" plugin is enabled. STEPS TO REPRODUCE 1. Open KRunner with alt+F2 2. type the address of an executable shell script file OBSERVED RESULT The proposed action is "Get GNU Image Manipulation Program" from the "Software center" plugin. EXPECTED RESULT The proposed action should be "Run script" from the "Command line" plugin. SOFTWARE/OS VERSIONS Linux: Archlinux KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428041] New: Network speed widget displays nothing
https://bugs.kde.org/show_bug.cgi?id=428041 Bug ID: 428041 Summary: Network speed widget displays nothing Product: plasmashell Version: 5.20.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: nicolam...@aol.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In an X11 session, the standard Network speed widget on my system does not display anything. The line chart is not drawn, and the up/down speeds are not reported (there are just two small cyan and orange rectangles on the left-bottom part). It feels like no network interface is discovered: indeed, editing the set of displayed sensors, in the "Network device" set there is only the "All network devices" subset. I'm pretty sure it worked just after I updated from 5.19.5 to 5.20.0, with the sensors for the individual network interfaces being available, but it stopped working shortly after, even before upgrading to 5.20.1. I can't say if this is due to updating another system package in the middle, but anyway now it's broken. STEPS TO REPRODUCE 1. add a Network speed widget to the desktop 2. verify that the line chart does not display any line, just the level lines having all a "0 B/s" label SOFTWARE/OS VERSIONS Linux: Archlinux KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Bug observed in an X11 session, didn't try with Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 Nicola Mori changed: What|Removed |Added Version|5.19.5 |5.20.1 --- Comment #4 from Nicola Mori --- Still present in 5.20.1. A panel height less or equal than 160 makes the line chart widget disappear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424527] Line chart Y range max value for system monitor widget is too small
https://bugs.kde.org/show_bug.cgi?id=424527 Nicola Mori changed: What|Removed |Added Version|5.19.5 |5.20.1 --- Comment #2 from Nicola Mori --- Still present in version 5.20.1. The maximum settable value is 99,999 which for the memory monitor widget corresponds to about 99 MB. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 409668] Screen switcher key stopped working in version 5.16
https://bugs.kde.org/show_bug.cgi?id=409668 Nicola Mori changed: What|Removed |Added Version|5.16.3 |5.20.1 --- Comment #1 from Nicola Mori --- Still present in version 5.20.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 --- Comment #3 from Nicola Mori --- The issue is still present in 5.20.0, although the behavior has improved slightly. Adding a cpu monitor widget to a small panel (height ~ 50) it is correctly displayed in the default bar chart setting. Changing the visualization to line chart make it disappear, and setting the panel height > 160 does not help. But by resizing the panel many times the line chart suddenly appeared, and remained visible also by setting the height to 30. However, I have not been able to reproduce the result with a second cpu monitor, no matter how many times I resized the panel. Furthermore, during these resize trials, at a given point the first sensor started to show level lines, which it didn't show before even at maximum height. All in all, there's a lot of apparently random behavior with this system monitor widget introduced in Plasma 5.19 (another example is the display style selector menu that randomly gets blocked), and it's a pity that they are still not solved in version 5.20. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 Nicola Mori changed: What|Removed |Added Version|5.19.4 |5.19.5 --- Comment #2 from Nicola Mori --- Still present in 5.19.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424527] Line chart Y range max value for system monitor widget is too small
https://bugs.kde.org/show_bug.cgi?id=424527 Nicola Mori changed: What|Removed |Added Version|5.19.3 |5.19.5 --- Comment #1 from Nicola Mori --- In 5.19.4 and 5.19.5 the automatic Y range seems to somehow set a sane and fixed maximum value. However, the problem with the manual set of the maximum Y value persists. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #14 from Nicola Mori --- I confirm that the bug is fixed in 5.19.5. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #13 from Nicola Mori --- Thanks David, I built a patched version of ksysguard and I confirm that the patch you linked fixes the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #9 from Nicola Mori --- @Matthias Homann: I think the underlying cause is the same I described, i.e. starting a container or a VM creates network interfaces. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 Nicola Mori changed: What|Removed |Added Version|5.19.3 |5.19.4 --- Comment #1 from Nicola Mori --- The bug is still present in 5.19.4. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Nicola Mori changed: What|Removed |Added Version|5.19.3 |5.19.4 --- Comment #7 from Nicola Mori --- Still present in 5.19.4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424599] New: Line chart monitor widgets not displayed in small panels with Intel graphics
https://bugs.kde.org/show_bug.cgi?id=424599 Bug ID: 424599 Summary: Line chart monitor widgets not displayed in small panels with Intel graphics Product: plasmashell Version: 5.19.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: nicolam...@aol.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I tried to create a small panel with a CPU monitor widget with line style. The widget is not displayed if the panel height is small (<= 160). This happens on one of my machines with Intel graphics (kernel 5.7.9 + xf86-video-intel 1:2.99.917+908+g7181c5a4), but on another one with NVidia graphics (using the proprietary NVidia driver version 340.108) the error is not present, so I guess it might be an issue with Intel graphics. STEPS TO REPRODUCE 1. Create a panel 2. Add a Total CPU Use monitor widget to the panel and set the style to line 3. Change the height of the panel OBSERVED RESULT If the panel height is equal or less than 160 then the widget is not displayed. EXPECTED RESULT The widget should be scaled and displayed also for panel height <= 160. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424527] New: Line chart Y range max value for system monitor widget is too small
https://bugs.kde.org/show_bug.cgi?id=424527 Bug ID: 424527 Summary: Line chart Y range max value for system monitor widget is too small Product: plasmashell Version: 5.19.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: nicolam...@aol.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When using the Line Chart style for system monitor widget, the manual setting for the maximum value of the Y axis is too small (99,999). This makes it impossible e.g. to create a memory monitor widget with line style and fixed Y range, since memory values are reported in KiB and on a 16 GB system the maximum should be about 16,000,000. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Nicola Mori changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423616] System monitor desktop widgets are frozen after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=423616 Nicola Mori changed: What|Removed |Added Version|5.19.2 |5.19.3 Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Nicola Mori --- I spoke too early, I got again a freeze with Plasma 5.19.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423616] System monitor desktop widgets are frozen after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=423616 Nicola Mori changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Nicola Mori --- With Plasma 5.19.3 I don't experience the problem anymore, so I guess that it has been incidentally fixed in this release. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Nicola Mori changed: What|Removed |Added Version|5.19.2 |5.19.3 --- Comment #6 from Nicola Mori --- Still present in 5.19.3. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 423616] System monitor desktop widgets are frozen after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=423616 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 423616] New: System monitor desktop widgets are frozen after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=423616 Bug ID: 423616 Summary: System monitor desktop widgets are frozen after resume from suspend Product: kdeplasma-addons Version: 5.19.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: systemloadviewer Assignee: plasma-b...@kde.org Reporter: nicolam...@aol.com Target Milestone: --- SUMMARY All my system monitor desktop widgets (Network speed, Memory usage, and a couple of customized ones) are not updated after resuming my laptop from suspend-to-ram. Killing and restarting the Plasma shell does not help. STEPS TO REPRODUCE 1. Suspend to ram 2. Resume from suspend OBSERVED RESULT After resume the widgets are not updated with time. EXPECTED RESULT The widgets should be refreshed to show the current system status. SOFTWARE/OS VERSIONS Linux: Archlinux KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Nicola Mori changed: What|Removed |Added Version|5.19.1 |5.19.2 --- Comment #4 from Nicola Mori --- Still present in 5.19.2. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Nicola Mori changed: What|Removed |Added Version|5.19.0 |5.19.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #2 from Nicola Mori --- The bug is present also in Plasma 5.19.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #1 from Nicola Mori --- Another case that might be useful to track down the bug: - Initial situation: lo, eth0, wlan0 - Action: add tun0 by starting a VPN service - Result: the "CPU 1" sensor of the "Individual Core Usage" widget becomes "Paged out Pages". All the other cpu sensors (from 2 to 12 in my system) are changed as well (e.g. "CPU 2" -> "lo Receiver Errors Rate"). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] New: Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Bug ID: 422839 Summary: Adding network interfaces screws the system monitor widgets Product: kdeplasma-addons Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: systemloadviewer Assignee: plasma-b...@kde.org Reporter: nicolam...@aol.com Target Milestone: --- SUMMARY In my system I have the following network interfaces: lo, wlan0, eth0, docker0, tun0. When adding a new network interface tun1 by starting another VPN service, some of the system monitoring widgets on my desktop suddenly become associated to different sensors. For example, the "Core 0" temperature sensor becomes "tun1 Transmitter FIFO overrun rates". Somehow, the read value seems to be correct, but is reported in wrong units: before starting the VPN I had a read of 34.0C, and after I get 34 s^-1. Stopping the VPN (thus removing tun1) the things get back to normality. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 409668] Screen switcher key stopped working in version 5.16
https://bugs.kde.org/show_bug.cgi?id=409668 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 409668] New: Screen switcher key stopped working in version 5.16
https://bugs.kde.org/show_bug.cgi?id=409668 Bug ID: 409668 Summary: Screen switcher key stopped working in version 5.16 Product: KScreen Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: se...@kde.org Reporter: nicolam...@aol.com Target Milestone: --- SUMMARY After the upgrade to Plasma 5.16 the screen switch key on my Dell XPS 15 9570 stopped working. In previous versions it opened a dialog window where one could choose the output (on laptop screen, on external screen etc.). Now pressing it has no effect. It still emits Meta+P but it seems it is no longer bound to anything (I have not set up any custom shortcut but it used to work anyway with Plasma 5.15). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel: 5.1.16 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 406778] KCM touchpad settings ignored in X11 session with Linux 5.0
https://bugs.kde.org/show_bug.cgi?id=406778 Nicola Mori changed: What|Removed |Added URL||https://bugzilla.kernel.org ||/show_bug.cgi?id=203401 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 406778] KCM touchpad settings ignored in X11 session with Linux 5.0
https://bugs.kde.org/show_bug.cgi?id=406778 --- Comment #4 from Nicola Mori --- Thanks Nate, I knew about that bug report but I opened a new one since I think my experience is slightly different. With Linux 4.19 and without any xorg config file the KCM touchpad settings are honored. I thought that maybe in this configuration a different touchpad driver is used, even if I dont have synaptics installed and I am not aware of any other driver apart from libinput, but here's the content of Xorg.0.log: [ 6.854] (II) config/udev: Adding input device SYNA2393:00 06CB:7A13 Touchpad (/dev/input/event13) [ 6.854] (**) SYNA2393:00 06CB:7A13 Touchpad: Applying InputClass "libinput touchpad catchall" [ 6.854] (II) Using input driver 'libinput' for 'SYNA2393:00 06CB:7A13 Touchpad So I guess that libinput is actually used, and KCM works fine in an X11 session with Linux 4.19. This does not fit with what bug report 387153 says; problems started only with Linux 5.0. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 406778] KCM touchpad settings ignored in X11 session with Linux 5.0
https://bugs.kde.org/show_bug.cgi?id=406778 --- Comment #2 from Nicola Mori --- @atulbi Actually I think that on my system there's just the libinput driver (e.g. no synaptic, I checked with the package manager); you can see the versions in my first message. Moreover, I load it explicitly when I use the attached xorg configuration file, but this does not make the KCM settings being respected. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 406778] New: KCM touchpad settings ignored in X11 session with Linux 5.0
https://bugs.kde.org/show_bug.cgi?id=406778 Bug ID: 406778 Summary: KCM touchpad settings ignored in X11 session with Linux 5.0 Product: Touchpad-KCM Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: atulbish...@gmail.com Reporter: nicolam...@aol.com Target Milestone: --- Created attachment 119564 --> https://bugs.kde.org/attachment.cgi?id=119564=edit Touchpd configuration file for xorg. SUMMARY Since I upgraded my system to Linux 5.0 the touchpad settings from KCM are ignored. Specifically, the tap-to-click can be set but is ignored, i.e. tap-to-click does not work. This happens without any xorg configuration files. If I add a configuration file /etc/X11/xorg.conf.d/30-touchpad.conf as the attached one then tap-to-click works again, but this time it cannot be disabled from the KCM module. Everything works as expected with Linux 4.19. STEPS TO REPRODUCE 1. Install Linux 5.0 2. Remove any xorg configuration file for the touchpad 3. Start Plasma OBSERVED RESULT The touchpad tap-to-click does not work, event when enabled from KCM. EXPECTED RESULT The touchpad tap-to-click behavior should comply with the KCM settings. SOFTWARE/OS VERSIONS System: Dell XPS 15 9570 $ dmesg |grep Touch 1216:[3.814366] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x0, board id: 3125, fw id: 2378871 1217:[3.850630] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input9 1234:[4.833956] input: SYNA2393:00 06CB:7A13 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-10/i2c-SYNA2393:00/0018:06CB:7A13.0001/input/input15 1250:[5.008216] input: SYNA2393:00 06CB:7A13 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-10/i2c-SYNA2393:00/0018:06CB:7A13.0001/input/input24 Linux/KDE Plasma: Archlinux with: linux-ck 5.0.9-1 libinput 1.13.1-1 xf86-input-libinput 0.28.2-1 xorg-server 1.20.4-1 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57 Qt Version: 5.12.2-2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 406778] KCM touchpad settings ignored in X11 session with Linux 5.0
https://bugs.kde.org/show_bug.cgi?id=406778 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 282704] KDE 4.7 is very slow on ext3 root partition
https://bugs.kde.org/show_bug.cgi?id=282704 --- Comment #38 from Nicola Mori --- Well, while I appreciate that someone cares about this bug I'd say that it's coming a bit late. After 7 years since my original report, 4 years after the last post, many confirmations and info posted by me and other users... Nevermind, please close the report, I'm no longer affected and probably nobody still uses KDE4 and/or ext3. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 Nicola Mori changed: What|Removed |Added Version|5.12.0 |5.13.1 CC||nicolam...@aol.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Nicola Mori --- I confirm the issue is still present in Plasma 5.13.1. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 383902] Screenshots aren't taking for some areas
https://bugs.kde.org/show_bug.cgi?id=383902 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com Version|unspecified |18.04.2 --- Comment #2 from Nicola Mori --- I confirm the issue. Using Spectacle 18.04.2, Plasma 5.13.1 on x86_64 Archlinux, Mobility Radeon HD3470. I can provide more info if needed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395631] New: CPU monitor on panel shows no graph in Wayland session
https://bugs.kde.org/show_bug.cgi?id=395631 Bug ID: 395631 Summary: CPU monitor on panel shows no graph in Wayland session Product: plasmashell Version: 5.13.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: nicolam...@aol.com Target Milestone: 1.0 Created attachment 113450 --> https://bugs.kde.org/attachment.cgi?id=113450=edit Screenshot showing the problem In a Wayland session the CPU monitor widget contained in a panels shows no graph lines. The same widget on the desktop works well. See the top-right corner of the attached screenshot. System info: Plasma 5.13.1 on x86_64 Archlinux, Mobility Radeon HD3470 with modesetting driver. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367993] No transparency effect in konsole 16.08.0
https://bugs.kde.org/show_bug.cgi?id=367993 --- Comment #5 from Nicola Mori <nicolam...@aol.com> --- Thanks, I'll wait for 16.08.1. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367993] No transparency effect in konsole 16.08.0
https://bugs.kde.org/show_bug.cgi?id=367993 --- Comment #2 from Nicola Mori <nicolam...@aol.com> --- Thanks Wolfgang, I trust your word but I see a little incoherence here. The bug report 366368 is about non-working effects in 16.04.03 but for me that version works, while 16.08.0 does not (both tested with frameworks 5.25). So is my report really a duplicate of 366368, or in other words, will the fix for 366368 work also for me? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367993] No transparency effect in konsole 16.08.0
https://bugs.kde.org/show_bug.cgi?id=367993 Nicola Mori <nicolam...@aol.com> changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367993] New: No transparency effect in konsole 16.08.0
https://bugs.kde.org/show_bug.cgi?id=367993 Bug ID: 367993 Summary: No transparency effect in konsole 16.08.0 Product: konsole Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: nicolam...@aol.com After upgrading to konsole 16.08.0 the transparency effect no longer works. In Settings->Appearance tab there is a message "Konsole was started before desktop effects were enabled. You need to restart Konsole to see transparent background.". Reverting to 16.04.3 solves the problem. ArchLinux 64 bit with frameworks 5.25. Reproducible: Always Steps to Reproduce: 1. Install konsole 16.08.0 2. Check that transparency effect does not work 3. See the error message in Settings->Appearance configuration tab -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 364478] Power settings concerning lid state are ignored / overridden
https://bugs.kde.org/show_bug.cgi?id=364478 --- Comment #5 from Nicola Mori <nicolam...@aol.com> --- Forgot to add details about my system: ArchLinux with Plasma 5.7.3 and systemd 231. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 364478] Power settings concerning lid state are ignored / overridden
https://bugs.kde.org/show_bug.cgi?id=364478 Nicola Mori <nicolam...@aol.com> changed: What|Removed |Added CC||nicolam...@aol.com --- Comment #4 from Nicola Mori <nicolam...@aol.com> --- I noticed the same problem on my laptop. The settings are ignored and when the laptop is closed the system is always suspended, but in one case: if I set "Do nothing" for both "On AC Power" and "On Battery" profiles then nothing is actually done. But if I change just one of the two profile settings to any value then the laptop is suspended. -- You are receiving this mail because: You are watching all bug changes.
