Bug#335658: kdesktop: Crash on startup since upgrade from 3.4.2-3 to 3.4.2-4
On October 25, 2005 08:52, Josh Metzler wrote:
> On Tuesday 25 October 2005 08:02 am, Christopher Martin wrote:
> > On October 25, 2005 04:13, MrB wrote:
> > > Package: kdesktop
> > > Version: 4:3.4.2-4
> > > Severity: important
> >
> > Did you also upgrade to the latest arts (libarts1 in particular) from
> > unstable? That should solve this crash.
>
> Then shouldn't libkonq4 4:3.4.2-4 depend on libarts1c2 (>= 1.4.2-5)
> rather than (>= 1.4.2-1)?
In theory, there was no need to make kdebase depend on the latest arts.
There we no code changes in either of the arts and kdebase uploads. The new
kdebase was (when uploaded) not even built against the new arts, because
the new arts package didn't exist at the time.
It turns out, however, that between gcc-4.0 4.0.1-8 and -9, incompatible
changes were introduced which meant that a kdebase built with -9 or later
would crash, in certain circumstances relating to Sound Previews in Konq
and on the desktop, when used with an arts that was built with a gcc -8 or
earlier. Hence the need to rebuild arts. All we could have done at that
point would have been some sort of really ugly, really kludgy libarts1c2
Conflicts: libkonq4 (<< 4:3.4.2-5). Tightened depends are already in place
on the 3.4.3 packages in experimental, though we can't upload those to
unstable yet as it would likely delay the whole transition to Etch (as per
the instructions from the Release Team). So eventually the problem will be
dealt with properly.
There's not much point in filing a bug against gcc at this point; all we can
do is just rebuild if we encounter any more packages that mysteriously
crash. Yes, this sucks, and should never have had to happen. But since we
don't have to worry about mixing arts and kdebase from both Testing and
Unstable at the present time, in practice the problem isn't too severe. Sid
users will just need to make sure that they update both kdebase and arts to
the latest, or update neither, and they should have no issues. And perhaps
restart KDE, I should add (which may have been the problem here, now that I
think of it).
Cheers,
Christopher Martin
Reply to: