[gwenview] [Bug 470880] Crash while opening .nef raw image
https://bugs.kde.org/show_bug.cgi?id=470880 --- Comment #2 from David Strobach --- (In reply to Nicolas Fella from comment #1) > Can you attach one of the affected files? Nope, not really, because of the size limit. You can, however, download it here: https://mega.nz/file/j3RGELSa#wMs5nJ-HlrMZrjytiC9NkESXF6TRIIVzPDlZsa-uI3E -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 470880] New: Crash while opening .nef raw image
https://bugs.kde.org/show_bug.cgi?id=470880
Bug ID: 470880
Summary: Crash while opening .nef raw image
Classification: Applications
Product: gwenview
Version: 23.04.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: laloc...@gmail.com
Target Milestone: ---
Application: gwenview (23.04.2)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.6-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
Gwenview reproducibly crashes while attempting to open some Nikon .nef raw
image files. The files may possibly be corrupted. They can, however, be
succesfully opened/edited in DarkTable and ImageMagick's `identify -verbose`
doesn't complain either.
The crash can be reproduced every time.
-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f70a97c97ab in std::__cxx11::list >::begin (this=,
this=) at /usr/include/c++/13.1.1/bits/stl_list.h:1033
#7 Exiv2::ExifData::findKey (this=0x0, key=...) at
/usr/src/debug/exiv2/exiv2-0.28.0/src/exif.cpp:457
#8 0x7f70a975442f in
Exiv2::Internal::Nikon3MakerNote::printFlashMasterDataFl7 (os=..., value=...,
metadata=0x0) at /usr/src/debug/exiv2/exiv2-0.28.0/src/nikonmn_int.cpp:3423
#9 0x7f70a97c0914 in Exiv2::Exifdatum::write (this=0x7f706c08c050, os=...,
pMetadata=0x0) at /usr/src/debug/exiv2/exiv2-0.28.0/src/exif.cpp:187
#10 0x7f70aa6231f4 in Exiv2::operator<< (md=..., os=...) at
/usr/include/exiv2/metadatum.hpp:277
#11 Gwenview::ImageMetaInfoModelPrivate::fillExivGroup > (container=...,
group=0x55d0a86c6560, parent=..., this=0x55d0a86c6540) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/imagemetainfomodel.cpp:282
#12 Gwenview::ImageMetaInfoModel::setExiv2Image (this=0x55d0a8829fe0,
image=0x7f706c001960) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/imagemetainfomodel.cpp:441
#13 0x7f70aa5e7c21 in Gwenview::Document::setExiv2Image
(this=0x55d0a8736590, image=...) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/document/document.cpp:388
#14 0x7f70aa5f2d8e in Gwenview::AbstractDocumentImpl::setDocumentExiv2Image
(this=0x55d0a887c6d0, image=std::unique_ptr = {...}) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/document/abstractdocumentimpl.cpp:81
#15 Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded (this=0x55d0a887c6d0) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/document/loadingdocumentimpl.cpp:497
#16 0x7f70a82cffe7 in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate (sender=0x55d0a8680418, signal_index=4,
argv=0x7ffd87cf8600) at kernel/qobject.cpp:3923
#18 0x7f70a80fd0d5 in QFutureWatcherBase::event (this=,
event=0x7f706c05da20) at thread/qfuturewatcher.cpp:334
#19 0x7f70a8f7893f in QApplicationPrivate::notify_helper (this=, receiver=0x55d0a8680418, e=0x7f706c05da20) at
kernel/qapplication.cpp:3640
#20 0x7f70a829ab18 in QCoreApplication::notifyInternal2
(receiver=0x55d0a8680418, event=0x7f706c05da20) at
kernel/qcoreapplication.cpp:1064
#21 0x7f70a829fa7b in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55d0a8018b20) at
kernel/qcoreapplication.cpp:1821
#22 0x7f70a82e6088 in postEventSourceDispatch (s=0x55d0a802a140) at
kernel/qeventdispatcher_glib.cpp:277
#23 0x7f70a6110981 in g_main_dispatch (context=0x7f709c000ee0) at
../glib/glib/gmain.c:3460
#24 g_main_context_dispatch (context=0x7f709c000ee0) at
../glib/glib/gmain.c:4200
#25 0x7f70a616db39 in g_main_context_iterate.isra.0
(context=context@entry=0x7f709c000ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#26 0x7f70a610e032 in g_main_context_iteration (context=0x7f709c000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#27 0x7f70a82e9f0c in QEventDispatcherGlib::processEvents
(this=0x55d0a80449a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7f70a8299824 in QEventLoop::exec (this=this@entry=0x7ffd87cf8a30,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7f70a829acc3 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x7f70a873b7c2 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1870
#31 0x7f70a8f76cda in QApplication::exec () at kernel/qapplication.cpp:2832
#32 0x55d0a6e6ea49 in main (argc=, argv=) at
/usr/src/debug/gwenview/gwenview-23.04.2/app/main.cpp:213
[Inferior 1 (process 17812) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug chan
[kwin] [Bug 433071] No background wallpapers in Desktop Grid on Wayland when Present Windows effect is enabled
https://bugs.kde.org/show_bug.cgi?id=433071 --- Comment #26 from David Strobach --- The bug is triggered by the "Show panels" option of the Present Windows effect. If the option is disabled, there's no wallpaper in the desktop grid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background wallpapers in Desktop Grid on Wayland when Present Windows effect is enabled
https://bugs.kde.org/show_bug.cgi?id=433071 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com --- Comment #25 from David Strobach --- (In reply to Nate Graham from comment #24) > Can confirm. Very interesting observation! +1. Same here on Plasma 5.23.5/Wayland. No background in Desktop Grid effect if Present Windows is enabled at the same time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415872] kwin_wayland random segfault libQt5Qml.so.5.14.0[7fe09a171000+307000]
https://bugs.kde.org/show_bug.cgi?id=415872 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416826] Moving around Windows with Kwin-tiling occasionally causes segfault
https://bugs.kde.org/show_bug.cgi?id=416826 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408806] [RFE] provide API to override keybindings
https://bugs.kde.org/show_bug.cgi?id=408806 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408787] "ReferenceError: workspace is not defined" in qdbus interactive shell
https://bugs.kde.org/show_bug.cgi?id=408787 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398678] Input devices (touch screen and keyboard) does not work as expected in sddm if an external monitor is connected to hdmi port during boot
https://bugs.kde.org/show_bug.cgi?id=398678 --- Comment #5 from David Strobach --- s/display/screen/g -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398678] Input devices (touch screen and keyboard) does not work as expected in sddm if an external monitor is connected to hdmi port during boot
https://bugs.kde.org/show_bug.cgi?id=398678 --- Comment #4 from David Strobach --- (In reply to David Edmundson from comment #3) > I can't see what could be wrong in SDDM. Xorg doesn't IMO by default map the touch screen coordinates to the "correct" display. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398678] Input devices (touch screen and keyboard) does not work as expected in sddm if an external monitor is connected to hdmi port during boot
https://bugs.kde.org/show_bug.cgi?id=398678 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com --- Comment #1 from David Strobach --- > I do not know if kwin if the correct product for this report. SDDM is not a part of KDE project, so no, it's probably not. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403071] The KWin scripting API provides no way to maximize or unmaximize a window
https://bugs.kde.org/show_bug.cgi?id=403071 David Strobach changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from David Strobach --- Closed by https://phabricator.kde.org/R108:1d4a9d24f86799b45994c545b054e205f371869f Scripting interface now exposes Client.setMaximize(v, h) method. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403071] The KWin scripting API provides no way to maximize or unmaximize a window
https://bugs.kde.org/show_bug.cgi?id=403071 David Strobach changed: What|Removed |Added Ever confirmed|0 |1 CC||laloc...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from David Strobach --- A patch is being reviewed: https://phabricator.kde.org/D20044 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 390964] Crash when clicking [Settings -> Configure Chat Application...] version 17.12.2
https://bugs.kde.org/show_bug.cgi?id=390964 David Strobach changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from David Strobach --- Fixed by commits d55f70722af76015dd79b278618fdbf9972c29ff 0862d220c9042baa25200b0e178cc9ce44525a13 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 390964] Crash when clicking [Settings -> Configure Chat Application...] version 17.12.2
https://bugs.kde.org/show_bug.cgi?id=390964 --- Comment #7 from David Strobach --- > Thanks for the fix, David. Was the patch already added to Phabricator? Hi Christoph, no, unfortunately not yet. I somehow can't digest the idea, that the change my patch does is the right(TM) way to integrate KCMs after the recent KCM refactoring. I would like to first check other KDE projects to see how they made their way through the KCM refactoring before submitting the fix. I expect to be able to move ahead during this week. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 390964] Crash when clicking [Settings -> Configure Chat Application...] version 17.12.2
https://bugs.kde.org/show_bug.cgi?id=390964 David Strobach changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from David Strobach --- @CapSel: Could you please check whether the attached patch fixes the bug for you? If it does, I'll post it to Phabricator for review, commit it and close the bug eventually. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 390964] Crash when clicking [Settings -> Configure Chat Application...] version 17.12.2
https://bugs.kde.org/show_bug.cgi?id=390964 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com --- Comment #2 from David Strobach --- Created attachment 19 --> https://bugs.kde.org/attachment.cgi?id=19&action=edit 0001-app-Fix-crash-while-displaying-Settings-dialog.patch The crash is due to the fact that the KPageWidgetItem does no longer hold a reference to KCModuleProxy instance. The KCModuleProxy instance is rather wrapped in a QScrollArea instance. Tentative patch attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370920] Meta key sometimes stops working after suspend phase
https://bugs.kde.org/show_bug.cgi?id=370920 --- Comment #8 from David Strobach --- (In reply to Martin Gräßlin from comment #7) > Once https://phabricator.kde.org/D3379 is merged I would like you to open > the debug console check whether any modifiers are considered active. If not, > I'll extend it further to also inspect the mod-only-trigger-state. I did. No active modifiers, sorry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371791] Add natural scrolling support
https://bugs.kde.org/show_bug.cgi?id=371791 David Strobach changed: What|Removed |Added Version Fixed In||5.8.4 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kwin ||/b19341777a566ba4b20485e161 ||c5eeb25b521d0a --- Comment #3 from David Strobach --- Git commit b19341777a566ba4b20485e161c5eeb25b521d0a by David Strobach. Committed on 03/11/2016 at 13:02. Pushed by strobach into branch 'Plasma/5.8'. [libinput] Add natural scrolling support Wraps libinput libinput_device_config_has_natural_scroll libinput_device_config_set_natural_scroll_enabled libinput_device_config_get_natural_scroll_enabled libinput_device_config_scroll_get_default_natural_scroll_enabled Differential Revision: https://phabricator.kde.org/D3193 FIXED-IN: 5.8.4 M +27 -0autotests/libinput/mock_libinput.cpp M +4-0autotests/libinput/mock_libinput.h M +16 -0libinput/device.cpp M +17 -0libinput/device.h http://commits.kde.org/kwin/b19341777a566ba4b20485e161c5eeb25b521d0a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371803] Add scroll method selection support
https://bugs.kde.org/show_bug.cgi?id=371803 David Strobach changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kwin ||/e4283543f633b8e56fe8ce999d ||cd8d12bfa31e64 Resolution|--- |FIXED Version Fixed In||5.8.4 --- Comment #2 from David Strobach --- Git commit e4283543f633b8e56fe8ce999dcd8d12bfa31e64 by David Strobach. Committed on 03/11/2016 at 13:03. Pushed by strobach into branch 'Plasma/5.8'. [libinput] Add scroll method configuration support Wraps libinput libinput_device_config_scroll_get_methods libinput_device_config_scroll_get_default_method libinput_device_config_scroll_set_method libinput_device_config_scroll_get_method libinput_device_config_scroll_set_button libinput_device_config_scroll_get_button libinput_device_config_scroll_get_default_button Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D3194 FIXED-IN: 5.8.4 M +49 -0autotests/libinput/mock_libinput.cpp M +7-0autotests/libinput/mock_libinput.h M +52 -1libinput/device.cpp M +60 -0libinput/device.h http://commits.kde.org/kwin/e4283543f633b8e56fe8ce999dcd8d12bfa31e64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371756] Add support for middle mouse button emulation
https://bugs.kde.org/show_bug.cgi?id=371756 David Strobach changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.8.4 Latest Commit||http://commits.kde.org/kwin ||/e00649d00224326cb782776d3c ||7af8a0d0727803 Resolution|--- |FIXED --- Comment #3 from David Strobach --- Git commit e00649d00224326cb782776d3c7af8a0d0727803 by David Strobach. Committed on 03/11/2016 at 13:00. Pushed by strobach into branch 'Plasma/5.8'. [libinput] Add middle mouse button emulation support Wraps libinput libinput_device_config_middle_emulation_is_available libinput_device_config_middle_emulation_set_enabled libinput_device_config_middle_emulation_get_enabled libinput_device_config_middle_emulation_get_default_enabled Differential Revision: https://phabricator.kde.org/D3187 FIXED-IN: 5.8.4 M +35 -0autotests/libinput/mock_libinput.cpp M +4-0autotests/libinput/mock_libinput.h M +4-0libinput/device.cpp M +17 -0libinput/device.h http://commits.kde.org/kwin/e00649d00224326cb782776d3c7af8a0d0727803 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370920] Meta key sometimes stops working after suspend phase
https://bugs.kde.org/show_bug.cgi?id=370920 --- Comment #4 from David Strobach --- I just realized that it only happens to me with evdev driver. xf86-input-libinput survives the VT switch just fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370920] Meta key sometimes stops working after suspend phase
https://bugs.kde.org/show_bug.cgi?id=370920 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com --- Comment #2 from David Strobach --- For me it gets reliably triggered by switching virtual terminals. I'm currently on 5.8.2, but IIRC it happens since 5.8.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371917] New: libinput device configuration does not persist across VT switches
https://bugs.kde.org/show_bug.cgi?id=371917 Bug ID: 371917 Summary: libinput device configuration does not persist across VT switches Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: laloc...@gmail.com Target Milestone: --- Since the org.kde.KWin.InputDevice interface is exposed on D-Bus it is possible to alter the input device configuration. The configuration gets however reset back to defaults once the user switches virtual terminals. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371803] Add scroll method selection support
https://bugs.kde.org/show_bug.cgi?id=371803 --- Comment #1 from David Strobach --- Patch: https://phabricator.kde.org/D3194 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371803] New: Add scroll method selection support
https://bugs.kde.org/show_bug.cgi?id=371803 Bug ID: 371803 Summary: Add scroll method selection support Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: laloc...@gmail.com Target Milestone: --- Supported by libinput since 0.7.0. Interface: libinput_device_config_scroll_get_methods libinput_device_config_scroll_get_default_method libinput_device_config_scroll_set_method libinput_device_config_scroll_get_method libinput_device_config_scroll_set_button libinput_device_config_scroll_get_button libinput_device_config_scroll_get_default_button -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371791] Add natural scrolling support
https://bugs.kde.org/show_bug.cgi?id=371791 --- Comment #2 from David Strobach --- @Martin: I'll try to extend the device_test.cpp later (I have scroll method implementation at the head of my queue), but I'm not much of a testing guy, so I don't promise anything ;-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366605] Tap-to-click missing on Wayland
https://bugs.kde.org/show_bug.cgi?id=366605 David Strobach changed: What|Removed |Added CC||laloc...@gmail.com --- Comment #10 from David Strobach --- (In reply to Götz from comment #9) > I did a "org.freedesktop.DBus.Properties.GetAll" on my input device to > search for a Natural Scrolling configuration option, and it seems to be > missing. Is this to be handled in a different but report or all input > related here as well? See here: https://bugs.kde.org/show_bug.cgi?id=371791 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371791] Add natural scrolling support
https://bugs.kde.org/show_bug.cgi?id=371791 --- Comment #1 from David Strobach --- Patch: https://phabricator.kde.org/D3193 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371791] New: Add natural scrolling support
https://bugs.kde.org/show_bug.cgi?id=371791 Bug ID: 371791 Summary: Add natural scrolling support Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: laloc...@gmail.com Target Milestone: --- Implemented in libinput since 0.7.0 by: libinput_device_config_has_natural_scroll libinput_device_config_set_natural_scroll_enabled libinput_device_config_get_natural_scroll_enabled libinput_device_config_scroll_get_default_natural_scroll_enabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371756] Add support for middle mouse button emulation
https://bugs.kde.org/show_bug.cgi?id=371756 --- Comment #2 from David Strobach --- Here you go: https://phabricator.kde.org/D3187 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371756] New: Add support for middle mouse button emulation
https://bugs.kde.org/show_bug.cgi?id=371756 Bug ID: 371756 Summary: Add support for middle mouse button emulation Product: kwin Version: git master Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: lal...@atlas.cz Target Milestone: --- Created attachment 101838 --> https://bugs.kde.org/attachment.cgi?id=101838&action=edit [PATCH] [libinput] Add middle mouse button emulation support Middle mouse button emulation is supported by libinput via libinput_device_config_middle_emulation_* group of functions. Some devices can still make use the feature even these days. Patch is attached. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 365256] Krunner dictionary is buggy
https://bugs.kde.org/show_bug.cgi?id=365256 David Strobach changed: What|Removed |Added CC||lal...@atlas.cz -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 355415] Cannot connect to Google Hangouts
https://bugs.kde.org/show_bug.cgi?id=355415 --- Comment #5 from David Strobach --- (In reply to Thomas Van Parys from comment #4) > I was waiting for Fedora to push 15.08.3 to see whether that actually fixes > the bugs, but if 15.12.0 still has the same issues, that's not very likely. > > But I wonder if it's only my (Fedora) install of Telepathy that's so > completely messed up, or if it's a general thing. These should be separate > bugs, but next to Google Hangouts, also ICQ is not working and Telegram > keeps asking for the non-existing 'morse' package. Actually, only XMPP is at > this point working as it should. I ended up completely deleting ~/.config/libaccounts-glib and ~/.config/signond and re-creating all the accounts from scratch. Conversation logs are stored under ~/.local/share/TpLogger. You can pair them back with the newly created accounts if you wish (mc-tool dump will be your guide). Look at https://community.kde.org/KTp/Setting_up_KAccounts for an illustration of how complicated the authentication in KTp is. With all the libraries, daemons, plugins and their ever-changing protocols and configuration formats, it's wonder that the KTp works at all (sometimes). Btw, I was horrified when I realized, that the signond "secrets" database is stored in plain text and is readable by group (which, in my case, is users!). -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 355415] Cannot connect to Google Hangouts
https://bugs.kde.org/show_bug.cgi?id=355415 David Strobach changed: What|Removed |Added CC||lal...@atlas.cz --- Comment #3 from David Strobach --- Same problem here on Arch Linux with KDE Apps 15.12.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356470] Plasmashell 5.5 segfaults on shutdown (like 5.3)
https://bugs.kde.org/show_bug.cgi?id=356470 --- Comment #8 from David Strobach --- (In reply to Paul Konecny from comment #7) > I just received the update for plasma-workspace 5.5.1 and the issue seems > fixed. > Neither kquitapp plasmashell nor a normal shutdown trigger the segfault now. > > Can you guys confirm this? Yes, the broken discovernotifier plasmoid is already fixed, but it only removed the trigger. The bug itself is still there. -- You are receiving this mail because: You are watching all bug changes.
