Control: severity -1 important In data sabato 16 dicembre 2017 23:25:16 CET, Adrian Bunk ha scritto: > Control: severity -1 serious > > On Sat, Dec 16, 2017 at 09:19:18PM +0100, Michael Biebl wrote: > > Control: severity -1 important > > > > > Dec 10 13:17:40 lavaine kernel: [ 3324.799650] gnome-shell-cal[2352]: segfault at 100000812 ip 00007f2eeafd0324 sp 00007ffd0bc3d6d0 error 4 in libical.so.2.0.0[7f2eeaf8d000+5e000] > > To explain what's happening here: > > gnome-shell links directly against libical (here against v2) and also > > against libecal (from evolution-data-server). > > evolution-data-server was updated to link against libical v3. The result > > is, that gnome-shell was now loading libical2 (directly) and libical3 > > (indirectly via libecal) into its address space. This is not supported > > and leads to the crash. > > > > I decided to add a Conflicts: libical2 to libecal (see #884012) to avoid > > this situation. > > > > So from my POV, this bug can be closed. Other DDs mentioned on > > #debian-devel though, that this conflicts should be added directly to > > libical3. I'm thus leaving this bug report open for further discussion > > but downgrade the severity, as the immediate issue (the segfault in > > gnome-shell) is addressed by #884012. > > KDE has/had similar problems, setting back to RC to prevent testing > migration until this is sorted out. What are the "similar problems" of "KDE"? Neither the kdelibs 4.x nor the KF5 stacks support libical3, so everything uses libical2 for now. The only exception is digikam, for which I just requested a rebuild (since kcalcore was fixed to properly use libical2, see #883921). Since I don't see any other message in this bug regarding problems, nor I see any bug filed in any part of the KDE stack, then I'm lowering the severity of this bug, so this rushed doko-transition can be finally unblocked (unblocking the marble+libkipi transition too). -- Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.