[Discover] [Bug 403538] Discover crashing after a few seconds
https://bugs.kde.org/show_bug.cgi?id=403538 jv changed: What|Removed |Added CC||jv3...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 400220] New: Korganizer crashes when changeing calendar color under resources.
https://bugs.kde.org/show_bug.cgi?id=400220 Bug ID: 400220 Summary: Korganizer crashes when changeing calendar color under resources. Product: korganizer Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jv3...@comcast.net Target Milestone: --- Application: korganizer (5.9.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-38-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: I was changing the color of my calendar to red. Korganizer crashes everytime I try to do this. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc20a32d880 (LWP 5232))] Thread 6 (Thread 0x7fc1cd21c700 (LWP 5246)): #0 0x7fc1fd7b09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fc1f6b99fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fc1f6b99f68, cond=0x7fc1f6b99f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fc1f6b99f90, mutex=0x7fc1f6b99f68) at pthread_cond_wait.c:655 #3 0x7fc1f68a4954 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fc1f68a4999 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fc1fd7aa6db in start_thread (arg=0x7fc1cd21c700) at pthread_create.c:463 #6 0x7fc205b1688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fc1e1725700 (LWP 5237)): #0 0x7fffbf5f297d in ?? () #1 0x7fffbf5f2c30 in clock_gettime () #2 0x7fc205b25ea6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fc1e1724a90) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fc20665be41 in qt_clock_gettime (ts=0x7fc1e1724a90, clock=) at kernel/qelapsedtimer_unix.cpp:111 #4 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #5 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #6 0x7fc20665a679 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fc1d8004cf0) at kernel/qtimerinfo_unix.cpp:91 #7 0x7fc20665ac55 in QTimerInfoList::timerWait (this=0x7fc1d8004cf0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #8 0x7fc20665c29e in timerSourcePrepareHelper (timeout=0x7fc1e1724b54, src=) at kernel/qeventdispatcher_glib.cpp:132 #9 timerSourcePrepare (source=, timeout=0x7fc1e1724b54) at kernel/qeventdispatcher_glib.cpp:165 #10 0x7fc1fb6d5998 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fc1fb6d636b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fc1fb6d654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fc20665c53b in QEventDispatcherGlib::processEvents (this=0x7fc1d8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #14 0x7fc2066007fa in QEventLoop::exec (this=this@entry=0x7fc1e1724d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #15 0x7fc20642bbba in QThread::exec (this=) at thread/qthread.cpp:525 #16 0x7fc206436adb in QThreadPrivate::start (arg=0x560a35ce56d0) at thread/qthread_unix.cpp:367 #17 0x7fc1fd7aa6db in start_thread (arg=0x7fc1e1725700) at pthread_create.c:463 #18 0x7fc205b1688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fc1e1f26700 (LWP 5235)): #0 0x7fc205b09bf9 in __GI___poll (fds=0x7fc1d4066100, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc1fb6d6439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc1fb6d654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc20665c53b in QEventDispatcherGlib::processEvents (this=0x7fc1d4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fc2066007fa in QEventLoop::exec (this=this@entry=0x7fc1e1f25d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fc20642bbba in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fc206436adb in QThreadPrivate::start (arg=0x560a35c999d0) at thread/qthread_unix.cpp:367 #7 0x7fc1fd7aa6db in start_thread (arg=0x7fc1e1f26700) at pthread_create.c:463 #8 0x7fc205b1688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc1e3137700 (LWP 5234)): #0 0x7fc205b050b4 in __GI___libc_read (fd=7, buf=0x7fc1e3136ae0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc1fb71aa00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc1fb6d5f27 in g_main_context_check () from
[korganizer] [Bug 396700] New: Korganizer crashes on startup after installing over 400 updates to KDE Neon.
https://bugs.kde.org/show_bug.cgi?id=396700 Bug ID: 396700 Summary: Korganizer crashes on startup after installing over 400 updates to KDE Neon. Product: korganizer Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jv3...@comcast.net Target Milestone: --- Application: korganizer (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: Trying to start korganizer. Korganizer worked fine until I installed over 400 updates for KDE Neon on 7/20/18. Now it crashes everytime it is started. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8dc6f3d940 (LWP 2557))] Thread 2 (Thread 0x7f8d9f95a700 (LWP 2559)): #0 0x7f8dc278674d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8db872138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8db872149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8dc32b40bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8dc325b5ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8dc30905e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8dc1c4af35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f8dc309b727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8dba42d6ba in start_thread (arg=0x7f8d9f95a700) at pthread_create.c:333 #9 0x7f8dc279241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f8dc6f3d940 (LWP 2557)): [KCrash Handler] #6 0xfff0 in ?? () #7 0x7f8dc6c0fd3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x004084ce in main (argc=1, argv=0x7ffecac75ec8) at /workspace/build/src/main.cpp:55 Possible duplicates by query: bug 396694, bug 389840, bug 389365, bug 386013, bug 385374. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 394967] Edit/Find defaults to a date range even with the date range box unchecked.
https://bugs.kde.org/show_bug.cgi?id=394967 --- Comment #4 from jv --- Yes. That is what I am saying. That is how it use to work in version 4.13.3. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 394967] Edit/Find defaults to a date range even with the date range box unchecked.
https://bugs.kde.org/show_bug.cgi?id=394967 --- Comment #2 from jv --- I respectively disagree with your explanation. First off if you do not select the date range field the system should not impose a date range on your search. Secondly. In Korganizer version 4.13.3 in Kubuntu 14.04 when you enter a string in the “Search for:” field and you do not select the “Include Events within the specified date range”, the system searches for all occurrences of that string in your calendar file. I did verify this. So this use to work as expected and somewhere since version 4.13.3 a change was made that broke this function. I’m still calling this a bug. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 394967] New: Edit/Find defaults to a date range even with the date range box unchecked.
https://bugs.kde.org/show_bug.cgi?id=394967 Bug ID: 394967 Summary: Edit/Find defaults to a date range even with the date range box unchecked. Product: korganizer Version: 5.8.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jv3...@comcast.net Target Milestone: --- When selecting Edit and then Find from the main menu the Search Calendar -- KOrganizer window pops up. In that window even though you do not have the "Include Events within the specified date range" selected the date range filter is still being applied. Since the default date ranges are From:"todays date" To:"one year from todays date" no historical events are produced by the search until you adjust the date range accordingly. -- You are receiving this mail because: You are watching all bug changes.
