Discussion:
[BalooWidgets] [Bug 378661] New: Baloo Crash on boot from sleep mode
b***@kde.org
2017-04-11 13:28:07 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=378661

Bug ID: 378661
Summary: Baloo Crash on boot from sleep mode
Product: BalooWidgets
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: ***@gmail.com
Reporter: ***@gmail.com
Target Milestone: ---

Created attachment 104966
--> https://bugs.kde.org/attachment.cgi?id=104966&action=edit
BackTrace report of crash

Initial crash I believe occurred some days ago when using the network manager
to connect to a new netgear wireless router
--
You are receiving this mail because:
You are watching all bug changes.
Christoph Feck
2017-04-21 02:12:54 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=378661

Christoph Feck <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|general |Baloo File Daemon
Product|BalooWidgets |frameworks-baloo
--
You are receiving this mail because:
You are watching all bug changes.
Nate Graham
2018-11-26 20:26:57 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=378661

Nate Graham <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
CC| |***@kde.org
Resolution|--- |WAITINGFORINFO

--- Comment #1 from Nate Graham <***@kde.org> ---
Strange crash:

Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb26f5780 (LWP 1380))]

Thread 2 (Thread 0xb231ab40 (LWP 1392)):
#0 0xb7785be0 in __kernel_vsyscall ()
#1 0xb5a063db in poll () at ../sysdeps/unix/syscall-template.S:81
#2 0xb56d63a8 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#3 0xb56d8394 in xcb_wait_for_event () from
/usr/lib/i386-linux-gnu/libxcb.so.1
#4 0xb24477d3 in QXcbEventReader::run (this=0x84302b8) at
qxcbconnection.cpp:1105
#5 0xb5c7f7eb in QThreadPrivate::start (arg=0x84302b8) at
thread/qthread_unix.cpp:337
#6 0xb59101aa in start_thread (arg=0xb231ab40) at pthread_create.c:333
#7 0xb5a10fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 1 (Thread 0xb26f5780 (LWP 1380)):
[KCrash Handler]
#7 __GI___libc_free (mem=0xffc900) at malloc.c:2933
#8 0xb238a3a7 in xkb_keymap_unref () from
/usr/lib/i386-linux-gnu/libxkbcommon.so.0
#9 0xb238b9cb in xkb_state_unref () from
/usr/lib/i386-linux-gnu/libxkbcommon.so.0
#10 0xb244bfae in QXcbKeyboard::updateKeymap (this=0x8431ce0) at
qxcbkeyboard.cpp:736
#11 0xb244722c in QXcbConnection::handleXcbEvent (this=0x8422a58,
event=0xb1a0ba28) at qxcbconnection.cpp:988
#12 0xb2447a50 in QXcbConnection::processXcbEvents (this=0x8422a58) at
qxcbconnection.cpp:1303
#13 0xb2473581 in QXcbConnection::qt_static_metacall (_o=<optimized out>,
_id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at
.moc/moc_qxcbconnection.cpp:185
#14 0xb5edb590 in QMetaCallEvent::placeMetaCall (this=0xb1a0bc78,
object=0x8422a58) at kernel/qobject.cpp:485
#15 0xb5eded03 in QObject::event (this=0x8422a58, e=0xb1a0bc78) at
kernel/qobject.cpp:1245
#16 0xb2447f59 in QXcbConnection::event (this=0x8422a58, e=0xb1a0bc78) at
qxcbconnection.cpp:1916
#17 0xb67ae82a in QApplicationPrivate::notify_helper (this=0x841c378,
receiver=0x8422a58, e=0xb1a0bc78) at kernel/qapplication.cpp:3720
#18 0xb67b4081 in QApplication::notify (this=0xbfba38d4, receiver=0x8422a58,
e=0xb1a0bc78) at kernel/qapplication.cpp:3503
#19 0xb5eaab8a in QCoreApplication::notifyInternal (this=0xbfba38d4,
receiver=0x8422a58, event=0xb1a0bc78) at kernel/qcoreapplication.cpp:935
#20 0xb5eace7c in sendEvent (event=0xb1a0bc78, receiver=0x8422a58) at
kernel/qcoreapplication.h:228
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x841ae10) at kernel/qcoreapplication.cpp:1552
#22 0xb5ead597 in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1410
#23 0xb5f065d3 in postEventSourceDispatch (s=0x8443580) at
kernel/qeventdispatcher_glib.cpp:271
#24 0xb4ac4d64 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#25 0xb4ac5089 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#26 0xb4ac5156 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#27 0xb5f069e4 in QEventDispatcherGlib::processEvents (this=0x84437c0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#28 0xb2474611 in QPAEventDispatcherGlib::processEvents (this=0x84437c0,
flags=...) at eventdispatchers/qeventdispatcher_glib.cpp:115
#29 0xb5ea7d93 in QEventLoop::processEvents (this=0xbfba37f8, flags=...) at
kernel/qeventloop.cpp:128
#30 0xb5ea81fa in QEventLoop::exec (this=0xbfba37f8, flags=...) at
kernel/qeventloop.cpp:204
#31 0xb5eb0315 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#32 0xb61e5a41 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#33 0xb67a9da4 in QApplication::exec () at kernel/qapplication.cpp:2956
#34 0x0805b6c4 in main (argc=1, argv=0xbfba3a74) at
../../../src/file/main.cpp:101



Can you reproduce this? Has it happened since originally reported?
--
You are receiving this mail because:
You are watching all bug changes.
Bug Janitor Service
2018-12-11 03:44:17 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=378661

--- Comment #2 from Bug Janitor Service <bug-***@kde.org> ---
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!
--
You are receiving this mail because:
You are watching all bug changes.
Loading...