[konsole] [Bug 371776] New: Konsole crash when opening lots of Konsoles
https://bugs.kde.org/show_bug.cgi?id=371776 Bug ID: 371776 Summary: Konsole crash when opening lots of Konsoles Product: konsole Version: 15.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: maar...@treewalker.org Target Milestone: --- Application: konsole (15.12.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was trying to find a way to reproduce bug 369050. I noticed that when I keep starting lots of Konsole instances (between 10 and 100), eventually they all crash during the startup of another instance. However, the backtrace from this crash is different from bug 369050; there seems to be a heap corruption (that's the only way I can explain a crash on malloc, since the system wasn't out of memory). So I don't know whether heap corruption is the root cause for both crashes and just manifests in different ways, or whether it is two separate bugs. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff5ca52f800 (LWP 18579))] Thread 2 (Thread 0x7ff5b6a3c700 (LWP 18580)): #0 QMutex::lock (this=this@entry=0x21688d0) at thread/qmutex.cpp:225 #1 0x7ff5c64afe75 in QMutexLocker::QMutexLocker (m=0x21688d0, this=) at ../../src/corelib/thread/qmutex.h:137 #2 QThreadData::canWaitLocked (this=0x21688a0) at ../../src/corelib/thread/qthread_p.h:253 #3 postEventSourcePrepare (s=0x7ff5b0003600, timeout=timeout@entry=0x7ff5b6a3bbe4) at kernel/qeventdispatcher_glib.cpp:259 #4 0x7ff5bf2f34ad in g_main_context_prepare (context=context@entry=0x7ff5b0001b00, priority=priority@entry=0x7ff5b6a3bc68) at gmain.c:3410 #5 0x7ff5bf2f3d80 in g_main_context_iterate (context=context@entry=0x7ff5b0001b00, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3788 #6 0x7ff5bf2f3f7c in g_main_context_iteration (context=0x7ff5b0001b00, may_block=1) at gmain.c:3869 #7 0x7ff5c64aff4b in QEventDispatcherGlib::processEvents (this=0x7ff5b8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7ff5c645f89b in QEventLoop::exec (this=this@entry=0x7ff5b6a3bda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #9 0x7ff5c62a602a in QThread::exec (this=this@entry=0x7ff5c48e4d00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #10 0x7ff5c467daa5 in QDBusConnectionManager::run (this=0x7ff5c48e4d00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #11 0x7ff5c62aa859 in QThreadPrivate::start (arg=0x7ff5c48e4d00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #12 0x7ff5c0fcd0a4 in start_thread () from /lib64/libpthread.so.0 #13 0x7ff5c9e7502d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff5ca52f800 (LWP 18579)): [KCrash Handler] #6 0x7ff5c9dc50c7 in raise () from /lib64/libc.so.6 #7 0x7ff5c9dc6478 in abort () from /lib64/libc.so.6 #8 0x7ff5c9e02784 in __libc_message () from /lib64/libc.so.6 #9 0x7ff5c9e08026 in malloc_printerr () from /lib64/libc.so.6 #10 0x7ff5c9e082e2 in malloc_consolidate () from /lib64/libc.so.6 #11 0x7ff5c9e08cfb in _int_free () from /lib64/libc.so.6 #12 0x7ff5c646362c in QScopedPointerDeleter::cleanup (pointer=0x7ff5b000d000) at ../../src/corelib/tools/qscopedpointer.h:60 #13 QScopedPointer >::~QScopedPointer (this=, __in_chrg=) at ../../src/corelib/tools/qscopedpointer.h:107 #14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x2153770) at kernel/qcoreapplication.cpp:1646 #15 0x7ff5c6463b68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #16 0x7ff5c64b06e3 in postEventSourceDispatch (s=0x21caff0) at kernel/qeventdispatcher_glib.cpp:276 #17 0x7ff5bf2f3c84 in g_main_dispatch (context=0x7ff5b0002450) at gmain.c:3122 #18 g_main_context_dispatch (context=context@entry=0x7ff5b0002450) at gmain.c:3737 #19 0x7ff5bf2f3ed8 in g_main_context_iterate (context=context@entry=0x7ff5b0002450, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3808 #20 0x7ff5bf2f3f7c in g_main_context_iteration (context=0x7ff5b0002450, may_block=1) at gmain.c:3869 #21 0x7ff5c64aff2c in QEventDispatcherGlib::processEvents (this=0x216c0c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7ff5c645f89b in QEventLoop::exec (this=this@entry=0x
[konsole] [Bug 371776] Konsole crash when opening lots of Konsoles
https://bugs.kde.org/show_bug.cgi?id=371776 --- Comment #1 from Maarten ter Huurne --- Note that for this particular crash, only one Konsole instance crashed, not dozens of them at the same time. So it may not be the same bug after all. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 366004] drkonqi crash when I cancel installation of debug packages
https://bugs.kde.org/show_bug.cgi?id=366004 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org --- Comment #4 from Maarten ter Huurne --- I just had a crash of drkonqi after installation of debug packages seemed to hang and I pressed the Cancel button. It told me in a pop-up that the installation had failed, then immediately after I closed the pop-up it crashed. I'm running drkonqi 5.8.2 on openSUSE 42.1 from the OBS. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371777] New: Memory leak when closing applications?
https://bugs.kde.org/show_bug.cgi?id=371777 Bug ID: 371777 Summary: Memory leak when closing applications? Product: plasmashell Version: 5.8.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: maar...@treewalker.org CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 101847 --> https://bugs.kde.org/attachment.cgi?id=101847&action=edit cat /proc/`pidof plasmashell`/smaps To reproduce: - allow Konsole instances to be grouped - open 100 (or any other big number) instances of Konsole - open top or systemmonitor and sort by memory size - close all Konsole instances by closing the group - watch the memory consumption of plasmashell rise as the Konsole instances exit After repeating this a few times, I have a plasmashell instance that takes up 1.4 GB of memory. I'll attach the output of "cat /proc/`pidof plasmashell`/smaps". It shows 1 GB of memory is occupied by the heap. The strange thing is that the memory consumption rises when closing Konsole instances, not when opening them. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 369050] Konsole crashs randomly.
https://bugs.kde.org/show_bug.cgi?id=369050 --- Comment #16 from Maarten ter Huurne --- I haven't found a reliable way yet to reproduce the crash, but I did observe some things that might be useful. One time Konsole crashed very shortly after a new e-mail came in and the new mail notification was displayed. If I keep opening lots of Konsole instances via a button in the panel, at some point they all crash at the same time. This seems to happen more often if I don't allow Konsole to be grouped in the task bar, but I'm not sure if this is a rule or a coincidence. I have been monitoring the DBUS session and system bus to see if there is any particular type of message that triggers this crash. There was no activity on the system bus when Konsole crashed, but lots of activity on the session bus, so I wasn't able to pin-point any particular message. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 371804] New: Crash when processing DBUS message
https://bugs.kde.org/show_bug.cgi?id=371804 Bug ID: 371804 Summary: Crash when processing DBUS message 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 Target Milestone: --- Application: kmix (4.6) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was scrolling in a web page in Konqueror, not interacting with kmix at all. The crash can be reproduced sometimes. -- Backtrace: Application: KMix (kmix), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f44672a1800 (LWP 12269))] Thread 2 (Thread 0x7f445377c700 (LWP 12270)): #0 0x7f4466b6cbfd in poll () from /lib64/libc.so.6 #1 0x7f445df1de64 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f444c010950, timeout=-1, context=0x7f444c001b00) at gmain.c:4103 #2 g_main_context_iterate (context=context@entry=0x7f444c001b00, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3803 #3 0x7f445df1df7c in g_main_context_iteration (context=0x7f444c001b00, may_block=1) at gmain.c:3869 #4 0x7f44627a6f4b in QEventDispatcherGlib::processEvents (this=0x7f444c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f446275689b in QEventLoop::exec (this=this@entry=0x7f445377bda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f446259d02a in QThread::exec (this=this@entry=0x7f4463d7ad00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x7f4463b13aa5 in QDBusConnectionManager::run (this=0x7f4463d7ad00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #8 0x7f44625a1859 in QThreadPrivate::start (arg=0x7f4463d7ad00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #9 0x7f445eabe0a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f4466b7502d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f44672a1800 (LWP 12269)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/4.8/bits/atomic_base.h:496 #7 QAtomicOps::load (_q_value=...) at ../../src/corelib/arch/qatomic_cxx11.h:103 #8 QBasicAtomicInteger::load (this=0x0) at ../../src/corelib/thread/qbasicatomic.h:99 #9 QtPrivate::RefCount::deref (this=0x0) at ../../src/corelib/tools/qrefcount.h:66 #10 QString::~QString (this=0x7f444c0531e8, __in_chrg=) at ../../src/corelib/tools/qstring.h:1075 #11 QList::node_destruct (this=, to=0x7f444c0531e8, from=0x7f444c013808) at ../../src/corelib/tools/qlist.h:492 #12 QList::dealloc (this=, data=0x7f444c0137c0) at ../../src/corelib/tools/qlist.h:861 #13 QList::~QList (this=, __in_chrg=) at ../../src/corelib/tools/qlist.h:823 #14 0x7f446279bf35 in QStringList::~QStringList (this=0x7f444c0008c0, __in_chrg=) at ../../src/corelib/tools/qstringlist.h:100 #15 v_clear (d=0x7f444c0008c0) at ../../src/corelib/kernel/qvariant_p.h:175 #16 QVariantDestructor<(anonymous namespace)::CoreTypesFilter>::FilteredDestructor::FilteredDestructor (d=0x7f444c0008c0, this=) at ../../src/corelib/kernel/qvariant_p.h:380 #17 QVariantDestructor<(anonymous namespace)::CoreTypesFilter>::delegate (this=) at ../../src/corelib/kernel/qvariant_p.h:406 #18 QMetaTypeSwitcher::switcher > (data=0x0, type=, logic=) at ../../src/corelib/kernel/qmetatypeswitcher_p.h:74 #19 (anonymous namespace)::clear (d=0x7f444c0008c0) at kernel/qvariant.cpp:119 #20 0x7f4463b1636c in QList::node_destruct (this=, to=0x7f444c00e2d8, from=0x7f444c00e2d0) at ../../src/corelib/tools/qlist.h:490 #21 QList::dealloc (data=0x7f444c00e2c0, this=) at ../../src/corelib/tools/qlist.h:861 #22 0x7f4463b2a96b in QDBusMessage::~QDBusMessage (this=, __in_chrg=) at qdbusmessage.cpp:571 #23 0x7f4463b25f9c in QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x7f444c013710, __in_chrg=) at qdbusintegrator_p.h:103 #24 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x7f444c013710, __in_chrg=) at qdbusintegrator_p.h:103 #25 0x7f446275a62c in QScopedPointerDeleter::cleanup (pointer=0x7f444c013710) at ../../src/corelib/tools/qscopedpointer.h:60 #26 QScopedPointer >::~QScopedPointer (this=, __in_chrg=) at ../../src/corelib/tools/qscopedpointer.h:107 #27 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x84bcb0) at kernel/qcoreapplication.cpp:1646 #28 0x7f446275ab68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=eve
[konsole] [Bug 371776] Konsole crash when opening lots of Konsoles
https://bugs.kde.org/show_bug.cgi?id=371776 Maarten ter Huurne changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Maarten ter Huurne --- I ran `for i in $(seq 0 20); do konsole -e 'sleep 3' & done` a dozen times and couldn't trigger any crashes. I have a different PC and a fresh install of openSUSE compared to 2016 though, so I don't know if this means the issue was fixed or my new PC is just not able to reproduce it. In any case, Konsole hasn't crashed for me in ages while I use it every day. So I'll close the bug. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 437853] New: Google calendar refuses invite sent to different mail address
https://bugs.kde.org/show_bug.cgi?id=437853
Bug ID: 437853
Summary: Google calendar refuses invite sent to different mail
address
Product: korganizer
Version: 5.17.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: import/export
Assignee: kdepim-b...@kde.org
Reporter: maar...@treewalker.org
Target Milestone: ---
SUMMARY
I received an invite as an ICS file on my main mail address, which is not a
GMail address. I wanted to add it to my Google Calendar (different account, but
both configured in Kontact), so I could access it from my Android phone.
KOrganizer reported "1 incidence was imported successfully" in a blue bar at
the bottom of the screen. However, the event wasn't added to the calendar.
STEPS TO REPRODUCE
1. Create an ICS file with a non-Google e-mail address as the attendee.
2. Try to add that event to a Google calendar.
OBSERVED RESULT
In the logging of Akonadi, I found this:
org.kde.kgapi: Bad request, Google replied '
"{\"error\":{\"errors\":[{\"domain\":\"calendar\",\"reason\":\"participantIsNeitherOrganizerNorAttendee\",\"message\":\"The
owner of the calendar must either be the organizer or an attendee of an event
that is imported.\"}],\"code\":400,\"message\":\"The owner of the calendar must
either be the organizer or an attendee of an event that is imported.\"}}" '
org.kde.pim.google: Got error: KGAPI2::EventCreateJob(0x564b09f142f0) "Bad
request."
EXPECTED RESULT
Ideally, KOrganizer would rewrite the attendee field to match the e-mail
address that is tied to the calendar, when the attendee is a different mail
identity of the user.
In any case, KOrganizer should not report a successful import when Google's
server rejected the API call.
SOFTWARE/OS VERSIONS
Linux distro: openSUSE Tumbleweed
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 21.04.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[konqueror] [Bug 385119] Focus location bar on startup
https://bugs.kde.org/show_bug.cgi?id=385119 Maarten ter Huurne changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Maarten ter Huurne --- I can no longer reproduce the problem with Konqueror 22.08.3. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 301937] Crash while editing message in Google Groups
https://bugs.kde.org/show_bug.cgi?id=301937 Maarten ter Huurne changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Maarten ter Huurne --- It's likely both khtml and the Google Groups code have changed significantly since 2012, so I'm not going to bother to try to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 320305] Crash while running in the background
https://bugs.kde.org/show_bug.cgi?id=320305 Maarten ter Huurne changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Maarten ter Huurne --- This crash likely depended on particular network traffic or timing; it's not something that I can reproduce even if the bug would still be there. -- 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 Maarten ter Huurne changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Maarten ter Huurne --- This issue doesn't happen anymore for me. I don't remember exactly when it stopped happening though. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 --- Comment #59 from Maarten ter Huurne --- (In reply to Andreas Nordal from comment #58) > Nobody mentioning bracketed paste? I had never heard of it until you mentioned it. I enabled it in ~/.inputrc and now bash indeed waits for an explicit Enter before executing anything. This is awesome! Why isn't this enabled by default in shells and/or readline? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 414086] New: Icon for Atom feed ignored
https://bugs.kde.org/show_bug.cgi?id=414086 Bug ID: 414086 Summary: Icon for Atom feed ignored Product: akregator Version: 5.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: maar...@treewalker.org Target Milestone: --- SUMMARY If I add an Atom feed, the icon at the URL inside tag is not displayed. STEPS TO REPRODUCE 1. Add feed: https://nasauber.de/blog/weblog.xml I borrowed this URL from bug 111507. It looks like the problem described in the third comment of that bug is still present. OBSERVED RESULT A generic icon (globe) is displayed in front of the feed's entry. When I test with my own feeds, the feed's icon URL is not even fetched from the web server. However, a fetch of "/favicon.ico" is attempted (result: 404) by the user agent "Konqueror/5", unlike the feed itself which is fetched by user agent "Akregator/5.12.3". EXPECTED RESULT The feed's icon is displayed in front of the feed's entry. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.1 (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Some Atom feeds do display icons for me, but I suspect these are loaded using the hardcoded "/favicon.ico" URL instead of from the URL in the tag. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 414086] Icon for Atom feed ignored
https://bugs.kde.org/show_bug.cgi?id=414086 Maarten ter Huurne changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 414086] Icon for Atom feed ignored
https://bugs.kde.org/show_bug.cgi?id=414086 --- Comment #2 from Maarten ter Huurne --- Awesome! -- 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 --- Comment #12 from Maarten ter Huurne --- The LANG environment variable assumes that the user will always want the application language and the regional settings to match. This assumption is wrong for people who prefer application language to be English and regional settings from their own country. In particular computer-savvy people who know all the terminology in English but may find the translated terminology confusing. My estimate would be that a lot of KDE users who are not native English speakers fall into this category. So please... don't set LANG. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387393] akonadiserver 17.08.03 crashed during idle
https://bugs.kde.org/show_bug.cgi?id=387393 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 398571] New: akonadiserver assert on realloc
https://bugs.kde.org/show_bug.cgi?id=398571 Bug ID: 398571 Summary: akonadiserver assert on realloc Product: Akonadi Version: 5.7.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: maar...@treewalker.org Target Milestone: --- Created attachment 114929 --> https://bugs.kde.org/attachment.cgi?id=114929&action=edit crash report from drkonqi I had Kontact open with the KMail module enabled, but Akregator was the currently focused module. I wasn't interacting with Kontact at all, in fact I wasn't even behind the PC when the crash happened. At first glance this backtrace looks a lot like the one from the bug I marked as possible duplicate, but I'll leave the final judgement on that to someone more familiar with the code. The system wasn't low on memory, so that wouldn't be a reason for realloc to fail. (drkonqi failed to submit this bug because the backtrace took the comments over 64 kB and bugzilla refused to accept the report; please fix this as it's been a pain for years and is probably causing you to miss out on useful bug reports) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 398571] akonadiserver assert on realloc
https://bugs.kde.org/show_bug.cgi?id=398571 --- Comment #1 from Maarten ter Huurne --- Possible duplicate of bug 387393. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 248807] Report with a long backtrace can't be sent (bugzilla 65k limit per comment)
https://bugs.kde.org/show_bug.cgi?id=248807 --- Comment #15 from Maarten ter Huurne --- (In reply to Alexander Mentyu from comment #14) > Possible solutions: > 1. Add option to paste whole backtrace in paste.kde.org service and insert > link into description. > 2. Add option to paste whole backtrace in attachment. > 3. Paste beginning of backtrace in attachment/paste.kde.org and rest with > max available characters in description/comment. A variation of option 3: 4. Put the backtrace of the crashed thread in the comment and attach the backtrace of all threads. I think in most cases only the backtrace of the thread that actually crashed is relevant, but for the few cases where other threads are relevant, it would be nice to have access to the full backtrace dump. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387393] akonadiserver 17.08.03 crashed during idle
https://bugs.kde.org/show_bug.cgi?id=387393 --- Comment #6 from Maarten ter Huurne --- Created attachment 114970 --> https://bugs.kde.org/attachment.cgi?id=114970&action=edit New crash information added by DrKonqi akonadiserver (5.7.3) using Qt 5.9.4 - What I was doing when the application crashed: I wasn't interacting with akonadi at all when it crashed. It might have been fetching mail in the background. Kontact was open. I never had this problem until I few days ago, but now there are two crashes. I wonder if this is a coincidence or a recent change increased the chance of this crash occurring. The last system (openSUSE Leap 15) update on 2018-09-12 installed the following packages: nvidia-gfxG04-kmp-default|390.87_k4.12.14_lp150.11-lp150.10.1|x86_64 nvidia-glG04|390.87-lp150.10.1|x86_64 nvidia-computeG04|390.87-lp150.10.1|x86_64 x11-video-nvidiaG04|390.87-lp150.10.1|x86_64 discover|5.12.6-lp150.2.3.1|x86_64 kde-user-manager|5.12.6-lp150.2.3.1|x86_64 kinfocenter5|5.12.6-lp150.3.3.1|x86_64 kscreen5|5.12.6-lp150.2.3.1|x86_64 kscreenlocker|5.12.6-lp150.2.3.1|x86_64 libKScreenLocker5|5.12.6-lp150.2.3.1|x86_64 libksysguard5|5.12.6-lp150.2.3.1|x86_64 libksysguard5-helper|5.12.6-lp150.2.3.1|x86_64 metatheme-breeze-common|5.12.6-lp150.2.3.1|x86_64 milou5|5.12.6-lp150.2.3.1|x86_64 plasma-nm5|5.12.6-lp150.3.3.1|x86_64 plasma5-addons|5.12.6-lp150.2.3.1|x86_64 plasma5-integration-plugin|5.12.6-lp150.2.3.1|x86_64 discover-lang|5.12.6-lp150.2.3.1|noarch kde-user-manager-lang|5.12.6-lp150.2.3.1|noarch kinfocenter5-lang|5.12.6-lp150.3.3.1|noarch kscreen5-lang|5.12.6-lp150.2.3.1|noarch kscreenlocker-lang|5.12.6-lp150.2.3.1|noarch kwin5|5.12.6-lp150.2.3.1|x86_64 libksysguard5-lang|5.12.6-lp150.2.3.1|noarch gtk3-metatheme-breeze|5.12.6-lp150.2.3.1|noarch milou5-lang|5.12.6-lp150.2.3.1|noarch plasma-nm5-lang|5.12.6-lp150.3.3.1|noarch plasma5-addons-lang|5.12.6-lp150.2.3.1|noarch plasma5-integration-plugin-lang|5.12.6-lp150.2.3.1|noarch kwin5-lang|5.12.6-lp150.2.3.1|noarch plasma5-workspace-libs|5.12.6-lp150.2.3.1|x86_64 ksysguard5|5.12.6-lp150.2.3.1|x86_64 gtk2-metatheme-breeze|5.12.6-lp150.2.3.1|noarch plasma-nm5-pptp|5.12.6-lp150.3.3.1|x86_64 plasma-nm5-openvpn|5.12.6-lp150.3.3.1|x86_64 plasma-nm5-openconnect|5.12.6-lp150.3.3.1|x86_64 plasma5-workspace|5.12.6-lp150.2.3.1|x86_64 khotkeys5|5.12.6-lp150.2.3.1|x86_64 ksysguard5-lang|5.12.6-lp150.2.3.1|noarch plasma5-workspace-lang|5.12.6-lp150.2.3.1|noarch khotkeys5-lang|5.12.6-lp150.2.3.1|noarch plasma5-desktop|5.12.6-lp150.3.3.1|x86_64 plasma5-desktop-lang|5.12.6-lp150.3.3.1|noarch plasma5-session|5.12.6-lp150.2.3.1|noarch plasma5-session-wayland|5.12.6-lp150.2.3.1|noarch While there are several KDE packages in that list, I don't think akonadiserver would depends on the listed packages. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f30d3ea26c1 in __GI_abort () at abort.c:79 [...] #9 0x7f30d3eeac43 in malloc_printerr (action=, str=0x7f30d3fed5d8 "double free or corruption (!prev)", ptr=, ar_ptr=) at malloc.c:5428 #10 0x7f30d3eec549 in _int_free (av=av@entry=0x7f30d421fc20 , p=, p@entry=0x564dce831ce0, have_lock=have_lock@entry=1) at malloc.c:4170 #11 0x7f30d3eef250 in _int_realloc (av=av@entry=0x7f30d421fc20 , oldp=oldp@entry=0x564dce831ce0, oldsize=oldsize@entry=4128, nb=8208) at malloc.c:4676 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 383003] New: Crash in mail filter agent
https://bugs.kde.org/show_bug.cgi?id=383003 Bug ID: 383003 Summary: Crash in mail filter agent Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Mail Filter Agent Assignee: kdepim-b...@kde.org Reporter: maar...@treewalker.org Target Milestone: --- Application: akonadi_mailfilter_agent (4.14) KDE Platform Version: 4.14.25 Qt Version: 4.8.6 Operating System: Linux 4.4.73-18.17-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I was going through my spam box and found a few mails that shouldn't have been flagged as spam. So I created new filter rules to make sure mails from those senders would never be put in the spam box. Then I applied the filters to them using Ctrl-J. The crash can be reproduced sometimes. -- Backtrace: Application: Mail Filter Agent (akonadi_mailfilter_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f52065e3d27 in MailCommon::SearchPattern::asString() const (this=0x699f058) at /usr/include/QtCore/qlist.h:102 #7 0x7f52065e3d27 in MailCommon::SearchPattern::asString() const (this=0x699f058) at /usr/include/QtCore/qlist.h:272 #8 0x7f52065e3d27 in MailCommon::SearchPattern::asString() const (this=0x699f058) at /usr/src/debug/kdepim-4.14.10/mailcommon/search/searchpattern.cpp:290 #9 0x0040fbe0 in FilterManager::Private::isMatching(Akonadi::Item const&, MailCommon::MailFilter const*) (this=, item=..., filter=filter@entry=0x699f050) at /usr/src/debug/kdepim-4.14.10/agents/mailfilteragent/filtermanager.cpp:245 #10 0x004129aa in FilterManager::process(QList const&, Akonadi::Item const&, bool, FilterManager::FilterSet, bool, QString const&) (this=0xebeda0, mailFilters=..., item=..., needsFullPayload=needsFullPayload@entry=true, set=set@entry=FilterManager::Explicit, account=account@entry=false, accountId=...) at /usr/src/debug/kdepim-4.14.10/agents/mailfilteragent/filtermanager.cpp:508 #11 0x0041301d in FilterManager::Private::slotItemsFetchedForFilter(QList const&) (this=0xeef850, items=...) at /usr/src/debug/kdepim-4.14.10/agents/mailfilteragent/filtermanager.cpp:131 #12 0x004152ad in FilterManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _id=, _a=, _c=) at /usr/src/debug/kdepim-4.14.10/build/agents/mailfilteragent/moc_filtermanager.cpp:76 #13 0x7f5205ee50ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #14 0x7f5204d04122 in Akonadi::ItemFetchJob::itemsReceived(QList const&) (this=this@entry=0x45201c0, _t1=...) at /usr/src/debug/kdepimlibs-4.14.10/build/akonadi/moc_itemfetchjob.cpp:114 #15 0x7f5204d059bb in Akonadi::ItemFetchJobPrivate::aboutToFinish() (this=) at /usr/src/debug/kdepimlibs-4.14.10/akonadi/itemfetchjob.cpp:79 #16 0x7f5204d059bb in Akonadi::ItemFetchJobPrivate::aboutToFinish() (this=) at /usr/src/debug/kdepimlibs-4.14.10/akonadi/itemfetchjob.cpp:69 #17 0x7f5204d1801b in Akonadi::JobPrivate::delayedEmitResult() (this=) at /usr/src/debug/kdepimlibs-4.14.10/akonadi/job.cpp:164 #18 0x7f5205ee948e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #19 0x7f5202e9a6fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #20 0x7f5202ea0c3d in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #21 0x7f5204076e3a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #22 0x7f5205ed117d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #23 0x7f5205ed444d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #24 0x7f5205efe7ee in () at /usr/lib64/libQtCore.so.4 #25 0x7f51feeef134 in g_main_context_dispatch (context=0xb94240) at gmain.c:3154 #26 0x7f51feeef134 in g_main_context_dispatch (context=context@entry=0xb94240) at gmain.c:3769 #27 0x7f51feeef388 in g_main_context_iterate (context=context@entry=0xb94240, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3840 #28 0x7f51feeef42c in g_main_context_iteration (context=0xb94240, may_block=1) at gmain.c:3901 #29 0x7f5205efdfae in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #30 0x7f5202f37606 in () at /usr/lib64/libQtGui.so.4 #31 0x7f5205ecfd3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #32 0x7f5205ed0035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #33 0x7f5205ed5489 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #34 0x7f5204c586a3 in Akonadi::AgentBase::init(Akonadi::
[kate] [Bug 302096] Crash while deleting lines
https://bugs.kde.org/show_bug.cgi?id=302096 Maarten ter Huurne changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Maarten ter Huurne --- I don't have a way to reproduce it and the backtrace is 6 years old now, so I'll close it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385117] New: Python indentation indents too often since recent update
https://bugs.kde.org/show_bug.cgi?id=385117 Bug ID: 385117 Summary: Python indentation indents too often since recent update Product: kate Version: 17.08.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: maar...@treewalker.org Target Milestone: --- I've been using Kate with Python projects for a long time, but since a recent update it hasn't been functioning well. The problem is that it will often indent a line to line up with the line above it. For languages like C this would be desired, but since in Python the end of a block is identified by the indentation level decreasing, an editor should never change the indentation of an existing line, since it changes the meaning of the code being edited. For example, if I start with this code fragment: if x == 0: foo() y = x and I then add "+ 1" to the third line, Kate will indent it like this: if x == 0: foo() y = x + 1 which incorrectly pulls the third line into the if's body. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 385119] New: Focus location bar on startup
https://bugs.kde.org/show_bug.cgi?id=385119 Bug ID: 385119 Summary: Focus location bar on startup Product: konqueror Version: 5.0.97 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: maar...@treewalker.org Target Milestone: --- When Konqueror 4.x opened a new window, I could immediately start typing a URL or web shortcut in the location bar. With Konqueror 5.x, I have to hit F6 first, to put the input focus on the location bar. Given how often I open a browser window on the average day, it would really help me if the locaton bar would be automatically focused again. Maybe not for all URLs, but at least for "about:" and "about:blank". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385117] Python indentation indents too often since recent update
https://bugs.kde.org/show_bug.cgi?id=385117 --- Comment #3 from Maarten ter Huurne --- I did test that exact fragment in Kate when I filed the bug. However, when I try to reproduce it now, Kate doesn't indent the third line. So there must be some yet unknown factor that makes this bad indentation trigger. I created the fragment inside the larger source file that I was editing at that moment, so it is possible either the context is relevant or some unseen state in Kate matters. The indent happened when I typed the '+', so not one of the letters mentioned in the other bug. I expect the problem will occur again, since it wasn't the first time it happened when I filed the bug. When it does, I'll try to figure out what is relevant about the context or state to be able to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 374420] Various kioslaves do not write correct dates
https://bugs.kde.org/show_bug.cgi?id=374420 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org --- Comment #2 from Maarten ter Huurne --- I'm seeing 2106-02-07 07:28 pop up a lot lately, after switching Konqueror and KDE PIM to KDE5. For example, files downloaded from Konqueror and some entries in my Akregator feeds. I'm using KDE Frameworks 5.38.0 from openSUSE. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 266673] Crash after clicking systray icon
https://bugs.kde.org/show_bug.cgi?id=266673 Maarten ter Huurne changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 from Maarten ter Huurne --- This is not a bug I'd be able to reproduce: it's something that happened one time and I submitted it in the hope the backtrace would be useful. But by now the code would have changed so much that investigating the backtrace is probably not worth the effort. I'll close the bug. -- 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
[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.
[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.
[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.
[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.
[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.
