project neon5 CRASHES ALL THE TIME

Bug #1295597 reported by Simon Andric
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Project Neon
Invalid
Undecided
Unassigned

Bug Description

when i log in immediately dr. konqi appears about plasma crash. after that ultiple dr. konqi's appear with same error - the desktop enivronemnt doesnt show itself, the screen stays black appart from multiple dr. konqi's open. if i may add - please create a section for projectneon5 coz dr. konqi wants to save the crash reports in the bugs.kde.org NOT i nproject eon page in launchpad..

thank you

Simon

Revision history for this message
Simon Andric (simonandric5) wrote :
information type: Private Security → Public
Revision history for this message
Simon Andric (simonandric5) wrote :
Download full text (41.4 KiB)

Application: (plasma-shell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
To enable execution of this file add
 add-auto-load-safe-path /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3903.0-gdb.py
line to your configuration file "/home/fani/.gdbinit".
To completely disable this security protection add
 set auto-load safe-path /
line to your configuration file "/home/fani/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
 info "(gdb)Auto-loading safe path"
[Current thread is 1 (Thread 0x7f6e9378f780 (LWP 2277))]

Thread 32 (Thread 0x7f6e7c2c6700 (LWP 2279)):
#0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1 0x00007f6e8c9e9657 in _L_lock_913 () from /lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007f6e8c9e9480 in __GI___pthread_mutex_lock (mutex=0x1978568) at ../nptl/pthread_mutex_lock.c:79
#3 0x00007f6e90118b98 in _xcb_conn_wait (c=c@entry=0x1978550, cond=cond@entry=0x1978590, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:464
#4 0x00007f6e9011a64f in xcb_wait_for_event (c=0x1978550) at ../../src/xcb_in.c:622
#5 0x00007f6e7e2914f1 in QXcbEventReader::run (this=0x1986a90) at qxcbconnection.cpp:1023
#6 0x00007f6e8dc6652d in QThreadPrivate::start (arg=0x1986a90) at thread/qthread_unix.cpp:345
#7 0x00007f6e8c9e7182 in start_thread (arg=0x7f6e7c2c6700) at pthread_create.c:312
#8 0x00007f6e8d5ebb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 31 (Thread 0x7f6e72015700 (LWP 2298)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007f6e789ee013 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2 0x00007f6e789ed937 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3 0x00007f6e8c9e7182 in start_thread (arg=0x7f6e72015700) at pthread_create.c:312
#4 0x00007f6e8d5ebb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 30 (Thread 0x7f6e71451700 (LWP 2304)):
#0 0x00007f6e8d5de74d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f6e892eed64 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f6e892eee6c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f6e8df4697b in QEventDispatcherGlib::processEvents (this=0x7f6de80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:428
#4 0x00007f6e8decbabe in QEventLoop::processEvents (this=0x7f6e71450e10, flags=...) at kernel/qeventloop.cpp:136
#5 0x00007f6e8decbd89 in QEventLoop::exec (this=0x7f6e71450e10, flags=...) at kernel/qeventloop.cpp:212
#6 0x00007f6e8dc5f298 in QThread::exec (this=0x1aa9340) at thread/qthread.cpp:509
#7 0x00007f6e92aa64ff in QQmlThreadPrivate::run (this=0x1aa9340) at qml/ftw/qqmlthread.cpp:148
#8 0x00007f6e8dc6652d in QThreadPrivate::start (arg=0x1aa9340) at thread/qthread_unix.cpp:345
#9 0x00007f6e8c9e7182 in start_thread (arg=0x7f6e71451700) at pthread_create.c:312
#10 0x00007f6e8d5ebb5d in c...

Revision history for this message
Harald Sitter (apachelogger) wrote :

Please use bugs.kde.org.

Changed in project-neon:
status: New → Invalid
Revision history for this message
Simon Andric (simonandric5) wrote :

thank you for your kind reply!

i did - it is here:

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

nice day :)

Simon

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.