[plasma-systemmonitor] [Bug 471979] plasma-systemmonitor: graphical artefacts with nouveau kernel module
https://bugs.kde.org/show_bug.cgi?id=471979 Sébastien P. changed: What|Removed |Added CC|sebastien.pica...@ovh.fr| -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 --- Comment #6 from Sébastien P. --- Same issue with new versions: 5.24.4 / Akanodi 23.08.3 / Frameworks 5.115.0 / Qt 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 471979] plasma-systemmonitor: graphical artefacts with nouveau kernel module
https://bugs.kde.org/show_bug.cgi?id=471979 --- Comment #5 from Sébastien P. --- (In reply to luca from comment #4) > I can confirm. > Same behavior in plasma-nm/speed charts. > The system crashes and the only solution is magic SysRq. You are “lucky”. SysRq is not working for me => hard reboot mandatory -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 471979] plasma-systemmonitor: graphical artefacts with nouveau kernel module
https://bugs.kde.org/show_bug.cgi?id=471979 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr --- Comment #2 from Sébastien P. --- Got something similar but also with other apps (plasmashell, so entire session). --- Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 0 - Unknown CUDA fault at address 00201b0800 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 0 - e0c: , e18: 0ff2, e1c: , e20: , e24: 0903 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 1 - Unknown CUDA fault at address 00201bbc00 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 1 - e0c: , e18: 0ff2, e1c: , e20: , e24: 0903 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: 0020 [] ch 12 [001ebee000 plasmashell[2525]] subc 3 class 8297 mthd 15f0 data 01780178 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: fb: trapped write at 00201b0800 on channel 12 [1ebee000 plasmashell[2525]] engine 00 [PGRAPH] client 0b [PROP] subclient 09 [LOCAL] reason 0002 [PAGE_NOT_PRESENT] --- The problem appears a few months ago (august), but I did not have the time to check it before (due to a dead mother board in august which has been changed now; I though it was linked… but no). This can lead to random crash (system hang, impossible to do anything, no mouse, no keyboard). Qt: 5.15.10 Framework: 5.110.0 Plasma: 5.27.8 KDE apps: 23.04.3 02:00.0 VGA compatible controller: NVIDIA Corporation G96C [GeForce 9500 GT] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96C [GeForce 9500 GT] => with Nouveau driver / kernel 6.1.57 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449706] Keypad decimal separator should respect regional formatting
https://bugs.kde.org/show_bug.cgi?id=449706 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr --- Comment #4 from Sébastien P. --- I had the same bug wiht French keyboard. Also notice that it depends on the variant. In my first test, I used “latin9” variant (system settings, input devices, keyboard, dispositions). And `env WAYLAND_DISPLAY= libreoffice` did not change anything. Same thing with variant called “variant”. But with no variant or with the variant “obsolete variant”, the decimal separator is good on LibreOffice Calc with `env WAYLAND_DISPLAY= libreoffice`. So the workaround is working only for some layout variants. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 --- Comment #5 from Sébastien P. --- Still the same issue with 5.23.3 / Akanodi 23.04.3 / Frameworks 5.110.0 / Qt 5.15.10 Also, I tried to create a new KDE user today. And reach the same issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 --- Comment #4 from Sébastien P. --- Just saw this page: https://community.kde.org/PIM/Akonadi/Debug_IMAP So: > 0 2 août 22:04 imap.log.23509.1 > 0 2 août 22:04 imap.log.23509.2 > 0 2 août 22:05 imap.log.23509.3 > 0 2 août 22:05 imap.log.23509.4 => Files are empty. > org.kde.pim.kimap: Connection to server lost QAbstractSocket::SocketError(13) > org.kde.pim.akonadiserver: Cannot connect to agent instance with identifier > 'akonadi_maildir_resource_0', error message: '' => Saw those two lines. First seems useful (network error?). Not sure the second is linked to this issue. $ curl -iv he25.mail.ovh.net:993 * Trying 5.135.57.20:993... * Connected to he25.mail.ovh.net (5.135.57.20) port 993 (#0) > GET / HTTP/1.1 > Host: he25.mail.ovh.net:993 > User-Agent: curl/8.0.1 > Accept: */* > * Recv failure: Connexion ré-initialisée par le correspondant * Closing connection 0 curl: (56) Recv failure: Connexion ré-initialisée par le correspondant => Network looks fine. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 --- Comment #3 from Sébastien P. --- I do remember today that I have another mail at another IMAP server from the same ISP. Same issue for me with he7.mail.ovh.net. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 --- Comment #2 from Sébastien P. --- Created attachment 160607 --> https://bugs.kde.org/attachment.cgi?id=160607=edit akonadiserver.error -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 --- Comment #1 from Sébastien P. --- Created attachment 160606 --> https://bugs.kde.org/attachment.cgi?id=160606=edit mysql.err -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472776] New: IMAP server status stuck to “server is unavailable“
https://bugs.kde.org/show_bug.cgi?id=472776 Bug ID: 472776 Summary: IMAP server status stuck to “server is unavailable“ Classification: Frameworks and Libraries Product: Akonadi Version: 5.23.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: sebastien.pica...@ovh.fr CC: c...@carlschwan.eu Target Milestone: --- Hi, Since, upgrade of akonadi from 22.12.3 (do not know the client version) to 23.04.2 (“akonadictl --version” tells me 5.23.2), my IMAP resource on OVH is not working. On Kmail, I can see “Le serveur n’est pas disponible” (“Server is not available“). I tried to remove it and recreate it => same issue I tried another IMAP server on Gmail => working and I get my mails. STEPS TO REPRODUCE 1. create IMAP resource with server he25.mail.ovh.net 2. put anything as user/password (it will not get to the server) 3. select SSL/993 port in advanced tab OBSERVED RESULT No connexion to the server. EXPECTED RESULT Connected to the server and get mails. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 23.04.2 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Same IMAP configuration is working on my smartphone for months/years. I tried to lock at error logs. But did not see anything that looks revelant. Even there is a lot of mysql error. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432220] Scale should not be cumulative for certain Sensors
https://bugs.kde.org/show_bug.cgi?id=432220 --- Comment #9 from Sébastien P. --- (In reply to Arjen Hiemstra from comment #8) > A few versions ago we improved the behaviour of setting the ranges for > charts, so the workaround for editing the config file should no longer be > needed and the range can simply be set to something like "8 GiB". I think > this should cover most of these cases. It is in my case. Thanks for the reply. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 --- Comment #8 from Sébastien P. --- Created attachment 145056 --> https://bugs.kde.org/attachment.cgi?id=145056=edit Still an issue As you can see, the text part is fine but not the chart. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 Sébastien P. changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #7 from Sébastien P. --- Or reopen it since it is the same issue^^. I tried to recreate a new load average applet but the numbers are not rounded. libksysguard 5.23.4 Frameworks 5.88.0 Qt 5.15.2 Screenshot to come. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 --- Comment #6 from Sébastien P. --- It is fine for CPU, but not for load average. I think I will create another issue for that. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438554] No more load average in plasmoid
https://bugs.kde.org/show_bug.cgi?id=438554 --- Comment #5 from Sébastien P. --- Thanks David! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 --- Comment #5 from Sébastien P. --- Ok, I will have to wait the full stabilisation of 5.23 on my distro. I had another issue since 5.21: https://bugs.kde.org/show_bug.cgi?id=438554 so I do not have any load average now :) -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 --- Comment #3 from Sébastien P. --- Hi Gerald, Do you have a commit hash/know version? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438554] No more load average in plasmoid
https://bugs.kde.org/show_bug.cgi?id=438554 Sébastien P. changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438554] No more load average in plasmoid
https://bugs.kde.org/show_bug.cgi?id=438554 --- Comment #2 from Sébastien P. --- Created attachment 139444 --> https://bugs.kde.org/attachment.cgi?id=139444=edit Screenshot When I want to select a sensor, I have the category: * ACPI; * Processors; * Disks; * GPU; * Harware sensors; * Memory; * Network; * OS; * Ernergy; * System; * Availability. No one contain a “load average” sensor. The selected sensor (empty purple square) is probably my old load average sensor. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438554] No more load average in plasmoid
https://bugs.kde.org/show_bug.cgi?id=438554 Sébastien P. changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438554] New: No more load average in plasmoid
https://bugs.kde.org/show_bug.cgi?id=438554 Bug ID: 438554 Summary: No more load average in plasmoid Product: plasma-systemmonitor Version: 5.21.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: sebastien.pica...@ovh.fr CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY I have upgraded from 5.20.5 to 5.21.5 (and Framework from 5.80.0 to 5.82.0 but not sure is does matter). My load average sensor does not work anymore. It is just empty. I took a look to the configuration settings and do not any “load average” in sensor field/textual sensor field. So I can not select it. STEPS TO REPRODUCE 1. Create a monitor 2. Open configuration settings 3. Go to sensor detail 4. Search for load average OBSERVED RESULT No load average sensor available EXPECTED RESULT Load average present in selector SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432221] Network plasma monitoring does not work
https://bugs.kde.org/show_bug.cgi?id=432221 Sébastien P. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Sébastien P. --- Works again after upgrade to 5.21.5 (first 5.21 that I have tested) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr --- Comment #7 from Sébastien P. --- I had a similar issue: * upgrade mariadb * later, a crash => impossible to restart akonadi ~/.local/share/akonadi/db_data/mysql.err.old: 2021-03-13 14:51:11 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.17. 2021-03-13 14:51:11 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error Removing ib_logfile0 and ib_logfile1 solved that. Maybe akonadi should tell us to look at this file? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432220] Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220 --- Comment #7 from Sébastien P. --- As you said, It is not fun. But it works. Thanks -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432221] Network plasma monitoring does not work
https://bugs.kde.org/show_bug.cgi?id=432221 Sébastien P. changed: What|Removed |Added Summary|Network plasma monitoring |Network plasma monitoring |does work |does not work -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432220] Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220 --- Comment #5 from Sébastien P. --- Not sure there is a maximum set for load averages, bandwith and CPU usage. I wrote a nonsense here. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432220] Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220 --- Comment #4 from Sébastien P. --- Created attachment 135356 --> https://bugs.kde.org/attachment.cgi?id=135356=edit Manual scale Hi David, It is not possible to set manually the maximum because the manual maximum is 9 bytes. I can not go further. Bad field limit? or unit (it should probably be in Mio)? Yes, it is technically correct. In fact, cumulate the maximum is useful for load averages, disk usages, bandwith, CPU usage… But not for physical limits like RAM, % of disk usages… -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795
--- Comment #2 from Sébastien P. ---
Created attachment 135334
--> https://bugs.kde.org/attachment.cgi?id=135334=edit
A very dirty fix
I tried to analyze a bit. Without the knowledge of Qt/C++… a bit difficult^^.
It looks like new grid system use a Unit not listed in
Formatter::formatValue cases. So it goes to default one “value.toString();”
(Formatter.cpp line 319 in master branch).
=> So I change the default to use formatNumber function. I do not know the
impacts… but works fine for me.
=> It looks like also that the grid value is not a QVariant double. So, I add a
dirty parameter (I did not find where I can change the type properly…)
With my usage of applets. Only load average and disk usage are affect by that.
diff --git a/formatter/Formatter.cpp b/formatter/Formatter.cpp
index 29ef6a6..17d8d6d 100644
--- a/formatter/Formatter.cpp
+++ b/formatter/Formatter.cpp
@@ -233,7 +233,7 @@ static Unit adjustedUnit(qreal value, Unit unit,
MetricPrefix prefix)
return Unit(prefix + baseUnit);
}
-static QString formatNumber(const QVariant , Unit unit, MetricPrefix
prefix, FormatOptions options)
+static QString formatNumber(const QVariant , Unit unit, MetricPrefix
prefix, FormatOptions options, bool forceDouble)
{
qreal amount = value.toDouble();
@@ -246,7 +246,7 @@ static QString formatNumber(const QVariant , Unit
unit, MetricPrefix prefi
amount /= std::pow(unitOrder(unit), adjusted - unit);
}
-const int precision = (value.type() != QVariant::Double && adjusted <=
unit) ? 0 : 1;
+const int precision = (value.type() != QVariant::Double && adjusted <=
unit && !forceDouble) ? 0 : 1;
const QString text = QLocale().toString(amount, 'f', precision);
return unitFormat(adjusted).subs(text).toString();
@@ -307,7 +307,7 @@ QString Formatter::formatValue(const QVariant , Unit
unit, MetricPrefix ta
case UnitVolt:
case UnitWatt:
case UnitSecond:
-return formatNumber(value, unit, targetPrefix, options);
+return formatNumber(value, unit, targetPrefix, options, false);
case UnitBootTimestamp:
qCWarning(FORMATTER) << "UnitBootTimestamp is deprecated and is not
formatted anymore";
@@ -316,7 +316,7 @@ QString Formatter::formatValue(const QVariant , Unit
unit, MetricPrefix ta
return formatTime(value);
default:
-return value.toString();
+return formatNumber(value, unit, targetPrefix, options, true);
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 432220] Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220
--- Comment #2 from Sébastien P. ---
Created attachment 135333
--> https://bugs.kde.org/attachment.cgi?id=135333=edit
A dirty patch…
My dirty patch… to detect the max scale. But it will probably fail in some
cases (which I do not have :/).
Better idea would be to have a detection of sensor that you have to cumulate
the scale or other not.
diff --git a/faces/facepackages/linechart/contents/ui/LineChart.qml
b/faces/facepackages/linechart/contents/ui/LineChart.qml
index 34f2888..252eafd 100644
--- a/faces/facepackages/linechart/contents/ui/LineChart.qml
+++ b/faces/facepackages/linechart/contents/ui/LineChart.qml
@@ -61,7 +61,7 @@ Charts.LineChart {
function calcStackedMaximum() {
let max = 0
for (let i = 0; i < sensorsModel.sensors.length; ++i) {
-max += sensorsModel.data(sensorsModel.index(0, i),
Sensors.SensorDataModel.Maximum)
+if (max
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 --- Comment #1 from Sébastien P. --- Come from the new grid system? https://invent.kde.org/plasma/libksysguard/-/merge_requests/44 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432220] Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220 --- Comment #1 from Sébastien P. --- Probably this: https://invent.kde.org/plasma/libksysguard/-/merge_requests/48 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432220] Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220 Sébastien P. changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432221] Network plasma monitoring does work
https://bugs.kde.org/show_bug.cgi?id=432221 Sébastien P. changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432221] Network plasma monitoring does work
https://bugs.kde.org/show_bug.cgi?id=432221 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432221] New: Network plasma monitoring does work
https://bugs.kde.org/show_bug.cgi?id=432221 Bug ID: 432221 Summary: Network plasma monitoring does work Product: ksysguard Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasmoid / Applet Assignee: ksysguard-b...@kde.org Reporter: sebastien.pica...@ovh.fr CC: plasma-b...@kde.org Target Milestone: --- Created attachment 135245 --> https://bugs.kde.org/attachment.cgi?id=135245=edit No data for network SUMMARY Since update from 5.19.5 to 5.20.5 network plasma monitoring does work. Comment: on ksysguard, I can see the network traffic. Only the plasmoid have this issue I tried to create a new one from scratch but same issue. STEPS TO REPRODUCE 1. Just create a network plasmoid monitor OBSERVED RESULT No data/chart/text EXPECTED RESULT Monitor of traffic network SOFTWARE/OS VERSIONS KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I do not know how I can help more… or if I am alone. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432220] Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432220] New: Scale should not be cumulative
https://bugs.kde.org/show_bug.cgi?id=432220 Bug ID: 432220 Summary: Scale should not be cumulative Product: ksysguard Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasmoid / Applet Assignee: ksysguard-b...@kde.org Reporter: sebastien.pica...@ovh.fr CC: plasma-b...@kde.org Target Milestone: --- Created attachment 135244 --> https://bugs.kde.org/attachment.cgi?id=135244=edit Current results SUMMARY Contrary to 5.19, automatic scales are now cumulative. Even when it makes nonsens (example memory charts). STEPS TO REPRODUCE 1. Create memory monitor plasmoid 2. Change to line diagram 3. Add sensors 4. Select cumulative lines option in diagram details OBSERVED RESULT I have 8 Gio of RAM. Left (with cumulative lines): scale is 3×8. Right: 8 (without cumulative lines, but less readable). EXPECTED RESULT I want cumulative line: it is better to see the distribution. Otherwise the line will be overlaid each other. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #43 from Sébastien P. --- Yeah. It is still slow (compare to 5.16) but better for me (looks quicker compare to 5.17). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #41 from Sébastien P. --- It looks fine on 5.18.5. I switched yesterday and the login was quick, like before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #38 from Sébastien P. --- (In reply to David Redondo from comment #37) > Git commit a58bbc050723583d75a47a3f00d19f41d70d17a4 by David Redondo. > Committed on 13/02/2020 at 20:48. > Pushed by davidre into branch 'Plasma/5.18'. > > Don't delay ksplash until the entire slideshow is loaded > > Summary: > Instead of loading the model and then showing the last shown image, we can > show > it early so that we signal "wallpaper.loading = false" earlier. > > Test Plan: Have massive slideshow, login > > Reviewers: davidedmundson, broulik, #plasma > > Reviewed By: davidedmundson, #plasma > > Subscribers: plasma-devel > > Tags: #plasma > > Differential Revision: https://phabricator.kde.org/D27084 > > M +4-1wallpapers/image/image.cpp > > https://commits.kde.org/plasma-workspace/ > a58bbc050723583d75a47a3f00d19f41d70d17a4 Hi, Still the same issue on 5.17.5 with this patch: * plasmashell 100% * no slideshow during this time (it should?) * system a bit slow * after the loading, it shows the latest slideshow I do not know if 5.18 instead of 5.17 will change that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #35 from Sébastien P. --- (In reply to Christian from comment #33) > (In reply to David Redondo from comment #32) > > Hi, does the following patch help? > > It shows the last image shown the last time on startup, which should signal > > ealier that wallpaper.loading = false; > > Thanks, David. The patch compiles and does show the last image shown the > last time on startup. But it doesn't fix the problem: > * The plasmashell process still consumes huge amount of processing time > immediately from the login > * During that time, many plasma things don't work, including the "Start > menu" or whatever KDE calls it, the status bar with the notification icons, > etc. Same here. It does not solve the main issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #23 from Sébastien P. --- As I said on the duplicate issue: > plasmashell process with 100% CPU on one core during the switching of picture. > 50Gio for 10929 files for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 Sébastien P. changed: What|Removed |Added Keywords||regression CC||sebastien.pica...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #22 from Sébastien P. --- (In reply to Nate Graham from comment #5) > Wallpaper processing was massively simplified for Plasma 5.17. Can anyone > who was originally experiencing this issue still reproduce it in Plasma 5.17? Hi Nate! This issue appears with 5.17 for me :/. No problem with 5.16.5. I switched from frameworks 5.60 to 5.64 at the begging of December (no issue at that moment). I switched from 5.16.5 to 5.17.4 this week. It “created” the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 Sébastien P. changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #21 from Sébastien P. --- *** Bug 413934 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 Sébastien P. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Sébastien P. --- Just see this issue with all his duplicates. I think we can duplicate this one too. *** This bug has been marked as a duplicate of bug 371455 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415008] KWin-5.17.4 hangs inside loop in QXcbConnection::getTimestamp()
https://bugs.kde.org/show_bug.cgi?id=415008 Sébastien P. changed: What|Removed |Added CC|sebastien.pica...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 Sébastien P. changed: What|Removed |Added Keywords||regression CC||sebastien.pica...@gmail.com --- Comment #5 from Sébastien P. --- Same thing here. plasmashell process with 100% CPU on one core during the switching of picture. For me 50Gio for 10929 files. Note: I have just updated my system from kde-plasma 5.16.5 to 5.17.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415008] KWin-5.17.4 hangs inside loop in QXcbConnection::getTimestamp()
https://bugs.kde.org/show_bug.cgi?id=415008 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 363927] KF5 port of the ipfilter plugin (in progress)
https://bugs.kde.org/show_bug.cgi?id=363927 Sébastien P. <sebastien.pica...@gmail.com> changed: What|Removed |Added CC||sebastien.pica...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
