Bug 404275 - Crash on startup
Summary: Crash on startup
Status: RESOLVED UPSTREAM
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
: 402958 404679 405296 406369 411435 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-02-13 03:09 UTC by Geoff Love
Modified: 2019-08-30 11:25 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (8.76 KB, text/plain)
2019-03-22 13:37 UTC, Seijiro Moriyama
Details
attachment-7905-0.html (3.21 KB, text/html)
2019-03-24 13:59 UTC, Seijiro Moriyama
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Geoff Love 2019-02-13 03:09:20 UTC
Application: korganizer (5.10.1)

Qt Version: 5.12.0
Frameworks Version: 5.54.0
Operating System: Linux 4.20.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I simply tried to start the application. I'm running a fresh install of openSUSE Tumbleweed. Tried multiple times but the program keeps crashing.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f53b980c000 (LWP 21635))]

Thread 5 (Thread 0x7f53b4f06700 (LWP 21641)):
#0  0x00007f53bdefdd24 in read () from /lib64/libc.so.6
#1  0x00007f53bb726b20 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f53bb6e0abb in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f53bb6e0f60 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007f53bb6e10dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f53be44d88b in QEventDispatcherGlib::processEvents (this=0x7f53a0000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x00007f53be3f802b in QEventLoop::exec (this=this@entry=0x7f53b4f05c60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x00007f53be2423b6 in QThread::exec (this=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x00007f53be243702 in QThreadPrivate::start (arg=0x55eb6cb1ef00) at thread/qthread_unix.cpp:361
#9  0x00007f53bc121ed4 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f53bdf0ccbf in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f53b5707700 (LWP 21639)):
#0  0x00007f53bb6e000e in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f53bb6e0e75 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f53bb6e10dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f53be44d88b in QEventDispatcherGlib::processEvents (this=0x7f53ac000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f53be3f802b in QEventLoop::exec (this=this@entry=0x7f53b5706c60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x00007f53be2423b6 in QThread::exec (this=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x00007f53be243702 in QThreadPrivate::start (arg=0x55eb6cb182f0) at thread/qthread_unix.cpp:361
#7  0x00007f53bc121ed4 in start_thread () from /lib64/libpthread.so.0
#8  0x00007f53bdf0ccbf in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f53b6928700 (LWP 21638)):
#0  0x00007f53bdefdd24 in read () from /lib64/libc.so.6
#1  0x00007f53bb726b20 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f53bb6e0abb in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f53bb6e0f60 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007f53bb6e10dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f53be44d88b in QEventDispatcherGlib::processEvents (this=0x7f53a8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x00007f53be3f802b in QEventLoop::exec (this=this@entry=0x7f53b6927c30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x00007f53be2423b6 in QThread::exec (this=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x00007f53bdb71565 in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x00007f53be243702 in QThreadPrivate::start (arg=0x7f53bdbebd80) at thread/qthread_unix.cpp:361
#10 0x00007f53bc121ed4 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f53bdf0ccbf in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f53b7946700 (LWP 21636)):
#0  0x00007f53bdf022b9 in poll () from /lib64/libc.so.6
#1  0x00007f53bb670cc7 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f53bb6728ea in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f53b7b6b5da in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f53be243702 in QThreadPrivate::start (arg=0x55eb6ca60100) at thread/qthread_unix.cpp:361
#5  0x00007f53bc121ed4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f53bdf0ccbf in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f53b980c000 (LWP 21635)):
[KCrash Handler]
#6  std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x51) at /usr/include/c++/8/bits/atomic_base.h:390
#7  QAtomicOps<int>::load<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#8  QBasicAtomicInteger<int>::load (this=0x51) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103
#9  QtPrivate::RefCount::ref (this=0x51) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55
#10 QString::QString (other=..., this=0x7ffd1f8213e0) at ../../include/QtCore/../../src/corelib/tools/qstring.h:958
#11 QTimeZonePrivate::Data::Data (this=0x7ffd1f8213e0) at tools/qtimezoneprivate_p.h:81
#12 QTzTimeZonePrivate::previousTransition (this=0x55eb6cc624c0, beforeMSecsSinceEpoch=28799999) at tools/qtimezoneprivate_tz.cpp:1026
#13 0x00007f53be2de739 in QTimeZonePrivate::dataForLocalTime (this=0x55eb6cc624c0, forLocalMSecs=forLocalMSecs@entry=86399999, hint=-1) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:236
#14 0x00007f53be28850d in QDateTimePrivate::zoneMSecsToEpochMSecs (zoneTime=0x7ffd1f821494, zoneDate=0x7ffd1f821498, hint=<optimized out>, zone=..., zoneMSecs=86399999) at tools/qdatetime.cpp:2987
#15 refreshDateTime (d=...) at tools/qdatetime.cpp:2655
#16 0x00007f53be28898b in checkValidDateTime (d=...) at tools/qdatetime.cpp:2718
#17 setDateTime (d=..., date=..., time=...) at tools/qdatetime.cpp:2802
#18 0x00007f53be288f12 in QDateTimePrivate::create (toTime=..., toTimeZone=..., toDate=...) at tools/qdatetime.cpp:2976
#19 QDateTime::QDateTime (this=0x7ffd1f8215e0, date=..., time=..., timeZone=...) at tools/qdatetime.cpp:3204
#20 0x00007f53bf639baa in KCalCore::MemoryCalendar::rawEvents (this=0x55eb6cc5cf20, start=..., end=..., timeZone=..., inclusive=false) at /usr/src/debug/kcalcore-18.12.1-1.1.x86_64/src/memorycalendar.cpp:671
#21 0x00007f53bf5ede99 in KCalCore::Calendar::events (this=this@entry=0x55eb6cc5cf20, start=..., end=..., timeZone=..., inclusive=inclusive@entry=false) at /usr/src/debug/kcalcore-18.12.1-1.1.x86_64/src/calendar.cpp:528
#22 0x00007f53bf98f69c in KODayMatrix::updateEvents (this=0x55eb6cc649c0) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:312
#23 0x00007f53bf990e68 in KODayMatrix::updateIncidences (this=0x55eb6cc649c0) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/kodaymatrix.cpp:262
#24 0x00007f53bf990f5c in KODayMatrix::updateIncidences (this=<optimized out>) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:310
#25 KODayMatrix::setCalendar (this=<optimized out>, calendar=...) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/kodaymatrix.cpp:86
#26 0x00007f53bf98ac20 in KDateNavigator::setCalendar (this=0x7f53be4cd720 <QListData::shared_null>, calendar=...) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/widgets/kdatenavigator.cpp:117
#27 0x00007f53bf984c3f in DateNavigatorContainer::setCalendar (this=0x55eb6cc61160, calendar=...) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/datenavigatorcontainer.cpp:98
#28 0x00007f53bf979337 in CalendarView::CalendarView (this=0x55eb6cbe1bf0, parent=<optimized out>) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/calendarview.cpp:319
#29 0x000055eb6c3ab063 in KOrganizer::KOrganizer (this=0x55eb6cb87910, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/korganizer.cpp:60
#30 0x000055eb6c3ac46a in KOrganizerApp::processCalendar (this=<optimized out>, url=...) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/koapp.cpp:111
#31 0x000055eb6c3acff3 in KOrganizerApp::activate (this=0x7ffd1f822180, args=..., workingDir=...) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/koapp.cpp:73
#32 0x00007f53bfa31045 in KontactInterface::PimUniqueApplication::start (arguments=..., unique=<optimized out>) at /usr/include/qt5/QtCore/qarraydata.h:236
#33 0x000055eb6c3aa0f3 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/korganizer-18.12.1-1.2.x86_64/src/main.cpp:55
[Inferior 1 (process 21635) detached]

