[Akonadi] [Bug 485799] Get a lot of `Failed to process EWS request: ` with empty details
https://bugs.kde.org/show_bug.cgi?id=485799 --- Comment #3 from Luca Beltrame --- (In reply to Luca Beltrame from comment #2) > I haven't found a way to debug *why* it's invalid. dd785b95af83fd74618b5e4ce2904fa86db771e3 in kdepim-runtime might be suspect, but I have no way of confirming it. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 485799] Get a lot of `Failed to process EWS request: ` with empty details
https://bugs.kde.org/show_bug.cgi?id=485799 Luca Beltrame changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||lbeltr...@kde.org Ever confirmed|0 |1 --- Comment #2 from Luca Beltrame --- This is because malformed data is sent, this is the reply from the server (you should set QT_LOGGING_RULES="*org.kde.pim.ews.client.proto*.debug=true" to have it dumped somewhere): http://schemas.xmlsoap.org/soap/envelope/;>http://schemas.microsoft.com/exchange/services/2006/types;>a:ErrorInvalidOperationId is malformed.http://schemas.microsoft.com/exchange/services/2006/errors;>ErrorInvalidOperationhttp://schemas.microsoft.com/exchange/services/2006/errors;>Id is malformed. I haven't found a way to debug *why* it's invalid. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478741] ksystemstats daemon.cpp:32:10: fatal error: 'ksystemstatsadaptor.h' file not found
https://bugs.kde.org/show_bug.cgi?id=478741 Luca Beltrame changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/ksystemstats/-/commit/23 ||d32490d626eee8f7b2115b31146 ||fece21b5517 --- Comment #2 from Luca Beltrame --- Git commit 23d32490d626eee8f7b2115b31146fece21b5517 by Luca Beltrame. Committed on 20/12/2023 at 07:48. Pushed by lbeltrame into branch 'master'. Adjust naming of the generated classes Since the DBus interface file changed, the names of the generated classes also changed. Adjust accordingly. M +2-2src/daemon.cpp https://invent.kde.org/plasma/ksystemstats/-/commit/23d32490d626eee8f7b2115b31146fece21b5517 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 --- Comment #9 from Luca Beltrame --- I reverted the change and then reinstalled Akonadi. It did not crash, but it did not crash also when I went back again to master... @Robby: Can you try issuing "akonadictl fsck" and see whether this changes anything? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 --- Comment #8 from Luca Beltrame --- I wonder if it's related to 72af8c0b4b20813983a0ee0384ac248e097c4a21. I'll check... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Luca Beltrame changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #6 from Luca Beltrame --- The EWS resource fails for me in the same manner, for the record. The backtrace lacks some debug symbols, here's a more complete one: Thread 1 (Thread 0x7fcbac2de180 (LWP 5068)): [KCrash Handler] #4 0x7fcb845536de in attributesToProtocolImpl (ns=false, entity=...) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/protocolhelper.cpp:93 #5 Akonadi::ProtocolHelper::attributesToProtocol(Akonadi::Item const&, bool) (ns=false, item=...) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/protocolhelper.cpp:184 #6 Akonadi::ItemCreateJob::doStart() (this=) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/jobs/itemcreatejob.cpp:158 #7 0x7fcb84559278 in Akonadi::JobPrivate::startQueued() (this=0x7fcba4055a20) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/jobs/job.cpp:189 #8 0x7fcbc1bcb2ae in QObject::event(QEvent*) () at /lib64/libQt6Core.so.6 #9 0x7fcbc2dc094e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #10 0x7fcbc1b878b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #11 0x7fcbc1b87c17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt6Core.so.6 #12 0x7fcbc1dad9e3 in () at /lib64/libQt6Core.so.6 #13 0x7fcbb6861f30 in () at /lib64/libglib-2.0.so.0 #14 0x7fcbb6863b58 in () at /lib64/libglib-2.0.so.0 #15 0x7fcbb686420c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #16 0x7fcbc1dabc6c in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt6Core.so.6 #17 0x7fcbc1b9211b in QEventLoop::exec(QFlags) () at /lib64/libQt6Core.so.6 #18 0x7fcbc1b8bd46 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #19 0x5607fa46041d in () #20 0x7fcbc12281b0 in __libc_start_call_main () at /lib64/libc.so.6 #21 0x7fcbc1228279 in __libc_start_main_impl () at /lib64/libc.so.6 #22 0x5607fa4609f5 in () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476666] Widgets based on System Monitor Sensor are all broken out of the box
https://bugs.kde.org/show_bug.cgi?id=47 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462044] libksysguard: crash in KSysGuard::SensorProperty::setName
https://bugs.kde.org/show_bug.cgi?id=462044 Luca Beltrame changed: What|Removed |Added CC||ahiems...@heimr.nl Product|ksysguard |plasma-systemmonitor Component|libksysguard|general --- Comment #1 from Luca Beltrame --- Actually the fault is in ksystemstats. https://invent.kde.org/plasma/ksystemstats/-/merge_requests/43 implemented part of its changes in the GPU-agnostic part of the backend, but the AMD GPU backend was not updated, so it tries to access a null pointer and crashes during initialization. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 462044] New: libksysguard: crash in KSysGuard::SensorProperty::setName
https://bugs.kde.org/show_bug.cgi?id=462044 Bug ID: 462044 Summary: libksysguard: crash in KSysGuard::SensorProperty::setName Classification: Applications Product: ksysguard Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libksysguard Assignee: ksysguard-b...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- Created attachment 153890 --> https://bugs.kde.org/attachment.cgi?id=153890=edit Backtrace SUMMARY When starting ksystemstats with libksysguard as of 97382e8455854a6114663c76c5ca1962f2f9f436 on my desktop machine, ksystemstats crashes with the attached backtrace. STEPS TO REPRODUCE 1. Start ksystemstats OBSERVED RESULT ksystemstats crashes. EXPECTED RESULT ksystemstats should not crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest (2022-11-20) git master (available in About System) KDE Plasma Version: latest (2022-11-20) git master KDE Frameworks Version: latest (2022-11-20) git master Qt Version: 5.15 + KDE patches ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 461747] New: Crash after setting an account
https://bugs.kde.org/show_bug.cgi?id=461747 Bug ID: 461747 Summary: Crash after setting an account Classification: Applications Product: Tokodon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lbeltr...@kde.org CC: c...@carlschwan.eu Target Milestone: --- Created attachment 153700 --> https://bugs.kde.org/attachment.cgi?id=153700=edit Backtrace SUMMARY After adding an account (tested with sakurajima.moe) subsequent starts of Tokodon will result in a crash deep in Qt. STEPS TO REPRODUCE 1. Add an account to a fresh configuration of Tokodon 2. Close the application 3. Restart OBSERVED RESULT Tokodon crashes. EXPECTED RESULT Tokodon should not crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest master (available in About System) KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: 5.15.7 + KDE patches ADDITIONAL INFORMATION I've tried to start fresh with no configuration and no cache and the crash still occurs. I can't rule out some kind of local issue, though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456285] The new language and region KCM hardcodes "locale-gen".
https://bugs.kde.org/show_bug.cgi?id=456285 --- Comment #4 from Luca Beltrame --- (In reply to Harald Sitter from comment #1) > It's not hardcoded though, is it? you just need to add a distro specific > handler, like already exists for ubuntu. I don't think it should be done like this, but this discussion is better suited for plasma-devel and not a bug report. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456285] The new language and region KCM hardcodes "locale-gen".
https://bugs.kde.org/show_bug.cgi?id=456285 --- Comment #3 from Luca Beltrame --- (In reply to hanyoung from comment #2) > If "/etc/locale.gen" doesn't exists, the KCM doesn't call "locale-gen". > Which is the case for fedora. I don't know about open SUSE, but I assume > distros that come with locale pre-generated will not ship the "locale.gen" > file. I confirm that locale.gen is not present here. The problem is that to use glibc-based locales you need to enable support for locale-gen, which in turn enables polkit support for it via the helper. This may be undesirable if not needed (it hasn't gone through any security review, has it? Not saying it needs one, but that some may not want it). Currently you either disable glibc support altogether, or you install the helper. Of course, if all the "glibc support" does once enabled is running locale-gen, downstreams can just disable it if needed. Can you confirm or deny it is the case? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456286] New: When locale-gen support is disabled in the new language KCM, changing languages has no effect
https://bugs.kde.org/show_bug.cgi?id=456286 Bug ID: 456286 Summary: When locale-gen support is disabled in the new language KCM, changing languages has no effect Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_language Assignee: h...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When building the KCM without support for "locale-gen" (not needed in openSUSE; see bug 456285), adding or removing languages has no effect. STEPS TO REPRODUCE 1. Open the KCM 2. Click on "Change it..." next to language 3. Add another language in addition to the current one 4. Save changes 5. Log out 6. Log back in 7. Open the KCM 8. Click on "Change it..." next to language 9. Check the language list OBSERVED RESULT The new language added is no longer present. EXPECTED RESULT The newly added language should be present. SOFTWARE/OS VERSIONS KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: 5.15.5 + latest KDE patches ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456285] New: The new language and region KCM hardcodes "locale-gen".
https://bugs.kde.org/show_bug.cgi?id=456285 Bug ID: 456285 Summary: The new language and region KCM hardcodes "locale-gen". Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_language Assignee: h...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The new merged language and regional options KCM requires "locale-gen" to handle translations. However, some distribution do not have a "locale-gen" binary available. For example, openSUSE ships all locales already generated in a specific package. This would affect also all distributions which handle locales in the same manner. That would not be a problem per se, however the need of "locale-gen" is hardcoded in the KCM. OBSERVED RESULT The KCM depends on "locale-gen" to handle locale generation. EXPECTED RESULT The KCM should not hardcode the need for "locale-gen" and should use already generated locales if available. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453608] New: Quick launch applet no longer starts program, opens .desktop files with associated application
https://bugs.kde.org/show_bug.cgi?id=453608 Bug ID: 453608 Summary: Quick launch applet no longer starts program, opens .desktop files with associated application Product: kdeplasma-addons Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quicklaunch Assignee: now...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Note: this may be a bug in a Framework or elsewhere, but this is where it manifests itself. Since about one week (today: 2022-05-10) the Quick Launch applet does no longer start added applications, but instead opens them with the program associated to .desktop files (in this case, it ended up being Kate). STEPS TO REPRODUCE 1. Add a Quick Launch applet to the desktop 2. Add any launcher (e.g. Konsole) 3. Click on Konsole OBSERVED RESULT The associated application for .desktop files opens (in my case, Kate). EXPECTED RESULT Konsole (or any other application added) should launch. SOFTWARE/OS VERSIONS KDE Plasma Version: Latest master as of 2022-05-09 KDE Frameworks Version: Latest master as of 2022-05-09 Qt Version: 5.15.3 + KDE patches -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 452817] screenlocker currently not working at all
https://bugs.kde.org/show_bug.cgi?id=452817
Luca Beltrame changed:
What|Removed |Added
CC||lbeltr...@kde.org
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #8 from Luca Beltrame ---
This happens because KLibexec looks up kscreenlocker_greet in /libexec, not
/usr/libexec.
>From strace I ran on a nested Wayland session:
[pid 13948] execve("/libexec/kscreenlocker_greet"
But in openSUSE Tumbleweed it is installed in /usr/libexec.
I had a discussion about it with Fabian on IRC about a possible cause:
[12:35] The relative path is formed by going from /usr/lib64/ to
/usr/libexec
[12:36] During runtime the shared library is opened from /lib64/
though, so it tries /libexec
[12:36] i.e. incompatible with usrmerge
[12:37] At least that's my theory
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 452988] New: kwin_wayland segfaults when laptop screen is closed, turned off, and then reopened
https://bugs.kde.org/show_bug.cgi?id=452988
Bug ID: 452988
Summary: kwin_wayland segfaults when laptop screen is closed,
turned off, and then reopened
Product: kwin
Version: git master
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: lbeltr...@kde.org
Target Milestone: ---
Created attachment 148356
--> https://bugs.kde.org/attachment.cgi?id=148356=edit
Backtrace from coredumpctl
SUMMARY
When I close my laptop screen (regardless if the machine suspends or not), if
the laptop screen is turned off, kwin_wayland will crash once the screen is
opened again and the screen is turned on again. This also happens if the screen
is simply turned off for energy saving.
A look at the backtrace (attached) suggests that it attempts to access a member
of an object that's however null.
STEPS TO REPRODUCE
1. Close laptop screen
2. Wait until laptop suspends
3. Open laptop screen
OBSERVED RESULT
kwin_wayland crashes.
EXPECTED RESULT
kwin_wayland should not crash.
SOFTWARE/OS VERSIONS
KDE Plasma Version: latest git master
KDE Frameworks Version: latest git master
Qt Version: Qt 5.15.3 + KDE patches
ADDITIONAL INFORMATION
Test machine: Lenovo Thinkpad T470, with latest stable Mesa and kernel 5.17.3.
Excerpt from gdb debug session:
Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0
--xwayland-fd 8 --xwayl'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 KWin::LockScreenFilter::pointerEvent (this=,
event=0x7ffe50e6bd80, nativeButton=0)
at
/usr/src/debug/kwin5-5.24.80git.20220423T142940~8455427dbc-ku.78.1.x86_64/src/input.cpp:354
354 if (window->isClient() && window->isLockScreen()) {
[Current thread is 1 (Thread 0x7f03e7d45980 (LWP 25016))]
(gdb) print window
$1 = (KWin::Window *) 0x0
(gdb)
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 --- Comment #9 from Luca Beltrame --- I also need to rectify what I wrote earlier. It seemed to me that new panels were correct: but I just tested it again and no, new panels appear dark as well. I made sure by clearing all caches before adding one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 --- Comment #8 from Luca Beltrame --- (In reply to Luca Beltrame from comment #7) > I'll test the color when I'm home, but I can already tell you that new > panels are properly transparent, but their dialogs are still black tinted. Well, this is weird. The panel stays black-ish when I change the setColor call. (I set it to Qt::red). I have no idea why that single call changes everything still. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 --- Comment #7 from Luca Beltrame --- (In reply to Vlad Zahorodnii from comment #6) > https://invent.kde.org/plasma/plasma-workspace/-/blob/ > 5824e6362008988f74d07c9fce930e93294b990d/shell/desktopview.cpp#L37 if you > change Qt::black to Qt::red, are panel corners red? Do new panels have > opaque background? I'll test the color when I'm home, but I can already tell you that new panels are properly transparent, but their dialogs are still black tinted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 --- Comment #4 from Luca Beltrame --- Created attachment 147021 --> https://bugs.kde.org/attachment.cgi?id=147021=edit KWin supporting information -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 --- Comment #3 from Luca Beltrame --- Created attachment 147020 --> https://bugs.kde.org/attachment.cgi?id=147020=edit Broken rendering with dialog (panel options) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 --- Comment #2 from Luca Beltrame --- Created attachment 147019 --> https://bugs.kde.org/attachment.cgi?id=147019=edit Detail of the artifacts on the panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 Luca Beltrame changed: What|Removed |Added CC||vlad.zahorod...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 --- Comment #1 from Luca Beltrame --- Created attachment 147018 --> https://bugs.kde.org/attachment.cgi?id=147018=edit Panel with correct rendering -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450672] New: Panel drawn with a black tint after commit 745e2c08
https://bugs.kde.org/show_bug.cgi?id=450672 Bug ID: 450672 Summary: Panel drawn with a black tint after commit 745e2c08 Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: lbeltr...@kde.org Target Milestone: 1.0 Created attachment 147017 --> https://bugs.kde.org/attachment.cgi?id=147017=edit Panel with the broken rendering SUMMARY After https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1474 landed, panels (and some Plasma dialogs) are drawn with a black tint on X11. Reverting 745e2c08 in plasmashell restores the previous behavior (no other changes needed). KWin supporting information and screenshots are attached. STEPS TO REPRODUCE 1. Start plasmashell with 745e2c08 applied. OBSERVED RESULT Panel is drawn with a black tint and has visible artifacts (see screenshots). Some Plasma dialogs too (see screenshots). EXPECTED RESULT Panel should be transparent. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed / latest master (available in About System) KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: latest 5.15 + the full KDE patch set ADDITIONAL INFORMATION This problem does not seem to occur on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450507] systemsettings crashes on close at display settings in Icon View mode
https://bugs.kde.org/show_bug.cgi?id=450507 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #2 from Luca Beltrame --- systemsettings is not the only affected application. In my setup, plasmashell crashes at startup with a similar backtrace. Reverting 0943bbf5 in kdeclarative fixes the crash. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442043] ksystemstats: NVMe drive temperature is no longer reported (sensor missing)
https://bugs.kde.org/show_bug.cgi?id=442043 Luca Beltrame changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Luca Beltrame --- Looks fixed with latest master (not sure if it also applies to stable). Both my NVMe SSDs are shown and with temperature readings. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440080] Discover crashes on every start using git snapshots
https://bugs.kde.org/show_bug.cgi?id=440080 Luca Beltrame changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #10 from Luca Beltrame --- Either way, this is not a bug in Discover per se, so let's close this. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440080] Discover crashes on every start using git snapshots
https://bugs.kde.org/show_bug.cgi?id=440080 --- Comment #8 from Luca Beltrame --- It's been a longstanding bug I've been experiencing (often with Mesa updates) in which the QML compiled cache is somehow not compatible and causes crashes. I hope you kept the files, so that at last it can be diagnosed somehow (I'm still not sure it's a Qt bug or a bug elsewhere). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440080] Discover crashes on every start using git snapshots
https://bugs.kde.org/show_bug.cgi?id=440080 --- Comment #6 from Luca Beltrame --- Or rather, move it away. Don't delete it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440080] Discover crashes on every start using git snapshots
https://bugs.kde.org/show_bug.cgi?id=440080 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #5 from Luca Beltrame --- Try removing the QML cache: ~/.cache//qmlcache -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441547] Crash in KWin::clamp_row() when switching activities
https://bugs.kde.org/show_bug.cgi?id=441547 Luca Beltrame changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Luca Beltrame --- Tested yesterday (behind master ~1 day, give or take) on the same system. Still got the crash. I didn't have time to look into the backtrace, though. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442042] ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins
https://bugs.kde.org/show_bug.cgi?id=442042 Luca Beltrame changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Luca Beltrame --- Yes, I confirm it's in the sensor browser, and it's displaying 0 C. My guess is that the temperature sensor fails to initialize properly (the cause of the crash before), but now we have a default sensor property with no data. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442042] ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins
https://bugs.kde.org/show_bug.cgi?id=442042 --- Comment #1 from Luca Beltrame --- Qt is meant to be 5.15.2, not 5.12.5. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442043] New: ksystemstats: NVMe drive temperature is no longer reported (sensor missing)
https://bugs.kde.org/show_bug.cgi?id=442043 Bug ID: 442043 Summary: ksystemstats: NVMe drive temperature is no longer reported (sensor missing) Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The new sensor-based plugins in ksystemstats have lost some features, for example the ability to report temperatures from NVMe drives, a regression from the state before these plugins were merged. Sensors report the temperature correctly. STEPS TO REPRODUCE 1. Search for "NVMe" in the sensors of a plasma system monitor applet OBSERVED RESULT No temperature sensor is found EXPECTED RESULT The temperature sensor should be displayed (like it was before the merge) SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest master (available in About System) KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: 5.15.5 + KDE patches ADDITIONAL INFORMATION sensors output: nvme-pci-0100 Adapter: PCI adapter Composite:+36.9°C (low = -273.1°C, high = +83.8°C) -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442042] New: ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins
https://bugs.kde.org/show_bug.cgi?id=442042 Bug ID: 442042 Summary: ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After fixing https://bugs.kde.org/show_bug.cgi?id=442023 (see latest comments there), ksystemstats does not report properly the temperature of my GPU anymore. This started happening after the merge of the new plugins based on libsensors. Note that libsensors reports the temperature properly (see below). STEPS TO REPRODUCE 1. Run ksystemstats (with the fix from bug 442023) 2. Check plasma-systemmonitor or the plasma applets for GPU temperatures OBSERVED RESULT "GPU 1 Temperature 0 C" is displayed EXPECTED RESULT The correct temperature (40 C) should be reported SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest master (available in About System) KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: 5.12.5 + KDE patches ADDITIONAL INFORMATION Kernel version: 5.13.13-1-default "sensors" output: amdgpu-pci-0b00 Adapter: PCI adapter vddgfx: 768.00 mV fan1:1438 RPM (min =0 RPM, max = 3500 RPM) edge: +40.0°C (crit = +85.0°C, hyst = -273.1°C) (emerg = +90.0°C) junction: +40.0°C (crit = +105.0°C, hyst = -273.1°C) (emerg = +110.0°C) mem: +42.0°C (crit = +95.0°C, hyst = -273.1°C) (emerg = +100.0°C) power1:6.00 W (cap = 260.00 W) -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442023] ksystemstats crashes on startup
https://bugs.kde.org/show_bug.cgi?id=442023 --- Comment #5 from Luca Beltrame --- This at least prevents ksystemstats from crashing. There's another issue now which I'll report a separate bug for later. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442023] ksystemstats crashes on startup
https://bugs.kde.org/show_bug.cgi?id=442023 --- Comment #3 from Luca Beltrame --- By sensor property I mean m_temperatureProperty in plugins/gpu/GpuDevice.cpp. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442023] ksystemstats crashes on startup
https://bugs.kde.org/show_bug.cgi?id=442023 --- Comment #2 from Luca Beltrame --- It looks like the sensor property is constructed improperly (garbage when trying to check it from gdb), but I'm not sure how to debug this further. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442023] ksystemstats crashes on startup
https://bugs.kde.org/show_bug.cgi?id=442023 Luca Beltrame changed: What|Removed |Added CC||k...@david-redondo.de -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442023] ksystemstats crashes on startup
https://bugs.kde.org/show_bug.cgi?id=442023 Luca Beltrame changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442023] New: ksystemstats crashes on startup
https://bugs.kde.org/show_bug.cgi?id=442023 Bug ID: 442023 Summary: ksystemstats crashes on startup Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: --- Created attachment 141307 --> https://bugs.kde.org/attachment.cgi?id=141307=edit Backtrace of the crash SUMMARY (Note: ksystemstats doesn't have its own bug component) Since https://invent.kde.org/plasma/ksystemstats/-/merge_requests/9, ksystemstats crashes at startup in GpuDevice::initialize. I assume this has to do with the discovery of GPUs which goes awry (see attached backtrace). STEPS TO REPRODUCE 1. Run ksystemstats OBSERVED RESULT ksystemstats crashes on startup EXPECTED RESULT ksystemstats should run. SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest master (available in About System) KDE Plasma Version: latest master KDE Frameworks Version: latest master Qt Version: 5.15.2 + KDE patches ADDITIONAL INFORMATION sudo lshw -c display *-display description: VGA compatible controller product: Vega 10 XL/XT [Radeon RX Vega 56/64] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:0b:00.0 logical name: /dev/fb0 version: c3 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb configuration: depth=32 driver=amdgpu latency=0 resolution=2560,1440 resources: irq:110 memory:e000-efff memory:f000-f01f ioport:d000(size=256) memory:f6a0-f6a7 memory:c-d -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441547] Crash in kwin_wayland when switching activities
https://bugs.kde.org/show_bug.cgi?id=441547 --- Comment #2 from Luca Beltrame --- It's not always reproducible. Sometimes a plain meta-tab would work, other times it would just crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441547] New: Crash in kwin_wayland when switching activities
https://bugs.kde.org/show_bug.cgi?id=441547 Bug ID: 441547 Summary: Crash in kwin_wayland when switching activities Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: lbeltr...@kde.org Target Milestone: --- Created attachment 141050 --> https://bugs.kde.org/attachment.cgi?id=141050=edit Backtrace SUMMARY When hitting meta-tab to switch between activities, kwin_wayland crashes immediately with the attached backtrace. Switching activities via DBus does not trigger any crash. STEPS TO REPRODUCE 1. Run Plasma under Wayland with at least two activities already defined 2. Hit Meta-Tab OBSERVED RESULT kwin_wayland crashes (backtrace attached). EXPECTED RESULT The activity switcher should appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 + KDE patches ADDITIONAL INFORMATION Given the fact that it crashes in the OpenGL context, I'll add that this occurs with the Intel driver (I'm unable to test with other drivers). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439251] Firefox does not remember window size on wayland
https://bugs.kde.org/show_bug.cgi?id=439251 --- Comment #5 from Luca Beltrame --- Created attachment 140493 --> https://bugs.kde.org/attachment.cgi?id=140493=edit Wayland debug log until the window appears -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439251] Firefox does not remember window size on wayland
https://bugs.kde.org/show_bug.cgi?id=439251 Luca Beltrame changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439251] Firefox does not remember window size on wayland
https://bugs.kde.org/show_bug.cgi?id=439251 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #4 from Luca Beltrame --- I can reproduce 100% of the time. I'll supply the requested information later today. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 439175] New: Make QtWebkitWidgets optional / remove the dependency
https://bugs.kde.org/show_bug.cgi?id=439175 Bug ID: 439175 Summary: Make QtWebkitWidgets optional / remove the dependency Product: cantor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: lbeltr...@kde.org Target Milestone: --- The recent merging of the documentation branch in cantor (master) added both a dependency on QWebEngine and QtWebKitWidgets. The latter is part of the unmaintained and unsupported QtWebKit (save for a third party fork not everyone ships), which some distributions are removing. Thus, the dependency on QtWebKitWidgets (which looks unused from a quick glance in the code, but I might be mistaken) should be either removed entirely (if unused) or made optional (if used) to allow also building on distributions which do not ship, or plan to not ship QtWebKit anymore (such as openSUSE). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436041] plasmashell crashes at start
https://bugs.kde.org/show_bug.cgi?id=436041 --- Comment #8 from Luca Beltrame --- Git commit ea95ebd0cdc8991938994daadaccea883ceabacc by Luca Beltrame. Committed on 24/04/2021 at 22:15. Pushed by lbeltrame into branch 'master'. Revert "don't make config key change and size change conflict" This reverts commit 156509b785b6b4312d984841f9ba6375687389d3. At least this prevents plasmashell from crashing until a solution is found. CCMAIL: notm...@gmail.com CCMAIL: plasma-de...@kde.org M +32 -58 components/containmentlayoutmanager/appletslayout.cpp M +2-22 components/containmentlayoutmanager/appletslayout.h https://invent.kde.org/plasma/plasma-workspace/commit/ea95ebd0cdc8991938994daadaccea883ceabacc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436041] plasmashell crashes at start
https://bugs.kde.org/show_bug.cgi?id=436041 --- Comment #7 from Luca Beltrame --- Git commit 1d68bc118a1b0eb0e3ce1bc25c17c781cd6cead5 by Luca Beltrame. Committed on 24/04/2021 at 22:15. Pushed by lbeltrame into branch 'master'. Revert "Save layouts per-resolution" This reverts commit 1390b55188e032336a9e92fb74bd55260493f1eb. At least this prevents plasmashell from crashing until a solution is found. CCMAIL: notm...@gmail.com CCMAIL: plasma-de...@kde.org M +1-3containments/desktop/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/1d68bc118a1b0eb0e3ce1bc25c17c781cd6cead5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436041] plasmashell crashes at start
https://bugs.kde.org/show_bug.cgi?id=436041 --- Comment #6 from Luca Beltrame --- Scratch that, I probably did something wrong in my checkout. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436041] plasmashell crashes at start
https://bugs.kde.org/show_bug.cgi?id=436041
--- Comment #5 from Luca Beltrame ---
(In reply to Luca Beltrame from comment #4)
> in p-d that need to be done ("fallbackConfigKey" in
> org.kde.plasma.desktop/main.qml).
Rather, reverting the commit makes the fallbackConfigKey in p-d not readable
anymore (at least when I tried).
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 436041] plasmashell crashes at start
https://bugs.kde.org/show_bug.cgi?id=436041
Luca Beltrame changed:
What|Removed |Added
CC||lbeltr...@kde.org
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #4 from Luca Beltrame ---
Confirmed. Reverting the commit isn't enough because there are also changes in
p-d that need to be done ("fallbackConfigKey" in
org.kde.plasma.desktop/main.qml).
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 431149] https://invent.kde.org/plasma/plasma-workspace/-/commit/0d02ac8996db2d9fff8b3bf5e3e313a563a118af renders garbage on top of Plasma Dialogs (panels, tooltips, applets, notifications)
https://bugs.kde.org/show_bug.cgi?id=431149 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #11 from Luca Beltrame --- I was affected the same way, and the reversion actually fixed the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428811] Visual regression: margins no longer honored for Folder View in applet mode
https://bugs.kde.org/show_bug.cgi?id=428811 --- Comment #1 from Luca Beltrame --- Created attachment 133124 --> https://bugs.kde.org/attachment.cgi?id=133124=edit Detail of a folder view instance on the desktop showing folders overflowing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428811] New: Visual regression: margins no longer honored for Folder View in applet mode
https://bugs.kde.org/show_bug.cgi?id=428811
Bug ID: 428811
Summary: Visual regression: margins no longer honored for
Folder View in applet mode
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Folder
Assignee: h...@kde.org
Reporter: lbeltr...@kde.org
CC: plasma-b...@kde.org
Target Milestone: 1.0
Created attachment 133123
--> https://bugs.kde.org/attachment.cgi?id=133123=edit
Plasmoidviewer showing the issue (look at the plasmoid margins in the top left
corner)
SUMMARY
In latest master, the margins of the folder view are no longer respected: you
get at best two lines which go beyond the screen (see attached screenshot).
I tried locating the commit which broke it, but I could not find anything
suspicious in plasma-{framework, desktop, workspace) or in kdeclarative or in
kitemmodels.
STEPS TO REPRODUCE
1. Load a Folder View in standalone mode (or use plasmoidviewer) in a folder
with many items
OBSERVED RESULT
Rows overflow the plasmoid borders and go beyond the screen / window
EXPECTED RESULT
Plasmoid margins are respected.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: latest maaster
(available in About System)
KDE Plasma Version: latest master
KDE Frameworks Version: latest master
Qt Version: 5.15.0
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 393449] Failure to build from source (CMake error)
https://bugs.kde.org/show_bug.cgi?id=393449 Luca Beltrame changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Luca Beltrame --- Confirmed building. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423426] POP3 setup wizard defaults to unencrypted connections.
https://bugs.kde.org/show_bug.cgi?id=423426 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423130] Wallpaper settings lost on plasmashell restart
https://bugs.kde.org/show_bug.cgi?id=423130 Luca Beltrame changed: What|Removed |Added See Also||https://github.com/rpm-soft ||ware-management/rpm/issues/ ||1278 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423130] Wallpaper settings lost on plasmashell restart
https://bugs.kde.org/show_bug.cgi?id=423130 Luca Beltrame changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|CONFIRMED |RESOLVED --- Comment #6 from Luca Beltrame --- Well, after a few rounds of debugging with fvogt on IRC (he did most of the work ;) it turns out that it's in fact, an RPM (the package manager) bug! For those ending up here from search engines: remove /usr/share/plasma/wallpapers/org.kde.slideshow/contents/config/main.xml and reinstall plasma5-workspace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423130] New: Wallpaper settings lost on plasmashell restart
https://bugs.kde.org/show_bug.cgi?id=423130 Bug ID: 423130 Summary: Wallpaper settings lost on plasmashell restart Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In current Plasma master, changing the wallpaper will only work as long as plasmashell is running. Once it is restarted, it will fall back to the default wallpaper. STEPS TO REPRODUCE 1. Change wallpaper 2. Restart plasmashell (kquitapp5 plasmashell && plasmashell) OBSERVED RESULT Wallpaper is set to default. EXPECTED RESULT User-selected wallpaper is shown. SOFTWARE/OS VERSIONS KDE Plasma Version: Current git master KDE Frameworks Version: Current git master Qt Version: 5.15.0 ADDITIONAL INFORMATION I'm not sure if it is noise or not, but the following is printed when applying settings in the dialog: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:176:13: Unable to assign [undefined] to int -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421696] New: Hard disk activity: duplicated sensors appear in the list
https://bugs.kde.org/show_bug.cgi?id=421696 Bug ID: 421696 Summary: Hard disk activity: duplicated sensors appear in the list Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Adding a new sensors representing the I/O of all disks causes the "All Sensors" list to grow two new "Disk Write Access" and "Disk Read Access" upon clicking "Apply". The new sensor name disappears as well, although the entry stays. STEPS TO REPRODUCE 1. Add a hard disk activity widget 2. Go to preferences > Sensors Details 3. Select "partitions" > All > select a sensor and add it 4. Click Apply OBSERVED RESULT Two new pair of sensors appear in the list and the newly-added sensor in "Chart Sensors" loses its name (replaced by a blank string) EXPECTED RESULT Sensor is added correctly and the list of available sensor stay the same. SOFTWARE/OS VERSIONS Plasma from git master, KF5 from git master, Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421695] New: Network speed widget: preferences checkbox "Show sensors legend" does not show checked state
https://bugs.kde.org/show_bug.cgi?id=421695 Bug ID: 421695 Summary: Network speed widget: preferences checkbox "Show sensors legend" does not show checked state Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The checkbox "Show sensors legend" in applet configuration stays forever in checked state, at least visually. Note that clicking on it, even though does not cause visual feedback, does switch the feature on/off. STEPS TO REPRODUCE 1. Add Network speed widget 2. Enter applet preferences 3. Click on "show sensors legend" OBSERVED RESULT Checkbox remains checked, although the corresponding functionality is enabled / disabled. EXPECTED RESULT Checkbox should change visual state (toggled / untoggled and vice versa) SOFTWARE/OS VERSIONS Plasma from git master, KF5 from git master, Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421694] Network speed widget: Upload/download labels overlap with speed
https://bugs.kde.org/show_bug.cgi?id=421694 --- Comment #1 from Luca Beltrame --- Created attachment 128556 --> https://bugs.kde.org/attachment.cgi?id=128556=edit Screenshot of labels overlapping -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421694] New: Network speed widget: Upload/download labels overlap with speed
https://bugs.kde.org/show_bug.cgi?id=421694 Bug ID: 421694 Summary: Network speed widget: Upload/download labels overlap with speed Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY As the title says, the upload/download speed labels in the sensors legend are overlapping with the speed. Screenshot attached. STEPS TO REPRODUCE 1. Add a network speed widget 2. Add the sensors legend 3. Enlarge the widget enough that labels are shown OBSERVED RESULT Labels overlapping (see screenshot) EXPECTED RESULT Labels are not overlapping SOFTWARE/OS VERSIONS Plasma git master, KF5 git master, Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421513] New: Configuration of the disk usage applet does not make clear which sensor relates to which partition / disk
https://bugs.kde.org/show_bug.cgi?id=421513 Bug ID: 421513 Summary: Configuration of the disk usage applet does not make clear which sensor relates to which partition / disk Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 128454 --> https://bugs.kde.org/attachment.cgi?id=128454=edit Configuration screen detail SUMMARY When configuring sensors in the disk usage applet, the list is full of "percentage used" but it is absolutely not clear which sensors refer to which disk. Screenshot attached. STEPS TO REPRODUCE 1. Add a Disk Usage applet do the desktop 2. Open applet configuration 3. Move to "Sensors Details" OBSERVED RESULT No relationship between the sensor color and the disk (neither on clicking, nor on hovering). EXPECTED RESULT Each sensor should tell which partition / disk / path it refers to. SOFTWARE/OS VERSIONS Plasma from git master (as of 2020-05-14), KF5 from git master (same as Plasma), Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421512] New: Visual regression in disk usage applet
https://bugs.kde.org/show_bug.cgi?id=421512 Bug ID: 421512 Summary: Visual regression in disk usage applet Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 128453 --> https://bugs.kde.org/attachment.cgi?id=128453=edit Screenshot of default applet SUMMARY The new system monitor applet with regards to disk usage generates, by default, an applet that is totally unreadable, with many bars and with no clear indication to which bar corresponds to which partition / mountpoint. Screenshot attached. STEPS TO REPRODUCE 1. Add "Disk Usage" to desktop OBSERVED RESULT Applet with unreadable and thin colored bars EXPECTED RESULT An applet similar to the one existing before the rewrite. SOFTWARE/OS VERSIONS Plasma from git master (as of 2020-05-14), KF5 from git master (same date) and Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 421364] App launched via a desktop icon opens its own desktop file
https://bugs.kde.org/show_bug.cgi?id=421364 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 419237] New: kig's FindBoostPython.cmake does not find the py3 version of python-boost
https://bugs.kde.org/show_bug.cgi?id=419237 Bug ID: 419237 Summary: kig's FindBoostPython.cmake does not find the py3 version of python-boost Product: kig Version: 20.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: david.narv...@computer.org Reporter: lbeltr...@kde.org Target Milestone: --- SUMMARY As the summary says, the Python support in kig is disabled when only Python 3 is installed, because it is not found by its own FindBoostPython macro. STEPS TO REPRODUCE 1. Have a system with no boost-python for Python 2, but with boost-python for Python 3 installed 2. Run CMake in a checkout of the sources OBSERVED RESULT boost-python is not found and the Python bindings are disabled. EXPECTED RESULT boost-python is found and the Python bindings are enabled. SOFTWARE/OS VERSIONS KDE Frameworks Version: master Qt Version: 5.14 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 418331] Make kdsoap an optional dependency
https://bugs.kde.org/show_bug.cgi?id=418331 Luca Beltrame changed: What|Removed |Added See Also||https://github.com/KDAB/KDS ||oap/issues/212 --- Comment #4 from Luca Beltrame --- It's still included in the distributed tarball, which shouldn't happen. I have filed an issue upstream already. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 418331] Make kdsoap an optional dependency
https://bugs.kde.org/show_bug.cgi?id=418331 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #2 from Luca Beltrame --- Currently there are licensing issues in kdsoap (EULA shipped in the source package which is incompatible with the other licenses there). Unless these are fixed, packaging kdsoap properly is a non-starter. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #10 from Luca Beltrame --- Yes, I confirm that setting DPI to 96 for fonts fixes the issue for me (although compared to the reporter, I have issues only in apps that use QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true)). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414252] SDDM breeze theme can not be loaded: StackView is not a type
https://bugs.kde.org/show_bug.cgi?id=414252 Luca Beltrame changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-workspace/47c76ebc83ee1 ||f96c7a5fd9be23c6234a93143e8 --- Comment #2 from Luca Beltrame --- Git commit 47c76ebc83ee1f96c7a5fd9be23c6234a93143e8 by Luca Beltrame. Committed on 18/11/2019 at 06:55. Pushed by lbeltrame into branch 'master'. Unbreak SDDM theme loading In b7b25010aa58c6366c8182c886d5daae496bab42 the import line was changed but nothing else was, causing errors in QML loading which ultimately prevented SDDM from loading the theme. CCMAIL: i...@guoyunhe.me M +1-1sddm-theme/Main.qml https://commits.kde.org/plasma-workspace/47c76ebc83ee1f96c7a5fd9be23c6234a93143e8 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414252] SDDM breeze theme can not be loaded: StackView is not a type
https://bugs.kde.org/show_bug.cgi?id=414252 --- Comment #1 from Luca Beltrame --- It looks to me that an import was changed from implicit "import QtQuickControls 2.0" as explicit "import QtQuickControls 2.0 as QQC2" without changing everything else in b7b25010aa58c6366c8182c886d5daae496bab42. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414252] New: SDDM breeze theme can not be loaded: StackView is not a type
https://bugs.kde.org/show_bug.cgi?id=414252
Bug ID: 414252
Summary: SDDM breeze theme can not be loaded: StackView is not
a type
Product: Breeze
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: lbeltr...@kde.org
Target Milestone: ---
SUMMARY
Something seems to have changed in the components used by the SDDM theme in
current Plasma master.
When starting the greeter, and also in test mode, I get:
[07:36:07.270] (WW) GREETER:
file:///usr/share/sddm/themes/breeze/Main.qml:151:9: StackView is not a type
StackView {
^
[07:36:07.270] (WW) GREETER:
file:///usr/share/sddm/themes/breeze/Main.qml:151:9: StackView is not a type
StackView {
It doesn't look like it is a recent change (a search through the git log shows
nothing useful), however, so I'm unsure of the cause.
STEPS TO REPRODUCE
1. Load the SDDM theme with testing mode: sddm-greeter --test-mode /sddm-theme
OBSERVED RESULT
SDDM falls back to the embedded theme with the error shown above.
EXPECTED RESULT
Breeze theme for SDDM should load.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: latest master
KDE Plasma Version: latest master
KDE Frameworks Version: latest master
Qt Version: 5.13.1
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 413416] New: Build failure with gcc 9
https://bugs.kde.org/show_bug.cgi?id=413416
Bug ID: 413416
Summary: Build failure with gcc 9
Product: kdenlive
Version: git-master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Installation
Assignee: vpi...@kde.org
Reporter: lbeltr...@kde.org
Target Milestone: ---
SUMMARY
When trying to build kdenlive git master on openSUSE Tumbleweed, with GCC 9,
compilation fails with this error:
[ 120s] cd
"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build/thumbnailer"
&& /usr/bin/c++ -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB
-DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG
-DQT_NO_URL_CAST_FROM_STRING -DQT_WIDGETS_LIB -DTRANSLATION_DOMAIN=\"kdenlive\"
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -Dmltpreview_EXPORTS
-I"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build/thumbnailer"
-I"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/thumbnailer"
-I"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build/thumbnailer/mltpreview_autogen/include"
-I/usr/include/mlt -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtCore
-isystem /usr/lib/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtGui
-isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5 -isystem
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem
/usr/include/KF5/KConfigCore -isystem /usr/include/qt5/QtNetwork -isystem
/usr/include/qt5/QtConcurrent -isystem /usr/include/qt5/QtDBus -isystem
/usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KJobWidgets -isystem
/usr/include/qt5/QtWidgets -isystem /usr/include/KF5/KCompletion -isystem
/usr/include/KF5/KWidgetsAddons -fomit-frame-pointer -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type
-flto=auto -g -DNDEBUG -fno-operator-names -fno-exceptions -Wall -Wextra
-Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith
-Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla
-Wdate-time -Wsuggest-override -Wlogical-op -fPIC -Wno-suggest-override -fPIC
-fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o
CMakeFiles/mltpreview.dir/mltpreview.cpp.o -c
"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/thumbnailer/mltpreview.cpp"
[ 120s]
/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/src/lib/external/media_ctrl/mediactrl.c:
In function 'find_first_device':
[ 120s]
/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/src/lib/external/media_ctrl/mediactrl.c:355:5:
error: 'for' loop initial declarations are only allowed in C99 or C11 mode
[ 120s] 355 | for (int i = 0; i < 32; i++) {
[ 120s] | ^~~
[ 120s]
/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/src/lib/external/media_ctrl/mediactrl.c:355:5:
note: use option '-std=c99', '-std=gnu99', '-std=c11' or '-std=gnu11' to
compile your code
[ 120s] make[2]: ***
[src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/build.make:76:
src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/mediactrl.c.o] Error 1
[ 120s] make[2]: Leaving directory
'/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build'
[ 120s] make[1]: *** [CMakeFiles/Makefile2:752:
src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/all] Error 2
I can't track which recent commit might have broken it, though.
STEPS TO REPRODUCE
1. Build the latest kdenlive git master
SOFTWARE/OS VERSIONS
gcc --version
gcc (SUSE Linux) 9.2.1 20190903 [gcc-9-branch revision 275330]
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
All the KF5 stack is built from its latest git master state.
--
You are receiving this mail because:
You are watching all bug changes.
[kolf] [Bug 413383] New: kolf installs a private library system-wide
https://bugs.kde.org/show_bug.cgi?id=413383 Bug ID: 413383 Summary: kolf installs a private library system-wide Product: kolf Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: majew...@gmx.net Reporter: lbeltr...@kde.org CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Kolf used to install a private shared library, now a static library. Probably it should not be installed as, being private, it cannot be used by other applications. Historically in openSUSE we always removed the shared library (and now the static library) prior to packaging and we experienced no problems with the application. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411286] With Qt 5.12.3, Discover crashes after opening when updates found, or clicking applications category
https://bugs.kde.org/show_bug.cgi?id=411286 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #42 from Luca Beltrame --- (In reply to ludger from comment #41) > I can also confirm now Discover works again smoothly. > > Thanks to all great developers for the fast fix! To be completely fair, Qt 5.12.4 was out in June, so the fix was already available for quite a while. Most other distros with the exception of Neon (of which this bug belongs to) had already a non-affected Qt version and thus suffered no crash. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 410802] Cantor uses a bundled, patched discount copy and fails to build if LANG is not poperly set
https://bugs.kde.org/show_bug.cgi?id=410802 --- Comment #3 from Luca Beltrame --- And on why LANG isn't set: build hosts (in this case openSUSE's OBS) only bootstrap the minimal system possible (in a VM or a chroot) to build the package. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 410802] Cantor uses a bundled, patched discount copy and fails to build if LANG is not poperly set
https://bugs.kde.org/show_bug.cgi?id=410802 Luca Beltrame changed: What|Removed |Added Summary|Cantor tries to download|Cantor uses a bundled, |data during building and|patched discount copy and |the process is undocumented |fails to build if LANG is ||not poperly set --- Comment #2 from Luca Beltrame --- (In reply to Nikita Sirgienko from comment #1) > "discount-2.2.6-patched.tar" placed in cantor/thirdparty directory. It is It looks like it fails if LANG isn't properly set. If setting LANG to "en_US.UTF-8" prior to building, it builds. I've edited the title to reflect this. That said, it is not acceptable for distros to have bundled third party deps (unless you can disable the bundled copy and use the system one), nor that the feature summary doesn't tell you that it's going to use a bundled library. The README should also mention this. > think, in future, I will send my Discount changes into master, but until the > moment, I think, using embeded library version is the best option. That won't fly with distributions for a lot of good reasons: what if the bundled library does not build anymore for newer compilers? What if there is a security vulnerability in the bundled library that is not patched? What if there are bugs in the bundled library that are fixed in newer versions? As this change is in master only, there is enough time for 19.12 to: a. Submit discount changes upstream b. Allow the build system to *not* use the bundled discount fork (because that's what it is) c. Write at the end of the cmake call whether a bundled library is being used or not. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 410802] Cantor tries to download data during building and the process is undocumented
https://bugs.kde.org/show_bug.cgi?id=410802 Luca Beltrame changed: What|Removed |Added CC||warqu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 410802] New: Cantor tries to download data during building and the process is undocumented
https://bugs.kde.org/show_bug.cgi?id=410802 Bug ID: 410802 Summary: Cantor tries to download data during building and the process is undocumented Product: cantor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: lbeltr...@kde.org Target Milestone: --- SUMMARY In distributions' build systems, the build hosts have no network access for a veriety of reasons (including security and reproducibility of builds - there's no guarantee a remote location won't change). Recent Cantor master tries to download something off the network when building: [ 162s] [ 2%] Performing download step (verify and extract) for 'discount_project' Which attempts to download something called "discount-2.2.6-patched.tar". In a build host, of course the downloading fails and so building Cantor fails. There are several problems in this scenario: 1. There's no indication in cmake that discount is required: it is neither searched for, nor shown that it is required; 2. It is unclear what kind of "patch" discount has, what is needed for, and why one can't use an unbundled discount (most of the distributions will not allow bundling third party libraries). There are no references anywhere in the README. This appears to have been added in eb047a4ec0234183652415cf458c17493f2574c3 without any kind of review. OBSERVED RESULT Building Cantor tries to download a tarball from somewhere, build fails if download does not work. EXPECTED RESULT Cantor uses a system-wide discount and builds. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 410020] Regression: fea2af1d63192226d18910e18627091206a2fcf5 breaks GPG wallets
https://bugs.kde.org/show_bug.cgi?id=410020 Luca Beltrame changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwa ||llet/ff6b077d9200856dc6e393 ||a04c6b3ae82d9792ed --- Comment #1 from Luca Beltrame --- Git commit ff6b077d9200856dc6e393a04c6b3ae82d9792ed by Luca Beltrame. Committed on 20/07/2019 at 07:21. Pushed by lbeltrame into branch 'master'. Move kwalletd initialization earlier In the previous code (before removing the kde4 migration agent) it was started inconditionally, while after the change it was gated behind an if. However this does not take into account GPG wallets, which, as far as I understand from the code, do not produce a password hash. Moving initialization out of the if restores GPG functionality Stefan, please check if everything is correct. CCMAIL: stefan.bru...@rwth-aachen.de M +1-1src/runtime/kwalletd/main.cpp https://commits.kde.org/kwallet/ff6b077d9200856dc6e393a04c6b3ae82d9792ed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 410020] Regression: fea2af1d63192226d18910e18627091206a2fcf5 breaks GPG wallets
https://bugs.kde.org/show_bug.cgi?id=410020 Luca Beltrame changed: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 410020] New: Regression: fea2af1d63192226d18910e18627091206a2fcf5 breaks GPG wallets
https://bugs.kde.org/show_bug.cgi?id=410020 Bug ID: 410020 Summary: Regression: fea2af1d63192226d18910e18627091206a2fcf5 breaks GPG wallets Product: frameworks-kwallet Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: va...@kde.org Reporter: lbeltr...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY After https://phabricator.kde.org/D21002 landed, GPG wallets are no longer loaded by kwalletd, nor are visible in kwalletmanager. This is despite GPG support being advertised and compiled in. Reverting fea2af1d63192226d18910e18627091206a2fcf5 and its follow up commit restores functionality. STEPS TO REPRODUCE 1. Start a session, investigate wallets through kwalletmanager OBSERVED RESULT No wallets are opened (nor the user is asked for the GPG passphrase if defined) and no wallets are even visible in kwalletmanager. EXPECTED RESULT Wallets should be regularly opened through GPG. SOFTWARE/OS VERSIONS Linux/KDE Plasma: master KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.13 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 406574] Can't load from *.xmi file (possibly error with temporary file)
https://bugs.kde.org/show_bug.cgi?id=406574 --- Comment #2 from Luca Beltrame --- Please submit your patch through Phabricator (https://phabricator.kde.org) or chances are it will not get the attention it deserves. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400983] org.kde.plasma.mediacontroller QML loading errors breaking media controller
https://bugs.kde.org/show_bug.cgi?id=400983 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 395107] Spell check does not work + missing language
https://bugs.kde.org/show_bug.cgi?id=395107 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #6 from Luca Beltrame --- This is actually a problem of the KDE4 version of kile: kdelibs is not compatible with enchant 2, so it won't build the spell checking support. As for why openSUSE Tumbleweed ships the KDE4 version, it's because the KF5 version of kile hasn't had a proper release yet. We do offer snapshots from git in a separate repository, and that would be a workaround for this issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403679] re-add multiple splits (+ support both horizontal and vertical split)
https://bugs.kde.org/show_bug.cgi?id=403679 Luca Beltrame changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 403548] New: plasma-nm Wireguard: endpoint UI should be reworked
https://bugs.kde.org/show_bug.cgi?id=403548 Bug ID: 403548 Summary: plasma-nm Wireguard: endpoint UI should be reworked Product: plasma-nm Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: lbeltr...@kde.org Target Milestone: --- SUMMARY The UI for the endpoint in the Wireguard VPN support for plasma-nm largely mimics what wg-quick does, offering a single text box to include address and port. It should be split into a text box for addresses / names, and a numerical input for ports. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 403547] New: plasma-nm Wireguard: redundant options offered in the Advanced configuration
https://bugs.kde.org/show_bug.cgi?id=403547 Bug ID: 403547 Summary: plasma-nm Wireguard: redundant options offered in the Advanced configuration Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: lbeltr...@kde.org Target Milestone: --- SUMMARY The Wireguard support in plasma-nm seems to rely heavily on the behavior of the wg-quick tool, and exposes many details that are redundant, given NM's own support for most of these. For example Pre-up, Post-up, Pre-down, Post-down commands are specific to wg-quick and don't integrate with NM (NM has dispatcher scripts for this). MTU overrides what can be set in NM. Most of these fields should be removed, leaving at best "Persistent Keepalive", "Preshared key", and "Listen Port". -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 403546] New: Redundant plasma-nm wireguard DNS entry in connection editor
https://bugs.kde.org/show_bug.cgi?id=403546 Bug ID: 403546 Summary: Redundant plasma-nm wireguard DNS entry in connection editor Product: plasma-nm Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: lbeltr...@kde.org Target Milestone: --- SUMMARY The DNS field in the connection editor for WireGuard VPNs is redundant, because it exposes an implementation detail (from the wg-quick utility) and does not leverage the IPv* connection options from NetworkManager. At the same time, it is completely non-functional for systems that don't use resolvconf. In short, it would probably need to be removed and NM's native handling used instead. STEPS TO REPRODUCE 1. Create a WireGuard connection in a distribution that doesn't use resolvconf 2. Fill in the DNS field in the UI OBSERVED RESULT The VPN connection, once established, does not use the configured DNS, as expected due to the lack of resolvconf. Setting DNS via the NetworkManager IP options (i.e. changing from "Automatic" to "Automatic (addresses only)" and setting the DNS) does change the VPN's DNS correctly. Linux/KDE Plasma: latest git master (available in About System) KDE Plasma Version: latest git master KDE Frameworks Version: latest git master Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 300370] Rss feeds are not formatted even though html was specified
https://bugs.kde.org/show_bug.cgi?id=300370 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 301934] Thread previews not working in Opera 12.0
https://bugs.kde.org/show_bug.cgi?id=301934 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 295028] Brainstorm login, clicking on "Return to the Previous Page" takes you to the wrong place
https://bugs.kde.org/show_bug.cgi?id=295028 Luca Beltrame changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||lbeltr...@kde.org Resolution|WAITINGFORINFO |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 255362] Unable to register with forum using konqueror
https://bugs.kde.org/show_bug.cgi?id=255362 Luca Beltrame changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||lbeltr...@kde.org Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #2 from Luca Beltrame --- No one is actually working on the forum theme currently. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 257667] Forum User Control Panel fails to copy/link to avatars from Gravatar.com
https://bugs.kde.org/show_bug.cgi?id=257667 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #2 from Luca Beltrame --- The current forum theme / software has no official maintainer currently. -- You are receiving this mail because: You are watching all bug changes.
