[korganizer] [Bug 404275] Crash on startup

2019-08-30 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=404275

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||opensou...@somekool.net

--- Comment #18 from Wolfgang Bauer  ---
*** Bug 411435 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-06-24 Thread Kishore Gopalakrishnan
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #17 from Kishore Gopalakrishnan  ---
(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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-06-24 Thread Seijiro Moriyama
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #16 from Seijiro Moriyama  ---
I have confirmed that Korganizer works as before after an update.
Thank you so much.

Seijiro Moriyama

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-06-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404275

ges...@gmail.com changed:

   What|Removed |Added

 CC||ges...@gmail.com

--- Comment #15 from ges...@gmail.com ---
(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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-04-26 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404275

Christoph Feck  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #14 from Christoph Feck  ---
Thanks for the confirmation; changing status.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-04-25 Thread Raghavendra kamath
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #13 from Raghavendra kamath  ---
Yes this is fixed in 5.12.3 , just got an update to qt on arch and it is fixed
there

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-04-25 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #12 from Wolfgang Bauer  ---
(In reply to geofflove77 from comment #0)
> Thread 1 (Thread 0x7f53b980c000 (LWP 21635)):
> [KCrash Handler]
> #6  std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x51)
> at /usr/include/c++/8/bits/atomic_base.h:390
> #7  QAtomicOps::load (_q_value=...) at
> ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
> #8  QBasicAtomicInteger::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=2879) 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=1119cd4ece6555be82212b273d05d581bffb79d1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-04-25 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404275

Christoph Feck  changed:

   What|Removed |Added

 CC||teru...@gmail.com

--- Comment #11 from Christoph Feck  ---
*** Bug 406369 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-04-23 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=404275

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #10 from Wolfgang Bauer  ---
(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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-04-19 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #9 from Christoph Feck  ---
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/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-04-19 Thread Kris S
https://bugs.kde.org/show_bug.cgi?id=404275

Kris S  changed:

   What|Removed |Added

 CC||k...@syntosis.net

--- Comment #8 from Kris S  ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-24 Thread Raghavendra kamath
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #7 from Raghavendra kamath  ---
In my case time zone is IST

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-24 Thread Seijiro Moriyama
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #6 from Seijiro Moriyama  ---
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 :

> https://bugs.kde.org/show_bug.cgi?id=404275
>
> --- Comment #5 from Christoph Feck  ---
> 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-24 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #5 from Christoph Feck  ---
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 the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-24 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404275

Christoph Feck  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #4 from Christoph Feck  ---
*** Bug 404679 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-24 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404275

Christoph Feck  changed:

   What|Removed |Added

 CC||rajat.cit...@gmail.com

--- Comment #3 from Christoph Feck  ---
*** Bug 405296 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-24 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404275

Christoph Feck  changed:

   What|Removed |Added

 CC||ra...@raghukamath.com

--- Comment #2 from Christoph Feck  ---
*** Bug 402958 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-22 Thread Seijiro Moriyama
https://bugs.kde.org/show_bug.cgi?id=404275

Seijiro Moriyama  changed:

   What|Removed |Added

 CC||seijiro.moriy...@anagix.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 404275] Crash on startup

2019-03-22 Thread Seijiro Moriyama
https://bugs.kde.org/show_bug.cgi?id=404275

--- Comment #1 from Seijiro Moriyama  ---
Created attachment 118969
  --> https://bugs.kde.org/attachment.cgi?id=118969=edit
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::load (__m=std::memory_order_relaxed, this=0x50) at
/usr/include/c++/7/bits/atomic_base.h:396
#7  QAtomicOps::load (_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#8  QBasicAtomicInteger::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

-- 
You are receiving this mail because:
You are the assignee for the bug.