[konsole] [Bug 369050] Konsole crashs randomly.
https://bugs.kde.org/show_bug.cgi?id=369050 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org --- Comment #2 from Maarten ter Huurne --- I had a crash of Konsole today with a very similar backtrace. However, I had seen that backtrace before, when kmix crashed, which I reported as bug 370650. So I think it's a problem in a library rather than in Konsole itself, but I don't know which library to file it on. Application: konsole (15.12.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" Thread 1 (Thread 0x7ff55aef1800 (LWP 2888)): [KCrash Handler] #6 0x7ff55a7870c7 in raise () from /lib64/libc.so.6 #7 0x7ff55a788478 in abort () from /lib64/libc.so.6 #8 0x7ff556c57c7e in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1680 #9 QMessageLogger::fatal (this=this@entry=0x7ffe718dfcb0, msg=msg@entry=0x7ff5550907b0 "Internal error: got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") at global/qlogging.cpp:793 #10 0x7ff5550497f4 in QDBusConnectionPrivate::deliverCall (this=0x7ff5400039c0, object=0x2562680, msg=..., metaTypes=..., slotIdx=11) at qdbusintegrator.cpp:948 #11 0x7ff556e4cdc6 in QObject::event (this=0x2562680, e=) at kernel/qobject.cpp:1263 #12 0x7ff557adaa9c in QApplicationPrivate::notify_helper (this=, receiver=0x2562680, e=0x7ff54000c230) at kernel/qapplication.cpp:3799 #13 0x7ff557ae1a20 in QApplication::notify (this=0x7ffe718e0470, receiver=0x2562680, e=0x7ff54000c230) at kernel/qapplication.cpp:3556 #14 0x7ff556e235c5 in QCoreApplication::notifyInternal2 (receiver=0x2562680, event=event@entry=0x7ff54000c230) at kernel/qcoreapplication.cpp:988 #15 0x7ff556e25623 in QCoreApplication::sendEvent (event=0x7ff54000c230, receiver=) at kernel/qcoreapplication.h:231 #16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x2217eb0) at kernel/qcoreapplication.cpp:1649 #17 0x7ff556e25b68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #18 0x7ff556e726e3 in postEventSourceDispatch (s=0x229c3c0) at kernel/qeventdispatcher_glib.cpp:276 #19 0x7ff54fcb5c84 in g_main_dispatch (context=0x7ff540002450) at gmain.c:3122 #20 g_main_context_dispatch (context=context@entry=0x7ff540002450) at gmain.c:3737 #21 0x7ff54fcb5ed8 in g_main_context_iterate (context=context@entry=0x7ff540002450, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3808 #22 0x7ff54fcb5f7c in g_main_context_iteration (context=0x7ff540002450, may_block=1) at gmain.c:3869 #23 0x7ff556e71f2c in QEventDispatcherGlib::processEvents (this=0x222df80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #24 0x7ff556e2189b in QEventLoop::exec (this=this@entry=0x7ffe718e0330, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #25 0x7ff556e29696 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #26 0x7ff55ab22e87 in kdemain () from /usr/lib64/libkdeinit5_konsole.so #27 0x7ff55a773b25 in __libc_start_main () from /lib64/libc.so.6 #28 0x004007ee in _start () -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #6 from Maarten ter Huurne --- I had a crash of Konsole with a very similar backtrace (also "Internal error: got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") and found bug 369050, which reports what looks like the same problem. So I think it's a bug in a library rather than the application, but I don't know which package it should be filed on. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #4 from Maarten ter Huurne --- (In reply to Jeff Hodd from comment #3) > Please let me know if this should be filed as a new bug for korgac vs. kmix. > It's certainly very possible that the issue is related to session management > and is not necessarily application-specific. Looking at the backtraces, I think it's a different issue: the cause of the crash is different (abort vs segfault) and the functions on the stack are different as well (event vs disconnect). So please open a separate bug report for it. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] New: Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 Bug ID: 370650 Summary: Crash on session restore Product: kmix Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: es...@kde.org Reporter: maar...@treewalker.org Application: kmix (4.6) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I have kmix running all the time. In the past this meant that it would get automatically started as part of the session restore. However, since a few months, kmix won't restore for some reason. Today I noticed an icon that indicated that kmix had crashed. I think it may also have crashed those other times it didn't start, but either I didn't notice or crash reporting for system tray apps didn't exist or work back then. I didn't interact with kmix in any way during the session restore. For example, I didn't press any media keys like volume +/- on my keyboard. The crash can be reproduced every time. -- Backtrace: Application: KMix (kmix), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0b44765800 (LWP 2535))] Thread 3 (Thread 0x7f0b297eb700 (LWP 2537)): #0 0x7f0b44030bfd in poll () from /lib64/libc.so.6 #1 0x7f0b3a1b8422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f0b3a1ba00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f0b2bd4e469 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f0b3fa65859 in QThreadPrivate::start (arg=0xaea0d0) at thread/qthread_unix.cpp:344 #5 0x7f0b3bf820a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f0b4403902d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0b30c40700 (LWP 2536)): #0 0x7f0b4402cccd in read () from /lib64/libc.so.6 #1 0x7f0b3562b073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.44 #2 0x7f0b3b422b60 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0b3b3e1999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7f0b3b3e1df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f0b3b3e1f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f0b3fc6af4b in QEventDispatcherGlib::processEvents (this=0x7f0b2c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f0b3fc1a89b in QEventLoop::exec (this=this@entry=0x7f0b30c3fda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #8 0x7f0b3fa6102a in QThread::exec (this=this@entry=0x7f0b4123ed00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #9 0x7f0b40fd7aa5 in QDBusConnectionManager::run (this=0x7f0b4123ed00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #10 0x7f0b3fa65859 in QThreadPrivate::start (arg=0x7f0b4123ed00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #11 0x7f0b3bf820a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7f0b4403902d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0b44765800 (LWP 2535)): [KCrash Handler] #6 0x7f0b43f890c7 in raise () from /lib64/libc.so.6 #7 0x7f0b43f8a478 in abort () from /lib64/libc.so.6 #8 0x7f0b3fa50c7e in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1680 #9 QMessageLogger::fatal (this=this@entry=0x7fff5f39f0c0, msg=msg@entry=0x7f0b410287b0 "Internal error: got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") at global/qlogging.cpp:793 #10 0x7f0b40fe17f4 in QDBusConnectionPrivate::deliverCall (this=0x7f0b2c0039c0, object=0xea5830, msg=..., metaTypes=..., slotIdx=10) at qdbusintegrator.cpp:948 #11 0x7f0b3fc45dc6 in QObject::event (this=0xea5830, e=) at kernel/qobject.cpp:1263 #12 0x7f0b408d3a9c in QApplicationPrivate::notify_helper (this=, receiver=0xea5830, e=0x7f0b2c015e00) at kernel/qapplication.cpp:3799 #13 0x7f0b408daa20 in QApplication::notify (this=0xab2010, receiver=0xea5830, e=0x7f0b2c015e00) at kernel/qapplication.cpp:3556 #14 0x7f0b3fc1c5c5 in QCoreApplication::notifyInternal2 (receiver=0xea5830, event=event@entry=0x7f0b2c015e00) at kernel/qcoreapplication.cpp:988 #15 0x7f0b3fc1e623 in QCoreApplication::sendEvent (event=0x7f0b2c015e00, receiver=) at kernel/qcoreapplication.h:231 #16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xa9e470) at kernel/qcoreapplication.cpp:1649 #17 0x7f0b3fc1eb68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #18 0x7f0b3fc6b6e3 in postEve
[konqueror] [Bug 361385] Konqueror crash using host libthread_db library "/lib64/libthread_db.so.1"
https://bugs.kde.org/show_bug.cgi?id=361385 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org --- Comment #1 from Maarten ter Huurne --- I had a very similar problem. It didn't happen if I started konqueror with an empty home directory, so I reduced the home dir contents until I found the culprit: ~/.cache/gstreamer-1.0/registry.x86_64.bin. You could try to remove that file and see if it solves the problem for you as well. For me the problem started happening after I updated gstreamer, using packages from Packman instead of the openSUSE project. So I don't know if the problem is the new version or that the gstreamer build was configured differently, but it might be one of those two. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344588] 'Regional Setting - Formats - Region' setting behaves unexpected
https://bugs.kde.org/show_bug.cgi?id=344588 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org --- Comment #10 from Maarten ter Huurne --- I'm running into the same problem: in KDE's settings, under Translations I set Preferred Languages: American English, while under Formats I set Region: Nederland - Nederlands (nl_NL). However, I get Dutch output from some programs now, for example Make. As Dennis wrote, the cause seems to be ~/.config/plasma-locale-settings.sh which sets LANG to nl_NL. If I unset LANG, Make returns to printing English messages. POSIX.1-2008 describes LANG as: This variable shall determine the locale category for native language, local customs, and coded character set in the absence of the LC_ALL and other LC_* (LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, LC_TIME) environment variables. This can be used by applications to determine the language to use for error messages and instructions, collating sequences, date formats, and so on. Since this definition mixes up language and regional settings, which should be two entirely separate things, in my opinion it's best to not set LANG at all. -- You are receiving this mail because: You are watching all bug changes.
