[frameworks-purpose] [Bug 443788] Sharing a file/folder via email causes the screen to panic
https://bugs.kde.org/show_bug.cgi?id=443788 --- Comment #3 from cbnavigator --- Sorry for piling another comment (this bugtracker really should have a feature to edit comments) but I also just confirmed that this issue happens as Kalzi described not only with desktop files or folders but with any file or folder when using the Dolphin share-by-email sub-menu leading to Dolphin crashing. It is reproducible 100% of the time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 443788] Sharing a file/folder via email causes the screen to panic
https://bugs.kde.org/show_bug.cgi?id=443788 --- Comment #2 from cbnavigator --- Forgot to mention I reproduced this bug on KDE Neon Testing edition with Frameworks 5.88.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 443788] Sharing a file/folder via email causes the screen to panic
https://bugs.kde.org/show_bug.cgi?id=443788 cbnavigator changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 443788] Sharing a file/folder via email causes the screen to panic
https://bugs.kde.org/show_bug.cgi?id=443788 cbnavigator changed: What|Removed |Added CC||sbmich...@tuta.io --- Comment #1 from cbnavigator --- Created attachment 142478 --> https://bugs.kde.org/attachment.cgi?id=142478=edit crash backtrace -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443102] New: Add the icons for Syncthing and Joplin in Breeze icon set
https://bugs.kde.org/show_bug.cgi?id=443102 Bug ID: 443102 Summary: Add the icons for Syncthing and Joplin in Breeze icon set Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: sbmich...@tuta.io CC: kain...@gmail.com Target Milestone: --- Currently Breeze icon set lacks the icons for Syncthing and Joplin. For this reason I must install Papirus icon theme. These are two well known programs in their respective categories. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: Plasma 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412834] "Cannot refresh cache whilst offline" -- except I'm online.
https://bugs.kde.org/show_bug.cgi?id=412834 --- Comment #5 from cbnavigator --- (In reply to Rik Mills from comment #4) > (In reply to Nate Graham from comment #3) > > No, because this issue is outside of KDE's control. Happily, it looks like > > it was actually fixed upstream in > > https://github.com/PackageKit/PackageKit/pull/506 17 days ago. Probably > > either no PackageKit release has been made with that fix yet, or you have an > > older PackageKit release that doesn't include it. > > For 21.10 there is a fixed packagekit currently waiting for approval by the > Ubuntu release team. I can confirm that as of today, latest PackageKit updates on Kubuntu 21.10 Beta fixed this issue with Discover. It is now able to search and apply updates and also install regular packages. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412834] "Cannot refresh cache whilst offline" -- except I'm online.
https://bugs.kde.org/show_bug.cgi?id=412834 cbnavigator changed: What|Removed |Added CC||sbmich...@tuta.io --- Comment #2 from cbnavigator --- Is there any development about this issue? It's happening on latest Kubuntu 21.10 Beta - I am unable to search and install updates through Discover with this error and also unable install packages from regular Ubuntu repositories "no network connection available" but it is able install snaps... so in essence Discover is crippled right now in Kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 cbnavigator changed: What|Removed |Added CC||sbmich...@tuta.io -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 439450] Spectacle crashing when exporting image to online service
https://bugs.kde.org/show_bug.cgi?id=439450 --- Comment #4 from cbnavigator --- Thank you very much for the swift response, as it is a feature I use regularly. I'll be waiting for the next point-release. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 439450] Spectacle crashing when exporting image to online service
https://bugs.kde.org/show_bug.cgi?id=439450 --- Comment #1 from cbnavigator --- To clarify further, the crash happens as soon as I selected an online service from the list at export > more services. It is not reproduced always but happens often. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 439450] New: Spectacle crashing when exporting image to online service
https://bugs.kde.org/show_bug.cgi?id=439450 Bug ID: 439450 Summary: Spectacle crashing when exporting image to online service Product: Spectacle Version: 21.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: sbmich...@tuta.io CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (21.04.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.13-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.2 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Took a screenshot, then exported to online service (imgur) - Unusual behavior I noticed: Spectacle crashed without completing the export to the online service. The crash can be reproduced sometimes. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f6cc9fcf180 (LWP 2728))] [KCrash Handler] #6 0x7f6cce8732e4 in KIPI::PluginLoader::interface (this=0x55730b35fbc0) at /usr/src/debug/libkipi-21.04.2-1.1.x86_64/src/pluginloader.cpp:378 #7 0x7f6ca409bf4e in KIPIPlugins::KPDialogBase::Private::Private (this=0x55730b431b40) at /usr/src/debug/kipi-plugins-21.04.2-1.1.x86_64/common/libkipiplugins/dialogs/kptooldialog.cpp:66 #8 KIPIPlugins::KPDialogBase::KPDialogBase (this=, dlg=, this=, dlg=) at /usr/src/debug/kipi-plugins-21.04.2-1.1.x86_64/common/libkipiplugins/dialogs/kptooldialog.cpp:78 #9 0x7f6ca409c188 in KIPIPlugins::KPToolDialog::KPToolDialog (this=, parent=, this=, parent=) at /usr/src/debug/kipi-plugins-21.04.2-1.1.x86_64/common/libkipiplugins/dialogs/kptooldialog.cpp:164 #10 0x7f6c8811171b in KIPIImgurPlugin::ImgurWindow::ImgurWindow (this=this@entry=0x55730b425270) at /usr/src/debug/kipi-plugins-21.04.2-1.1.x86_64/imgur/imgurwindow.cpp:55 #11 0x7f6c88113372 in KIPIImgurPlugin::Plugin_Imgur::slotActivate (this=0x55730b404480) at /usr/src/debug/kipi-plugins-21.04.2-1.1.x86_64/imgur/plugin_imgur.cpp:116 #12 0x7f6cccbb2fe8 in doActivate (sender=0x55730b4044f0, signal_index=4, argv=0x7ffedb9794f0) at kernel/qobject.cpp:3898 #13 0x7f6cccbac47f in QMetaObject::activate (sender=sender@entry=0x55730b4044f0, m=m@entry=0x7f6ccdc400a0, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffedb9794f0) at kernel/qobject.cpp:3946 #14 0x7f6ccd721182 in QAction::triggered (this=this@entry=0x55730b4044f0, _t1=) at .moc/moc_qaction.cpp:376 #15 0x7f6ccd723db4 in QAction::activate (this=0x55730b4044f0, event=) at kernel/qaction.cpp:1161 #16 0x7f6ccd8a93b2 in QMenuPrivate::activateCausedStack (this=this@entry=0x55730b257a10, causedStack=..., action=action@entry=0x55730b4044f0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1384 #17 0x7f6ccd8b1161 in QMenuPrivate::activateAction (this=0x55730b257a10, action=0x55730b4044f0, action_e=QAction::Trigger, self=) at widgets/qmenu.cpp:1461 #18 0x7f6ccd76971e in QWidget::event (this=0x55730b362330, event=0x7ffedb979b00) at kernel/qwidget.cpp:9020 #19 0x7f6ccd727a7f in QApplicationPrivate::notify_helper (this=this@entry=0x55730acd7db0, receiver=receiver@entry=0x55730b362330, e=e@entry=0x7ffedb979b00) at kernel/qapplication.cpp:3632 #20 0x7f6ccd72f584 in QApplication::notify (this=0x7ffedb979820, receiver=0x55730b362330, e=0x7ffedb979b00) at kernel/qapplication.cpp:3076 #21 0x7f6cccb7c96a in QCoreApplication::notifyInternal2 (receiver=0x55730b362330, event=0x7ffedb979b00) at kernel/qcoreapplication.cpp:1064 #22 0x7f6ccd72e093 in QApplicationPrivate::sendMouseEvent (receiver=0x55730b362330, event=event@entry=0x7ffedb979b00, alienWidget=0x0, nativeWidget=0x55730b362330, buttonDown=, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614 #23 0x7f6ccd783493 in QWidgetWindow::handleMouseEvent (this=0x55730b3c67e0, event=0x7ffedb979dd0) at kernel/qwidgetwindow.cpp:580 #24 0x7f6ccd785da5 in QWidgetWindow::event (this=0x55730b3c67e0, event=0x7ffedb979dd0) at kernel/qwidgetwindow.cpp:300 #25 0x7f6ccd727a7f in QApplicationPrivate::notify_helper (this=, receiver=0x55730b3c67e0, e=0x7ffedb979dd0) at kernel/qapplication.cpp:3632 #26 0x7f6cccb7c96a in QCoreApplication::notifyInternal2 (receiver=0x55730b3c67e0, event=0x7ffedb979dd0) at kernel/qcoreapplication.cpp:1064 #27 0x7f6cccfd3817 in QGuiApplicationPrivate::processMouseEvent (e=0x55730b426ff0) at kernel/qguiapplication.cpp:2282 #28 0x7f6cccfa99cc in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1169 #29 0x7f6cca6a5a00 in userEventSourceDispatch
[systemsettings] [Bug 436447] Linking SDDM settings with lockscreen settings
https://bugs.kde.org/show_bug.cgi?id=436447 cbnavigator changed: What|Removed |Added Summary|Linking SDDM settings with |Linking SDDM settings with |lockscreen appearance |lockscreen settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436447] New: Linking SDDM settings with lockscreen appearance
https://bugs.kde.org/show_bug.cgi?id=436447 Bug ID: 436447 Summary: Linking SDDM settings with lockscreen appearance Product: systemsettings Version: 5.21.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: sbmich...@tuta.io CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- SUMMARY Trying to personalize both my SDDM and lockscreen for the first time, it was not intuitive for me to have the option to change the background of the lockscreen apart from SDDM settings. Now I use Plasma for a while and I found unintuitive, so I'd assume a completely new user would feel the same way. If not desirable to unite lockscreen settings with SDDM settings in the same module (login & lock screen), I suggest presenting a link that directly takes the user to the other module. STEPS TO REPRODUCE 1. open SDDM KCM module 2. navigate to lockscreen KCM module OBSERVED RESULT The user (especially a new user) has to figure out that lockscreen settings and SDDM settings are in different modules and browse through SystemSettings to find each. EXPECTED RESULT Either a) When accessing the lockscreen module, find a link to navigate directly to SDDM module. When accessing SDDM module, find a link to navigate directly to lockscreen module or b) unite lockscreen settings with SDDM module SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
