Bug 270321 - software system windows ussualy crashed (
Summary: software system windows ussualy crashed (
Status: RESOLVED WORKSFORME
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
: 262001 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-07 14:23 UTC by Alexander Serdts
Modified: 2018-12-01 03:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Serdts 2011-04-07 14:23:38 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.1
Operating System: Linux 2.6.35.11-83.fc14.i686.PAE i686
Distribution: "RFRemix release 14.1 (Laughlin)"

-- Information about the crash:
- What I was doing when the application crashed:
I tried make print screen this window. Becouse if I tried open by duble click that next windows ussualy crashed (

-- Backtrace:
Application: Параметры системы (systemsettings), signal: Segmentation fault
[KCrash Handler]
#7  0x032dce96 in isSignalConnected (sender=0x8f44618, m=0x4f0e444, local_signal_index=9, argv=0xbfa372d4) at kernel/qobject_p.h:220
#8  QMetaObject::activate (sender=0x8f44618, m=0x4f0e444, local_signal_index=9, argv=0xbfa372d4) at kernel/qobject.cpp:3195
#9  0x04ee7d7a in PackageKit::Transaction::finished(PackageKit::Enum::Exit, unsigned int) () from /usr/lib/libpackagekit-qt.so.14
#10 0x04ee3cd0 in PackageKit::ClientPrivate::serviceUnregistered() () from /usr/lib/libpackagekit-qt.so.14
#11 0x04ee4160 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.14
#12 0x032cdbeb in QMetaObject::metacall (object=0x8e932b8, cl=QMetaObject::InvokeMetaMethod, idx=5, argv=0xbfa37448) at kernel/qmetaobject.cpp:237
#13 0x032dd0c7 in QMetaObject::activate (sender=0x8e99710, m=0x359a7c4, local_signal_index=1, argv=0xbfa37448) at kernel/qobject.cpp:3272
#14 0x0357df84 in QDBusServiceWatcher::serviceUnregistered (this=0x8e99710, _t1=...) at .moc/release-shared/moc_qdbusservicewatcher.cpp:139
#15 0x0357e067 in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged (this=0x8e99720, service=..., oldOwner=..., newOwner=...) at qdbusservicewatcher.cpp:86
#16 0x0357ea8e in QDBusServiceWatcher::qt_metacall (this=0x8e99710, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfa375ec) at .moc/release-shared/moc_qdbusservicewatcher.cpp:91
#17 0x0353fa15 in QDBusConnectionPrivate::deliverCall (this=0x8e93440, object=0x8e99710, msg=..., metaTypes=..., slotIdx=7) at qdbusintegrator.cpp:919
#18 0x0354b3f8 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8e79120, object=0x8e99710) at qdbusintegrator_p.h:103
#19 0x032dcbcf in QObject::event (this=0x8e99710, e=0x8e79120) at kernel/qobject.cpp:1211
#20 0x03a0326c in QApplicationPrivate::notify_helper (this=0x8c31e68, receiver=0x8e99710, e=0x8e79120) at kernel/qapplication.cpp:4445
#21 0x03a07ed2 in QApplication::notify (this=0xbfa37e8c, receiver=0x8e99710, e=0x8e79120) at kernel/qapplication.cpp:3845
#22 0x0468692b in KApplication::notify (this=0xbfa37e8c, receiver=0x8e99710, event=0x8e79120) at /usr/src/debug/kdelibs-4.6.1/kdeui/kernel/kapplication.cpp:311
#23 0x032c73b3 in QCoreApplication::notifyInternal (this=0xbfa37e8c, receiver=0x8e99710, event=0x8e79120) at kernel/qcoreapplication.cpp:732
#24 0x032cb105 in sendEvent (receiver=0x0, event_type=0, data=0x8c118b8) at kernel/qcoreapplication.h:215
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8c118b8) at kernel/qcoreapplication.cpp:1373
#26 0x032cb2de in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#27 0x032f4f35 in sendPostedEvents (s=0x8c34ab0) at kernel/qcoreapplication.h:220
#28 postEventSourceDispatch (s=0x8c34ab0) at kernel/qeventdispatcher_glib.cpp:277
#29 0x00c3f192 in g_main_dispatch (context=0x8c34090) at gmain.c:2149
#30 g_main_context_dispatch (context=0x8c34090) at gmain.c:2702
#31 0x00c3f978 in g_main_context_iterate (context=0x8c34090, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#32 0x00c3fc35 in g_main_context_iteration (context=0x8c34090, may_block=1) at gmain.c:2843
#33 0x032f50ad in QEventDispatcherGlib::processEvents (this=0x8c11368, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#34 0x03ab6406 in QGuiEventDispatcherGlib::processEvents (this=0x8c11368, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#35 0x032c654a in QEventLoop::processEvents (this=0xbfa37de4, flags=...) at kernel/qeventloop.cpp:149
#36 0x032c67fa in QEventLoop::exec (this=0xbfa37de4, flags=...) at kernel/qeventloop.cpp:201
#37 0x032cb3a7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#38 0x03a01078 in QApplication::exec () at kernel/qapplication.cpp:3719
#39 0x08057248 in main (argc=) at /usr/src/debug/kdebase-workspace-4.6.1/systemsettings/app/main.cpp:49

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-07-06 15:17:14 UTC
*** Bug 262001 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Crouthamel 2018-10-29 22:45:33 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 George R. Goffe 2018-10-30 15:03:46 UTC
Andrew,

I see that this bug was reported in 2011! Why is that?

I would suggest that bugs older than a year be closed automatically with a request for more info needed... like, "Is this bug still happening".

I think it's a big waste of everyone's time and energy to spend time on these old bugs.

George...
Comment 4 Andrew Crouthamel 2018-10-31 03:44:46 UTC
Hi George, while I agree with you, there are a number of people within KDE that have the opposite opinion. So, I'm doing my best to follow follow up on these old bugs, while trying to keep everyone happy.
Comment 5 George R. Goffe 2018-11-01 00:33:36 UTC
Andrew,

Thanks for your help.

I would point to this bug as evidence to the wast of time statement.

Again, bugs with NO activity for N years should go through an automatic closure process... i.e., contact the user and/or the developer and/or maintainer and give them one more chance to avoid the closure.

In any event... Best regards,

George...
Comment 6 Andrew Crouthamel 2018-11-01 13:28:03 UTC
(In reply to George R. Goffe from comment #5)
> Andrew,
> 
> Thanks for your help.
> 
> I would point to this bug as evidence to the wast of time statement.
> 
> Again, bugs with NO activity for N years should go through an automatic
> closure process... i.e., contact the user and/or the developer and/or
> maintainer and give them one more chance to avoid the closure.
> 
> In any event... Best regards,
> 
> George...

Just FYI, the NEEDSINFO status I placed this in, will cause it to auto-close in 30 days with no response. :)
Comment 7 Bug Janitor Service 2018-11-16 11:30:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2018-12-01 03:45:32 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!