Bug 306707 - Using KDE, FC17, Virt-Manager
Summary: Using KDE, FC17, Virt-Manager
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
: 344251 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-09-12 22:45 UTC by tmichett
Modified: 2018-11-30 03:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
I didn't restart before uploading it. (45.11 KB, application/x-trash)
2015-02-16 22:28 UTC, ali.sherif10
Details
Xorg.0.log for more information. (35.35 KB, application/x-7z-compressed)
2015-02-16 22:33 UTC, ali.sherif10
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tmichett 2012-09-12 22:45:25 UTC
Application: ksmserver (0.4)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.2
Operating System: Linux 3.5.3-1.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

- Unusual behavior I noticed:
KDE Freezes and X11 crashes when using VIRT-MANAGER. Also, continually crashes opening Plasma desktop. States something about NOUVEAU driver.

The crash can be reproduced every time.

-- Backtrace:
Application: The KDE Session Manager (ksmserver), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  QString (other=..., this=0x7fff1a794c60) at ../../src/corelib/tools/qstring.h:725
#7  dbusInterfaceString () at qdbusintegrator.cpp:83
#8  QDBusConnectionPrivate::disconnectSignal (this=this@entry=0xec8950, it=...) at qdbusintegrator.cpp:2206
#9  0x0000003dfc622431 in QDBusConnectionPrivate::objectDestroyed (this=0xec8950, obj=0xfc2d10) at qdbusintegrator.cpp:1179
#10 0x0000003dfb98cb9f in QMetaObject::activate (sender=sender@entry=0xfc2d10, m=m@entry=0x3dfbcc6a20, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff1a794e50) at kernel/qobject.cpp:3547
#11 0x0000003dfb98d5df in QObject::destroyed (this=this@entry=0xfc2d10, _t1=_t1@entry=0xfc2d10) at .moc/release-shared/moc_qobject.cpp:148
#12 0x0000003dfb98d6d3 in QObject::~QObject (this=0xfc2d10, __in_chrg=<optimized out>) at kernel/qobject.cpp:844
#13 0x0000003dfc635f69 in QDBusInterface::~QDBusInterface (this=0xfc2d10, __in_chrg=<optimized out>) at qdbusinterface.cpp:231
#14 0x0000003dfb988a32 in QObjectPrivate::deleteChildren (this=this@entry=0xfbcd80) at kernel/qobject.cpp:1908
#15 0x0000003dfb98dc06 in QObject::~QObject (this=0xfb9d70, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
#16 0x0000003e07814e59 in KSMServer::~KSMServer (this=0xfb9d70, __in_chrg=<optimized out>) at /usr/src/debug/kde-workspace-4.8.5/ksmserver/server.cpp:721
#17 0x0000003e0781435e in sighandler (sig=16566832) at /usr/src/debug/kde-workspace-4.8.5/ksmserver/server.cpp:534
#18 <signal handler called>
#19 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
#20 0x0000003dfb87baeb in wait (time=18446744073709551615, this=0xe70180) at thread/qwaitcondition_unix.cpp:86
#21 QWaitCondition::wait (this=<optimized out>, mutex=0xe71468, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#22 0x0000003dfb87b1fc in QThread::wait (this=<optimized out>, time=18446744073709551615) at thread/qthread_unix.cpp:660
#23 0x0000003dfb953c52 in QProcessManager::~QProcessManager (this=0x3dfbccc3c0, __in_chrg=<optimized out>) at io/qprocess_unix.cpp:212
#24 0x0000003defc38b71 in __run_exit_handlers (status=1, listp=0x3deffb0688, run_list_atexit=run_list_atexit@entry=true) at exit.c:78
#25 0x0000003defc38bf5 in __GI_exit (status=<optimized out>) at exit.c:100
#26 0x0000003dfe633ff8 in qt_xio_errhandler () at kernel/qapplication_x11.cpp:770
#27 0x0000003e00845098 in KApplication::xioErrhandler (this=0xe5e850, dpy=0xe521c0) at /usr/src/debug/kdelibs-4.8.5/kdeui/kernel/kapplication.cpp:419
#28 0x0000003df2c455ce in _XIOError (dpy=dpy@entry=0xe521c0) at XlibInt.c:1618
#29 0x0000003df2c4306d in _XEventsQueued (dpy=dpy@entry=0xe521c0, mode=mode@entry=2) at xcb_io.c:365
#30 0x0000003df2c3462b in XEventsQueued (dpy=0xe521c0, mode=2) at Pending.c:43
#31 0x0000003dfe66a14c in x11EventSourceCheck (s=s@entry=0xe70000) at kernel/qguieventdispatcher_glib.cpp:85
#32 0x0000003df204747b in g_main_context_check (context=context@entry=0xe6ee00, max_priority=0, fds=fds@entry=0xfccdd0, n_fds=n_fds@entry=8) at gmain.c:3023
#33 0x0000003df2047902 in g_main_context_iterate (context=context@entry=0xe6ee00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3143
#34 0x0000003df2047a84 in g_main_context_iteration (context=0xe6ee00, may_block=1) at gmain.c:3207
#35 0x0000003dfb9a44e6 in QEventDispatcherGlib::processEvents (this=0xe37ba0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#36 0x0000003dfe66a2ee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#37 0x0000003dfb97513f in QEventLoop::processEvents (this=this@entry=0x7fff1a795860, flags=...) at kernel/qeventloop.cpp:149
#38 0x0000003dfb9753c8 in QEventLoop::exec (this=0x7fff1a795860, flags=...) at kernel/qeventloop.cpp:204
#39 0x0000003dfb97a1b8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#40 0x0000003e07812b99 in kdemain (argc=1, argv=0x7fff1a795b88) at /usr/src/debug/kde-workspace-4.8.5/ksmserver/main.cpp:311
#41 0x0000003defc21735 in __libc_start_main (main=0x400800 <main(int, char**)>, argc=1, ubp_av=0x7fff1a795b88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff1a795b78) at libc-start.c:226
#42 0x0000000000400831 in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2012-09-12 23:13:33 UTC
XIOError, so probably the X server died. Is there any information about the reason in /var/log/Xorg.0.log[.old]?
Comment 2 Christoph Feck 2015-02-16 22:11:14 UTC
*** Bug 344251 has been marked as a duplicate of this bug. ***
Comment 3 ali.sherif10 2015-02-16 22:28:58 UTC
Created attachment 91118 [details]
I didn't restart before uploading it.
Comment 4 ali.sherif10 2015-02-16 22:33:57 UTC
Created attachment 91119 [details]
Xorg.0.log for more information.
Comment 5 Andrew Crouthamel 2018-10-31 04:13:15 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 6 Bug Janitor Service 2018-11-15 10:38:51 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 7 Bug Janitor Service 2018-11-30 03:51:38 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!