[kontact] [Bug 472719] New: KMail/Kontact crashes when trying to send a mail
https://bugs.kde.org/show_bug.cgi?id=472719 Bug ID: 472719 Summary: KMail/Kontact crashes when trying to send a mail Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dzilte...@lyrion.ch Target Milestone: --- Application: kontact (5.23.3 (23.04.3)) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.4-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: KMail crashes reliably (and takes Kontact with it) when I try to send a mail by using the normal "Send" button. It works, however, when I longpress the "Send" button and choose a sending account. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7fa72f40c45b in () at /lib64/libQt5WaylandClient.so.5 #5 0x7fa72bf49962 in () at /lib64/libffi.so.8 #6 0x7fa72bf462df in () at /lib64/libffi.so.8 #7 0x7fa72bf48f26 in ffi_call () at /lib64/libffi.so.8 #8 0x7fa72fce2a23 in () at /lib64/libwayland-client.so.0 #9 0x7fa72fce3203 in () at /lib64/libwayland-client.so.0 #10 0x7fa72fce3494 in wl_display_dispatch_queue_pending () at /lib64/libwayland-client.so.0 #11 0x7fa72f40ca12 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib64/libQt5WaylandClient.so.5 #12 0x7fa739d25743 in () at /lib64/libQt5Core.so.5 #13 0x7fa739d464c5 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #14 0x7fa739cebf8b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #15 0x7fa73af77475 in KJob::exec() () at /lib64/libKF5CoreAddons.so.5 #16 0x7fa6a693aa1e in Kleo::KeyResolver::lookupContactPreferences(QString const&) const () at /lib64/libKPim5MessageComposer.so.5 #17 0x7fa6a693273b in Kleo::KeyResolver::getEncryptionItems(QStringList const&) () at /lib64/libKPim5MessageComposer.so.5 #18 0x7fa6a6932f3b in Kleo::KeyResolver::setPrimaryRecipients(QStringList const&) () at /lib64/libKPim5MessageComposer.so.5 #19 0x7fa6a6922c3a in MessageComposer::ComposerViewBase::generateCryptoMessages(bool&) () at /lib64/libKPim5MessageComposer.so.5 #20 0x7fa6a6923dc7 in MessageComposer::ComposerViewBase::slotEmailAddressResolved(KJob*) () at /lib64/libKPim5MessageComposer.so.5 #21 0x7fa739d257a2 in () at /lib64/libQt5Core.so.5 #22 0x7fa73af6f845 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #23 0x7fa73af73beb in () at /lib64/libKF5CoreAddons.so.5 #24 0x7fa6a6911900 in MessageComposer::EmailAddressResolveJob::start() () at /lib64/libKPim5MessageComposer.so.5 #25 0x7fa6a692186c in MessageComposer::ComposerViewBase::readyForSending() () at /lib64/libKPim5MessageComposer.so.5 #26 0x7fa6a6921c0e in MessageComposer::ComposerViewBase::send(MessageComposer::MessageSender::SendMethod, MessageComposer::MessageSender::SaveIn, bool) () at /lib64/libKPim5MessageComposer.so.5 #27 0x7fa6a6f7064b in () at /lib64/libkmailprivate.so.5 #28 0x7fa739d257a2 in () at /lib64/libQt5Core.so.5 #29 0x7fa73af6f845 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #30 0x7fa73af73beb in () at /lib64/libKF5CoreAddons.so.5 #31 0x7fa6a6f82fcb in () at /lib64/libkmailprivate.so.5 #32 0x7fa739d257a2 in () at /lib64/libQt5Core.so.5 #33 0x7fa73af6f845 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #34 0x7fa73af73beb in () at /lib64/libKF5CoreAddons.so.5 #35 0x7fa6a6f73235 in () at /lib64/libkmailprivate.so.5 #36 0x7fa739d257a2 in () at /lib64/libQt5Core.so.5 #37 0x7fa6a6f74ecb in () at /lib64/libkmailprivate.so.5 #38 0x7fa739d257a2 in () at /lib64/libQt5Core.so.5 #39 0x7fa73a99e8b2 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #40 0x7fa73a9a142f in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #41 0x7fa73aa9862a in () at /lib64/libQt5Widgets.so.5 #42 0x7fa73aa98777 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #43 0x7fa73ab9102a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #44 0x7fa73a9e6d68 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #45 0x7fa73a9a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #46 0x7fa73a9ad5cf in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #47 0x7fa739ced4f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #48 0x7fa73a9ab92e in QApplicationPriva
[kwin] [Bug 472357] New: On multi-monitor setups, the bigger monitor randomly starts glitching and flickering with artifacts
https://bugs.kde.org/show_bug.cgi?id=472357 Bug ID: 472357 Summary: On multi-monitor setups, the bigger monitor randomly starts glitching and flickering with artifacts Classification: Plasma Product: kwin Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dzilte...@lyrion.ch Target Milestone: --- Created attachment 160359 --> https://bugs.kde.org/attachment.cgi?id=160359&action=edit A screenshot of the issue Since as long as I am trying Plasma Wayland on a multi monitor setup, the background, and sometimes also part of the control panel, break after a while. It seems what keeps working is a rectangle of about the size of the smaller monitor. The rest "loses" rendering, and dragging a window over it etc. causes it to flicker wildly with artifacts of whatever moved over it. The screenshot shows both screens as recorded by Spectacle. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 Daniel Ziltener changed: What|Removed |Added CC||dzilte...@lyrion.ch Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #38 from Daniel Ziltener --- Is anyone interested in baking a cake or throwing a party for this bug's upcoming 9th or 10th birthday? It spent its entire life without a caretaker, and I am sure it would enjoy spending some time with friendly people. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 470977] New: Neochat crashes on startup
https://bugs.kde.org/show_bug.cgi?id=470977 Bug ID: 470977 Summary: Neochat crashes on startup Classification: Applications Product: NeoChat Version: 23.04.2 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: zi...@lyrion.ch CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (23.04.2) Qt Version: 5.15.9 Frameworks Version: 5.107.0 Operating System: Linux 5.14.21-150500.53-default x86_64 Windowing System: Wayland Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: It fails reliably on every startup. Here is the console output it gives me: ``` Reading access token from the keychain for "@zilti:matrix.org" quotient.e2ee: End-to-end encryption (E2EE) support is turned off. quotient.main: No state cache file "/home/zilti/.cache/KDE/neochat/@zilti_matrix.org/state.json" quotient.main: Major version of the cache file is 0 but 11 is required; discarding the cache quotient.jobs.sync: Sent GET https://matrix-client.matrix.org/_matrix/client/r0/sync quotient.jobs: Sent GET https://matrix-client.matrix.org/_matrix/client/r0/capabilities quotient.jobs.sync: 200 <- GET https://matrix-client.matrix.org/_matrix/client/r0/sync KCrash: Application 'neochat' crashing... KCrash: Attempting to start /usr/lib/drkonqi kf5idletime_wayland: This plugin does not support polling idle time ``` The crash can be reproduced every time. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x7fe2314fcdd6 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fe2314fd76d in QJsonObject::value(QLatin1String) const () from /usr/lib64/libQt5Core.so.5 #6 0x7fe23302e0a4 in Quotient::RoomEvent::senderId() const () from /usr/lib64/libQuotient.so.0.6 #7 0x55b8a06ca979 in ?? () #8 0x55b8a06cac8c in ?? () #9 0x7fe23300514c in Quotient::Room::Private::addNewMessageEvents(std::vector >, std::allocator > > >&&) () from /usr/lib64/libQuotient.so.0.6 #10 0x7fe2330059f6 in Quotient::Room::updateData(Quotient::SyncRoomData&&, bool) () from /usr/lib64/libQuotient.so.0.6 #11 0x7fe232fdcef0 in Quotient::Connection::Private::consumeRoomData(std::vector >&&, bool) () from /usr/lib64/libQuotient.so.0.6 #12 0x7fe232fdd0ba in Quotient::Connection::onSyncSuccess(Quotient::SyncData&&, bool) () from /usr/lib64/libQuotient.so.0.6 #13 0x7fe232fdd160 in ?? () from /usr/lib64/libQuotient.so.0.6 #14 0x7fe2314b1b9b in ?? () from /usr/lib64/libQt5Core.so.5 #15 0x7fe232fbfa82 in Quotient::BaseJob::success(Quotient::BaseJob*) () from /usr/lib64/libQuotient.so.0.6 #16 0x7fe233042aa3 in Quotient::BaseJob::finishJob() () from /usr/lib64/libQuotient.so.0.6 #17 0x7fe2314b1b9b in ?? () from /usr/lib64/libQt5Core.so.5 #18 0x7fe23286ac17 in ?? () from /usr/lib64/libQt5Network.so.5 #19 0x7fe232906b99 in ?? () from /usr/lib64/libQt5Network.so.5 #20 0x7fe2314a863b in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #21 0x7fe2320e053c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #22 0x7fe2320e72ff in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7fe2314741a3 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #24 0x7fe231476bc1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #25 0x7fe2314d7443 in ?? () from /usr/lib64/libQt5Core.so.5 #26 0x7fe23024582b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x7fe230245bd0 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x7fe230245c5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x7fe2314d6aec in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #30 0x7fe231472a0a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #31 0x7fe23147c247 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #32 0x55b8a05aac88 in main () [Inferior 1 (process 11757) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 435232] KOrganizer automatically add slash (/) in the final of the URL and don't import correctly
https://bugs.kde.org/show_bug.cgi?id=435232 Daniel Ziltener changed: What|Removed |Added CC||zi...@lyrion.ch -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462713] New: [Wayland] Misaligned quick info and hamburger menu on multi-screen setup with a scaled screen
https://bugs.kde.org/show_bug.cgi?id=462713 Bug ID: 462713 Summary: [Wayland] Misaligned quick info and hamburger menu on multi-screen setup with a scaled screen Classification: Applications Product: dolphin Version: 22.11.90 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: zi...@lyrion.ch CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When using Dolphin under a dual-screen Wayland setup where one of the screens is scaled to 125%, I noticed some weird placements of the burger menu and the "quick info" tooltips. The burger menu is on both screens placed too far down (about 150 pixels I'd estimate) and centered below the button; and the "quick info" is correctly(?) centered below the item on the 125% screen but several hundred pixels moved to the right on the 100% screen. My screen setup: Built-in laptop screen 1920x1080@125% on the left, 3440x1440 on the right and set as primary. I am not really sure what (if any) additional information etc. you need to investigate and/or fix this. Let me know if I can be of further assistance, run some tests, etc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 447683] Cannot fetch CalDAV calendar events
https://bugs.kde.org/show_bug.cgi?id=447683 Daniel Ziltener changed: What|Removed |Added Ever confirmed|0 |1 CC||zi...@lyrion.ch Status|REPORTED|CONFIRMED --- Comment #2 from Daniel Ziltener --- Can confirm. This bug has been around since 2013, and nobody cares... Honestly, it's best to just dump Kontact and use Thunderbird instead at this point. Kontact is dead. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 341067] Events from caldav resource do not appear in Korganizer
https://bugs.kde.org/show_bug.cgi?id=341067 Daniel Ziltener changed: What|Removed |Added Status|REOPENED|CONFIRMED CC||zi...@lyrion.ch --- Comment #12 from Daniel Ziltener --- I can confirm this on OpenSUSE Tumbleweed, KOrganizer 22.04.2, with Zoho in this case. I can add events in KOrganizer, and they will get uploaded and appear on other devices. But events created on other devices will never show up in KOrganizer. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 454051] New: After setting a trash folder, kmail always crashes until removing the local mailbox in akonadiconsole.
https://bugs.kde.org/show_bug.cgi?id=454051 Bug ID: 454051 Summary: After setting a trash folder, kmail always crashes until removing the local mailbox in akonadiconsole. Product: kmail2 Version: 5.20.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: zi...@lyrion.ch Target Milestone: --- Created attachment 149003 --> https://bugs.kde.org/attachment.cgi?id=149003&action=edit Crash log This bug has been around for about a decade now, I'm not sure there is anything to say about it anymore. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446369] New: Trying to update a Flatpak always crashes Discover
https://bugs.kde.org/show_bug.cgi?id=446369 Bug ID: 446369 Summary: Trying to update a Flatpak always crashes Discover Product: Discover Version: 5.23.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: zi...@lyrion.ch CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- SUMMARY Trying to update one or more Flatpak applications crashes Discover. One of them will be updated, nonetheless, and on the next launch the remaining ones are still there to update. STEPS TO REPRODUCE 1. Open Discover 2. Go to the updates section 3. Click "Update" OBSERVED RESULT Discover updates one Flatpak, then crashes. EXPECTED RESULT Discover updates all Flatpaks and all other packages without crashing. Linux/KDE Plasma: 5.15.5-1 default (64-bit) (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The KDE crash assistant made a debug trace, but it discarded it when I chose to report the issue. So I don't have a trace to provide for now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440118] Adding collections is not adding any images
https://bugs.kde.org/show_bug.cgi?id=440118 --- Comment #1 from Daniel Ziltener --- As I noticed, it does show videos - but only videos. No .png, no .jpg, and no .raw photos. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440118] New: Adding collections is not adding any images
https://bugs.kde.org/show_bug.cgi?id=440118 Bug ID: 440118 Summary: Adding collections is not adding any images Product: digikam Version: 7.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Setup-Collections Assignee: digikam-bugs-n...@kde.org Reporter: zi...@lyrion.ch Target Milestone: --- SUMMARY Adding a collection adds the albums (folders), but they appear all empty in digiKam. STEPS TO REPRODUCE 1. Start digiKam 2. Add a collection 3. See result OBSERVED RESULT The folders get added, but they all appear empty (no photos are showing) EXPECTED RESULT The folders get added, and the photos are all listed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.13.2-1-default (64-bit) (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 438678] New: Gwenview crashes when trying to rotate a jpg file
https://bugs.kde.org/show_bug.cgi?id=438678 Bug ID: 438678 Summary: Gwenview crashes when trying to rotate a jpg file Product: gwenview Version: 21.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: zi...@lyrion.ch Target Milestone: --- Created attachment 139339 --> https://bugs.kde.org/attachment.cgi?id=139339&action=edit Crash log Rotating an image in Gwenview crashes it reliably. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 --- Comment #31 from Daniel Ziltener --- Created attachment 136981 --> https://bugs.kde.org/attachment.cgi?id=136981&action=edit Crash log -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 --- Comment #30 from Daniel Ziltener --- (In reply to Sérgio Basto from comment #29) > have you tried solution on https://bugs.kde.org/show_bug.cgi?id=339214#c24 ? That's not a solution, that's a workaround at best. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 427113] It shows a kdesu dialog every time it fails to connect to a systemwide wifi
https://bugs.kde.org/show_bug.cgi?id=427113 Daniel Ziltener changed: What|Removed |Added Version|unspecified |5.76.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 427234] New: The dialog "reboot required" shows at the start of the installation process
https://bugs.kde.org/show_bug.cgi?id=427234 Bug ID: 427234 Summary: The dialog "reboot required" shows at the start of the installation process Product: plasma-pk-updates Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: zi...@lyrion.ch Target Milestone: --- The dialog "reboot required" shows at the start of the installation process, and clicking the "Reboot" button on it immediately reboots the system without installing the updates. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 Daniel Ziltener changed: What|Removed |Added CC||zi...@lyrion.ch --- Comment #27 from Daniel Ziltener --- This bug is still alive and kicking. Happens reliably every time when creating a mailbox and changing its trash folder from the local folders one to the account's IMAP folder. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 Daniel Ziltener changed: What|Removed |Added Version|5.1.3 |5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 427113] New: It shows a kdesu dialog every time it fails to connect to a systemwide wifi
https://bugs.kde.org/show_bug.cgi?id=427113
Bug ID: 427113
Summary: It shows a kdesu dialog every time it fails to connect
to a systemwide wifi
Product: frameworks-networkmanager-qt
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: zi...@lyrion.ch
CC: lamar...@kde.org, lukas.ti...@merlin.cz
Target Milestone: ---
SUMMARY
It shows a kdesu dialog every time it fails to connect to a systemwide wifi
("Allow all users to connect to this wifi")
STEPS TO REPRODUCE
1. Add a wireless connection
2. Configure it as global ("Allow all users...")
3. When Network Manager fails to connect, a kdesu dialog is shown.
OBSERVED RESULT
A kdesu dialog is shown when the connection fails.
EXPECTED RESULT
No kdesu dialog, it should simply retry in the background.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 415360] Default for executables changes to show an error message
https://bugs.kde.org/show_bug.cgi?id=415360 --- Comment #2 from Daniel Ziltener --- Yes, it's: ./Riot-x86_64.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, stripped -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415360] New: Default for executables changes to show an error message
https://bugs.kde.org/show_bug.cgi?id=415360
Bug ID: 415360
Summary: Default for executables changes to show an error
message
Product: dolphin
Version: 19.12.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: zi...@lyrion.ch
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
I updated my Tumbleweed distribution today, and suddenly, when clicking an
executable that is marked as such, I start getting error messages saying that
the file I clicked is an executable and that it "won't be run for security
reasons" ("Es wird aus Sicherheitsgründen nicht gestartet.")
STEPS TO REPRODUCE
Update KDE I guess?
OBSERVED RESULT
I get denied executing the program.
EXPECTED RESULT
The program is run as normal.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed, Kernel 5.3.12-1-default
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 388230] New: KWin crashes all the time.
https://bugs.kde.org/show_bug.cgi?id=388230 Bug ID: 388230 Summary: KWin crashes all the time. Product: kwin Version: 5.11.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dzilte...@lyrion.ch Target Milestone: --- Application: kwin_x11 (5.11.4) Qt Version: 5.9.3 Frameworks Version: 5.40.0 Operating System: Linux 4.14.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was normally using KDE with a few open windows. Nothing special, really. Radeon RX580, and have selected OpenGL 3.1. It crashes about a dozen times every day, during Alt+Tab. Seems more likely when one of the windows has content like a playing video or a VM. Most of the time I have to manually start kwin_x11 again. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6407139dc0 (LWP 23319))] Thread 13 (Thread 0x7f63d2fa4700 (LWP 23337)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f63b77fe700 (LWP 23334)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f640304d554 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f640304d599 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f63c4bd0700 (LWP 23332)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f63c53d1700 (LWP 23331)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f63c5bd2700 (LWP 23330)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f63c63d3700 (LWP 23329)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f63c6bd4700 (LWP 23328)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f63c73d5700 (LWP 23327)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f63c7ddb700 (LWP 23326)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6406ab76df in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f63c85dc700 (LWP 23325)): #0 0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f63d09dd06b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f63d09dcf87 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f
[plasmashell] [Bug 388212] New: Comically huge default cursor
https://bugs.kde.org/show_bug.cgi?id=388212 Bug ID: 388212 Summary: Comically huge default cursor Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: dzilte...@lyrion.ch Target Milestone: 1.0 The cursor Plasma-Wayland renders as "resolution dependent" size is comically huge. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 377122] kwallet cannot ask for GPG password on wayland
https://bugs.kde.org/show_bug.cgi?id=377122 Daniel Ziltener changed: What|Removed |Added CC||dzilte...@lyrion.ch --- Comment #4 from Daniel Ziltener --- Well, it seems like I'm definitely not the only one with that problem :) -- You are receiving this mail because: You are watching all bug changes.
