https://bugs.kde.org/show_bug.cgi?id=490323

            Bug ID: 490323
           Summary: Discover freeze and crash report after pressing X
    Classification: Applications
           Product: Discover
           Version: 6.1.2
          Platform: openSUSE
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: discover
          Assignee: plasma-b...@kde.org
          Reporter: arminand...@gmail.com
                CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (6.1.2)

Qt Version: 6.7.2
Frameworks Version: 6.4.0
Operating System: Linux 6.9.9-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 6.1.2 [CoredumpBackend]

-- Information about the crash:
When I was using YaST Software Manager, Discover and so on... 
I needed to close Discover. I have pressed X. 
I think the Window freezed a bit and it closed but by showing a crash report,
which is unusual.

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#4  0x00007f8511aa0ce7 in AggregatedResultsStream::resourceDestruction
(this=0x556e57bd4f70, obj=0x556e4fab2a30) at
/usr/src/debug/discover-6.1.2/libdiscover/resources/ResourcesModel.cpp:356
#5  0x00007f850efe7f90 in QtPrivate::QSlotObjectBase::call (a=0x7fff50ae3d10,
r=0x556e57bd4f70, this=0x556e484b47d0) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobjectdefs_impl.h:469
#6  doActivate<false> (sender=0x556e4fab2a30, signal_index=0,
argv=0x7fff50ae3d10) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobject.cpp:4086
#7  0x00007f850efd7f0f in QObject::destroyed (this=<optimized out>,
_t1=<optimized out>) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/build/src/corelib/kernel/moc_qobject.cpp:229
#8  0x00007f850efd7618 in QObject::~QObject (this=<optimized out>,
this=<optimized out>) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobject.cpp:1074


Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to