Possible duplicates by query: bug 400220, bug 398459.

Reported using DrKonqi
Comment 1 Seijiro Moriyama 2019-03-22 13:37:30 UTC
Created attachment 118969 [details]
New crash information added by DrKonqi

korganizer (5.10.3) using Qt 5.12.0

- What I was doing when the application crashed:
Ran korganizer from console. Log shown below:

seijirom@macmini:~$ korganizer
org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = korganizer path = /usr/bin pid = 5436
KCrash: Arguments: /usr/bin/korganizer 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

[1]+  Stopped                 korganizer
seijirom@macmini:~$

-- Backtrace (Reduced):
#6  std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x50) at /usr/include/c++/7/bits/atomic_base.h:396
#7  QAtomicOps<int>::load<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#8  QBasicAtomicInteger<int>::load (this=0x50) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103
[...]
#10 QString::QString (other=..., this=0x7ffc3b8f9740) at ../../include/QtCore/../../src/corelib/tools/qstring.h:958
#11 QTimeZonePrivate::Data::Data (this=0x7ffc3b8f9740) at tools/qtimezoneprivate_p.h:81
Comment 2 Christoph Feck 2019-03-24 13:48:17 UTC
*** Bug 402958 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2019-03-24 13:48:38 UTC
*** Bug 405296 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2019-03-24 13:49:04 UTC
*** Bug 404679 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2019-03-24 13:50:28 UTC
Crash is inside QTimeZone when creating a QDateTime.

Do you have any special time zone settings that allows us to reproduce on any distribution?
Comment 6 Seijiro Moriyama 2019-03-24 13:59:35 UTC
Created attachment 118994 [details]
attachment-7905-0.html

Hi Christoph-san,

Timezone setting is JST as you can see below:

seijirom@macmini:~$ timedatectl
                     Local time: 日 2019-03-24 22:56:29 JST
                 Universal time: 日 2019-03-24 13:56:29 UTC
                       RTC time: 日 2019-03-24 13:56:29
                      Time zone: Asia/Tokyo (JST, +0900)
      System clock synchronized: yes
systemd-timesyncd.service active: yes
                RTC in local TZ: no
seijirom@macmini:~$

Is this information enough?

Thank you so much for working on the issue. It is so inconvenient w/o
Kalendar.

Seijiro

