| Summary: | DigiKam crash on startup | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jim Thale <jsthale> |
| Component: | Preview-Image | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, gpsanino, jeff |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.7.0 | |
| Sentry Crash Report: | |||
|
Description
Jim Thale
2015-08-03 17:22:34 UTC
digiKam 4.6.0 is Qt4 version. the crash appears in Qt5 ! We don't use Qt5. It's a packaging problem... Gilles Caulier Hi Jim I am having exactly the same problem, despite I installed DK 4.13.0. In fact I got this qt5 issue despite if installing DK 4.10.0 / 4.11.0 or 4.13.0. My opensuse updated as usual some KDE packages and started my problems with Digikam. As Gilles states this looks like a package issue. However it is more a KDE issue than a Digikam, since I am experienced this segfault with other applications as well. Not sure what to do about it because I already did a fresh install of OpenSuSE 13.2 and with even default repos / updates + KDE:EXTRA, this qt5 issue shows up at some point. When the system is doing its default updates during the installation, there are steps with many packages being updated. No idea which is the one messing this up. Please share with us an update on this. Did you solved it somehow? Removing libvlccore is what did the trick. No trees were harmed in the creation of this email, however several billion electrons were seriously inconvenienced. On 09/10/2015 08:10 PM, GPSanino wrote: > https://bugs.kde.org/show_bug.cgi?id=350927 > > GPSanino <orcatech@vtr.net> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |orcatech@vtr.net > > --- Comment #2 from GPSanino <orcatech@vtr.net> --- > Hi Jim > I am having exactly the same problem, despite I installed DK 4.13.0. In fact I > got this qt5 issue despite if installing DK 4.10.0 / 4.11.0 or 4.13.0. My > opensuse updated as usual some KDE packages and started my problems with > Digikam. As Gilles states this looks like a package issue. However it is more a > KDE issue than a Digikam, since I am experienced this segfault with other > applications as well. > Not sure what to do about it because I already did a fresh install of OpenSuSE > 13.2 and with even default repos / updates + KDE:EXTRA, this qt5 issue shows up > at some point. When the system is doing its default updates during the > installation, there are steps with many packages being updated. No idea which > is the one messing this up. > > Please share with us an update on this. Did you solved it somehow? > Thanks so much Jim On 09/11/2015 11:58 AM, Jim Thale wrote: > https://bugs.kde.org/show_bug.cgi?id=350927 > > --- Comment #3 from Jim Thale <jsthale@comcast.net> --- > Removing libvlccore is what did the trick. > > No trees were harmed in the creation of this email, > however several billion electrons were seriously inconvenienced. > > On 09/10/2015 08:10 PM, GPSanino wrote: >> https://bugs.kde.org/show_bug.cgi?id=350927 >> >> GPSanino <orcatech@vtr.net> changed: >> >> What |Removed |Added >> ---------------------------------------------------------------------------- >> CC| |orcatech@vtr.net >> >> --- Comment #2 from GPSanino <orcatech@vtr.net> --- >> Hi Jim >> I am having exactly the same problem, despite I installed DK 4.13.0. In fact I >> got this qt5 issue despite if installing DK 4.10.0 / 4.11.0 or 4.13.0. My >> opensuse updated as usual some KDE packages and started my problems with >> Digikam. As Gilles states this looks like a package issue. However it is more a >> KDE issue than a Digikam, since I am experienced this segfault with other >> applications as well. >> Not sure what to do about it because I already did a fresh install of OpenSuSE >> 13.2 and with even default repos / updates + KDE:EXTRA, this qt5 issue shows up >> at some point. When the system is doing its default updates during the >> installation, there are steps with many packages being updated. No idea which >> is the one messing this up. >> >> Please share with us an update on this. Did you solved it somehow? >> Thanks so much Jim, I did removed libvlccore8 (despite it also removed vlc-codecs) and Digikam is not crashing again. I'd been getting this on ArchLinux. I'm using KDE 5 and have Qt 5 installed, but Qt 4 is also installed. This is *not* a packaging issue, it's a VLC issue. In my case, I had an outdated git build of VLC installed, and that made Phonon feel bad. I uninstalled vlc-git and replace with a fresh vlc from the repos (now newer than the git build I installed way back when) and everything is working fine. It crash in Phonon. This KDE component is used to render video. Since 5.2.0, we switch to QtAV/ffmpeg framework. So this problem will never appear again. |