Bug 451984

Summary: Title was filled out incorrectly
Product: [Frameworks and Libraries] frameworks-solid Reporter: Christopher Yeleighton <giecrilj>
Component: generalAssignee: Lukáš Tinkl <lukas>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde, kdelibs-bugs, nate, sitter
Priority: NOR Keywords: drkonqi
Version: 5.92.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christopher Yeleighton 2022-03-28 08:23:36 UTC
Application: plasmashell (5.24.3)

Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.16.15-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.24.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:

I attached an iPhone over USB and continued to work on my own business.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plazma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>}
[KCrash Handler]
#6  0x00007f9067bbf6fe in __GI___libc_free (mem=0xf2e66c35dec8948) at malloc.c:3368
#7  0x00007f90675c5d81 in idevice_free (device=0x7f906a5a904c <__tls_get_addr+60>) at /usr/src/debug/libimobiledevice-1.3.0+git.20210921-1.2.x86_64/src/idevice.c:432
#8  0x00007f906a1dc5c1 in operator() (__closure=<synthetic pointer>) at /usr/src/debug/solid-5.92.0-1.1.x86_64/src/solid/devices/backends/imobile/imobiledevice.cpp:37
#9  QScopeGuard<Solid::Backends::IMobile::IMobileDevice::IMobileDevice(const QString&)::<lambda()> >::~QScopeGuard (this=<optimized out>, this=<optimized out>) at /usr/include/qt5/QtCore/qscopeguard.h:80
#10 Solid::Backends::IMobile::IMobileDevice::IMobileDevice (this=<optimized out>, udi=..., this=<optimized out>, udi=...) at /usr/src/debug/solid-5.92.0-1.1.x86_64/src/solid/devices/backends/imobile/imobiledevice.cpp:72
#11 0x00007f906a1e03df in Solid::Backends::IMobile::Manager::createDevice (this=0x562a1e769bf0, udi=...) at /usr/src/debug/solid-5.92.0-1.1.x86_64/src/solid/devices/backends/imobile/imobilemanager.cpp:67
#12 0x00007f906a1e38cc in Solid::DeviceManagerPrivate::createBackendObject(QString const&) [clone .constprop.0] (udi=..., this=<optimized out>) at /usr/src/debug/solid-5.92.0-1.1.x86_64/src/solid/devices/frontend/devicemanager.cpp:285
#13 0x00007f906a1af0e8 in Solid::DeviceManagerPrivate::findRegisteredDevice (udi=..., this=0x562a1e402b70) at /usr/src/debug/solid-5.92.0-1.1.x86_64/src/solid/devices/frontend/devicemanager.cpp:254
#14 Solid::DeviceManagerPrivate::findRegisteredDevice (udi=..., this=0x562a1e402b70) at /usr/src/debug/solid-5.92.0-1.1.x86_64/src/solid/devices/frontend/devicemanager.cpp:247
#15 Solid::Device::Device (this=<optimized out>, udi=..., this=<optimized out>, udi=...) at /usr/src/debug/solid-5.92.0-1.1.x86_64/src/solid/devices/frontend/device.cpp:45
#16 0x00007f9062cb43fd in KFilePlacesModelPrivate::deviceAdded (udi=..., this=0x562a1e64ed20) at /usr/src/debug/kio-5.92.0-1.1.x86_64/src/filewidgets/kfileplacesmodel.cpp:764
#17 operator() (device=..., __closure=<optimized out>) at /usr/src/debug/kio-5.92.0-1.1.x86_64/src/filewidgets/kfileplacesmodel.cpp:746
#18 QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<const QString&>, void, KFilePlacesModelPrivate::initDeviceList()::<lambda(const QString&)> >::call (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#19 QtPrivate::Functor<KFilePlacesModelPrivate::initDeviceList()::<lambda(const QString&)>, 1>::call<QtPrivate::List<QString const&>, void> (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#20 QtPrivate::QFunctorSlotObject<KFilePlacesModelPrivate::initDeviceList()::<lambda(const QString&)>, 1, QtPrivate::List<const QString&>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=<optimized out>, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#21 0x00007f9068263503 in QtPrivate::QSlotObjectBase::call (a=0x7ffe8f5138a0, r=0x562a1e779390, this=0x562a1e7792a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 doActivate<false> (sender=0x562a1e402b70, signal_index=3, argv=0x7ffe8f5138a0) at kernel/qobject.cpp:3886
#23 0x00007f906825c9cf in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f906a219520 <Solid::DeviceNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe8f5138a0) at kernel/qobject.cpp:3946
#24 0x00007f906a1a7152 in Solid::DeviceNotifier::deviceAdded (this=<optimized out>, _t1=...) at /usr/src/debug/solid-5.92.0-1.1.x86_64/build/src/solid/KF5Solid_autogen/include/moc_devicenotifier.cpp:144
#25 0x00007f90682594ae in QObject::event (this=0x562a1e402b70, e=0x7f9020001d00) at kernel/qobject.cpp:1314
#26 0x00007f9068fcca7f in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x562a1e402b70, e=0x7f9020001d00) at kernel/qapplication.cpp:3632
#27 0x00007f906822ce3a in QCoreApplication::notifyInternal2 (receiver=0x562a1e402b70, event=0x7f9020001d00) at kernel/qcoreapplication.cpp:1064
#28 0x00007f906822fe77 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x562a1dc73a90) at kernel/qcoreapplication.cpp:1821
#29 0x00007f9068284d03 in postEventSourceDispatch (s=s@entry=0x562a1dd69fe0) at kernel/qeventdispatcher_glib.cpp:277
#30 0x00007f9066574e72 in g_main_dispatch (context=0x7f905c005010) at ../glib/gmain.c:3381
#31 g_main_context_dispatch (context=0x7f905c005010) at ../glib/gmain.c:4099
#32 0x00007f9066575208 in g_main_context_iterate (context=context@entry=0x7f905c005010, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4175
#33 0x00007f90665752bf in g_main_context_iteration (context=0x7f905c005010, may_block=1) at ../glib/gmain.c:4240
#34 0x00007f9068284384 in QEventDispatcherGlib::processEvents (this=0x562a1dd92b90, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#35 0x00007f906822b83b in QEventLoop::exec (this=this@entry=0x7ffe8f513c90, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#36 0x00007f9068233b10 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#37 0x00007f906867d25c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
#38 0x00007f9068fcc9f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#39 0x0000562a1bf647a5 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma5-workspace-5.24.3-1.2.x86_64/shell/main.cpp:238
[Inferior 1 (process 1652) detached]