2019年3月24日(日) 22:50 Christoph Feck <bugzilla_noreply@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=404275
>
> --- Comment #5 from Christoph Feck <cfeck@kde.org> ---
> Crash is inside QTimeZone when creating a QDateTime.
>
> Do you have any special time zone settings that allows us to reproduce on
> any
> distribution?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 7 Raghavendra kamath 2019-03-24 15:03:18 UTC
In my case time zone is IST
Comment 8 Kris S 2019-04-19 11:03:53 UTC
I can confirm the same problem.

Crash on startup if /etc/localtime is linked to Asia/Tokyo. If I link to America/New_York, korganizer starts with no problems.
Comment 9 Christoph Feck 2019-04-19 12:12:33 UTC
This is possibly fixed with https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/tools?id=82ad4be4a2e0c2bccb6cd8ea2440aefee4ec48ec in Qt 5.12.4.

If not, please report this issue directly to Qt developers via https://bugreports.qt.io/
Comment 10 Wolfgang Bauer 2019-04-23 13:25:12 UTC
(In reply to Christoph Feck from comment #9)
> This is possibly fixed with
> https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/
> tools?id=82ad4be4a2e0c2bccb6cd8ea2440aefee4ec48ec in Qt 5.12.4.

It seems that the crash is actually already fixed in Qt 5.12.3.
At least I was able to reproduce it with 5.12.2 (by setting /etc/localtime to point to Asia/Tokyo), and korganizer starts fine now after I updated to Qt 5.12.3.
Comment 11 Christoph Feck 2019-04-25 19:24:46 UTC
*** Bug 406369 has been marked as a duplicate of this bug. ***
Comment 12 Wolfgang Bauer 2019-04-25 20:08:54 UTC
(In reply to geofflove77 from comment #0)
> Thread 1 (Thread 0x7f53b980c000 (LWP 21635)):
> [KCrash Handler]
> #6  std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x51)
> at /usr/include/c++/8/bits/atomic_base.h:390
> #7  QAtomicOps<int>::load<int> (_q_value=...) at
> ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
> #8  QBasicAtomicInteger<int>::load (this=0x51) at
> ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103
> #9  QtPrivate::RefCount::ref (this=0x51) at
> ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55
> #10 QString::QString (other=..., this=0x7ffd1f8213e0) at
> ../../include/QtCore/../../src/corelib/tools/qstring.h:958
> #11 QTimeZonePrivate::Data::Data (this=0x7ffd1f8213e0) at
> tools/qtimezoneprivate_p.h:81
> #12 QTzTimeZonePrivate::previousTransition (this=0x55eb6cc624c0,
> beforeMSecsSinceEpoch=28799999) at tools/qtimezoneprivate_tz.cpp:1026

Judging from the backtrace, I'd say this upstream commit in Qt 5.12.3 fixed it:
https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/tools/qtimezoneprivate_tz.cpp?h=5.13&id=1119cd4ece6555be82212b273d05d581bffb79d1
Comment 13 Raghavendra kamath 2019-04-26 03:41:01 UTC
Yes this is fixed in 5.12.3 , just got an update to qt on arch and it is fixed there
Comment 14 Christoph Feck 2019-04-26 06:22:12 UTC
Thanks for the confirmation; changing status.
Comment 15 gesf02 2019-06-24 23:21:57 UTC
(In reply to Wolfgang Bauer from comment #10)
> (In reply to Christoph Feck from comment #9)
> > This is possibly fixed with
> > https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/
> > tools?id=82ad4be4a2e0c2bccb6cd8ea2440aefee4ec48ec in Qt 5.12.4.
> 
> It seems that the crash is actually already fixed in Qt 5.12.3.
> At least I was able to reproduce it with 5.12.2 (by setting /etc/localtime
> to point to Asia/Tokyo), and korganizer starts fine now after I updated to
> Qt 5.12.3.

How to update to Qt 5.12.3 without default repository? I'm using Fedora 30.
Comment 16 Seijiro Moriyama 2019-06-25 00:45:16 UTC
I have confirmed that Korganizer works as before after an update.
Thank you so much.

Seijiro Moriyama
Comment 17 Kishore Gopalakrishnan 2019-06-25 03:31:39 UTC
(In reply to gesf02 from comment #15)
> (In reply to Wolfgang Bauer from comment #10)
> > (In reply to Christoph Feck from comment #9)
> > > This is possibly fixed with
> > > https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/
> > > tools?id=82ad4be4a2e0c2bccb6cd8ea2440aefee4ec48ec in Qt 5.12.4.
> > 
> > It seems that the crash is actually already fixed in Qt 5.12.3.
> > At least I was able to reproduce it with 5.12.2 (by setting /etc/localtime
> > to point to Asia/Tokyo), and korganizer starts fine now after I updated to
> > Qt 5.12.3.
> 
> How to update to Qt 5.12.3 without default repository? I'm using Fedora 30.

Ask the fedora maintainers to update Qt or backport the fix.
Comment 18 Wolfgang Bauer 2019-08-30 11:25:06 UTC
*** Bug 411435 has been marked as a duplicate of this bug. ***