[konsole] [Bug 431337] konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus
https://bugs.kde.org/show_bug.cgi?id=431337 --- Comment #23 from Bill Wayson --- Thanks, Bings. Yes, please restore the ability to control the visibility of profiles in menus. It's my personal preferences, but I don't care for the color choices of the built-in "Default" or the supplied "Root Shell" profiles. I've created my own profiles which are the only ones I wish to see in the Konsole menus. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 431337] konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus
https://bugs.kde.org/show_bug.cgi?id=431337 --- Comment #17 from Bill Wayson --- That we use profiles similarly to PuTTY profiles is a good way to put it. Is there anything available that describes your or KDE's intent for konsole profiles? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 431337] konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus
https://bugs.kde.org/show_bug.cgi?id=431337 --- Comment #15 from Bill Wayson --- @tcanabrava, I apologize for the delay. Thank you for considering our situations. I have only three custom profiles. They are just clones of built-in profiles: the Root Shell profile and the Default profile. The latter, I use for normal command line stuff, the former for root stuff. The main customization is in the Appearance: I changed the Color scheme & font to Black on Random Light, because that is what I like. My custom Root Shell profile is also called Root Shell (I know I could name it something else, but it is my root-privileges shell), but I rename my custom Defaut profile to "Shell" (for "normal user" shell). These are my only customizations of these two profiles. The third, also a clone of the Default, is specific for ssh-ing to a NAS of mine. It uses the Green on Black color scheme to make the window contents easier to see when I am ssh-ed to the NAS. Under the old konsole behavior (and the current behavior for version 20.04.2), once I create my normal-user Shell profile (and make it the default profile? -- which I do), a profile named Default no longer appears. So, the only issue is that I now have two profiles named Root Shell. When both are visible, they are ordered in menus randomly. Sometimes mine is first, sometimes it is second. Because of this, and because I don't ever want to use the built-in Root Shell white background, I hide it. Now, I can see and use only my custom R.S. profile, which is what I want to do. The new konsole behavior adds a new complication. Even though my custom Shell profile was set as the default (that setting has gone away, too, but my Shell profile still acts as the default), I now see a Default profile in menus along with my Shell profile. Similar to my desires above for the two Root Shell profiles, I don't want to ever use the built-in Default profile. So having it and both built-in Root Shell profiles appearing in the menus (and the two Root Shell profiles are still ordered randomly, so its a crap shoot as to which one I get when I pick one) is an annoyance. Being able to select which profiles to appear in the menus removes that annoyance. I am not going to throw myself on my sword over this. But I would like to see the user choices of visibility and setting the default profile returned. And, I can see that EB's and Marcin's issue is more than just an annoyance. Thank you again for all the work you do on konsole -- I really appreciate it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 431337] konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus
https://bugs.kde.org/show_bug.cgi?id=431337 --- Comment #9 from Bill Wayson --- I, like EB, would like this to be an issue and that the old visibility option and behavior be restored. The current behavior under openSUSE Tumbleweed is less that optimal. EB's use case is an even stonger one to bring back the previous behavior. Many other applications, including KDE's, allow users to customize them, often easily through their UIs. For example, I can enable and disable Plasma's desktop effects using checkboxes. Many effects are installed by default, but I don't necessarily want them all to be activated. Almost universally, such user customizations are stored in files under their home directory, and many are plain text files. Certainly, the user could modify them and introduce "bugs," but that is on them. If this is such a serious issue with Konsole, as suggested in comment 6, perhaps Konsole could run a lint-like sanity check of a user's profiles on startup and deal appropriately with any errors found. I am not a fan of modifying defaults if such defaults are implemented in protected areas (e.g. the program itself or files under /usr). Unless I am missing something, the easiest way to restore the behavior (i.e. fix the bug) is to have Konsole honor the "Favorites" line in the "Favorite Profiles" section that still exists in ~/.config/konsolerc (and IS still honored by the Konsole Profiles plasma widget). The other options offered seem to be too round-about and complicated, especially when compared to behavior that worked so simply up until now. So, +1 from me: bring back the visibility checkboxes and behavior in konwole. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 431337] konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus
https://bugs.kde.org/show_bug.cgi?id=431337 --- Comment #5 from Bill Wayson --- Possibly, Nate. User modifications would need to survive updates to konsole -- a problem with modifying the built-in Root Shell.profile file. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 431337] konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus
https://bugs.kde.org/show_bug.cgi?id=431337 --- Comment #3 from Bill Wayson --- My use case (i.e. why the old behavior is better for me) is that I don't want to use or see the builtin Default profile (which seems to be built in to konsole and not a separate profile file) and I want to only see my modified Root Shell profile. The two profiles I now see but don't want to are those that come packaged with konsole. I know that, as root, I could modify the delivered Root Shell.profile file to implement my modifications, but that seems to me to contradict keeping personalizations personal and not global. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 431337] New: konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus
https://bugs.kde.org/show_bug.cgi?id=431337 Bug ID: 431337 Summary: konsole Profile Visibility Can No Longer Be Controlled, and More Of Them Appear in Menus Product: konsole Version: 20.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: bill_way...@yahoo.com Target Milestone: --- Created attachment 134667 --> https://bugs.kde.org/attachment.cgi?id=134667&action=edit Comparison of konsole's profile-related behavior between v20.12.0 and v20.04.2 SUMMARY After a TW update around the weekend of December 19, 2020, konsole (at version 20.12.0 as of January 8, 2021) lost the ability to set the visibility of its profiles in konsole's menus (e.g. File -> New Tab). At the same time, a larger number of profiles appears in its menus. STEPS TO REPRODUCE 1. Ensure that konsole (and konsole-part) is at version 20.12.0 2. Run konsole and expose the menubar 3. Select Settings -> Manage Profiles... OBSERVED RESULT In the list of profiles, there is no "eye" column to control visibility in konsole menus (e.g. File -> New Tab). I have looked in vain for a replacement for this functionality. EXPECTED RESULT A column in the list of profiles (or some other way in the GUI) where I can elect to make a profile visible or not in konsole menus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.10.4; openSUSE Tumbleweed 20210106 (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This has been reported to openSUSE (https://bugzilla.opensuse.org/show_bug.cgi?id=1180343). I have attached a zip file showing some konsole profile-related differences between TW (konsole is at version 20.12.0 as of January 8, 2021) and Leap 15.2 (konsole is at version 20.04.2 as of January 8, 2021). The konsole_*-manage_profiles pictures show that the visibility "eye" column no longer appears and TW shows the correct number of profiles (three I created and the default Root Shell profile). Similarly, the konsole_*-new_tab and konsole_*-switch_profile pictures show the strange menu differences between the two OSes. (As an aside, the problem switching profiles using the shown menu in TW was fixed a week or so ago.) The "Favorite Profiles" section of ~/.config/konsolerc looks correct to me, and it is the same in both OSes. I'm happy to provide any additional information, files, etc., if requested. The list of profiles in the Konsole Profiles Plasma widget is correct in TW. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 384165] Plasma5 Crash after Updating System with Update Plugin
https://bugs.kde.org/show_bug.cgi?id=384165 Bill Wayson changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #11 from Bill Wayson --- Sorry - I did not know I needed to change the status. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 383217] Kontact Crash Upon Closing Kontact
https://bugs.kde.org/show_bug.cgi?id=383217 Bill Wayson changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Bill Wayson --- Sorry - I did not know I needed to change the status. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 384165] Plasma5 Crash after Updating System with Update Plugin
https://bugs.kde.org/show_bug.cgi?id=384165 --- Comment #9 from Bill Wayson --- (In reply to Justin Zobel from comment #6) > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as resolved. > > I have set the bug status to "needsinfo" pending your response, please > change back to "reported" or "resolved/worksforme" when you respond, thank > you. Hello again, This is no longer an issue for me. Thanks! Bill -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 383217] Kontact Crash Upon Closing Kontact
https://bugs.kde.org/show_bug.cgi?id=383217 --- Comment #2 from Bill Wayson --- (In reply to Justin Zobel from comment #1) > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as resolved. > > I have set the bug status to "needsinfo" pending your response, please > change back to "reported" or "resolved/worksforme" when you respond, thank > you. Hi Justin, The issue no longer occurs for me. Thanks for cleaning this up. Bill -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385887] Kstars Crashes Upon Closing It
https://bugs.kde.org/show_bug.cgi?id=385887 --- Comment #5 from Bill Wayson --- Hello Jasem, I want to report that, despite my 2017-11-02, the crashing problem when closing Kstars under openSUSE Tumbleweed did reappear. But, since then, version 2.9.2 of Kstars was installed from the Tumbleweed update repository, and the crashing problem has disappeared. It has not occurred to me since the update, which was a while ago. Bill Wayson -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385887] Kstars Crashes Upon Closing It
https://bugs.kde.org/show_bug.cgi?id=385887 --- Comment #4 from Bill Wayson --- Hi Jasem, First, thank you for all your work on Kstars. Now, after running kstars for a bit and shutting it down and restarting it several times, it no longer seems to crash upon closing under Tumbleweed. The kstars version is still 2.7.10, but Qt is now at 5.9.2, Frameworks appears to be at 5.39.0, and the kernel is 4.13.10-1-default x86_64. Tumbleweed is at version 20171101. Let me know if there is anything else you'd like. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 384165] Plasma5 Crash after Updating System with Update Plugin
https://bugs.kde.org/show_bug.cgi?id=384165 --- Comment #5 from Bill Wayson --- After today's update of openSUSE Tumbleweed, *no* problem was experienced after the Software Update system tray applet finished, which is good. On this PC with Tumbleweed, this is the first time Plasma has not crashed in many weeks. Tumbleweed is now at version 20171101; Qt is version 5.9.2; Frameworks is version 5.39.0 (I think); and kernel is 4.13.10-1-default x86_64. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 384165] Plasma5 Crash after Updating System with Update Plugin
https://bugs.kde.org/show_bug.cgi?id=384165 Bill Wayson changed: What|Removed |Added CC||bill_way...@yahoo.com --- Comment #4 from Bill Wayson --- This is affecting me, also. It has been happening every time for a few weeks. Updates are done through the Software Updates system tray applet. The updating finishes, and while it is refreshing (the software list, I think), Plasma crashes. Qt is version 5.9.1, Frameworks is (I believe) 5.38.0, the kernel is Linux 4.13.6-1-default, and this is openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385887] Kstars Crashes Upon Closing It
https://bugs.kde.org/show_bug.cgi?id=385887 --- Comment #2 from Bill Wayson --- Hi Jasem, I'd like to, but I am having trouble finding an installation source. And the rpm version numbers I see don't seem to correspond to the kstars version (e.g. my kstars 2.7.1 comes from the kstars-17.08.1-1.1.x86_64 rpm file). From the various openSUSE repositories I see, 17.08.1 seems to be the latest rpm available. I see you have an Ubuntu/Mint repository. Do you have any suggestions? Will I need to build from source? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385887] New: Kstars Crashes Upon Closing It
https://bugs.kde.org/show_bug.cgi?id=385887 Bug ID: 385887 Summary: Kstars Crashes Upon Closing It Product: kstars Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bill_way...@yahoo.com Target Milestone: --- Application: kstars (2.7.10) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.5-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had simply clicked the 'X' button in the upper right of the kstars window. Kstars closed, and a message that it ah closed unexpectedly appeared immediately. I tried this twice with the same results. The crash can be reproduced every time. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f916db1e940 (LWP 3197))] Thread 5 (Thread 0x7f911bfff700 (LWP 3213)): #0 0x7f9165b28cab in poll () from /lib64/libc.so.6 #1 0x7f9160a6d149 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9160a6d25c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f916756369b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f916750c34a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f916733c31a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f9167340d2e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f916932e558 in start_thread () from /lib64/libpthread.so.0 #8 0x7f9165b3345f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f912a1c8700 (LWP 3212)): #0 0x7ffdc1d57979 in ?? () #1 0x7ffdc1d57c30 in clock_gettime () #2 0x7f9165b40d46 in clock_gettime () from /lib64/libc.so.6 #3 0x7f91675630b1 in qt_gettime() () from /usr/lib64/libQt5Core.so.5 #4 0x7f9167561989 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #5 0x7f9167561f05 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #6 0x7f916756344e in timerSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f9160a6c688 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #8 0x7f9160a6d07b in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f9160a6d25c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7f916756369b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7f916750c34a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #12 0x7f916733c31a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #13 0x7f916bf4b705 in ?? () from /usr/lib64/libQt5Qml.so.5 #14 0x7f9167340d2e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #15 0x7f916932e558 in start_thread () from /lib64/libpthread.so.0 #16 0x7f9165b3345f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f914fb67700 (LWP 3200)): #0 0x7f9160ab2714 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9160a6c678 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9160a6d07b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9160a6d25c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f916756369b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f916750c34a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f916733c31a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f9167c3fa45 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7f9167340d2e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f916932e558 in start_thread () from /lib64/libpthread.so.0 #10 0x7f9165b3345f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f9156cff700 (LWP 3199)): #0 0x7f9165b28cab in poll () from /lib64/libc.so.6 #1 0x7f915feb7387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f915feb917a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f9159abf4b9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f9167340d2e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7f916932e558 in start_thread () from /lib64/libpthread.so.0 #6 0x7f9165b3345f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f916db1e940 (LWP 3197)): [KCrash Handler] #6 StarBlockList::releaseBlock (this=0x55e5f45d9620, block=block@entry=0x55e5f69d6410) at /usr/src/debug/kstars-17.08.1/kstars/skycomponents/starblocklist.cpp:52 #7 0x55e5f24f5e69 in StarBlock::~StarBlock (this=0x55e5f69d6410, __in_chrg=) at /usr/src/debug/k
[frameworks-baloo] [Bug 385312] Baloo crashed while compiling fpc and lazarus
https://bugs.kde.org/show_bug.cgi?id=385312 --- Comment #1 from Bill Wayson --- Created attachment 108350 --> https://bugs.kde.org/attachment.cgi?id=108350&action=edit New crash information added by DrKonqi baloo_file (5.38.0) using Qt 5.9.1 - What I was doing when the application crashed: I had completely deleted two audacity project files and folders under my home directory (similar to bug 385056, bypassing sending them to trash). This is the second time this issue happened to me. -- Backtrace (Reduced): #11 0x55e9b7968e5f in QTypedArrayData::deallocate (data=) at /usr/include/qt5/QtCore/qarraydata.h:237 #12 QString::~QString (this=0x7fff7963cbe0, __in_chrg=) at /usr/include/qt5/QtCore/qstring.h:1084 #13 Baloo::PendingFileQueue::enqueue (this=0x55e9b933bfe0, file=...) at /usr/src/debug/baloo-5.38.0/src/file/pendingfilequeue.cpp:66 #14 0x55e9b7966d09 in Baloo::FileWatch::slotFileDeleted (this=0x7fff7963d3e0, urlString=..., isDir=) at /usr/src/debug/baloo-5.38.0/src/file/filewatch.cpp:116 [...] #16 0x55e9b796dcce in KInotify::deleted (_t2=, _t1=..., this=0x55e9b9363640) at /usr/src/debug/baloo-5.38.0/build/src/file/baloofilecommon_autogen/include/moc_kinotify.cpp:330 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 385312] Baloo crashed while compiling fpc and lazarus
https://bugs.kde.org/show_bug.cgi?id=385312 Bill Wayson changed: What|Removed |Added CC||bill_way...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 383217] New: Kontact Crash Upon Closing Kontact
https://bugs.kde.org/show_bug.cgi?id=383217 Bug ID: 383217 Summary: Kontact Crash Upon Closing Kontact Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bill_way...@yahoo.com Target Milestone: --- Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.74-18.20-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I had just tried to close Kontact via the 'X' in the upper left of its window. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f261e0947c0 (LWP 3700))] Thread 44 (Thread 0x7f24360b4700 (LWP 5295)): #0 QMutex::lock (this=this@entry=0x398c808) at thread/qmutex.cpp:225 #1 0x7f261b5e4265 in QMutexLocker::QMutexLocker (m=0x398c808, this=) at ../../src/corelib/thread/qmutex.h:128 #2 QThreadData::canWaitLocked (this=0x398c7e0) at ../../src/corelib/thread/qthread_p.h:246 #3 postEventSourcePrepare (s=0x7f241801e2d0, timeout=0x7f24360b3c54) at kernel/qeventdispatcher_glib.cpp:253 #4 0x7f2615dbf95d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2615dc0230 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f2615dc042c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #7 0x7f261b5e433b in QEventDispatcherGlib::processEvents (this=0x7f2418015c50, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #8 0x7f261b591feb in QEventLoop::exec (this=this@entry=0x7f24360b3e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #9 0x7f261b3ccf1a in QThread::exec (this=) at thread/qthread.cpp:500 #10 0x7f261b3d19e9 in QThreadPrivate::start (arg=0x398c710) at thread/qthread_unix.cpp:341 #11 0x7f26169fd744 in start_thread () from /lib64/libpthread.so.0 #12 0x7f261aac8aad in clone () from /lib64/libc.so.6 Thread 43 (Thread 0x7f241fffe700 (LWP 5293)): #0 0x7f2615dbf370 in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #1 0x7f2615dc01d5 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2615dc042c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f261b5e433b in QEventDispatcherGlib::processEvents (this=0x7f240003a380, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f261b591feb in QEventLoop::exec (this=this@entry=0x7f241fffde10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f261b3ccf1a in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f261b3d19e9 in QThreadPrivate::start (arg=0x398aab0) at thread/qthread_unix.cpp:341 #7 0x7f26169fd744 in start_thread () from /lib64/libpthread.so.0 #8 0x7f261aac8aad in clone () from /lib64/libc.so.6 Thread 42 (Thread 0x7f2428d0e700 (LWP 4249)): #0 0x7f2615dbd67a in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f2615dbf8fb in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2615dc0230 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2615dc042c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f261b5e433b in QEventDispatcherGlib::processEvents (this=0x7f2414005d20, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f261b591feb in QEventLoop::exec (this=this@entry=0x7f2428d0de10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f261b3ccf1a in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f261b3d19e9 in QThreadPrivate::start (arg=0x6a51240) at thread/qthread_unix.cpp:341 #8 0x7f26169fd744 in start_thread () from /lib64/libpthread.so.0 #9 0x7f261aac8aad in clone () from /lib64/libc.so.6 Thread 41 (Thread 0x7f242bda6700 (LWP 4181)): #0 0x7f261aac020d in poll () from /lib64/libc.so.6 #1 0x7f2615dc0314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2615dc042c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f261b5e433b in QEventDispatcherGlib::processEvents (this=0x7f2424001a50, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f261b591feb in QEventLoop::exec (this=this@entry=0x7f242bda5e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f261b3ccf1a in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f261b3d19e9 in QThreadPrivate::start (arg=0x6dc7850) at thread/qthread_unix.cpp:341 #7 0x7f26169fd744 in start_thread () from /lib64/libpthread.so.0 #8 0x7f261aac8aad in clone () from /lib64/libc.so.6 Thread 40 (Thread 0x7f242a71e700 (LWP 4179)): #0 0x7f261aac020d in poll () from /lib64/libc.so.6 #1 0x7f2615dc031
[kontact] [Bug 363113] New: Kontact Crashes When Exiting
https://bugs.kde.org/show_bug.cgi?id=363113 Bug ID: 363113 Summary: Kontact Crashes When Exiting Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bill_way...@yahoo.com Application: kontact (4.14.10) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I had just pressed the Kontact window's 'X' button in the upper right fo the window, to esit the program. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6397448800 (LWP 4499))] Thread 4 (Thread 0x7f637a809700 (LWP 4500)): #0 0x7f638e9a103f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6393b28eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f6393b28ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f638e99d0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6394918fed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f6339f06700 (LWP 4501)): #0 0x7f638e9a103f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f639389bb3d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f6393b50a06 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f638e99d0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6394918fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f632ae83700 (LWP 4504)): #0 0x7f639490cc8d in read () from /lib64/libc.so.6 #1 0x7f638e411b60 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f638e3d0999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f638e3d0df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f638e3d0f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f639510ffde in QEventDispatcherGlib::processEvents (this=0x7f63240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f63950e1d4f in QEventLoop::processEvents (this=this@entry=0x7f632ae82de0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f63950e2045 in QEventLoop::exec (this=this@entry=0x7f632ae82de0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f6394fdf4df in QThread::exec (this=) at thread/qthread.cpp:538 #9 0x7f6394fe1bbf in QThreadPrivate::start (arg=0x1729bb0) at thread/qthread_unix.cpp:349 #10 0x7f638e99d0a4 in start_thread () from /lib64/libpthread.so.0 #11 0x7f6394918fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f6397448800 (LWP 4499)): [KCrash Handler] #6 0x7f6389d6686d in KMime::Headers::ContentType* KMime::Content::header(bool) () from /usr/lib64/libkmime.so.4 #7 0x7f632eb6232a in MessageViewer::PartNodeBodyPart::asText (this=0x7fffc3959350) at /usr/src/debug/kdepim-4.14.10/messageviewer/viewer/partnodebodypart.cpp:66 #8 0x7f6328ac7c05 in (anonymous namespace)::UrlHandler::handleClick (this=, viewerInstance=, bodyPart=, path=...) at /usr/src/debug/kdepim-4.14.10/plugins/messageviewer/bodypartformatter/text_vcard.cpp:195 #9 0x7f632eb876e7 in MessageViewer::URLHandlerManager::BodyPartURLHandlerManager::handleClick (this=, url=..., w=0x1a9ba30) at /usr/src/debug/kdepim-4.14.10/messageviewer/viewer/urlhandlermanager.cpp:286 #10 0x7f632eb85438 in MessageViewer::URLHandlerManager::handleClick (this=, url=..., w=w@entry=0x1a9ba30) at /usr/src/debug/kdepim-4.14.10/messageviewer/viewer/urlhandlermanager.cpp:373 #11 0x7f632eb69106 in MessageViewer::ViewerPrivate::slotUrlOpen (this=0x1a9ba30, url=...) at /usr/src/debug/kdepim-4.14.10/messageviewer/viewer/viewer_p.cpp:2117 #12 0x7f632ec029a5 in MessageViewer::ViewerPrivate::qt_static_metacall (_o=0x1a9ba30, _c=, _id=, _a=) at /usr/src/debug/kdepim-4.14.10/build/messageviewer/moc_viewer_p.cpp:255 #13 0x7f63950fb49e in QObject::event (this=0x1a9ba30, e=) at kernel/qobject.cpp:1231 #14 0x7f6395aed79c in QApplicationPrivate::notify_helper (this=this@entry=0x14021f0, receiver=receiver@entry=0x1a9ba30, e=e@entry=0x4268050) at kernel/qapplication.cpp:4565 #15 0x7f6395af3cdd in QApplication::notify (this=this@entry=0x7fffc395dfb0, receiver=receiver@entry=0x1a9ba30, e=e@entry=0x4268050) at kernel/qapplication.cpp:4351 #16 0x7f6396804e9a in KApplication::notify (this=0x7fffc395dfb0, receiver=0x1a9ba30, event=0x4268050) at /usr/src/debug/kdelibs-4.14.18/kdeui/kernel/kapplication.cpp:311 #17 0x7f63950e318d in QCoreApplication::notifyInternal (t
[kontact] [Bug 360702] Kmail crashed when accepting Meeting Invitation
https://bugs.kde.org/show_bug.cgi?id=360702 --- Comment #1 from Bill Wayson --- Created attachment 98996 --> https://bugs.kde.org/attachment.cgi?id=98996&action=edit New crash information added by DrKonqi kontact (4.14.10) on KDE Platform 4.14.18 using Qt 4.8.6 - What I was doing when the application crashed: I had just accepted a meeting invitation. My experience is similar to the bug reporter's: some invitations are accepted and recorded just fine, others cannot be accepted or recorded (nothing appears to happen when I accept) until Kontact is restarted, and others crash Kmail/Kontact completely. My Kontact version is 4.14.10, and it and all of its components were installed from the release or update RPM packages for openSUSE Leap 42.1, -- Backtrace (Reduced): #9 0x7f3c930df975 in ~QDebug (this=0x7ffe694896c0, __in_chrg=) at /usr/include/QtCore/qdebug.h:85 #10 Akonadi::ITIPHandler::Private::onSchedulerFinished (this=, result=, errorMessage=...) at /usr/src/debug/kdepimlibs-4.14.10/akonadi/calendar/itiphandler_p.cpp:48 [...] #12 0x7f3c93111d73 in Akonadi::Scheduler::transactionFinished (this=, _t1=Akonadi::Scheduler::ResultSuccess, _t2=...) at /usr/src/debug/kdepimlibs-4.14.10/build/akonadi/calendar/moc_scheduler_p.cpp:110 [...] #14 0x7f3c930a8204 in Akonadi::CalendarBase::createFinished (this=, _t1=true, _t2=...) at /usr/src/debug/kdepimlibs-4.14.10/build/akonadi/calendar/moc_calendarbase.cpp:106 [...] #16 0x7f3c93111986 in Akonadi::IncidenceChanger::createFinished (this=, _t1=1, _t2=..., _t3=Akonadi::IncidenceChanger::ResultCodeSuccess, _t4=...) at /usr/src/debug/kdepimlibs-4.14.10/build/akonadi/calendar/moc_incidencechanger.cpp:109 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 360702] Kmail crashed when accepting Meeting Invitation
https://bugs.kde.org/show_bug.cgi?id=360702 Bill Wayson changed: What|Removed |Added CC||bill_way...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 356922] Archiving Kmail Local Folders Aborts Kontact
https://bugs.kde.org/show_bug.cgi?id=356922 Bill Wayson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Bill Wayson --- I am closing this. The crash was due to a (probably) corrupt folder in my kmail. I deleted it, and the archive of Local Folders completed without error. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 356922] New: Archiving Kmail Local Folders Aborts Kontact
https://bugs.kde.org/show_bug.cgi?id=356922 Bug ID: 356922 Summary: Archiving Kmail Local Folders Aborts Kontact Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bway...@gmail.com Application: kontact (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-29-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was archiving the Local Folders kmail folder. The abort occurred during the archviing process. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1b9f881800 (LWP 19450))] Thread 5 (Thread 0x7f1b82346700 (LWP 19451)): #0 0x7f1b96e8105f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1b9a627686 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f1b9a6276b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f1b96e7d0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1b9ce0a08d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f1b41a43700 (LWP 19452)): #0 0x7f1b96e8105f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1b9a399e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f1b9a64f1e6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f1b96e7d0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1b9ce0a08d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1b32782700 (LWP 19455)): #0 0x7f1b9ce01c5d in poll () from /lib64/libc.so.6 #1 0x7f1b968b1be4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1b968b1cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1b9d5840de in QEventDispatcherGlib::processEvents (this=0x7f1b2c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f1b9d555e6f in QEventLoop::processEvents (this=this@entry=0x7f1b32781de0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f1b9d556165 in QEventLoop::exec (this=this@entry=0x7f1b32781de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f1b9d4530bf in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7f1b9d45579f in QThreadPrivate::start (arg=0x135b920) at thread/qthread_unix.cpp:349 #8 0x7f1b96e7d0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f1b9ce0a08d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1b2b4fc700 (LWP 19466)): #0 0x7f1b9cdfdd2d in read () from /lib64/libc.so.6 #1 0x7f1b968f2750 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1b968b1714 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1b968b1b7b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f1b968b1cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1b9d5840de in QEventDispatcherGlib::processEvents (this=0x7f1b1c003a50, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f1b9d555e6f in QEventLoop::processEvents (this=this@entry=0x7f1b2b4fbda0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f1b9d556165 in QEventLoop::exec (this=this@entry=0x7f1b2b4fbda0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f1b9d4530bf in QThread::exec (this=this@entry=0x28a4bb0) at thread/qthread.cpp:538 #9 0x7f1b9d537783 in QInotifyFileSystemWatcherEngine::run (this=0x28a4bb0) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7f1b9d45579f in QThreadPrivate::start (arg=0x28a4bb0) at thread/qthread_unix.cpp:349 #11 0x7f1b96e7d0a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7f1b9ce0a08d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1b9f881800 (LWP 19450)): [KCrash Handler] #5 0x7f1b9cd5a187 in raise () from /lib64/libc.so.6 #6 0x7f1b9cd5b538 in abort () from /lib64/libc.so.6 #7 0x7f1b9d131145 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #8 0x7f1b9d12f2e6 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x7f1b9d12f313 in std::terminate() () from /usr/lib64/libstdc++.so.6 #10 0x7f1b9d12f586 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6 #11 0x7f1b9d556356 in QEventLoop::exec (this=this@entry=0x7ffef63334e0, flags=...) at kernel/qeventloop.cpp:218 #12 0x7f1b9d55b5b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #13 0x004037f2 in main (argc=1, argv=0x7ffef6333728) at /usr/src/debug/kdepim-4.14.9/kontact/src/main.cpp:219 Possible duplicates by query: bug 356867, bu
