digikam 3.5.0 freezes at initialization on 14.04

Bug #1300255 reported by Michel Tissier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When I want to start digikam, it freezes on the first windows : "initialisation of the main wiew"
And then only a kill can make it to disapear.
Same thing if I start digikam from the terminal, but with these messages:

Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.

(digikam:16581): GLib-GObject-WARNING **: cannot register existing type 'GstObject'

(digikam:16581): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(digikam:16581): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(digikam:16581): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(digikam:16581): GStreamer-CRITICAL **: gst_plugin_feature_get_name: assertion 'GST_IS_PLUGIN_FEATURE (feature)' failed

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-20-generic 3.13.0-20.42
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michel 3920 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 31 10:06:53 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=1686c3e5-794f-4e2e-976a-b7c1ccbf18fb
InstallationDate: Installed on 2012-12-04 (481 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: LENOVO 2320CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=515d5296-7f6c-424d-bd52-4ec6a2bac9bd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-20-generic N/A
 linux-backports-modules-3.13.0-20-generic N/A
 linux-firmware 1.126
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-03-29 (1 days ago)
WifiSyslog:

dmi.bios.date: 09/11/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET82WW (2.02 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2320CTO
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2320CTO:pvrThinkPadX230:rvnLENOVO:rn2320CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2320CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

Revision history for this message
Michel Tissier (michel-tissier) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Michel Tissier (michel-tissier) wrote :

Same thing with Linux version 3.14.0-031400-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201403310035 SMP Mon Mar 31 04:36:23 UTC 2014

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
James Dupin (james.dupin) wrote :

I have the same problem on an i386 while the program runs correctly on a macbook.

I386 bitches about gstreamer while it passes on amd+mac

Revision history for this message
James Dupin (james.dupin) wrote :

the problem may be coming from phonon-backend-gstreamer:i386 and/or
phonon-backend-gstreamer-common:i386

Indeed I noticed that on amd+mac (digikam runs ok), the packages are phonon-backend-gstreamer1.0:amd64 and phonon-backend-gstreamer1.0-common:amd64

So, I installed phonon-backend-gstreamer1.0 and phonon-backend-gstreamer1.0-common and now digikam opens correctly on the i386

Revision history for this message
Michel Tissier (michel-tissier) wrote :

As James Dupin suggests, I installed phonon-backend-gstreamer1.0 (but no phonon-backend-gstreamer1.0-common which was not listed in my configuration) with synaptic.
It uninstalled automaticaly phonon-backend-gstreamer and phonon-backend-gstreamer-common.

And then digikam runs like a charm.

penalvch (penalvch)
affects: linux (Ubuntu) → digikam (Ubuntu)
Changed in digikam (Ubuntu):
importance: Medium → Undecided
status: Confirmed → New
Revision history for this message
Harald Sitter (apachelogger) wrote :

This was fixed a while ago.

Changed in digikam (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.