Possible duplicates by query: bug 451864, bug 451777, bug 451287, bug 450900, bug 450809.

Reported using DrKonqi
Comment 1 Harald Sitter 2022-03-28 10:57:08 UTC
That is expected. For performance reasons the search doesn't cover all of bugzilla but instead operates on a "group". plasmashell has no group that includes solid and thus solid is not included in the search. I'm moving this bug to plasma. If desired to include solid then the mappings file in drkonqi needs updating accordingly, without a mapping drkonqi wouldn't know which bugzilla products to search.
Comment 2 Christopher Yeleighton 2022-03-28 19:35:10 UTC
You have just prevented adding the mapping, which is desired because Plasma built-in notifications rely on Solid, to DrKonqi.

(In reply to Harald Sitter from comment #1)

> bug to plasma. If desired to include solid then the mappings file in drkonqi
> needs updating accordingly, without a mapping drkonqi wouldn't know which
> bugzilla products to search.
Comment 3 Nate Graham 2022-03-28 21:31:52 UTC
Please bring up issues with the crash reporting system in a separate Bugzilla ticket from the one being used to report a crash.

*** This bug has been marked as a duplicate of bug 448329 ***
Comment 4 Christopher Yeleighton 2022-03-29 00:29:29 UTC
(In reply to Nate Graham from comment #3)
> Please bring up issues with the crash reporting system in a separate
> Bugzilla ticket from the one being used to report a crash.
> 
> *** This bug has been marked as a duplicate of bug 448329 ***

This ticket was not intended to report the crash, it was intended to report the problem in DrKonqi.  And then Harald came and spoiled it all.
Comment 5 Nate Graham 2022-03-29 00:34:21 UTC
> This ticket was not intended to report the crash, it was intended to report the problem in DrKonqi

Then it shouldn't have had a crash log in it and been report against Plasma.

Please file a new bug report for the DrKonqi configuration issue. We use separate bug reports to report separate issues in KDE; see https://community.kde.org/Get_Involved/Issue_Reporting#One_issue_per_Bugzilla_ticket
Comment 6 Christopher Yeleighton 2022-03-29 08:19:55 UTC
(In reply to Nate Graham from comment #5)
> > This ticket was not intended to report the crash, it was intended to report the problem in DrKonqi
> 
> Then it shouldn't have had a crash log in it and been report against Plasma.
> 
> Please file a new bug report for the DrKonqi configuration issue. We use
> separate bug reports to report separate issues in KDE; see
> https://community.kde.org/Get_Involved/
> Issue_Reporting#One_issue_per_Bugzilla_ticket

There is this little nice thingy called History:
<URL: https://bugs.kde.org/show_activity.cgi?id=451984 >
As you can see, the bug was not reported against Plasma.  Or, more precisely, it was immediately corrected.  You can also see who stepped in and made a mess.
Comment 7 Harald Sitter 2022-03-29 09:06:45 UTC
:)
Comment 8 Christopher Yeleighton 2022-03-29 15:56:56 UTC
(In reply to Harald Sitter from comment #7)
> :)

There is nothing to :) at.  You would never :)  if you knew how high I am on Nate’s kill list.
Comment 9 Nate Graham 2022-03-29 15:58:05 UTC
What on earth are you talking about? I don't understand why you're acting so hostile here. Can you please tone it down?
Comment 10 Christopher Yeleighton 2022-03-29 16:03:23 UTC
(In reply to Nate Graham from comment #9)
> What on earth are you talking about? I don't understand why you're acting so
> hostile here. Can you please tone it down?

Toning down: Smileys do not help.  Claiming that jokes are hostile does not help.  Undoing your mistakes would help but there is no indication it is going to happen here 🙁