[gwenview] [Bug 474463] Add svgs to supported mimetype
https://bugs.kde.org/show_bug.cgi?id=474463 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #5 from Bernie Innocenti --- I just tried opening SVGs in Koko, and it's no better than Gwenview: it gets rendered to a bitmap, and zooming results in upscaling. Currently (Plasma 6.1.1), when clicking on an SVG image, I get a read-only XML dump in Okular. I came here thinking it was a bug that should be reported. Thus, I'm reopening this bug to request re-evaluating last year's decision. While non-ideal, I feel that associating "image/xml+svg" with Gwenview leads to a less surprising and more desirable result for a user wanting to "see" an SVG image. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487779] ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
https://bugs.kde.org/show_bug.cgi?id=487779 --- Comment #3 from Bernie Innocenti --- Found an existing bug in the Chromium bug tracker: https://issues.chromium.org/issues/331796411 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487779] ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
https://bugs.kde.org/show_bug.cgi?id=487779 --- Comment #1 from Bernie Innocenti --- Forgot to mention: videos play correctly, I wouldn't have noticed the issue without looking in the journal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487779] New: ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
https://bugs.kde.org/show_bug.cgi?id=487779 Bug ID: 487779 Summary: ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ber...@codewiz.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When Chrome is playing a video, plasmashell floods the user journal with multiple errors per second: May 29 23:45:33 goreboot plasmashell[77995]: [78055:78123:0529/234533.88:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE May 29 23:45:33 goreboot plasmashell[77995]: [78055:78123:0529/234533.929884:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE May 29 23:45:33 goreboot plasmashell[77995]: [78055:78123:0529/234533.970093:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE ... STEPS TO REPRODUCE 1. Launch a KDE Plasma Wayland session 2. Launch Chrome 3. Go to YouTube and play any video SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION HDR enabled AMD Radeon RX 7900 XT (RADV NAVI31) Mesa 24.1.0-arch1.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480834] New: Can't install cursor themes with "Get New..."
https://bugs.kde.org/show_bug.cgi?id=480834 Bug ID: 480834 Summary: Can't install cursor themes with "Get New..." Classification: Applications Product: systemsettings Version: 5.93.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: ber...@codewiz.org Target Milestone: --- SUMMARY Installing a new cursor theme with Get New fails with: qrc:/qt/qml/org/kde/newstuff/EntryDetails.qml:86: ReferenceError: entryId is not defined STEPS TO REPRODUCE 1. Open "Get New..." 2. Search for Capitaine Cursors by Keefer 3. Click "Install..." 4. A window opens, prompting to choose a tarball from a list. Click Install on capitaine-cursors-light-r4.tar.gz OBSERVED RESULT The window closes and nothing happens. The process logs this error: qrc:/qt/qml/org/kde/newstuff/EntryDetails.qml:86: ReferenceError: entryId is not defined EXPECTED RESULT Cursor theme should have been installed. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #73 from Bernie Innocenti --- I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from the Fedora COPR repo "hazel-bunny/ports". I confirm it fixes this particular bug: the authentication window renders and you can type your login and password. I still couldn't log into my Google account because it has 2FA enabled and the webengine doesn't seem to support USB security keys :-( It seems KDE would be better off switching to gnome-online-accounts or other actively developed framework. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #50 from Bernie Innocenti --- I filed this Fedora bug to request upgrading signon-ui: https://bugzilla.redhat.com/show_bug.cgi?id=2230099 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #43 from Bernie Innocenti --- (In reply to Harald Sitter from comment #41) > signon-ui 0.15 is even more ancient than ubuntu's. Upstream seems dead: https://launchpad.net/signon-ui Arch has signon-ui 0.17, released on August 2015 from a fork on GitLab: https://gitlab.com/accounts-sso/signon-ui/-/commits/master?ref_type=heads Time for KDE to consider switching to GOA? https://wiki.gnome.org/Projects/GnomeOnlineAccounts/Providers -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 Bernie Innocenti changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #40 from Bernie Innocenti --- On Fedora Rawhide (pre-release of Fedora 39), I don't get a blank window as in the original bug report, but the Google authentication process gets stuck after submitting the email address, before the password prompt. The busy animation keeps playing forever. If I close the window, the following message appears on stdout: ``` Error: "Access grant not present" ``` Versions: - libaccounts-qt5-1.16-8.fc39.x86_64 - kaccounts-providers-23.04.3-2.fc39.x86_64 - accounts-qml-module-0.7-10.fc39.x86_64 - plasma-systemsettings-5.27.6-2.fc39.x86_64 - signon-ui-0.15-20.fc39.x86_64 - signon-8.60-13.fc39.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 458746] Apply button doesn't become active after editing wireguard connection
https://bugs.kde.org/show_bug.cgi?id=458746 --- Comment #2 from Bernie Innocenti --- I figured out that the problem occurs when importing a WireGuard conf file with IPv6 routes (Interface / Address contains IPv6 routes). In this case, IPv6 / Method is switched to Manual, but the address list remains empty. Moreover, the Address listview does not become red to bring attention to the form validation error. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 458746] Apply button doesn't become active after editing wireguard connection
https://bugs.kde.org/show_bug.cgi?id=458746 Bernie Innocenti changed: What|Removed |Added Platform|Archlinux |Fedora RPMs Version|5.25.4 |5.27.6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 458746] Apply button doesn't become active after editing wireguard connection
https://bugs.kde.org/show_bug.cgi?id=458746 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Bernie Innocenti --- Still present on Fedora Rawhide with Plasma 2.27.6 and KF 5.108.0. These WireGuard connections were imported from .conf files, and have a mysterious "-" in the IPv4 Search Domains field (but not in the corresponding IPv6 page). Moreover, the importer set the "Connect automatically" flag on all connections, leading to multiple nested VPNs when you login. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 467772] QML error when selecting network connection
https://bugs.kde.org/show_bug.cgi?id=467772 Bernie Innocenti changed: What|Removed |Added Version|5.27.2 |5.27.6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 467772] QML error when selecting network connection
https://bugs.kde.org/show_bug.cgi?id=467772 Bernie Innocenti changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||ber...@codewiz.org Ever confirmed|0 |1 --- Comment #1 from Bernie Innocenti --- Confirmed on Plasma 5.27.6 and KF 5.108.0. In fact, every time I switch to a new connection I see two of these errors: ``` file:///usr/share/kcm_networkmanagement/qml/ListItem.qml:25: Error: Cannot assign to non-existent property "prefix" file:///usr/share/kcm_networkmanagement/qml/ListItem.qml:26: Error: Cannot assign to non-existent property "prefix" ``` These are the offending lines: ``` 25 onPressed: if (changeBackgroundOnPress) background.prefix = "pressed" 26 onReleased: if (changeBackgroundOnPress) background.prefix = "normal" 27 onCanceled: if (changeBackgroundOnPress) background.prefix = "normal" ``` -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 469465] Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
https://bugs.kde.org/show_bug.cgi?id=469465 --- Comment #4 from Bernie Innocenti --- The message seems to come from gtk3-3.24.37-1.fc38.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 469465] Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
https://bugs.kde.org/show_bug.cgi?id=469465
--- Comment #3 from Bernie Innocenti ---
.config/gtk-3.0/gtk.css contains only this one line:
```
@import 'colors.css';
```
The offending lines seem to be from /usr/share/themes/Breeze/gtk-3.0/gtk.css
1649 and 1652:
```
1648 .normal-icons {
1649 -gtk-icon-size: 16px; }
1650
1651 .large-icons {
1652 -gtk-icon-size: 32px; }
```
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 469465] Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
https://bugs.kde.org/show_bug.cgi?id=469465 Bernie Innocenti changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Bernie Innocenti --- The app I used for this bug's description was eog, but I get similar output from gedit: ``` bernie@giskard:~% gedit (gedit:26024): Gtk-WARNING **: 02:36:48.122: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name (gedit:26024): Gtk-WARNING **: 02:36:48.122: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name ``` -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 469465] New: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
https://bugs.kde.org/show_bug.cgi?id=469465 Bug ID: 469465 Summary: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name Classification: Plasma Product: Breeze Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: plasma-b...@kde.org Reporter: ber...@codewiz.org CC: agrine...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY On startup, all GTK-3 apps print a bunch of warnings when using the Breeze theme: bernie@giskard:~[1]% eog (eog:157555): Gtk-WARNING **: 16:43:47.616: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name (eog:157555): Gtk-WARNING **: 16:43:47.616: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name (eog:157555): Handy-WARNING **: 16:43:47.691: Using GtkSettings:gtk-application-prefer-dark-theme together with HdyStyleManager is unsupported. Please use HdyStyleManager:color-scheme instead. (eog:157555): Gtk-WARNING **: 16:43:47.696: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 with Plasma 5.27.4 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 466845] New: kdialog crashed when clicking on parent directory
https://bugs.kde.org/show_bug.cgi?id=466845 Bug ID: 466845 Summary: kdialog crashed when clicking on parent directory Classification: Applications Product: kdialog Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: ber...@codewiz.org Target Milestone: --- Application: kdialog (22.12.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.2.0-63.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma Prerelease) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: This was a file open dialog brought up by Chrome to select an avatar. I went to a directory, enabled previews, clicked on a few images, then clicked on the parent directory, and kdialog crashed. (I might have missed some step). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDialog (kdialog), signal: Segmentation fault [KCrash Handler] #4 0x75f7c1cd in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #5 0x764e5c2e in QVector::realloc(int, QFlags) () from /lib64/libQt5Core.so.5 #6 0x766900e2 in QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&, QVector const&, QModelIndex const&, Qt::Orientation, bool) () from /lib64/libQt5Core.so.5 #7 0x76692b89 in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int, int, Qt::Orientation) () from /lib64/libQt5Core.so.5 #8 0x7669592d in QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) () from /lib64/libQt5Core.so.5 #9 0x766e8038 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x766622ea in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () from /lib64/libQt5Core.so.5 #11 0x7666b4d0 in QAbstractItemModel::endInsertRows() () from /lib64/libQt5Core.so.5 #12 0x7192498a in KDirModelPrivate::_k_slotNewItems(QUrl const&, KFileItemList const&) () from /lib64/libKF5KIOWidgets.so.5 #13 0x766e7eb1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #14 0x77d05af0 in KCoreDirLister::itemsAdded(QUrl const&, KFileItemList const&) () from /lib64/libKF5KIOCore.so.5 #15 0x77d06c84 in KCoreDirListerPrivate::emitItems() () from /lib64/libKF5KIOCore.so.5 #16 0x77d027a8 in KCoreDirListerCache::slotEntries(KIO::Job*, QList const&) () from /lib64/libKF5KIOCore.so.5 #17 0x766e7eb1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #18 0x77cc00c5 in KIO::ListJob::entries(KIO::Job*, QList const&) () from /lib64/libKF5KIOCore.so.5 #19 0x766e7eb1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #20 0x77cb0dac in KIO::SlaveInterface::listEntries(QList const&) () from /lib64/libKF5KIOCore.so.5 #21 0x77cb5a18 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #22 0x77cb0acb in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #23 0x77cb33f1 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #24 0x766e7eb1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #25 0x766def9b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #26 0x773aeca5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x766b35a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #28 0x766b6a55 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #29 0x7670669f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #30 0x74d127f8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #31 0x74d70f38 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #32 0x74d10183 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #33 0x76706189 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #34 0x766b1f7b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #35 0x775cc9db in QDialog::exec() () from /lib64/libQt5Widgets.so.5 #36 0x775cc8b4 in QDialog::exec() () from /lib64/libQt5Widgets.so.5 #37 0x555659e5 in main () [Inferior 1 (process 451920) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 465613] Crash in Baloo::PostingDB::get
https://bugs.kde.org/show_bug.cgi?id=465613 --- Comment #2 from Bernie Innocenti --- Stacktrace looks similar to https://bugs.kde.org/show_bug.cgi?id=425025 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 465613] Crash in Baloo::PostingDB::get
https://bugs.kde.org/show_bug.cgi?id=465613 --- Comment #1 from Bernie Innocenti --- Saw this in the console just before the crash: ASSERT: "!term.isEmpty()" in file /home/bernie/kde/src/baloo/src/engine/postingdb.cpp, line 75 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 465613] New: Crash in Baloo::PostingDB::get
https://bugs.kde.org/show_bug.cgi?id=465613
Bug ID: 465613
Summary: Crash in Baloo::PostingDB::get
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: ber...@codewiz.org
Target Milestone: ---
Application: baloo_file_extractor (5.103.0)
(Compiled from sources)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.0-rc5-1-drm-tip-git-ga9e72f4e0baf x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.80 [KCrashBackend]
-- Information about the crash:
Baloo repeatedly crashes a few seconds after starting:
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 0x7f79604a08ec in ?? () from /usr/lib/libc.so.6
#6 0x7f7960451ea8 in raise () from /usr/lib/libc.so.6
#7 0x7f796043b53d in abort () from /usr/lib/libc.so.6
#8 0x7f7960a9fede in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
#9 0x7f7960a9ff3c in qt_assert(char const*, char const*, int) () from
/usr/lib/libQt5Core.so.5
#10 0x7f79619edcb2 in Baloo::PostingDB::get (this=0x7ffe2b951bb0, term=...)
at /home/bernie/kde/src/baloo/src/engine/postingdb.cpp:75
#11 0x7f79619fdbad in Baloo::WriteTransaction::commit (this=0x56050be36300)
at /home/bernie/kde/src/baloo/src/engine/writetransaction.cpp:282
#12 0x7f79619f6396 in Baloo::Transaction::commit (this=0x7f79580149f0) at
/home/bernie/kde/src/baloo/src/engine/transaction.cpp:272
#13 0x560509d5fd3a in Baloo::App::processNextFile (this=0x7ffe2b952250) at
/home/bernie/kde/src/baloo/src/file/extractor/app.cpp:109
#14 0x560509d63922 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void (Baloo::App::*)()>::call(void (Baloo::App::*)(),
Baloo::App*, void**) (f=(void (Baloo::App::*)(Baloo::App * const))
0x560509d5fb42 , o=0x7ffe2b952250,
arg=0x7ffe2b951dc0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152
#15 0x560509d6386a in QtPrivate::FunctionPointer::call, void>(void (Baloo::App::*)(),
Baloo::App*, void**) (f=(void (Baloo::App::*)(Baloo::App * const))
0x560509d5fb42 , o=0x7ffe2b952250,
arg=0x7ffe2b951dc0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185
#16 0x560509d634a5 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (which=1, this_=0x56050bf53a00, r=0x7ffe2b952250,
a=0x7ffe2b951dc0, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:418
#17 0x7f7960cc1387 in ?? () from /usr/lib/libQt5Core.so.5
#18 0x7f7960cb1b56 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#19 0x7f7960c8df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#20 0x7f7960cd84b3 in QTimerInfoList::activateTimers() () from
/usr/lib/libQt5Core.so.5
#21 0x7f7960cd8af2 in ?? () from /usr/lib/libQt5Core.so.5
#22 0x7f795f91682b in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x7f795f96dcc9 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x7f795f9150e2 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x7f7960cd8c6c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#26 0x7f7960c866ec in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#27 0x7f7960c91219 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#28 0x560509d5edbd in main (argc=1, argv=0x7ffe2b9524d8) at
/home/bernie/kde/src/baloo/src/file/extractor/main.cpp:43
[Inferior 1 (process 879717) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 256242] Please support Multi-Screen-Setup (seperate X-Servers) in kwin
https://bugs.kde.org/show_bug.cgi?id=256242 Bernie Innocenti changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||ber...@codewiz.org --- Comment #132 from Bernie Innocenti --- Should we close this old bug, given that X11 is legacy and unlikely to receive new features? If anything remains to be done, it should be targeted at Wayland. Feel free to reopen in case someone is actually planning to improve multiscreen support in kwin_x11. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #21 from Bernie Innocenti --- (In reply to devsk from comment #20) > Or the devs you already have are interested only in next shiny thing than to > fix bugs in their code...:-) Sure, we can't force devs to stick around > forever and fix bugs in their code but sometimes, its good to stop new > development and just fix the bugs. You will have more adoption and > participation, and that can potentially get you more devs. As a user, I also wish session restore to worked on Wayland, but inflammatory comments won't help expedite it. I would like to know what's making this difficult. X11 had a session management protocol; does Wayland define something equivalent? If not, could Plasma do something limited to KDE apps? Where is the current session save/restore code? Any documentation we could link in this bug to support someone who wants to give a shot at it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459626] Plasmashell crashes due to an assertion failure in screencasting.cpp
https://bugs.kde.org/show_bug.cgi?id=459626 Bernie Innocenti changed: What|Removed |Added Summary|Plasmashell crashes due to |Plasmashell crashes due to |an Assertion failure in |an assertion failure in |screencasting.cpp |screencasting.cpp -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370204] Kimpanel icon size is different from system tray icons
https://bugs.kde.org/show_bug.cgi?id=370204 --- Comment #6 from Bernie Innocenti --- Forgot to mention that I'm using a Wayland session and I'm using IBus rather than XIM... In case kimpanel isn't supposed to be used in this session, would it be possible to hide it from the widgets list? If this isn't feasible, then change the friendly name shown to users from "Input Method Panel" to something more specific to X11 or XIM... or maybe remove it from the default install of Plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370204] Kimpanel icon size is different from system tray icons
https://bugs.kde.org/show_bug.cgi?id=370204 --- Comment #5 from Bernie Innocenti --- Created attachment 152401 --> https://bugs.kde.org/attachment.cgi?id=152401=edit ximpanel in Plasma 5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370204] Kimpanel icon size is different from system tray icons
https://bugs.kde.org/show_bug.cgi?id=370204 Bernie Innocenti changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370204] Kimpanel icon size is different from system tray icons
https://bugs.kde.org/show_bug.cgi?id=370204 --- Comment #4 from Bernie Innocenti --- With Plasma 5.25.5, I see no icon at all for the Input Method widget (ximpanel). Tested both on ArchLinux and on Fedora 37 beta. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459626] Plasmashell crashes due to an Assertion failure in screencasting.cpp
https://bugs.kde.org/show_bug.cgi?id=459626 --- Comment #1 from Bernie Innocenti --- plasmashell does *not* crash when using Plasma 5.25.5 Wayland session with the same config. Looks like a 5.26 regression introduced a few days or weeks ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459626] New: Plasmashell crashes due to an Assertion failure in screencasting.cpp
https://bugs.kde.org/show_bug.cgi?id=459626
Bug ID: 459626
Summary: Plasmashell crashes due to an Assertion failure in
screencasting.cpp
Classification: Plasma
Product: plasmashell
Version: master
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Task Manager and Icons-Only Task Manager
Assignee: plasma-b...@kde.org
Reporter: ber...@codewiz.org
Target Milestone: 1.0
I'm running Plasma built today via kdesrc-build, and plasmashell crashed a
dozen times in less than one hour.
I don't use screenscasting and I don't see a screencasting widget on my taskbar
or on the desktop.
Console output:
Remember requesting the interface on your desktop file:
X-KDE-Wayland-Interfaces=zkde_screencast_unstable_v1
ASSERT: "isInitialized()" in file
/home/bernie/kde/src/plasma-workspace/libtaskmanager/declarative/screencasting.cpp,
line 80
Stacktrace:
Thread 1 "plasmashell" received signal SIGABRT, Aborted.
0x746a149c in ?? () from /usr/lib/libc.so.6
(gdb) bt
#0 0x746a149c in () at /usr/lib/libc.so.6
#1 0x74651958 in raise () at /usr/lib/libc.so.6
#2 0x7463b53d in abort () at /usr/lib/libc.so.6
#3 0x74c9fede in qt_assert(char const*, char const*, int) () at
/usr/lib/libQt5Core.so.5
#4 0x74c9ff3c in qt_assert_x(char const*, char const*, char const*,
int) () at /usr/lib/libQt5Core.so.5
#5 0x7fff2c166f84 in
ScreencastingPrivate::ScreencastingPrivate(Screencasting*)
(this=0x5adc4b00, q=0x5addfa90) at
/home/bernie/kde/src/plasma-workspace/libtaskmanager/declarative/screencasting.cpp:80
#6 0x7fff2c1664a8 in Screencasting::Screencasting(QObject*)
(this=0x5addfa90, parent=0x5ada8c60) at
/home/bernie/kde/src/plasma-workspace/libtaskmanager/declarative/screencasting.cpp:93
#7 0x7fff2c167e61 in ScreencastingRequest::setUuid(QString const&)
(this=0x5ada8c60, uuid=@0x7fffc910: {
d = 0x5adc4e20
}) at
/home/bernie/kde/src/plasma-workspace/libtaskmanager/declarative/screencastingrequest.cpp:50
#8 0x7fff2c16008c in ScreencastingRequest::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x5ada8c60,
_c=QMetaObject::WriteProperty, _id=0, _a=0x7fffc870)
at
/home/bernie/kde/build/plasma-workspace/libtaskmanager/declarative/taskmanagerplugin_autogen/EWIEGA46WW/moc_screencastingrequest.cpp:139
#9 0x76a3cabe in () at /usr/lib/libQt5Qml.so.5
#10 0x76a4417f in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData
const&, QVariant const&, QQmlContextData*, QFlags)
() at /usr/lib/libQt5Qml.so.5
#11 0x76a99c20 in QQmlBinding::slowWrite(QQmlPropertyData const&,
QQmlPropertyData const&, QV4::Value const&, bool,
QFlags) () at /usr/lib/libQt5Qml.so.5
#12 0x76a916ab in () at /usr/lib/libQt5Qml.so.5
#13 0x76a97b4e in () at /usr/lib/libQt5Qml.so.5
#14 0x76a991c3 in
QQmlBinding::update(QFlags) () at
/usr/lib/libQt5Qml.so.5
#15 0x76aa450d in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at
/usr/lib/libQt5Qml.so.5
#16 0x76a4abdf in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at
/usr/lib/libQt5Qml.so.5
#17 0x76a4b586 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () at /usr/lib/libQt5Qml.so.5
#18 0x76a4b802 in QQmlComponent::create(QQmlIncubator&, QQmlContext*,
QQmlContext*) () at /usr/lib/libQt5Qml.so.5
#19 0x770bcb5b in () at /usr/lib/libQt5Quick.so.5
#20 0x74ebd530 in () at /usr/lib/libQt5Core.so.5
#21 0x76a456d3 in QQmlComponent::statusChanged(QQmlComponent::Status)
() at /usr/lib/libQt5Qml.so.5
#22 0x76a45028 in QQmlComponentPrivate::typeDataReady(QQmlTypeData*) ()
at /usr/lib/libQt5Qml.so.5
#23 0x76a2129d in () at /usr/lib/libQt5Qml.so.5
#24 0x76a28431 in () at /usr/lib/libQt5Qml.so.5
#25 0x76ac0806 in () at /usr/lib/libQt5Qml.so.5
#26 0x76ac0866 in () at /usr/lib/libQt5Qml.so.5
#27 0x75d78b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#28 0x74e8cb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#29 0x74e8d693 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#30 0x74ed3728 in () at /usr/lib/libQt5Core.so.5
#31 0x7307081b in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#32 0x730c6ec9 in () at /usr/lib/libglib-2.0.so.0
#33 0x7306f0d2 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#34 0x74ed750c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#35 0x74e8532c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#36 0x74e8fe59 in QCoreApplication::exec() ()
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448 --- Comment #10 from Bernie Innocenti --- Better debug trace: 2022-09-04 21:42:40.000 HTTPProtocol::readBody:4454: EOD received! Left = "0" 2022-09-04 21:42:40.000 HTTPProtocol::cacheFileClose:4875: HTTPProtocol::cacheFileClose() 2022-09-04 21:42:40.000 HTTPProtocol::httpClose:3923: keepAlive = true 2022-09-04 21:42:40.000 HTTPProtocol::cacheFileClose:4875: HTTPProtocol::cacheFileClose() 2022-09-04 21:42:40.000 HTTPProtocol::httpClose:3938: keep alive ( 60 ) 2022-09-04 21:42:40.000 KIO::SlaveBasePrivate::verifyState:196: verifyState() get() 2022-09-04 21:42:46.553 unknown:17: qrc:/qml/DiscoverPage.qml:17:13: QML InlineMessage: Cannot anchor to an item that isn't a parent or sibling. 2022-09-04 21:42:46.579 KIO::SlaveBasePrivate::verifyState:196: verifyState() fileSystemFreeSpace() 2022-09-04 21:42:46.579 KIO::SlaveBasePrivate::verifyState:196: verifyState() fileSystemFreeSpace() 2022-09-04 21:43:40.003 HTTPProtocol::special:3998: 2022-09-04 21:43:40.003 HTTPProtocol::httpCloseConnection:3958: 2022-09-04 21:43:40.004 KIO::SlaveBasePrivate::verifyState:196: verifyState() timeoutSpecialCommand() 2022-09-04 21:43:40.004 unknown:197: ASSERT failure in void KIO::SlaveBasePrivate::verifyState(const char*): "timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave", file /home/bernie/kde/src/kio/src/core/slavebase.cpp, line 197 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448 --- Comment #9 from Bernie Innocenti --- I can reproduce this crash in plasma-discover too, it just takes longer because the keep-alive timeout is 60 seconds instead of 5 seconds. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448 --- Comment #8 from Bernie Innocenti --- As you can see from the timestamps, there's a gap of 5 seconds between the end of the request in HTTPProtocol::readBody() and the keepalive timeout: Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: EOD received! Left = "0" ... Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: keep alive ( 5 ) Sep 04 20:59:15 goreboot kioslave5[173862]: kf.kio.slaves.http: Sep 04 20:59:15 goreboot kioslave5[173862]: kf.kio.slaves.http: Sep 04 20:59:15 goreboot kioslave5[173862]: ASSERT failure in void KIO::SlaveBasePrivate::verifyState(const char*): "timeoutSpecialCommand() did not call finished() or error()! Please f> This code seems to be expecting that an empty qCDebug() would print the function name, but it does not. Not knowing how to enable this, I'll add some more output manually... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #7 from Bernie Innocenti ---
I enabled debug logging in kio/src/ioslaves/http/http.cpp, and this is what I
got:
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http:
Sending Header:
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "GET
/rest/product/kde HTTP/1.1"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "Host:
bugs.kde.org"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "Connection:
keep-alive"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "User-Agent:
DrKonqi"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "Pragma:
no-cache"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "Cache-control:
no-cache"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "Accept:
application/json"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http:
"Accept-Encoding: gzip, deflate, x-gzip, x-deflate"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http:
"Accept-Charset: utf-8,*;q=0.5"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http:
"Accept-Language: en-US,en;q=0.9"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: "Content-Type:
application/json"
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http: sent it!
Sep 04 20:59:09 goreboot kioslave5[173862]: kf.kio.slaves.http:
Sep 04 20:59:10 goreboot drkonqi[173769]:
QJsonDocument({"akonadiserver":{"index":"15","key":"5e2ae85b669b42c19e30b4dcf419b9fb","project":"akonadiserver"},"baloo_file_extractor":{"index>
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http:
Received Status Response:
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: "HTTP/1.1 200
OK"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http:
QUrl("https://bugs.kde.org/rest/product/kde;) response code: 200 previous
response code: 0
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: wasAuthError=
false isAuthError= false sameAuthError= false
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: -- full
response:
"HTTP/1.1 200 OK\r\nDate: Mon, 05
Sep 2022 03:59:09 GMT\r\nServer: Apache/2.4.29
(Ubuntu)\r\nAccess-control-allow-headers: origin, content-t>
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Content-type:
"application/json"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Encoding-type:
"charset" = "UTF-8"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: before fixup
"application/json"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: after fixup
"application/json"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: parsed expire
date from 'expires' header: "Mon, 05 Sep 2022 03:59:09 GMT"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Cache, adding
QUrl("https://bugs.kde.org/rest/product/kde;)
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http:
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Emitting
mimetype "application/json"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Previous
Response: 0
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Current
Response: 200
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: "-1" bytes
left.
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Chunk size =
13240 bytes
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: bytesReceived:
4096 m_iSize: -1 Chunked: true BytesLeft: 9144
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Caching
disabled because content size is too big.
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http:
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: bytesReceived:
4096 m_iSize: -1 Chunked: true BytesLeft: 5048
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: bytesReceived:
4096 m_iSize: -1 Chunked: true BytesLeft: 952
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: bytesReceived:
952 m_iSize: -1 Chunked: true BytesLeft: -1
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: Chunk size = 0
bytes
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: bytesReceived:
0 m_iSize: -1 Chunked: true BytesLeft: 0
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: EOD received!
Left = "0"
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http:
Sep 04 20:59:10 goreboot kioslave5[173862]: kf.kio.slaves.http: keepAlive =
true
Sep 04 20:59:10 goreboot ki
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448 --- Comment #6 from Bernie Innocenti --- Ok, perhaps something is special about the virtual override in HTTPProtocol::special() ? As far as I understand, `HTTPProtocol::httpClose(keepAlive = true)` will set timeoutData to 99, which causes special() to call httpCloseConnection(). Should it have called finished() afterwards? Elsewhere, I see calls to finished() just after httpClose()... but not everywhere: - HTTPProtocol::error(): the doc of finished() says you shouldn't call it after calling error(), so I guess this is ok? - HTTPProtocol::~HTTPProtocol(): Is it possible to destroy the instance while a timeout is still pending? - HTTPProtocol::proceedUntilResponseContent(): might return early is status != 0. Otherwise, it will call finish() either in sendHttpError() or outside. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448 --- Comment #5 from Bernie Innocenti --- This is the MR: https://invent.kde.org/frameworks/kio/-/merge_requests/946 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448
Bernie Innocenti changed:
What|Removed |Added
CC||sit...@kde.org
--- Comment #4 from Bernie Innocenti ---
The failing check was added in this commit:
tree 74aa6a361d80ac78a36f4e9827cd88aed131a567
parent 7a267428fa3483137ee728ffc5bac6ba185d3052
author Harald Sitter Wed Aug 3 13:08:20 2022 +0200
committer Harald Sitter Tue Aug 9 19:15:01 2022 +
clear state after timeout'd special call
this fixes a crash with the sftp worker.
what happens is that when a worker uses the timeoutSpecialCommand
infrastructure they'll get a special() call before the regular dispatch
call. this would cause double-finished or double-errors emissions
because we hadn't cleared the state after the timeout special call.
to solve this problem we'll simply treat the timeout call like any other
dispatch call and verify the state and then reset it back to idle
we could also have continued but to prevent side effects of this fix
I've opted to keep the previous control flow going where the timeout
occurs in the same loop iteration as the dispatch.
diff --git a/src/core/slavebase.cpp b/src/core/slavebase.cpp
index 7f96bef8e..0ed1caf04 100644
--- a/src/core/slavebase.cpp
+++ b/src/core/slavebase.cpp
@@ -314,6 +314,9 @@ void SlaveBase::dispatchLoop()
d->nextTimeout.invalidate();
d->timeoutData = QByteArray();
special(data);
+// special calls finished(), verify and clear the state so the
following dispatch starts with a clean slate
+d->verifyState("timeoutSpecialCommand()");
+d->m_state = d->Idle;
}
Q_ASSERT(d->appConnection.inited());
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448
--- Comment #3 from Bernie Innocenti ---
This is the check that fails:
194 void verifyState(const char *cmdName)
195 {
196 KIO_STATE_ASSERT(finalState(),
197 Q_FUNC_INFO,
198 qUtf8Printable(QStringLiteral("%1 did not call
finished() or error()! Please fix the %2 KIO slave")
199
.arg(QLatin1String(cmdName))
200
.arg(QCoreApplication::applicationName(;
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 458448] timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448 --- Comment #2 from Bernie Innocenti --- I have 90 of these crashes in /var/lib/systemd/coredump/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 458448] New: timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave
https://bugs.kde.org/show_bug.cgi?id=458448 Bug ID: 458448 Summary: timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave Product: frameworks-kio Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: HTTP Assignee: kio-bugs-n...@kde.org Reporter: ber...@codewiz.org CC: kdelibs-b...@kde.org Target Milestone: --- This crash happened shortly after login, while I was running Discover: kioslave5[169959]: ASSERT failure in void KIO::SlaveBasePrivate::verifyState(const char*): "timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave", file /home/bernie/kde/src/kio/src/core/slavebase.cpp, line 196 Stack trace: [KCrash Handler] #5 0x7fe8ccea14dc in ?? () from /usr/lib/libc.so.6 #6 0x7fe8cce51998 in raise () from /usr/lib/libc.so.6 #7 0x7fe8cce3b53d in abort () from /usr/lib/libc.so.6 #8 0x7fe8cd49fede in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #9 0x7fe8cd49ff9d in qt_assert_x(char const*, char const*, char const*, int) () from /usr/lib/libQt5Core.so.5 #10 0x7fe8cdeba025 in KIO::SlaveBasePrivate::verifyState (this=0x558d0bca0a90, cmdName=0x7fe8cdfaf8cc "timeoutSpecialCommand()") at /home/bernie/kde/src/kio/src/core/slavebase.cpp:196 #11 0x7fe8cdeb2025 in KIO::SlaveBase::dispatchLoop (this=0x7ffef834bcb0) at /home/bernie/kde/src/kio/src/core/slavebase.cpp:318 #12 0x7fe8c8e4a49c in kdemain (argc=4, argv=0x7ffef834bfc0) at /home/bernie/kde/src/kio/src/ioslaves/http/http.cpp:106 #13 0x558d0a4307e9 in main (argc=5, argv=0x7ffef834c118) at /home/bernie/kde/src/kio/src/kioslave/kioslave.cpp:152 [Inferior 1 (process 169481) detached] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #23 from Bernie Innocenti --- I can't reproduce this bug on my Arch and Fedora desktops, running KDE Frameworks 5.96.0 and Plasma 5.25.3. Does it also happen when logging in with a new account? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443706] Crash in WindowShadowTile::~WindowShadowTile()
https://bugs.kde.org/show_bug.cgi?id=443706 Bernie Innocenti changed: What|Removed |Added Version|5.23.90 |5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454919] ASSERT: "d->m_texture" in file kwin/src/libkwineffects/kwingltexture.cpp, line 451
https://bugs.kde.org/show_bug.cgi?id=454919 --- Comment #2 from Bernie Innocenti --- I suspect Elite Dangerous triggers the bug by using a different screen resolution when running full-screen. I tried a different game on Steam, and switching between the game and the desktop did not crash kwin... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454919] ASSERT: "d->m_texture" in file kwin/src/libkwineffects/kwingltexture.cpp, line 451
https://bugs.kde.org/show_bug.cgi?id=454919 --- Comment #1 from Bernie Innocenti --- Journal: ``` Jun 05 23:28:15 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a screencast cursor update because the compositor is slow Jun 05 23:28:15 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a screencast cursor update because the compositor is slow Jun 05 23:28:15 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a screencast cursor update because the compositor is slow Jun 05 23:28:25 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jun 05 23:28:27 goreboot xdg-desktop-portal-kde[147351]: xdp-kde-background: GetAppState called: no parameters Jun 05 23:28:32 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jun 05 23:28:32 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jun 05 23:28:44 goreboot kwin_wayland[47828]: kwin_screencast: Dropping a screencast frame because the compositor is slow Jun 05 23:28:45 goreboot kwin_wayland[47828]: ASSERT: "d->m_texture" in file /home/bernie/kde/src/kwin/src/libkwineffects/kwingltexture.cpp, line 451 Jun 05 23:28:46 goreboot systemd-coredump[147552]: [ï¡•] Process 47828 (kwin_wayland) of user 1000 dumped core. ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454919] New: ASSERT: "d->m_texture" in file kwin/src/libkwineffects/kwingltexture.cpp, line 451
https://bugs.kde.org/show_bug.cgi?id=454919 Bug ID: 454919 Summary: ASSERT: "d->m_texture" in file kwin/src/libkwineffects/kwingltexture.cpp, line 451 Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ber...@codewiz.org Target Milestone: --- SUMMARY kwin_wayland asserts and crashes when recording the screen with the OBS pipewire plugin STEPS TO REPRODUCE 1. Open OBS and setup the Screen Capture (PipeWire) plugin 2. Start recording to a file (not sure if this step is necessary 3. Open Steam and start a game (probably any fullscreen OpenGL app will do) 4. Switch back to the desktop OBSERVED RESULT kwin_wayland dies, and the entire session is lost EXPECTED RESULT kwin_wayland should stay alive SOFTWARE/OS VERSIONS KDE Plasma Version: everything built from git as of today Qt Version: 5.15.4+kde+r0-1 ADDITIONAL INFORMATION Using amdgpu, in case it matters BTW I use Arch :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 453558] Floating (detached) Qt toolbar can't be dragged nor re-attached to window
https://bugs.kde.org/show_bug.cgi?id=453558 Bernie Innocenti changed: What|Removed |Added Version|5.91.0 |5.93.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 453558] Floating (detached) Qt toolbar can't be dragged nor re-attached to window
https://bugs.kde.org/show_bug.cgi?id=453558 --- Comment #1 from Bernie Innocenti --- I can also reproduce the bug on Arch Linux with everything built from sources (pre-5.26). (but not bumping to CONFIRMED because I'm the reporter) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 453558] New: Floating (detached) Qt toolbar can't be dragged nor re-attached to window
https://bugs.kde.org/show_bug.cgi?id=453558 Bug ID: 453558 Summary: Floating (detached) Qt toolbar can't be dragged nor re-attached to window Product: frameworks-kwayland Version: 5.91.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: client Assignee: mgraess...@kde.org Reporter: ber...@codewiz.org CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY I ran into this using Okular, but I believe the bug is not Okular specific. In a Plasma Wayland session, it is possible to drag a Qt toolbar outside the toolbar area, just like in X11. However, when the toolbar detaches and becomes floating, it is no longer possible to drag it or re-attach it to the docking area. I found this workaround: change the toolbar orientation to left or right to make dock again. Moreover, the detached state is saved and, upon restart, the floating toolbar is invisible (possibly a separate bug? There's a workaround for this too: toggle the toolbar visibility in the Settings menu and the toolbar will re-appear. STEPS TO REPRODUCE 1. Open any document in Okular. I used a JPEG image. 2. Right-click on any toolbar to open the context menu 3. Uncheck "Lock Toolbar Positions" 4. Grab a toolbar and drag it outside the docking area 5. Release the toolbar and try grabbing it again OBSERVED RESULT The toolbar can't be dragged any more! EXPECTED RESULT It should work just like in X11 SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3-1.fc36 ADDITIONAL INFORMATION This is Fedora 36 one week before the official release, but I don't think it matters. Not sure why Fedora 36 is releasing with KF5 5.91 instead of 5.93... THIS should matter. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #25 from Bernie Innocenti --- (In reply to Nate Graham from comment #23) > Indeed, it is likely that this is the same as Bug 449948, which says that > the issue is 100% reproducible if kwin_wayland has crashed and restarted > automatically, or was killed and restarted manually. > > Can everyone else confirm? Confirming: today kwin_wayland crashed, and after it restarted I immediately tried to logout and plasmashell froze for serveral seconds. I was using Fedora 36 with plasma-desktop-5.24.4-1.fc36.x86_64 (but possibly the session was started when I was still running 5.24.3). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450950] Discover installs older version of "Win7 Volume Mixer" instead of latest available
https://bugs.kde.org/show_bug.cgi?id=450950 Bernie Innocenti changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #3 from Bernie Innocenti --- (In reply to Nate Graham from comment #1) > Does the same thing happen if you download it from the "Add new widgets" > dialog that's accessed from the Widget Explorer sidebar? Not the same thing: the knewstuff dialog gives me an option to install either v25 or v26 (see screenshot on comment #2). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450950] Discover installs older version of "Win7 Volume Mixer" instead of latest available
https://bugs.kde.org/show_bug.cgi?id=450950 --- Comment #2 from Bernie Innocenti --- Created attachment 147647 --> https://bugs.kde.org/attachment.cgi?id=147647=edit knewstuff offering to download either v25 or v26 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 451088] Unknown Error on the Collaborative Services API (0)
https://bugs.kde.org/show_bug.cgi?id=451088 --- Comment #8 from Bernie Innocenti --- Created attachment 147645 --> https://bugs.kde.org/attachment.cgi?id=147645=edit screenshot for the plasma widgets explorer -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 451088] Unknown Error on the Collaborative Services API (0)
https://bugs.kde.org/show_bug.cgi?id=451088 Bernie Innocenti changed: What|Removed |Added Assignee|plasma-b...@kde.org |ad...@leinir.dk Component|kcm_icons |general Version|5.24.2 |5.91.0 Product|systemsettings |frameworks-knewstuff CC||alexander.loh...@gmx.de, ||ber...@codewiz.org, ||kdelibs-b...@kde.org --- Comment #7 from Bernie Innocenti --- It just happened to me as well upon opening the "Download New Plasma Widgets" explorer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439135] Color management on Wayland
https://bugs.kde.org/show_bug.cgi?id=439135 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 449948] After kwin_wayland crashes and restarts or is manually restarted, Reboot, shutdown and logout do not work due to ksmserver relying on XWayland which also died and did not come
https://bugs.kde.org/show_bug.cgi?id=449948 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #3 from Bernie Innocenti --- Could bug #448517 be related to this one? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #22 from Bernie Innocenti --- I wonder if there's any relation to bug #449948? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450950] New: Discover installs older version of "Win7 Volume Mixer" instead of latest available
https://bugs.kde.org/show_bug.cgi?id=450950 Bug ID: 450950 Summary: Discover installs older version of "Win7 Volume Mixer" instead of latest available Product: Discover Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KNewStuff Backend Assignee: lei...@leinir.dk Reporter: ber...@codewiz.org CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open plasma-discover 2. Search for "win7 volume" 3. Note how the version reported in the UI is "26, released on 01/12/2020" 3. Click Install 4. A new volume applet will appear in the System Tray 5. Right-click on it and select "Audio Volume Settings..." 6. In the settings dialog, go to About OBSERVED RESULT "Audio Volume (Win7 Mixer) 25" .local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/metadata.desktop also contains "X-KDE-PluginInfo-Version=26" EXPECTED RESULT Version 26 should have been installed. If you download volumewin7mixer-v26-plasma5.12.plasmoid from https://store.kde.org/p/1100894/ and unzip it in the right place, you'll get version 26. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.80 (git) KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 + kde -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450949] New: Discover crashed in KNSBackend while uninstalling a plasma widget
https://bugs.kde.org/show_bug.cgi?id=450949
Bug ID: 450949
Summary: Discover crashed in KNSBackend while uninstalling a
plasma widget
Product: Discover
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: discover
Assignee: lei...@leinir.dk
Reporter: ber...@codewiz.org
CC: aleix...@kde.org
Target Milestone: ---
Application: plasma-discover (5.24.80)
(Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.16.11-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.24.80 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
1. Open plasma-discover from a terminal
2. Search for "win7 volume" (previously installed in a separate Discover
instance)
3. Click on the installed result
4. Click "Remove"
5. Discover crashes as shown in the stack trace
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#5 0x7fd738e7b34c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#6 0x7fd738e2e4b8 in raise () at /usr/lib/libc.so.6
#7 0x7fd738e18534 in abort () at /usr/lib/libc.so.6
#8 0x7fd7393beee4 in qt_assert(char const*, char const*, int) () at
/usr/lib/libQt5Core.so.5
#9 0x7fd7393bef44 in qt_assert_x(char const*, char const*, char const*,
int) () at /usr/lib/libQt5Core.so.5
#10 0x7fd7057d6ad0 in KNSBackend::setResponsePending(bool)
(this=0x5619cf0d86a0, pending=false) at
/home/bernie/kde/src/discover/libdiscover/backends/KNSBackend/KNSBackend.cpp:240
#11 0x7fd7057d8c6e in operator()() const (__closure=0x5619d00fba40) at
/home/bernie/kde/src/discover/libdiscover/backends/KNSBackend/KNSBackend.cpp:724
#12 0x7fd7057dc6e5 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, KNSBackend::findResourceByPackageName(const
QUrl&):: >::call(struct {...} &, void
**) (f=..., arg=0x5619d140bac8) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#13 0x7fd7057dc261 in
QtPrivate::Functor, 0>::call,
void>(struct {...} &, void *, void **) (f=..., arg=0x5619d140bac8) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#14 0x7fd7057dbec0 in
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=1, this_=0x5619d00fba30, r=0x5619cf0d86a0, a=0x5619d140bac8, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#15 0x7fd7395cfdc6 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#16 0x7fd73a9a31a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#17 0x7fd7395abb9a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#18 0x7fd7395ac699 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#19 0x7fd7395f3bd8 in () at /usr/lib/libQt5Core.so.5
#20 0x7fd737e70ee3 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#21 0x7fd737ec70f9 in () at /usr/lib/libglib-2.0.so.0
#22 0x7fd737e6e455 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#23 0x7fd7395f7ada in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#24 0x7fd7395a3e6b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#25 0x7fd7395af5c7 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#26 0x5619cd9abee7 in main(int, char**) (argc=1, argv=0x7ffc55a1ed38) at
/home/bernie/kde/src/discover/discover/main.cpp:217
[Inferior 1 (process 5835) detached]
Possible duplicates by query: bug 445052, bug 419428, bug 330999, bug 330615,
bug 330486.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 425265] Discover shows error messages and gets stuck in "installing" state after I cancel update of SDDM theme from KDE Store
https://bugs.kde.org/show_bug.cgi?id=425265 --- Comment #2 from Bernie Innocenti --- Related bugs: #450948 and #413516 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413516] There's no API for cancelling installation of KNS assets
https://bugs.kde.org/show_bug.cgi?id=413516 --- Comment #2 from Bernie Innocenti --- Related bugs: #450948 and #425265 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450948] New: No installable candidates in the KNewStuff entry "..." with id "..." on the backend "plasmoids.knsrc"
https://bugs.kde.org/show_bug.cgi?id=450948 Bug ID: 450948 Summary: No installable candidates in the KNewStuff entry "..." with id "..." on the backend "plasmoids.knsrc" Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KNewStuff Backend Assignee: lei...@leinir.dk Reporter: ber...@codewiz.org CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover finds the "Win7 Volume Mixer" plasmoid, but is unable to install it. The installation gets stuck as described in bug #413516 and bug #425265. STEPS TO REPRODUCE 1. Run plasma-discover from a terminal and search for "win7 volume" 2. Click Install 3. (I think I uninstalled and re-installed a second time, but not so sure) Discover will print this on stdout: No installable candidates in the KNewStuff entry "Win7 Volume Mixer" with id "1100894" on the backend "plasmoids.knsrc" There should always be at least one downloadable item in an OCS entry, and if there isn't, we should consider it broken. OCS can technically show them, but if there is nothing to install, it cannot be installed. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.80 (git) KDE Frameworks Version: 5.92.0 (git) Qt Version: 5.15.2 + kde (ArchLinux) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 425265] Discover shows error messages and gets stuck in "installing" state after I cancel update of SDDM theme from KDE Store
https://bugs.kde.org/show_bug.cgi?id=425265 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org Status|REPORTED|CONFIRMED Component|discover|KNewStuff Backend Ever confirmed|0 |1 --- Comment #1 from Bernie Innocenti --- This seems to be a KNewStuff backend bug. It just happened to me with Discover and KF built from git master today. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413516] There's no API for cancelling installation of KNS assets
https://bugs.kde.org/show_bug.cgi?id=413516 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #1 from Bernie Innocenti --- The UI has changed in Discover 5.24.80, but the problem remains: an addon failed to install, and the corresponding task hung with no way to cancel it. I'll file a separate bug for the installation failing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 427739] Panel and Plasma are unresponsive when establishing connection to WiFi / VPN
https://bugs.kde.org/show_bug.cgi?id=427739 --- Comment #4 from Bernie Innocenti --- I filed this upstream NetworkManager bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/934 I feel that plasmashell also shouldn't block the whole UI while waiting for a reply from NetworkManager -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #20 from Bernie Innocenti --- I'm running Fedora 36 with Plasma 5.24.0 and I just installed the updates to 5.24.1. I was going to restart the session to start using the updated desktop components, but I hit this bug again. ksmserver was indeed dead, exactly as described in comment #19. I restarted it (systemctl --user restart plasma-ksmserver.service), but it did not cure the problem: the menu still freezes when I select Restart. -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 415927] Impossible to pick a screen color on Wayland
https://bugs.kde.org/show_bug.cgi?id=415927 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 389935] Kcolorchooser doesn't work in wayland
https://bugs.kde.org/show_bug.cgi?id=389935 Bernie Innocenti changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #8 from Bernie Innocenti --- Upstream Qt bug: https://bugreports.qt.io/browse/QTBUG-81538 Closing as duplicate of bug #415927 *** This bug has been marked as a duplicate of bug 415927 *** -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 415927] Impossible to pick a screen color on Wayland
https://bugs.kde.org/show_bug.cgi?id=415927 Bernie Innocenti changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #4 from Bernie Innocenti --- *** Bug 389935 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 389935] Kcolorchooser doesn't work in wayland
https://bugs.kde.org/show_bug.cgi?id=389935 --- Comment #7 from Bernie Innocenti --- Ok, this is just QColorDialog, and the color picker is still broken in Qt 6.2.3, as can be seen by running this example app: /usr/lib64/qt6/examples/widgets/dialogs/standarddialogs/standarddialogs) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 389935] Kcolorchooser doesn't work in wayland
https://bugs.kde.org/show_bug.cgi?id=389935 Bernie Innocenti changed: What|Removed |Added Product|kcolorchooser |frameworks-kdelibs4support Version|unspecified |5.91.0 Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 389935] Kcolorchooser doesn't work in wayland
https://bugs.kde.org/show_bug.cgi?id=389935 Bernie Innocenti changed: What|Removed |Added Platform|Neon Packages |Fedora RPMs CC||ber...@codewiz.org Product|frameworks-kdelibs4support |kcolorchooser Component|general |general Version|5.87.0 |unspecified Assignee|kdelibs-b...@kde.org|unassigned-b...@kde.org --- Comment #6 from Bernie Innocenti --- Bug still present with KF 5.91.0... but is this dialog part of kdelibs4support or is it QColorDialog in Qt5? Also, in Wayland you can send the color chooser dialog behind its parent window by clicking outside of it (leaving novice users wondering where the dialog went). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 450595] File list rendering glitches when scrolling / hovering
https://bugs.kde.org/show_bug.cgi?id=450595 --- Comment #1 from Bernie Innocenti --- Created attachment 146956 --> https://bugs.kde.org/attachment.cgi?id=146956=edit file dialog with rendering issues -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 450595] New: File list rendering glitches when scrolling / hovering
https://bugs.kde.org/show_bug.cgi?id=450595 Bug ID: 450595 Summary: File list rendering glitches when scrolling / hovering Product: frameworks-kio Version: 5.91.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: ber...@codewiz.org CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Some file dialogs (e.g. systemsettings > Connections > Import VPN, but *not* konsole > File > Save Output As...) have rendering glitches while scrolling the file list or hovering with the mouse. Happens on 2 different machines with different distros (Fedora 36 vs Arch Linux) and different GPUs (Intel vs AMD). Both use Breeze Dark and have similar style configuration. STEPS TO REPRODUCE 1. Open the connections kcm (either from SystemSettings or from the panel applet 2. Click Add New Connection 3. Click "Import VPN connection..." at the bottom 4. To trigger the bug, scroll up and down, hover on the list, go to a directory with many files OBSERVED RESULT See attached screenshot SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 (qt5-qtbase-5.15.2-33.fc36.x86_64) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368723] cursor size not respected on X11 window borders
https://bugs.kde.org/show_bug.cgi?id=368723 Bernie Innocenti changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #12 from Bernie Innocenti --- I just tried this in Plasma Wayland 5.24: 1. Open System Settings / Appearance / Cursors 2. Change the cursor size (I changed it from 36 to 24) 3. Click apply 4. The cursor size does not change while the cursor is within the System Settings window 5. The cursor changes to the expected size when hovering over the window borders 6. Closing and re-opening System Settings does NOT change the cursor size in the window 7. XWayland clients behave exactly the same (the cursor size inside the window doesn't change, but gets smaller/larger in the borders) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434968] With Touch Screen gestures enabled, snap-to-border halo stays visible after dropping a window near a screen border
https://bugs.kde.org/show_bug.cgi?id=434968 Bernie Innocenti changed: What|Removed |Added Version|5.23.5 |5.24.0 Platform|Other |Fedora RPMs Summary|With Wobbly Windows |With Touch Screen gestures |enabled, snap-to-border |enabled, snap-to-border |halo effect remains visible |halo stays visible after |after dropping a window |dropping a window near a |close to a screen border|screen border --- Comment #14 from Bernie Innocenti --- I apologize for blaming Wobbly Windows, I was confused by the different behaviors observed on my laptop and my PC. Steps to reproduce the bug on both my Plasma 5.24 desktops: 1. Go to Workspace Behavior / Touch Screen and set the top border gesture to "Show Destop" (you don't actually need a touch screen to do this) 2. Go to Workspace Behavior / Screen Edges and set "Switch desktop on edge" to "Only When Moving Windows" 3. Grab a Qt window and move it close to the top border until the top border's halo appears (doesn't work with Chromium and Signal Deskop) 4. Release the window 5. The halo remains visible. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 449728] Battery "plugged in but still discharging" message while not plugged in
https://bugs.kde.org/show_bug.cgi?id=449728 --- Comment #1 from Bernie Innocenti --- Created attachment 146373 --> https://bugs.kde.org/attachment.cgi?id=146373=edit Screenshot of Battery in Device Viewer -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 449728] New: Battery "plugged in but still discharging" message while not plugged in
https://bugs.kde.org/show_bug.cgi?id=449728 Bug ID: 449728 Summary: Battery "plugged in but still discharging" message while not plugged in Product: Powerdevil Version: 5.23.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ber...@codewiz.org Target Milestone: --- Created attachment 146371 --> https://bugs.kde.org/attachment.cgi?id=146371=edit Screenshot SUMMARY See screenshot. This happened 3-4 times on my Thinkpad X1 Gen 7, but I still haven't figured how to reproduce it. The laptop is unplugged and discharging, but the battery monitor applet thinks it's plugged. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.90 KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 This is Fedora Rawhide, but I'm almost certain I have seen this bug also when I was still running Fedora 35 with Plasma 5.23.5. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Bernie Innocenti changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #13 from Bernie Innocenti --- (In reply to Nate Graham from comment #12) > Interesting. If you get it out of that state (e.g. by killing and restarting > plasmashell) does the hang-on-logout issue still happen? If not, then it may > be a separate issue. It just happened to me again in Fedora Rawhide. Killing and restarting plasmashell doesn't fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #11 from Bernie Innocenti --- It just happened to me again with plasmashell from plasma-workspace-5.23.90-2.fc36.x86_64. Just before this, I did "something" that made the panel miss some button release event, and the task bar was constantly dragging around the apps while moving the mouse over it. The application menu would open with the Super key, but then would not respond to clicks or keyboard input. After some fiddling, I managed to get out of this state, but now clicking logout freezes the panel with the application menu open for 10 seconds. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434968] With Wobbly Windows enabled, snap-to-border halo effect remains visible after dropping a window close to a screen border
https://bugs.kde.org/show_bug.cgi?id=434968 --- Comment #12 from Bernie Innocenti --- Did someone just fix it? I can no longer reproduce this on my desktop, which runs KDE built from git. Still present in Fedora Rawhide, which runs 5.23.90 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #7 from Bernie Innocenti --- I captured the the journal just before a plasmashell crash: ---cut--- trying to show an empty dialog qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.svg: :303:258: Could not add child element to parent element because the types are incorrect. qt.svg: :303:463: Could not add child element to parent element because the types are incorrect. qt.svg: :303:659: Could not add child element to parent element because the types are incorrect. qt.svg: :303:913: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1049: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1251: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1453: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1631: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1739: Could not add child element to parent element because the types are incorrect. qt.svg: :303:1980: Could not add child element to parent element because the types are incorrect. qt.svg: :303:2223: Could not add child element to parent element because the types are incorrect. QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection The Wayland connection broke. Did the Wayland compositor die? ---cut--- No, kwin_wayland did not die. This is not a crash, it's a clean exit with $?=1 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 --- Comment #6 from Bernie Innocenti --- Created attachment 145783 --> https://bugs.kde.org/attachment.cgi?id=145783=edit Plasmashell freezing when you click Logout. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 448517] Logout/shutdown/restart in wayland session sometimes freezes the UI you used to trigger it and then doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=448517 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #5 from Bernie Innocenti --- I think I'm hitting this same bug in Fedora Rawhide (plasmashell 5.23.90, sddm 0.19.0). Attaching a screenshot which shows the frozen application menu. In most cases, the shell recovers after about 10 seconds. I've also seen it crash in a couple of cases, but I wasn't able to attach gdb nor get a stacktrace. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 434976] [PipeWire] Switching to internal speaker impossible after unplugging default output
https://bugs.kde.org/show_bug.cgi?id=434976 --- Comment #6 from Bernie Innocenti --- (In reply to Nicolas Fella from comment #5) > Please report this to Pipewire. Plasma is not involved in determining where > audio should play, except for the case where the user explicitly moves a > stream. But even then it should be PipeWire's responsibility to ensure that > the stream is switched away once the device becomes unavailable > > > However maybe there's something we can do in this case anyway. > > I really really don't want Plasma to do any kind of "Business logic" about > what should happen in such cases. It would only lead to conflicts, chaos, > and confusion with PipeWire's builtin handling I understand and strongly agree: putting policy and bug workarounds in the UI layer would be the wrong solution. The behavior changed slightly in the current Fedora Rawhide (pipewire-0.3.43 + plasma-pa-5.23-90): 1. Connect a laptop to an external HDMI monitor 2. Switch sound to the HDMI output using the radio buttons of the Audio Volume applet's menu 3. Unplug the HDMI monitor 4. As previously reported, the sound does not automatically switch back to the laptop's internal speakers 5. Open the Audio Volume menu by clicking on the icon 6. The sound immediately returns to the speakers (no need to interact with the controls) So it looks like plasma-pa *is* doing something to switch the sound output... it just doesn't do it when pipewire sends the unplug event. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448150] Battery applet shown in system tray even if there are no batteries
https://bugs.kde.org/show_bug.cgi?id=448150 --- Comment #4 from Bernie Innocenti --- (In reply to Nate Graham from comment #1) > That's expected; as of Bug 415073 it should still appear as long as there > are any brightness controls in it. Is that the case for your system? No, there are no brightness controls. This is a regular desktop with a regular display hooked to a DisplayPort connector of an AMD GPU card. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448150] Battery applet shown in system tray even if there are no batteries
https://bugs.kde.org/show_bug.cgi?id=448150 --- Comment #3 from Bernie Innocenti --- Created attachment 145741 --> https://bugs.kde.org/attachment.cgi?id=145741=edit Empty Battery and Brightness popup -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448150] Battery applet shown in system tray even if there are no batteries
https://bugs.kde.org/show_bug.cgi?id=448150 --- Comment #2 from Bernie Innocenti --- Created attachment 145740 --> https://bugs.kde.org/attachment.cgi?id=145740=edit battery applet icon with "X" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434968] With Wobbly Windows enabled, snap-to-border halo effect remains visible after dropping a window close to a screen border
https://bugs.kde.org/show_bug.cgi?id=434968 Bernie Innocenti changed: What|Removed |Added Version|5.21.4 |5.23.5 Version Fixed In|5.22| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434968] With Wobbly Windows enabled, snap-to-border halo effect remains visible after dropping a window close to a screen border
https://bugs.kde.org/show_bug.cgi?id=434968 Bernie Innocenti changed: What|Removed |Added Resolution|FIXED |--- Summary|Snap-to-border halo effect |With Wobbly Windows |remains visible after |enabled, snap-to-border |dropping a window close to |halo effect remains visible |a screen border |after dropping a window ||close to a screen border Status|RESOLVED|REOPENED --- Comment #11 from Bernie Innocenti --- AHA! I can reproduce it again now: it happens only when the Wobbly Windows effect is enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448150] New: Battery applet shown in system tray even if there are no batteries
https://bugs.kde.org/show_bug.cgi?id=448150 Bug ID: 448150 Summary: Battery applet shown in system tray even if there are no batteries Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: ber...@codewiz.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 145255 --> https://bugs.kde.org/attachment.cgi?id=145255=edit System Tray Settings I'm using Plasma built from sources, but this has been happening also when using with the Arch Linux packages for a long time (at least 2 years). KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 + kde -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443706] Crash notification after restarting plasmashell process manually on Wayland
https://bugs.kde.org/show_bug.cgi?id=443706 Bernie Innocenti changed: What|Removed |Added Ever confirmed|0 |1 CC||ber...@codewiz.org Status|REPORTED|CONFIRMED --- Comment #4 from Bernie Innocenti --- Still happening in plasmashell 5.24.4 (Fedora Rawhide). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 446830] Konsole crashes when splitting a window
https://bugs.kde.org/show_bug.cgi?id=446830
--- Comment #2 from Bernie Innocenti ---
#4 0x77d2a7ef in Konsole::ViewManager::splitView (this=0x55827c20,
orientation=Qt::Horizontal)
at /home/bernie/kde/src/konsole/src/ViewManager.cpp:603
603 Q_ASSERT(currentSessionId >= 0);
(gdb) list
598
599 void ViewManager::splitView(Qt::Orientation orientation)
600 {
601 int currentSessionId = currentSession();
602 // At least one display/session exists if we are splitting
603 Q_ASSERT(currentSessionId >= 0);
604
605 Session *activeSession =
SessionManager::instance()->idToSession(currentSessionId);
606 Q_ASSERT(activeSession);
607
(gdb) p currentSessionId
$1 = -1
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 446830] Konsole crashes when splitting a window
https://bugs.kde.org/show_bug.cgi?id=446830 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Bernie Innocenti --- I was able to reproduce this with konsole built from git master: (gdb) r Starting program: /home/bernie/kde/usr/bin/konsole [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffefefc640 (LWP 226434)] QIBusPlatformInputContext: invalid portal bus. QSocketNotifier: Can only be used with threads started with QThread [New Thread 0x7fffe17d1640 (LWP 226436)] [New Thread 0x7fffe0fd0640 (LWP 226437)] [New Thread 0x7fffdbfff640 (LWP 226438)] [New Thread 0x7fffdb7fe640 (LWP 226439)] [New Thread 0x7fffdaffd640 (LWP 226440)] [New Thread 0x7fffda7fc640 (LWP 226441)] [New Thread 0x7fffd9ffb640 (LWP 226442)] [New Thread 0x7fffd97fa640 (LWP 226443)] [New Thread 0x7fffd8ff9640 (LWP 226444)] [Detaching after fork from child process 226445] [New Thread 0x7fffabc95640 (LWP 226467)] [Detaching after fork from child process 226468] [Detaching after fork from child process 226470] [Detaching after fork from child process 226472] [Detaching after fork from child process 226474] [Detaching after fork from child process 226476] [Detaching after fork from child process 226478] QIBusPlatformInputContext: invalid portal bus. QSocketNotifier: Can only be used with threads started with QThread [Detaching after fork from child process 226492] [Detaching after fork from child process 226494] [Detaching after fork from child process 226496] [Detaching after fork from child process 226499] [Detaching after fork from child process 226501] [Detaching after fork from child process 226544] [Detaching after fork from child process 226545] qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x55c37360) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x56289160) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents ASSERT: "currentSessionId >= 0" in file /home/bernie/kde/src/konsole/src/ViewManager.cpp, line 603 Thread 1 "konsole" received signal SIGABRT, Aborted. 0x74bd9d22 in raise () from /usr/lib/libc.so.6 (gdb) bt #0 0x74bd9d22 in raise () from /usr/lib/libc.so.6 #1 0x74bc3862 in abort () from /usr/lib/libc.so.6 #2 0x7516e910 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #3 0x7516dcf5 in qt_assert(char const*, char const*, int) () from /usr/lib/libQt5Core.so.5 #4 0x77d2a7ef in Konsole::ViewManager::splitView (this=0x55827c20, orientation=Qt::Horizontal) at /home/bernie/kde/src/konsole/src/ViewManager.cpp:603 #5 0x77d2a77b in Konsole::ViewManager::splitLeftRight (this=0x55827c20) at /home/bernie/kde/src/konsole/src/ViewManager.cpp:591 #6 0x77d38176 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (Konsole::ViewManager::*)()>::call(void (Konsole::ViewManager::*)(), Konsole::ViewManager*, void**) ( f=(void (Konsole::ViewManager::*)(Konsole::ViewManager * const)) 0x77d2a75e , o=0x55827c20, arg=0x7fffc8b0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152 #7 0x77d375c0 in QtPrivate::FunctionPointer::call, void>(void (Konsole::ViewManager::*)(), Konsole::ViewManager*, void**) (f=(void (Konsole::ViewManager::*)(Konsole::ViewManager * const)) 0x77d2a75e , o=0x55827c20, arg=0x7fffc8b0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185 #8 0x77d3617d in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x55831810, r=0x55827c20, a=0x7fffc8b0, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:418 #9 0x753ce7cb in ?? () from /usr/lib/libQt5Core.so.5 #10 0x760a4203 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #11 0x760a6f18 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #12 0x76234103 in ?? () from /usr/lib/libQt5Widgets.so.5 #13 0x7623be39 in ?? () from /usr/lib/libQt5Widgets.so.5 #14 0x760ee0be in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x760aad62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x760b2ac9 in QApplication::notify(QObject*,
[konsole] [Bug 442371] Split-View windows can vanish
https://bugs.kde.org/show_bug.cgi?id=442371 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #2 from Bernie Innocenti --- Reproduced on konsole built from git master. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446501] All flatpaks returned as results when searching installed packages
https://bugs.kde.org/show_bug.cgi?id=446501 --- Comment #4 from Bernie Innocenti --- > Hmm, I tried reproducing this bug, and I hit another error: Could you re-run plasma-discover under gdb and get a stack trace? Is the plasma-discover-flatpak package installed? Any other backends? This is what's installed on my Rawhide system: plasma-discover-libs-5.23.3.1-1.fc36.x86_64 plasma-discover-flatpak-5.23.3.1-1.fc36.x86_64 plasma-discover-5.23.3.1-1.fc36.x86_64 plasma-discover-notifier-5.23.3.1-1.fc36.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp
https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #10 from Bernie Innocenti --- Just to be clear: I could 100% reproduce the crash in baloo_file with these directory operations in my home: cd ~ mkdir foo <- CRASH! mv foo bar <- CRASH! chmod -x bar <- CRASH! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp
https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #8 from Bernie Innocenti --- On a tangential note, why didn't the autotests catch this regression? -- You are receiving this mail because: You are watching all bug changes.
